Define the purpose of the review

An asset review should be framed around the client's intended decision. The information needed for an acquisition may differ from the information needed for a change of use or a system upgrade. Define the scope, access arrangements and limitations before the inspection or document review begins.

Understand the quality of the records

Available drawings and reports are a starting point, not automatic proof of the current condition. Establish what each document covers, when it was prepared and whether later changes are recorded. Gaps can then be considered in the assessment rather than hidden inside unspoken assumptions.

Distinguish observation from verification

A site observation can identify a condition that merits attention without establishing every aspect of system performance. The report should distinguish what was seen, what was supported by documentation and what requires testing, calculation or further specialist investigation. This helps the client understand the strength of the evidence.

Turn findings into useful next steps

A long list of observations is difficult to act on without context. Recommendations should explain what further information or engineering work is needed and how that supports the intended decision. The next appointment can then be defined around clear questions and proportionate deliverables.

For your next project discussion

  • Purpose and boundaries of the assessment
  • Available records and known changes
  • Access limitations and evidence gaps
  • Further investigation and engineering requirements

Planning a review with FESOL

For existing and occupied facilities, our fire risk assessments and compliance reviews help define the evidence and engineering work needed for the next decision.

These perspectives are general project-planning information. Project-specific engineering requirements are established within a defined professional appointment.

Discuss your project