Home / Blog / Berkhamsted

Berkhamsted · Leak detection guidance

Leak detection in Berkhamsted: how long should investigation evidence be kept?

Exact Source · 2 November 2026 · 2 min read

Keeping every duplicate forever creates privacy and security risk, while deleting the only technical record can obstruct a repair, claim or dispute. A retention policy should distinguish the authoritative evidence from convenience copies and tie each period to a practical or legal purpose.

Classify the records

List quotation, authority, technical report, raw readings, photographs, access variation, repair note, invoice, certificates and correspondence. Identify the master and owner. Separate transient duplicates, device copies and redacted extracts from original evidence.

Record personal data and security information contained in each class. ICO principles require data minimisation, accuracy and appropriate security. Remove unrelated material and restrict access rather than treating a technical purpose as permission to keep everything.

Set reasoned retention and holds

Define a period or review trigger for each class based on service needs, contractual records, active claims and professional advice. A dispute, complaint or legal hold may require preservation; obtain advice before deletion. Do not invent a universal statutory period for every leak file.

Record who approves extension or disposal. Ensure backups and shared links follow the same decision. A deleted local copy is not meaningful if unrestricted duplicates remain with many recipients.

Close and dispose safely

At project close, index the final master, verify readability and remove superseded working copies that lack continuing purpose. Keep the revision trail needed to understand decisions. Tell recipients how to request correction or the current version.

When a review date arrives, check open monitoring, warranties, claims and actions before secure disposal. Record what was destroyed, when and under whose authority without retaining the deleted content itself. This balances an accountable leak record with privacy and security. Build the policy into field practice: transfer originals from devices, verify the master, then clear temporary copies through an approved process. Sharing links need expiry and recipient review. If a customer requests a copy, provide the controlled version and record delivery. Any correction should propagate to active copies. The policy should name a responsible role rather than relying on an individual contractor’s memory. Review cloud backups, messaging attachments and exported claim packs, not only the main case folder. Document any copy that must remain with an external recipient.

Further reading

Prepared with AI assistance using the sources listed above. General information cannot diagnose an individual property. Contact us to discuss your circumstances.

Would you like to talk it through?

Tell us what you have noticed and request a callback for further information.

Speak to a specialist