Home / Blog / Bagshot

Bagshot · Leak detection guidance

Leak detection in Bagshot: when does an equipment fault invalidate a test?

Exact Source · 9 November 2026 · 2 min read

A flat battery, damaged hose, drifting sensor or incomplete data file can affect a leak test without being obvious at first. During leak detection in Bagshot, the report should show which result remains usable, which is invalid and what was repeated. Removing a poor result from the narrative without an audit note weakens the whole record.

Recognise and isolate the anomaly

Record the symptom, time and stage: unstable zero, implausible jump, lost connection, visible damage or failed self-check. Stop using the equipment where the fault could affect safety or validity. Preserve the displayed error and relevant file rather than repeatedly restarting until a preferred number appears.

Check simple external causes such as connection state, test medium or environmental interference according to the equipment procedure. Do not perform unauthorised repair or calibration in the field. Label the instrument out of use when its condition remains uncertain.

Assess which evidence is affected

An equipment fault may invalidate only one interval, one channel or the entire run. State the boundary and reason. Independent observations—such as a visible escape or another correctly controlled test—do not become false automatically, but they must not be used to disguise the failed measurement.

UKAS guidance on metrological traceability highlights the need for measurement results to connect through appropriate references where traceability is claimed. Record equipment identity and status so a reviewer can understand whether the result was produced under the controls described.

Repeat without overwriting history

Use suitable equipment, restore the same starting conditions where possible and assign the repeat a new test identifier. Compare results only after documenting changes in temperature, pressure, isolation or method. Keep the invalid run clearly marked in the file rather than deleting it.

For leak detection in Bagshot, an honest fault record can increase confidence in the final conclusion. It shows why a result was rejected and how the replacement was obtained. If conditions cannot be recreated, report the limitation and choose the next decision from the remaining evidence instead of inventing a clean comparison.

Notify any recipient who received a provisional result from the failed run and identify the replacement test clearly. If equipment is sent for service, retain the fault reference and eventual outcome where it affects confidence. A later pass does not erase the need to explain why the first data was excluded.

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