Guide · How-to
A site inspection report is only as good as its observations. Vague language, missing photos and ownerless actions are the common failures, all rooted in writing from memory rather than on site.
Free forever: 20 reports a month. No card, no trial clock.
Structure
Site, client, date, inspector and reference. Then state plainly what the inspection covered and what it did not.
Each finding gives the location, what was found, compliant or not against the standard, and a photo where the finding is visual.
A numbered action list with priority, owner and target date for each item, then inspector signature and date.
Common mistakes
Vague observation language tells nobody anything useful. A written defect description is weaker evidence than a captioned photo. An action with no owner and no deadline is a wish list. Worst and most common: completing the report from memory at the van produces a reconstruction, not a record.
Voice notes
An inspector standing in front of a defect speaks what they see: immediate, detailed and honest. Engineers using Quickler speak observations into WhatsApp during the workflow. The system transcribes them automatically, so the report holds what the engineer actually said at the point of finding, not a sanitised write-up later.
Get started
Quickler transcribes voice notes automatically. PDF and CSV export, one-click email to client.
A site inspection report is only as good as the observations it carries. Vague language, missing photos and ownerless actions are the usual failures. All of them trace back to one habit: writing from memory at the van instead of capturing on site.
This is a practical guide on how to write site inspection report documents that hold up. What every report needs, where reports go wrong, and what sharp observation language actually looks like.
Structure
The structure of a site inspection report barely changes across job types. The content does. Every report carries the same six sections, and skipping any one of them weakens the whole document.
Header. Site or project name and address, client name, date and time of inspection, inspector name, role and contact details, a report reference number, and any relevant project or contract reference. This section makes the report findable and attributable. Retrieved in two years, it must say plainly who wrote it, when, and for which site.
Scope. What the inspection covered and what it did not. The most neglected section of all. An inspector who checks the accessible areas of a roof but cannot reach the flat section above the plant room must say so. A report with no declared scope implies that everything was inspected. That implication is wrong and potentially misleading.
Methodology. How the inspection was conducted. Visual only, or did it include testing? Were drawings or previous reports reviewed? Was access obtained to all areas? Was specialist equipment used? For complex inspections, this section tells the reader how much weight to place on the findings.
The core
Findings. What was observed. Each finding names the location, describes what was found, states whether it is compliant or non-compliant against the relevant standard, and includes photographic evidence where the finding is visual. This is the core of the report. Everything else exists to support it.
Actions required. What needs to be done, by whom, and by when. A numbered list, not embedded in the findings narrative. Priority, responsible person and target completion date for every item. Without those three elements, the action is advisory rather than managed.
Sign-off. Inspector signature or digital equivalent, and date. For formal inspection types the sign-off may also carry the inspector's qualification reference and the certification statement required by the relevant standard. Looking for a layout to start from? Our inspection report template shows each section in place.
Common mistakes
Vague observation language. The most common failure by far. Condition described without specifics tells nobody anything useful. Compare the two below.
Weak: "Brickwork to north elevation in deteriorating condition."
Strong: "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. Strong site inspection report examples always pin location, extent, evidence and a deadline.
No photo evidence. A written description of a defect is weaker evidence than a captioned photograph. An inspector who records cracked render but does not photograph it has given the client something open to interpretation. A photograph is not open to interpretation. It is what the wall looked like on the day.
Writing from memory. The most damaging practice, and the most common. Walk the site, take a few notes, write up at the van an hour later, and you produce a reconstruction, not a record. Memory fades. Ambiguous situations resolve in favour of whatever seems most likely.
Voice notes
An inspector standing in front of a defect speaks what they see. Immediate, detailed and honest, because they are describing exactly what is in front of them. The same inspector writing from memory an hour later describes what they remember, filtered through what they already concluded about it at the time.
Voice notes captured at the moment of observation preserve that immediacy. Engineers using Quickler speak their observations into WhatsApp as voice notes during the workflow. The system transcribes them automatically. The report holds what the engineer actually said at the point of finding, not a sanitised version typed up later. For more on the technique, see our guide to voice notes for site reports.
Actions
The findings section tells the client what was found. The actions section tells them what to do about it. This 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, 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 the judgements they hired the inspector to make. Priority ratings of urgent, required and monitor give the client a basis for allocating resources. For a fuller worked example, see our construction site inspection report guide.
Site and project identification, date and time of inspection, inspector name and role, scope (what was and was not covered), methodology, findings with photo evidence, any non-compliant or at-risk items, recommended actions with owner and target date, and inspector sign-off.
The terms are often used interchangeably. Strictly, an observation is a factual record of what was seen. A finding is an observation assessed against a standard and judged compliant or non-compliant. An observation is neutral. A finding carries a judgement, and good 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. The more specific the observation, the more useful the report.
Yes. Captured at the moment of observation they 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 without the inspector needing to type them.
Construction and site safety