How to Write a Site Inspection Report

A site inspection report turns a walk around site into a usable record. Whether it's read by a client, a project manager, a subcontractor, or a court years later, the report has to clearly say what was inspected, what was found, and what needs to happen. A report that's vague, unstructured, or undated isn't worth writing.

This guide explains how to write a clear, professional site inspection report.

Start with the essentials

Every report needs a header that establishes the basics at a glance:

• Project name and reference.
• Date and time of the inspection.
• Inspector's name and role.
• Type and scope of the inspection.
• Weather/conditions if relevant.
• Who was present.

These details matter more than they look — they're what make the report traceable and credible later.

Structure the findings logically

Don't write findings as a wall of text. Organise them so they're easy to act on, usually by location (area to area) or by element/trade. For each finding, give:

• A clear, factual description of what you observed.
• The exact location.
• The requirement or standard it relates to (where relevant).
• A photo showing the issue.
• A severity or priority.
• The action required and who's responsible.

Numbering each finding makes it easy to reference and track.

Write factually and objectively

The golden rule of inspection writing: record what you observed, not opinions or blame. "Fire door FD12 held open with a wedge, no self-closing function operating" is useful and defensible. "The site team are careless about fire doors" is neither. Stick to observable facts, measurements, and the standard the work is being judged against.

Use photos properly

Photographs are the most powerful part of an inspection report. Each should be clearly linked to its finding, show the issue and enough context to locate it, and ideally include something for scale where size matters. A report where photos float unlabelled at the end is far weaker than one where each image sits with its finding.

Summarise and prioritise

Busy readers want the headline first. A short summary at the top — overall status, number of findings by severity, and any critical items needing immediate attention — lets the reader grasp the situation before diving into detail. Lead with what matters.

Make actions unambiguous

The report's whole purpose is to drive fixes. Every finding that needs action should clearly state what must be done, by whom, and by when. A finding with no owner and no date is an observation, not an action — and it won't get resolved.

Carry forward open items

A good report references the status of items from previous inspections — what's been closed and what remains open. This running thread is what stops issues quietly dropping off the list.

From walk to report, instantly

The traditional report is written up in the office hours after the inspection, matching scribbled notes to camera photos. A site inspection app flips this: you record each finding with its photo, location, severity, and action during the walk, and the structured report — summary, numbered findings, embedded photos, assigned actions — generates itself the moment you finish. It's faster, more accurate, and consistent every time.

Key takeaways

A good site inspection report has clear header details, findings organised by location or element, factual descriptions tied to the standard, labelled photos, severities, and unambiguous assigned actions — with a summary up front and open items carried forward. Write what you observed, make every action ownable, and keep it consistent.