An architect site visit report works when every observation carries a photo, a place on the plan, an owner and a date. The visit takes an hour. Writing it up, placing the photos and laying out the pages can take the rest of the afternoon, and the client waits for it.
TL;DR: Build every architect site visit report from five parts: a header (date, weather, who attended), observations, actions with an owner and a date, photos beside the points they support, and a signature from the person who made the visit. Use the form your appointment names, such as AIA G711 or RIBA 5/F4. Write the findings yourself, let a general AI assistant tidy the wording, then give the finished DOCX to DocsAura, an AI document design tool, and send a designed page the same day.
What an Architect Site Visit Report Contains
Two professional bodies publish a standard form, and the two forms agree on the bones.
The AIA's G711-2018 Architect's Field Report supports the architect's duty under the B101-2017 owner-architect agreement to become generally familiar with the progress and quality of the work and to determine, in general, whether it will conform to the contract documents when complete. It records the project and parties, who is present at the site, observations (deviations from the documents or the schedule, defects, deliveries), the action required, and attachments such as photographs. The person who made the visit signs it, and the Architect of Record does not need to unless the agreement says so.[^1]
RIBA's Job Book form 5/F4, "Report form for predictive site visits," has a visit number, a purpose, the observations, a record of what was checked (samples, test verification, vouchers, records) and recorded (photos, video), and a four-line summary: work properly executed, materials properly stored and protected, proceeding in a workmanlike manner, progress to programme. The Stage 5 checklist asks the architect to keep methodical records of all site visits and of the results of tests witnessed or reported.[^2]
Read side by side, the report needs these parts:
- Header. Project, date, weather, who attended, who was absent.
- Purpose. Periodic check, predictive check, follow-up on earlier points.
- Observations. What you saw, where, against which drawing or specification line.
- Actions. Each point with a named owner and a date.
- Attachments. Photos and sketches, labelled and dated.
- Signature. The person who made the visit.
Who Reads It, and What the Wording Has to Do
An architect site visit report has two readers with different needs. The contractor needs a list of what to fix. The client needs to know whether the building is going the way they paid for.
The wording has a legal side as well. The Royal Architectural Institute of Canada's practice handbook defines general review as visits at intervals appropriate to the stage of construction, to become familiar with progress and quality and to determine whether the work is in general conformity with the construction documents, with a written report to the client, the constructor and the authorities. It adds that "supervision" and "inspection" describe levels of service an architect does not normally provide, and that the architect is not responsible for construction means and methods or for site safety. The handbook also says the architect must report an unsafe condition to the contractor and owner at once.[^3] So write "observed" and "reviewed" in the report, describe what you saw, and leave the repair method to the contractor.
Contract wording varies by country and appointment. Check your own agreement for the frequency and format of visit reports before you change a template.
Put the Photos Beside the Point They Support
The AIA's risk-management guidance sorts site photos into three groups: deviations from the contract documents, areas where significant progress has been made since the previous visit, and overall progress. For deviations, it suggests shooting from as many angles as needed and including a scale or an object of known size, such as a pen. It warns that photographing a defect and leaving it out of the report can invite a negligence claim, because the defect was plainly visible. Each photo should support a specific point in the narrative.[^4]
That guidance points to a layout rule. Place the photo in the same row or block as the observation it proves, with a caption that gives the zone and the date. A reader who has to flip from page 3 to page 11 will skim, and a skimmed report is a weak record.
What we found reading four top-ranking site visit report guides
On 21 October 2026 we read four of the guides that rank for site visit report templates for architects and construction teams, each published by a field-reporting software vendor. All four list a header with date, weather and attendees, and all four tell the writer to give each action an owner and a deadline. One of the four says photos belong beside the observation; the other three leave placement open. One gives advice on writing so a client without technical background can follow. None mentions AI, and all four end by pointing the reader to the vendor's own field-capture app. None describes the step after capture: turning the written report into a clean page for the client.
Open With a Summary the Client Can Read in Thirty Seconds
The contractor reads the whole table. The client reads the top. Give the client a three-line summary above the observations:
- Overall: one sentence on whether the work is in general conformity with the documents and on programme.
- Needs your attention: the one or two points that involve cost, programme or a decision from the client, with the date you need an answer.
- Everything else: "Eleven further points are listed with the contractor, none affecting cost or programme."
This mirrors the lesson of the stage report: the client acts on the page that opens with what they have to do. The rest of the report remains the formal record, and the summary only points to it. Keep the summary factual and leave out reassurance you cannot support, because a report read in a dispute is read for what it recorded on the day.
What one observation row looks like
| # | Zone | Observation | Reference | Photo | Owner | Date |
|---|---|---|---|---|---|---|
| 4 | Roof terrace | Membrane lap at parapet measured at 100 mm against 150 mm specified | Spec. section on waterproofing, detail 7 | P-05 | Contractor | 3 Nov |
This row is an illustration of the level of detail to aim for. One line locates the point, names the reference, points to the photo and assigns the owner and the date.
A Seven-Step Routine That Keeps Your Judgement in the Report
This routine uses AI for the writing-up and layout, and leaves the observations to the person who stood on the site.
- Prepare. Open last visit's report and list the open points to check first.
- Capture on site. Photograph as you walk and say each observation aloud into a voice note: location, what you see, which drawing it relates to. How to Turn a Voice Note Into a Professional Document covers that step.
- Draft the text. Paste your notes into a general AI assistant and ask it to arrange them under the six headings above, keeping your wording and your numbers.
- Read every line. Check each observation against what you saw. The assistant tidies; the observations come from your visit.
- Add photos and actions. Place each photo next to its point and finish the action table with owners and dates.
- Save the file as DOCX or PDF. It stays your document, in your words.
- Lay it out with DocsAura. Upload the file, pick A4 for a report that is emailed or printed, and let the AI document design tool return a designed HTML page in about two minutes. Open the editor, click any text to change it, then export a PDF or share a link.
DocsAura takes a DOCX or PDF the studio already wrote and returns a designed page. It does not draw, model or generate plans, and it does not connect to Revit, ArchiCAD or AutoCAD. It changes how the finished report looks on the client's screen. Site reports contain addresses, photos and sometimes tenant details, so run the first trial on a visit report that holds no client data, as described in How to Test a New AI Tool Safely.
Check Before You Send
- Every observation has a place and a date. "Check the roof" gives the contractor nothing to act on. "Roof terrace, membrane lap at parapet below the specified 150 mm, photo 05" does.
- Every action has one owner and one date.
- The wording says "observed" and describes the condition. It leaves the repair method to the contractor.
- Photos sit beside their points and carry captions.
- The signature belongs to the person who made the visit.
- It goes out the day of the visit. A report that arrives after the wall is closed and painted has lost most of its value.
Time Is the Pitch, and Judgement Stays With You
The decisions in a site visit report are yours: what is acceptable, what must be reopened, what the client should hear first. The same applies to the stage report your client signs off, covered in How to Make an Architecture Stage Report Clients Actually Read, and to the concept pages before it, covered in Can AI Make an Architecture Concept Presentation Look Professional? What AI can take off your desk is the formatting that follows each visit, and an AI document design tool is built for that layer.
Try It on One Report You Already Wrote
Pick your most recent site visit report. Drop it into DocsAura, the AI document design tool, and see what comes back in about two minutes. There is nothing to install, no template to build and no new system to keep next to your drawing software. If the page suits the studio, send it. If a section needs a change, edit it in the editor and export.
[^1]: AIA Contract Documents, "Instructions: G711-2018, Architect's Field Report," help.aiacontracts.com, and "FAQs: G711-2018, Architect's Field Report." [^2]: Royal Institute of British Architects, RIBA Job Book (10th edition) checklists and forms, form 5/F4 "Report form for predictive site visits" and the Stage 5 construction checklist, item 5.3.9, riba.org. [^3]: Royal Architectural Institute of Canada, Canadian Handbook of Practice for Architects, Chapter 6.6 "Construction Contract Administration and Field Review," chop.raic.ca. [^4]: American Institute of Architects, "Using photography to evaluate on-site work," Best Practices, aia.org, 21 May 2024.
Turn voice notes and screenshots into beautiful documents.
Status updates, proposals, case studies, SOPs — generated in minutes, not hours.
Try DocsAura Free