Site visit reports with Claude: connect observations, photos and actions
Method and example: Site visit reports with Claude: connect observations, photos and actions. Sources, assumptions and checks before sharing.
By Educasium
Write a site visit report with Claude →
An architect carries out a one-off visit alone: no contractor representative is present, but marks are visible around a hall door. The report, sent that same evening, describes the observation and proposes a joint check. Two weeks later, the contractor replies that it has "nothing to add" and considers the report accepted "under building-industry rules," citing an eight-day window to dispute it. Does this eight-day rule actually exist, and where would one need to find it in writing to rely on it?
A site visit report records what a person personally observed at a specific date and time, without turning that observation into an agreement between the parties. It is an exercise in constant delimitation: between what was seen, what a third party reported, and what remains to be checked. Blurring these three categories, or misunderstanding a silence rule, can give a document more weight than it actually carries.
This article details what a site visit report can establish and what it cannot, the reality behind the "silence equals acceptance" rule often wrongly attributed to a building-industry standard, the method for connecting each finding to a checkable action, and the situations where the report alone is not enough.
Summary
- What a site visit report can establish, and what it cannot
- Silence is not acceptance: what the NF P 03-001 standard actually says
- Connect each finding to a checkable action
- Building the report step by step
- When a site visit report is not enough
- What we observe among architects and construction firms
- Training to make site visit reports more reliable
- Frequently asked questions
What a site visit report can establish, and what it cannot
A site visit report establishes what its author personally observed, at a given date and time, in the areas they had access to. On its own, it cannot establish a technical cause, contractor agreement, or that an unverified repair actually took place.
Three categories that must never be blended
A direct observation ("marks are visible around the hall door frame") is distinct from a statement reported by a third party ("the contractor states it worked on this the previous week") and from a point still to be checked ("the cause of the marks is not determined at this stage"). A report that presents a contractor's statement as an established fact, or a hypothesis as a settled conclusion, loses much of its value the day its content is challenged.
The absence of a representative does not block the report, but limits its scope
A visit conducted without a contractor representative remains useful for documenting a dated finding, but the report cannot then report any reaction from the contractor to that finding, nor conclude tacit agreement on the existence or cause of the observed defect.
Silence is not acceptance: what the NF P 03-001 standard actually says
The NF P 03-001 standard, the general administrative conditions for French private building contracts, is a voluntary standard: it only produces contractual effect if the parties expressly reference it among the contract documents. Nothing in its usual application turns a one-off site visit report into a document automatically accepted after eight days of silence.
What is true, what is a frequent distortion
| Claim | Status | What is actually true |
|---|---|---|
| "NF P 03-001 applies automatically to every private building contract" | False | It only applies if the contract expressly cites it among its contractual documents |
| "A site visit report not disputed within 8 days becomes accepted" | False absent a clause | The general principle is that silence does not equal acceptance, unless the law, usage, business relations or a contract clause provide otherwise |
| "A contract clause can set a dispute window" | True | If the contract expressly stipulates a deadline and its effects, that clause applies — but it comes from the contract, not automatically from the standard itself |
| "Site minutes carry the same weight as a one-off visit report" | Needs case-by-case checking | The two documents follow different logics; the regime of one does not mechanically transfer to the other |
Why the confusion is so frequent, and so costly
The principle that silence does not equal acceptance, except in circumstances set out by law, usage or a contract clause, is set out in Article 1120 of the French Civil Code. A contractor invoking a dispute window must therefore be able to point to the contract clause that expressly provides for it, never settle for a general reference to "building-industry rules." Writing a report that implies such a window applies as a matter of course exposes its author to having to justify, later, a claim no written clause supports.
Connect each finding to a checkable action
A report is only useful for the rest of the site if every finding leads to an identifiable action, with a precise purpose and a known owner — or, failing that, a field explicitly marked "to confirm."
An action without an agreed deadline remains a proposal
Fictional example: the visit finds marks around the hall door; reference photo P01 will be supplied later and no contractor representative is present. The report can propose a joint check on a date to be agreed; it cannot unilaterally fix that date as a contractor commitment. A date suggested in a draft remains a proposal until both parties explicitly confirm it.
Photo references do not guarantee their insertion
A report that mentions a photo reference in its text does not prove that the corresponding image is actually embedded in the final document. This purely mechanical check must be made when the file is opened before circulation, never assumed simply because the reference appears in a list.
Building the report step by step
Step 1: Set the visit's precise purpose before starting. A visit focused on checking paint does not support conclusions about the general state of the site; the report must stay within its announced scope.
Step 2: Systematically record the date, times, accessible areas and people present. This factual base determines the value of everything that follows in the document.
Step 3: Separate direct observation, reported statement and point to check for every finding. Making this distinction while taking notes prevents any confusion later when drafting.
Step 4: Attach each finding to an action with a purpose, a known owner and a deadline to confirm. An action missing any of these three elements should remain explicitly marked incomplete, never filled in with an assumption.
Step 5: Open the final document and check tables, images and recipients before circulation. A photo reference in the text does not replace a visual check that the image is actually present in the file.
When a site visit report is not enough
A properly built report does not cover every situation that can arise after a visit.
If the contractor formally disputes the report's content, the appropriate response is not a unilateral rewrite of the document but a documented exchange, possibly followed by a joint visit organized with both parties present. If an observed defect requires technical expertise to determine its cause, the report should limit itself to describing what was seen and recommending that expertise, without asserting a cause that has not been established. Finally, if a contract clause does provide for a dispute window applicable to site visit reports, that clause must be checked in the contract itself before drawing any consequence from it for the document — never assumed from a general reference to a standard.
What we observe among architects and construction firms
In our exchanges about writing site visit reports, the difficulty is almost never the writing itself: a building professional knows how to describe what they saw. What costs time is reformatting the document after a sometimes long visit — retrieving a template consistent with earlier reports for the same site, cleanly separating observation from reported statement in notes taken quickly, or checking that every mentioned photo is actually embedded. That is formatting work, not a lack of rigor — and it is exactly the kind of task a well-structured template removes, without ever turning an observation into an agreement between the parties on its author's behalf.
Training to make site visit reports more reliable
Setting up a report template once and for all is not enough: it also needs adapting to every visit without losing time or letting an unestablished conclusion slip in. For an architect practising as a self-employed professional (NAF code 7111Z in France), the FIFPL fund covers part of the cost of Qualiopi-certified training under 2026 criteria set at €300 per day and €900 per year, with e-learning capped at 50% of the daily rate. This funding must be arranged before training starts, not after.
Frequently asked questions
Does a site visit report not disputed within eight days become automatically accepted?
No, unless a contract clause expressly provides for it. The general principle set out by Article 1120 of the Civil Code is that silence does not equal acceptance, outside cases set out by law, usage, business relations or an express contract clause; a general reference to "building-industry rules" is never enough on its own to establish such a window. A contractor invoking this window must therefore be able to point to the specific contract clause that provides for it, rather than relying on a verbal reference to a supposed industry custom.
Does the NF P 03-001 standard automatically apply to every private site?
No: it is a voluntary standard that only produces contractual effect if the contract expressly cites it among its contractual documents. Without such a reference in the contract, it binds neither party. It is therefore worth checking the list of contractual documents for the project before invoking this standard, rather than assuming it applies out of industry habit.
What should be done if no contractor representative is present during the visit?
The report remains useful for documenting a dated finding, but it cannot then report any contractor reaction to that finding. Propose a later joint check rather than concluding, from that visit alone, the contractor's agreement or disagreement. The report should then explicitly note the representative's absence, so a later reader does not mistake that silence for the contractor's tacit agreement with the finding.
Does the site visit report replace site meeting minutes?
No, the two documents serve different needs: a site visit report records a one-off finding at a given moment, while meeting minutes trace decisions taken collectively during a site meeting. Using one in place of the other deprives the file of one of the two kinds of traceability. The two documents are best kept together in the site-tracking file, since a later disagreement may require cross-checking a one-off observation against a decision made at a meeting.
Should a finding not resolved during the visit be transferred elsewhere?
Yes, if the finding needs tracking across several visits, it is best transferred with a stable ID to the defect register, which tracks its status over time, rather than left isolated in a one-off report that will not be systematically re-read. A one-off site visit report is only reread occasionally, whereas a structured register is designed to be updated at every new visit. Keeping the same ID across both documents makes it easy to trace the original observation if its status is ever disputed later.
A reliable site visit report rests on three elements that do not change from one visit to the next: a strict separation between observation, reported statement and point to check, no assumed silence rule without a written clause providing for it, and actions always tied to a known owner or explicitly marked "to confirm." Once that foundation is in place, it is exactly what the visit-report generator applies automatically, while leaving its author the decision on what was actually observed.
To track a finding across several visits through to resolution, our defect-tracking register guide details the method, and for the final handover decision, our handover-record preparation method revisits the document that formalizes it.
Training 100% fundable via OPCO/FIFPL. Qualiopi-certified programme. To structure your site visit reports and site documents with AI as part of our AI for architectural management training, contact Educasium and specify your status (employee, self-employed, business owner) and your goal.