How to Write a Construction Site Inspection Report

A site inspection report is the record of what an inspector saw on a given day, what it means, and what has to happen next. Owners, contractors, and consultants all act on it, and it may be read again years later in a dispute or a warranty claim. A good report is easy to act on today and easy to defend later.

What a site inspection report should include

Most firms have their own template, but nearly every good inspection report covers the same ground:

1. Project details. Project name and number, site address, client, and the contract or permit the inspection relates to.
2. Visit details. Date, arrival and departure time, weather, and who attended from each party.
3. Scope of the visit. What was reviewed (for example, "roof membrane installation, grid lines A–D") and what was not reviewed.
4. Observations. One numbered entry per finding, each with a location, a description, and supporting photos.
5. Deficiencies and required actions. What must be corrected, by whom, and by when.
6. Status of previous items. Whether findings from earlier visits are open, in progress, or closed.
7. References. The drawings, specifications, or code clauses each finding relies on.
8. Sign-off. The author, the reviewer, and the date the report was issued.

How to write each finding

The observations section is where reports succeed or fail. Each finding should answer four questions:

• Where? Use grid lines, levels, room numbers, or a marked-up plan. "North wall" is not enough on a large site.
• What? Describe what you observed, not what you assume. "Sealant joint open approximately 6 mm for 1.2 m" is better than "poor sealant work."
• Against what? Cite the drawing, specification section, or standard the condition is measured against.
• So what? State the required action and who owns it.

Attach the photo that proves the finding, and caption it with the finding number. A reader should be able to match every photo to a finding without guessing.

Keep an audit trail

Inspection reports are often reviewed long after the site has changed. Keep each finding traceable to its source: the original photo, the time it was taken, and who recorded it. Keep revision history on the report itself so you can show what changed between the draft and the issued version, and who approved it.

Common mistakes

• Writing the report days after the visit. Details fade quickly. Capture notes and voice memos on site and draft the same day.
• Mixing observations with opinions. Keep the factual description separate from the recommendation.
• Untraceable photos. Photos with no location or finding number are hard to use and easy to dispute.
• Inconsistent formatting between inspectors. Clients notice when two reports from the same firm look different. Use one template and stick to it.

Getting from field notes to a finished report faster

Most of the time spent on inspection reports goes into retyping field notes, sorting photos, and reformatting text to match the firm's template. That is the work Opusense is built to remove: inspectors capture photos and voice notes on site, and Opusense drafts the report in the firm's own template, with each finding linked back to its source photo and a built-in reviewer sign-off before anything is issued.

If your team writes inspection or field review reports every week, book a demo to see it with your own template.