Site Visit Report Format

What is a Site Visit Report?

A site visit report records what was seen, who was there, what was agreed and what happens next. It converts a walk round into something the people who did not attend can act on. Without one, the visit survives only as two different memories: the contractor recalls agreeing an extension, the client recalls agreeing nothing, and the instruction supposedly given on site is unprovable when it matters.

Architects, project managers, quantity surveyors, engineers, field officers, auditors, sales engineers, franchise supervisors and school inspectors all write them. The visit might be a progress check on a construction phase, a supervision visit to a branch or clinic, a survey before quoting, a snag walk before handover, or a monitoring visit to a funded programme. The report is read by people who need to act: the head office deciding whether to release the next payment, or the donor confirming that money was spent on what was promised.

Where a visit is contractual or regulated, the format and the timing are usually set by something other than you. A construction contract may set out how instructions are issued and how quickly the record must be circulated, a funder's grant agreement may prescribe a monitoring template, and workplace safety law may require certain observations to be recorded and acted upon. Check the contract clause, the funding agreement or the sector regulator's guidance for your country before assuming a general-purpose report is enough.

A site visit report is a record, not an instruction. In most construction contracts, telling a contractor to change something on site does not become a valid variation just because you wrote it in your report — the contract has its own mechanism, and using the wrong one leaves the cost dispute open. The report also does not certify quality or safety: noting that scaffolding ‘looked secure’ from ground level is an observation, not an inspection, and should not be written as though it were one.

What to put in a Site Visit Report

These are the details this template asks for. Anything left blank is marked in red on the preview so you can see what is still missing.

How to write a Site Visit Report

1. Fix the visit in time and place

   Record the site name and address, the date, the arrival and departure times, and the weather if it affects the work — a rained-off day argued about six months later is settled by that line. List everyone present with their organisation and role, including people you met only briefly. Note anyone who was expected and did not attend.

2. Set out the purpose before the observations

   One or two lines saying why you went: fourth progress visit, snagging before handover, investigation of a reported leak, quarterly monitoring. Readers use this to judge what your silence means. In a progress visit, no mention of the roof means you did not look at it; in a snagging visit, no mention means it was fine.

3. Separate what you saw from what you heard

   Two different reliabilities belong in two different places. ‘Blockwork to first floor complete on the north elevation, observed’ and ‘site manager states steel is due Thursday, not verified’ are both useful, and confusing them is how reports become unreliable. Photograph anything contentious, number the photographs, and reference the number against the observation.

4. Record decisions with an owner and date

   Write every agreement as an action line: what was agreed, who owns it, by when. ‘Contractor to submit revised programme to the client by the 14th’ is actionable. ‘Programme discussed’ is not. Carry the open items forward from the previous visit at the top of the list so nothing quietly disappears between reports.

5. Circulate it fast and invite corrections

   Send the report to everyone named in it within a day or two, and say plainly that anyone who disagrees should respond by a stated date. An uncorrected report that everyone received becomes the agreed account of the visit. One written three weeks later, after positions have hardened, is just another opinion in the file.

Common mistakes

• Mixing what you observed with what someone told you leaves the whole report open to challenge, because one wrong hearsay line makes every other line look uncertain.
• Writing an instruction to change the works into a visit report, instead of using the contract's variation mechanism, usually leaves the resulting cost claim unsupported.
• Omitting the attendance list means that when an agreement is later denied, there is nothing to show who was standing there when it was made.
• Recording agreements without an owner and a date produces a report full of items that everyone assumes somebody else is doing.
• Sitting on the report for weeks lets memories diverge, and a late account carries far less weight than one circulated while everyone still agrees what happened.

Frequently asked questions

This page explains general practice and is not legal advice. Requirements differ between countries and, in some cases, between states — check what applies where the document will be used.

Related templates

All templates · Operations templates