Site-Meeting Record: Structure and Legal Weight

On Monday morning after the weekly site meeting, the architect who just jotted down progress, decisions, and sticking points in no particular order knows a clean document has to go out before the day ends, without always being sure what that document actually commits everyone to once it's sent. The site-meeting minutes occupy a particular place among a project architect's documents: they are not a simple meeting summary, but a document where a contractor's silence, past a certain deadline, counts as acceptance.

This article details the 8 sections a compliant site-meeting record must cover, what gives it near-contractual weight, and a method for producing it every week without starting from scratch.

Summary

1. A document with near-contractual weight
2. The 8 sections expected in a compliant record
3. Writing your record step by step
4. When a simple record isn't enough
5. What we see among architects who track a site
6. Training to make this administrative document reliable
7. Frequently asked questions

A document with near-contractual weight

A site-meeting record is not just a meeting aide-memoire. In private construction contracts, the NF P 03-001 standard, described in a construction-law brief from Le Moniteur, governs private construction contracts without listing site-meeting records among the contractual documents. Their binding force therefore comes from a clause inserted into the contract, along the lines of "after 8 days without written objection from the contractor, the record becomes contractual". Without that clause the record is not automatically deemed accepted, though courts do give it real evidential weight. In other words, your contract decides whether this document binds anyone, and checking that is better than assuming it, which makes its rigor far more than a matter of form.

What a contractor's silence changes

In practice, if no contractor contests a point in the record in writing within the deadline set by the contract, that point (a progress percentage, a decision, a reserve/defect) is deemed tacitly accepted by the parties present at the meeting. It's this mechanism that gives the document its near-contractual weight: it isn't an administrative formality, it's a record that, absent a written response, becomes the version of events that stands.

What's at stake in a dispute

In a dispute over a delay or a defect, the succession of weekly records becomes the site's reference timeline: who knew what, on what date, with which defect already flagged. A vague or incomplete record today weakens the project architect's position later, at precisely the moment they need it most. That's reason enough never to improvise its structure from one week to the next.

The 8 sections expected in a compliant record

A complete site-meeting record follows a fixed 8-block structure: identification, attendance, per-lot progress, decisions, reserves, forward planning, photo references, distribution. Each block corresponds to information that the contract or a potential dispute will make necessary sooner or later — not a free-form outline left to the drafter's discretion.

Identification, attendance, and per-lot progress

The header block sets the frame: project, site address, client, project architect, document reference, the day's weather, date of the next meeting. Then comes the attendance table, with present, absent, and excused marked distinctly: the last two statuses aren't interchangeable — an unexcused absence doesn't carry the same weight in a later dispute as a contractor who gave notice. Per-lot progress follows, with a subheading per lot (structural work, framing, finishing...), a recorded percentage, and an assessment of ahead, on track, or delayed against the initial schedule.

Decisions and reserves: the part that commits

Every decision made at the meeting is documented with the subject discussed, the decision reached, an action owner, and a deadline. Reserves follow the same logic but with a severity field: minor, major, or critical. This grading isn't cosmetic — it drives the urgency of the corrective action and, in a dispute, how a third party will read the file.

Photos, planning, and distribution: what closes the document

The photos themselves aren't embedded in the document: only a numbered reference (number, description, affected lot) appears, with the photo file kept archived separately. Forward planning lists the tasks expected before the next meeting, lot by lot. The document closes with the distribution list (client, present and absent contractors, inspection body, safety coordinator where applicable) followed by the legal mention of the contestation deadline.

Writing your record step by step

Step 1: gather the meeting notes, even rough ones. Minutes dictated right after the meeting, a list of points jotted down on the fly, or notes taken while contractors are still talking are a sufficient starting point: structure comes next, not first.

Step 2: fill in the identification block and the attendance table. This information changes little from one project to the next once the site is underway; gathering it once in a reusable template avoids re-entering it every week.

Step 3: detail per-lot progress and log the decisions. A subheading per lot with a percentage and an assessment, then each decision with its owner and deadline: this is the part that documents the site's actual progress, week after week.

Step 4: grade every reserve and set an owner and a deadline. Minor, major, or critical, with a precise corrective action: a reserve with no assigned severity or deadline commits no one to anything concrete.

Step 5: close with the planning, photo references, and distribution. The legal mention of the contestation deadline closes the document; without it, even the most complete record loses some of its weight.

When a simple record isn't enough

It has to be said plainly: the site-meeting record documents a planned, regular meeting — it doesn't cover every moment of site tracking, and confusing it with another document weakens both.

