A site inspection report is only as good as the observations it contains. Vague language, missing photos, and actions with no owner or deadline are the most common failures. and all of them stem from the same root cause: completing the report from memory rather than on site. This guide covers what every report needs, what goes wrong, and what good observation language looks like.
The structure of a site inspection report does not vary much across inspection types. The content does. Every report should have the following sections.
Site or project name and address. Client name. Date and time of inspection. Inspector name, role, and contact details. Report reference number. Any relevant project or contract reference. This section exists to make the report findable and attributable: if it is retrieved in two years, it must be clear who wrote it, when, and for which site.
What the inspection covered and what it did not. This is one of the most neglected sections. An inspector who checks the accessible areas of a roof but cannot access the flat section above the plant room must say so. A report that does not declare its scope implies that everything was inspected. That implication is wrong and potentially misleading.
How the inspection was conducted. Visual inspection only, or did it include testing? Were drawings or previous reports reviewed? Was access obtained to all areas? Was any specialist equipment used? For complex inspections, the methodology section tells the reader how much weight to place on the findings.
What was observed. Each finding should identify the location, describe what was found, state whether it is compliant or non-compliant against the relevant standard, and include photographic evidence where the finding is visual. The findings section is the core of the report. Everything else supports it.
What needs to be done, by whom, and by when. This section should be a numbered list, not embedded in the findings narrative. Priority, responsible person, and target completion date for each item. Without these three elements, the action is advisory rather than managed.
Inspector signature (or digital equivalent) and date. For formal inspection types, the sign-off section may also include the inspector's qualification reference and the certification statement required by the relevant standard.
The most common failure. Observations that describe condition without specificity tell nobody anything useful. Compare the following.
"Brickwork to north elevation in deteriorating condition."
"Spalling brickwork to north elevation at first-floor level. approximately 3m run with visible mortar loss, two areas of exposed brick face and one area where the face of the brick has detached. Water ingress likely at this location. Photo 7. Recommend specialist repair within 30 days before further deterioration over winter."
The second observation is actionable. The first is not.
A written description of a defect is weaker evidence than a photograph with a caption. An inspector who identifies cracked render, records it in the report, but does not photograph it has given the client a description that is open to interpretation. A photograph is not open to interpretation. It is what the wall looked like on the day the inspector visited.
An action list with no owner and no deadline is a wish list. "Monitor for further deterioration" assigned to nobody, with no next inspection date, achieves nothing. "Review at next quarterly inspection. site manager responsible" is a managed action.
The most damaging practice, and the most common. An inspector who walks the site, takes a few notes, and writes the report at the van an hour later produces a weaker document than one who captures observations at the point of finding. Memory fades. Ambiguous situations get resolved in favour of what seems most likely. The report that gets written at the van is a reconstruction, not a record.
An inspector standing in front of a defect speaks what they see. The description is immediate, detailed, and honest. they are describing exactly what is in front of them. The same inspector, writing the report from memory an hour later, describes what they remember, filtered through what they concluded about it at the time.
Voice notes captured at the moment of observation preserve the immediacy of the inspection. Engineers using Quickler speak their observations into WhatsApp as voice notes during the workflow. The system transcribes them automatically. The report contains what the engineer actually said at the point of finding, not a sanitised version written up later.
The findings section tells the client what was found. The actions section tells them what to do about it. The actions section is where most reports fall short.
Every action needs three things: what needs to be done, who is responsible, and when it must be done by. A report that identifies twenty defects but provides no actions is a record of problems, not a management tool. The client reads it, feels alarmed, and then has no structured way to respond.
The priority column matters too. Not every defect is equally urgent. An action list that presents everything as equally important forces the client to make judgements they hired the inspector to make. Priority ratings, urgent, required, monitor, give the client a basis for allocating resources.
A site inspection report must include: site and project identification, date and time of inspection, name and role of the inspector, scope of the inspection (what was and was not covered), methodology, findings with supporting evidence (photos), any items that are non-compliant or at risk, recommended actions with owner and target date, and sign-off by the inspector.
In practice the terms are often used interchangeably. Some frameworks distinguish between an observation (a factual record of what was seen) and a finding (an observation that has been assessed against a standard and found to be compliant or non-compliant). An observation is neutral; a finding carries a judgement. Good inspection reports make the distinction clear.
Specific enough that someone who was not on site can understand exactly what was found and where. "Deteriorating condition" is not specific. "Approximately 3m of spalling brickwork to the north elevation at first floor level, with visible mortar loss and two areas of exposed brick face. photo attached" is specific. The more specific the observation, the more useful the report.
Yes. Voice notes captured at the moment of observation are typically more detailed and accurate than notes written later from memory. The inspector speaks what they see as they stand in front of it. Quickler transcribes voice notes automatically during the WhatsApp workflow, so observations appear in the report without the inspector needing to type them.
Paste this as your first workflow description when you sign up:
Site inspection report — inspector answers each section on WhatsApp during the visit, PDF ready for the client the same day.
Quickler builds the WhatsApp flow from your description. Engineers go live within a week.
Set up inspection reports →Quickler transcribes voice notes automatically. PDF and CSV export. One-click email to client.