Home / Blog / Cobham

Cobham · Leak detection guidance

Leak detection in Cobham: how should conflicting occupant accounts be reported?

Exact Source · 5 November 2026 · 2 min read

Two occupants may remember a leak event differently, especially when it was intermittent or discovered after travel. Leak detection in Cobham should preserve each account, identify where they agree and design safe tests around the uncertainty rather than treating one person’s certainty as a measured fact.

Record accounts separately

Name the source by role only as needed and capture their words in neutral summary: approximate time, location, appearance, activity and action taken. Mark estimates. Do not merge accounts into an artificial exact timeline.

Avoid including unrelated disputes or personal information. ICO data minimisation applies even when a report may be shared with managers or insurers. The technical purpose is to understand the event, not assess credibility generally.

Map agreements and differences

Create a comparison of points agreed, contradicted and unknown. One person may have seen active dripping while another saw only a later stain. Those observations can both be true at different times.

Check photographs, messages, logger data, appliance records or weather information where they genuinely help. Preserve missing data and clock differences. Do not search for evidence outside the authorised purpose.

Design tests that discriminate

Use the differences to define safe observations: a particular appliance cycle, heating state or rainfall period. Set boundaries and stopping points. Do not ask occupants to recreate flooding or operate controls outside normal safe use.

If the event cannot be reproduced, state which accounts remain possible and what future evidence to capture. An inconclusive technical result does not mean one occupant was wrong.

Write a balanced conclusion

Separate account, observation, test result and interpretation. Explain which evidence carried weight and why. Keep liability, tenancy or interpersonal judgements outside the leak report.

If later access confirms a source, add the new fact without rewriting earlier accounts. This creates an honest chronology and prevents uncertain recollections from becoming unsupported certainty in a repair or insurance decision. Give each account a reference and allow factual corrections without deleting the first version. A correction should identify who supplied it and when. The final conclusion should cite technical evidence separately, making it clear that agreement between witnesses is useful context but is not itself a diagnostic test.

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