A one-off visit outside a planned meeting, a reserve that drags on for weeks with no tracker centralizing it, or the formal handover of the works: in these three cases, the site-meeting record isn't the right tool, even though it shares the same demand for rigor with each of them.

What we see among architects who track a site

In the conversations we have with architects and project leads about tracking a construction site, the bottleneck is almost never understanding what the document should contain: the 8-block structure is well known, often inherited from a template passed down from one firm to the next. What costs time is reformatting it every week — finding last week's file, checking that no open reserve fell through the cracks, rewording notes taken on the fly while contractors are still talking. It's repetitive, low-value work, not a skills gap — and it's exactly the kind of task a well-maintained template, or a tool that applies it automatically from raw notes, removes without taking anything away from the project lead's judgment on the substance of the decisions and reserves.

Training to make this administrative document reliable

Setting a record structure once and for all isn't enough if it still has to be rebuilt by hand every week from notes taken while contractors are still talking. It's a concrete use of AI applied to a site's administrative management, alongside fee proposals or invoices. For an architect practicing as a freelancer (a profession under NAF code 7111Z), FIFPL covers part of the cost of a Qualiopi-certified training course under 2026 criteria set at €300 per day and €900 per year, with e-learning capped at 50% of the daily rate. This funding needs to be applied for before training starts, not after.

Frequently asked questions

Does a site-meeting record need to be signed to have legal weight?

No, it's generally not a signature that gives it its weight, but the tacit-acceptance mechanism: a point not contested in writing within the deadline set by the contract is deemed accepted by the contractors present. What matters more than a signature is being able to prove the document was actually distributed to every relevant party, with an identifiable send date, since it's that distribution that starts the contestation clock. In practice, keeping a dated proof of sending (a read receipt or simply a grouped email send) for every record makes it easy to show, if needed, that the contestation deadline did run for every recipient.

What happens if a contractor contests a record after the deadline?

The very principle of tacit acceptance means a late contestation doesn't automatically invalidate what was recorded, but a real construction site is rarely as clear-cut as a principle. Keeping every successive record, along with proof it was distributed, remains the best protection: it's that complete timeline, more than the single contested record, that shows the point in question was flagged when it should have been. In that situation, it's better to reply to the contractor in writing, restating the distribution date and the applicable contractual deadline, rather than leaving the objection without a formal response.

Do you need a record for a site visit outside a planned meeting?

No, that's not the role of the site-meeting record in the strict sense. A one-off visit, an interim check, or a single client visit outside the rhythm of planned meetings falls under a site-visit report instead — a lighter document, without the same distribution formalism or the same near-contractual weight. Using the record template for this kind of visit anyway would wrongly give it the same near-contractual weight as a planned meeting, which can create confusion if a disagreement comes up later.

How do you know whether a reserve should be classed minor, major, or critical?

The core criterion is impact, not visibility: a minor reserve covers a cosmetic or finishing deviation with no consequence for the structure's soundness or use, a major reserve affects the use or performance of a secondary structure, and a critical reserve puts people's safety or the structure's own soundness at stake. A minor or major reserve carried across several successive records with no corrective action deserves to be upgraded, precisely because the lack of follow-through becomes a risk factor in itself. In practice, it's worth documenting that upgrade in the next record, noting the date the reserve first appeared, so the history stays traceable if a disagreement arises.

Who should receive the site-meeting record?

The typical distribution list includes the client, the contractors present at the meeting, those who were absent or excused, the inspection body when one is involved in the project, and the safety coordinator when the site has one. Distributing to an incomplete list directly weakens the tacit-acceptance mechanism described above: a contractor who never received the document obviously can't be deemed to have accepted its content through silence. Any change to that list during the project, such as an inspection body brought on after the start of works, needs to be reflected in the following records so that new party is actually covered by the tacit-acceptance mechanism that concerns them.

Going further

A compliant site-meeting record rests on three requirements that don't change from one week to the next: the full 8 sections, an honest grading of reserves, and proven distribution to every party. Once this structure is set in a reusable template, the only real variable from one meeting to the next is the site's own content — which is precisely what the site-meeting-record generator applies automatically from raw notes, including the reminder of the objection period set by the contract, while leaving the project lead the decision on the substance of every reserve and every decision.

To go further on AI uses specific to architecture, our complete guide to AI for architects covers other uses, from visual rendering to site administrative management.

Training 100% fundable through OPCO/FIFPL. Qualiopi-certified programme. To structure your site administrative documents (records, reserves, handover) with AI as part of our AI-driven practice management training, contact Educasium and specify your status (employee, freelancer, director) and your goal.