The site visit report: what to include, and a template you can copy

By Adam Chandler, founder of Pangea · September 2, 2026

A site visit report is the dated, signed record of one visit to a project site: who was present, what stage the work had reached, what you observed, and what has to happen next. Whoever made the visit writes it — the architect, the engineer, the owner's representative — and issues it to the project team within a day or two, while everyone's memory can still check it. One visit, one report. That is the line between a site visit report and a daily log, which covers every calendar day whether anyone visited or not.

Below is what belongs in one, a template you can copy as-is, the wording that keeps your report from claiming something you did not do, and what happens to it after you hit send.

What is a site visit report?

It records what one person saw, at one place, at one time, written down before it turns into a memory. The report does not decide anything; it observes and it asks.

Three documents get confused with each other constantly, and the differences matter because they carry different weight:

Architecture has a standard form for this. AIA's G711–2018, Architect's Field Report exists so a project representative can "maintain a concise record of periodic site visits," capturing known deviations from the contract documents, deviations from the contractor's most recent schedule, and defects and deficiencies observed in the work. If you are an architect on an AIA job, that form is not a suggestion. It is the shape of what your agreement already obligates you to report.

What should a site visit report include?

Eleven sections cover almost any visit on any project type. The first four fix the visit in time and place, the middle four carry the substance, and the last three turn a note into something someone can act on:

1. Identification — project name and number, report number in sequence, date, arrival and departure times, and who prepared it.
2. Purpose of the visit — one line. "Monthly progress observation," "review of formwork at grid C prior to pour," "response to owner's question on lobby ceiling height." A report with no stated purpose reads as a wander.
3. Weather and site conditions — temperature, precipitation, ground conditions, access. Skip it on an interior fit-out; never skip it when the work is weather-sensitive.
4. Present at site — names, firms, and roles of everyone you spoke with, plus the trades working and rough headcounts.
5. Stage of the work — where the job actually is, by area or activity, and how that compares to the current schedule. "Slab on grade complete through grid 8; steel erection two weeks behind the June 3 schedule" beats a percentage.
6. Observations — numbered, one item per observation, each tied to a location. This is the body of the report and the part people read years later.
7. Deviations and deficiencies — anything you saw that does not match the contract documents, called out separately from general observations so nobody has to hunt for it.
8. Items to verify — what you could not confirm on this visit and intend to look at next time. Writing this down protects you, because it records that you knew the limit of what you saw.
9. Information or action required — the ask. Each item gets an owner by name and a date. Without this section the report is a diary entry.
10. Attachments — photo file names with location and subject, sketches, marked-up drawings. Label and date anything on a separate sheet.
11. Signature and distribution — the person who made the visit signs, and the report lists everyone it went to.

Site visit report template

Copy this into a document, save it as your firm's blank, and fill one per visit. It is written as a form rather than a spreadsheet row because most of these sections need more room than a cell.

Header: Project name / Project no. ____ / Report no. ____ / Date ____ / Time on site ____ to ____ / Weather ____ / Temp ____ / Prepared by ____ / Title ____ / Firm ____

Purpose of visit: ____________________

Present at site — one line each: Name | Firm | Role | Discussed

Trades working — one line each: Trade / company | Approx. workers | Work area

Stage of the work: Area / activity ____ / Status observed ____ / Compared to schedule dated ____: ahead / on / behind by ____

Observations — number them, one per line: No. | Location or grid | Observed | Photo ref.

Deviations & deficiencies observed — one line each: No. | Location | Observed condition | Contract document reference | Reported to ____ at __:__

Items to verify next visit — one line each: No. | What | Why it could not be confirmed today

Information or action required — one line each: No. | Item | Responsible party | Needed by | Related RFI / submittal / change no.

Attachments: Photo file names ____ / Location and subject of each ____ / Sketches ____ / Marked drawings ____

Prepared by: ____________________ Signature ____________________ Date ________

Distribution: ____________________ Date issued ________

Keep a one-row-per-visit index alongside the reports: Report no. | Date | Visited by | Purpose | Open action items | Closed?. It takes ten seconds a visit and answers the two questions that otherwise cost an afternoon — how often did we actually go out there, and what did we ask for that nobody ever answered.

Why does "observed" matter more than "inspected"?

Because on most design contracts you are paid to observe, and the word "inspect" describes a duty you did not take on. Writing it is an easy way to hand someone a claim against you, and it usually happens by accident, in a hurry, in the third line of a report.

