M&E fault finding before handover: what to gather first

Describe the behaviour, not a presumed cause

“The system does not work” is a starting point, but it is difficult to investigate. Describe what happens, where it happens and under which operating conditions. Record what the team expected to see and which information establishes that expectation.

Note whether the issue is continuous, intermittent or linked to a particular mode or time. Keep observations separate from explanations that have not yet been tested.

Bring the design and site records together

Gather the latest relevant information and identify gaps. An investigation is easier to scope when the reviewer can see which records relate to the current installation.

• Design drawings, schematics and relevant schedules.
• Control descriptions and available operating records.
• Commissioning results and the conditions under which they were recorded.
• Relevant equipment information and changes from the intended selection.
• Site observations, photographs and previous technical queries.

Record what has already changed

Describe previous adjustments, the reason for making them and the observed response. If settings or components have changed repeatedly without a record, say so. Avoid presenting the current arrangement as the original condition.

Do not alter safety controls or undertake intrusive checks to prepare an enquiry. Access, testing, isolation and specialist attendance need to be agreed by the responsible project team.

Define the decision the investigation must support

Explain whether the team needs to establish a cause, assess a proposed remedial option or understand what further information is required. Include the handover programme and access constraints.

Engin’s Forensic Validations service reviews the evidence and scopes the necessary observations or checks. The useful output is a recorded finding and practical next step, with any limits and remaining questions made clear.