The AIA B101–2017 owner-architect agreement is explicit about it. Under § 3.6.2.1 the architect visits "at intervals appropriate to the stage of construction" to become "generally familiar with the progress and quality of the portion of the Work completed," and to determine "in general" whether the work observed indicates the finished work will conform. Then comes the sentence worth memorizing: "However, the Architect shall not be required to make exhaustive or continuous on-site inspections to check the quality or quantity of the Work."

The agreement does use the word inspection, but it fences it into two places. Section 3.6.6.1 has the architect conduct inspections "to determine the date or dates of Substantial Completion and the date of final completion," and issue the final certificate for payment based on a final inspection. Everywhere else, the work is observed.

So the writing habit is simple. Use "observed," "noted," "appeared," and "was informed by." Avoid "inspected," "approved," "certified," "verified," "confirmed compliance," and "all work is satisfactory." Those words claim an exhaustive review, and if a defect turns up later ten feet from where you were standing, the report you wrote is the exhibit.

The same section says what you do owe. On the basis of the site visits, keep the owner reasonably informed, and promptly report known deviations from the contract documents, known deviations from the contractor's most recent schedule, and defects and deficiencies observed in the work. That is a reporting duty with a clock on it. A deviation you noticed on the 3rd and mentioned on the 24th is a problem no matter how carefully you worded it.

How do you write observations that hold up?

Same day or next morning, in specific language, with locations attached. Six habits do most of the work:

• Write it before you write anything else. The report gets harder and vaguer every hour you wait. If you cannot finish it in the truck, at least dump the numbered observations and photo references while they are still exact.
• Locate every observation. Grid line, column number, room number, station. "Water infiltration at the northeast corner, grid F/4, below the curtain wall sill" is findable in two years. "Some leaking on the east side" is not.
• Describe the condition, not the person. "Reinforcing at footing F-12 observed at 1½ in. clear cover; drawings call for 3 in." is a fact anyone can go check. "The concrete sub is careless again" is an opinion that gets read back to you out loud.
• Separate what you saw from what you were told. If the superintendent says the hoist arrives Thursday, write "superintendent reported the hoist is scheduled for Thursday." Attribute it rather than adopting it. Reports get into trouble when hearsay ends up in the observation column.
• Record what you could not see. Ceilings closed, area locked, work covered before you arrived. A report that quietly implies full coverage is worse than one that names its gaps.
• Never edit an issued report. If you got something wrong, correct it in the next report with a reference to the original item number. A silently revised report casts doubt on every report in the file.

Photographs get one rule of their own: caption them in the report with where they were taken and what they show, not just in a folder somewhere. An uncaptioned photo of a wall is evidence of nothing a year later.

Who gets the site visit report, and how quickly?

Issue it within one to two business days to the owner, the contractor, and any consultant whose scope you touched, and name that distribution list on the report itself. The speed is practical rather than polite: a deviation that sits unsent for a week is a week of work built on top of it, and the report exists to give someone the chance to act while acting is still cheap.

Number the reports sequentially per project and never reuse a number, so the series itself shows whether one is missing.

Then close the loop, which is where most firms lose the value. Every "information or action required" item is an open request with a name and a date on it. If those items only live inside issued PDFs, nobody is tracking them, and the third report in a row asking about the same missing louver schedule tells you it became someone's inbox problem instead of the project's. Roll open items into the next visit report, onto the OAC meeting agenda, or onto the RFI log when the answer needs a formal response. A report that raises a question and never routes it has done half a job.

Where Pangea fits

Pangea is an AI notetaker built for project-based firms — land developers, engineers, and architects — and what it does differently is file by project rather than by meeting. It records your meetings, including in-person ones with a phone on the table and no bot in the call, reads the project email and files you connect, and keeps a living record for every job: minutes, decisions, deadlines, and action items, each traceable back to the moment someone said it.

It does not write your site visit report, and it is not a field app. What it handles is the half of the loop that happens off the site. The debrief in the truck on the way back, the coordination call where the deficiency gets discussed, the owner's answer that arrives by email three days later: those get captured and filed to the project, so when you sit down to write report no. 14 you are not reconstructing who said the louver schedule was coming. Open action items stay attached to the job instead of to whoever remembers them, and approved updates can push into the PM software you already run.

If the person writing the reports is also the person chasing every answer they ask for, the AI project coordinator page is the closer read. Otherwise start at pangeanotes.com — the trial is 14 days, no credit card.