The essentials in 30 seconds
- The minutes are the written memory of the site: what was observed, decided and requested, by whom, and by when.
- Useful minutes follow the same structure every time: attendees, progress per trade package, decisions, additional works awaiting approval, blocking points, next deadline.
- They are written the same day, in 20 minutes, from notes structured by trade package, never "when I find the time".
- They go out to all parties, with an objection period: without observations within 8 days, deemed approved.
- A decision with a financial impact recorded in the minutes is backed by a written client approval. The minutes record, the agreement commits.
What are site meeting minutes actually for?
Three things, in increasing order of importance. First, steering: the site meeting produces decisions (a material approved, a deadline reset, a rework requested), and the minutes turn those words into dated, assigned actions that can be checked at the next meeting. Second, informing: the client, rarely present at meetings, and the absent companies all receive the same version of the facts, which cuts short the game of telephone between trades, where each one reports its own reading back to the client. Finally, proving: the day a disagreement arises over a disputed delay, a discovered defect or an extra under discussion, the series of minutes reconstructs the complete chronology of the works. It is very often the strongest piece in the file.
The minutes are the central link in the method described in our guide to site supervision: the visit observes, the minutes record, the schedule by trade packages absorbs. And they must not be confused with the handover report: the minutes accompany the works week after week; the handover report is the single document that closes the works and starts the warranties running. Naming each document correctly prevents an end-of-works visit written up in the minutes from one day being requalified as handover.
The template, section by section
Good minutes fit in two to three pages, always structured the same way. Here is the framework, and what each section prevents:
| Section | Content | What happens when it is missing |
|---|---|---|
| Header | Project, address, minutes No., visit date, author | Minutes impossible to order or to cite ("the one from three weeks ago…") |
| Present / absent / excused | Name, company, role; invitations for the next meeting | "Nobody told me" becomes irrefutable |
| Progress per trade package | Package by package: done / in progress / behind, with the % or the milestone | Schedule slippage is discovered too late to be absorbed |
| Decisions recorded | One line per decision: who, what, by when | Every trade leaves with its own version of the decision |
| Additional works | Request, reason, estimate, status: to be priced / awaiting approval / approved on… | The final invoice becomes an end-of-works negotiation |
| Blocking points | What is preventing progress, who must unblock it, by when | The blockage repeats from meeting to meeting with no owner |
| Photos attached | Captioned and dated: state of progress, defects observed | An observation without a picture can always be disputed |
| Next deadline + objection clause | Date of the next meeting; "without observations within 8 days, the minutes are deemed approved" | The minutes lose most of their evidential force |
Two details make the difference. Continuous numbering (minutes No. 14 on project X): it proves that no set of minutes is missing from the series, which matters the day you need to establish that a given issue was never raised. And the carry-over of open items: an unresolved blocking point is copied into the next minutes with its original date. A problem that has been dragging on for four weeks must be visible at a single glance.
The 20-minute method
Minutes that take two hours to write are minutes you eventually stop writing. The sustainable version:
- Prepare before the visit (5 minutes). Duplicate the previous minutes: the framework, the list of trade packages and the open items are already there. The meeting follows the order of the document.
- Take notes during the meeting, inside the framework. Write directly into the sections, not in a notebook to transcribe later. Photograph every observation as it is being discussed; the time-stamped photo becomes its own caption.
- Write the same day (20 minutes). Factual sentences, no opinion: "Package 04 (tiling): laying 80 % complete, remaining grout in the shower area, completion expected 12 September". A decision = who, what, when. A defect = where, what, photo. The memory of nuances disappears within 48 hours; minutes written that evening are twice as short and twice as precise as those written two days later.
- Send immediately. To all parties, with the objection clause. Minutes sent a week after the meeting have already lost half their value: the actions they assign are supposed to be under way.
Distribution: to whom, how, and with what effect?
The rule is that everyone receives the same document: the companies of every trade package, present or not, and the client. This is more than courtesy: a single information channel is what prevents side conversations from undoing what the meeting has built. A project where the client negotiates directly with a company, without the designer in the loop, is a project where the budget and the schedule have already started to drift. The field rule allows no exception: no direct client-company exchange about the content of the works without the designer copied in.
The objection clause gives the minutes their force: sent with an 8-day period, they become the version of the facts deemed accepted by all. A company that disputes, six months later, an observation that was recorded, distributed and never contested starts from a losing position. It also protects the companies themselves: minutes noting "package 06 waiting on the client's approval of the tapware since 15 July" date the origin of a delay that, without a written record, would be blamed on them.
Finally, mind the border between recording and committing. The minutes can note "the client requests two extra sockets in the study, company B to price by 12 September": that is a record. The financial commitment, for its part, arises from the client's written approval of the priced quote, not from the line in the minutes. A €15,000 extra discovered mid-works (the wall assumed to be a partition that turns out to be load-bearing, structural engineer and steel beam included) is handled through a dedicated written agreement, approved by the client before execution. The minutes trace the discovery and its status; the agreement commits. Together they make handover serene: nothing left to negotiate on the last day, everything was approved as the project went along.
What is this written record worth in a dispute?
Site meeting minutes are neither a contract nor an amendment. They replace neither the accepted quotes nor the written agreements on changes. But in a site dispute, the decisive question is almost always chronological: who knew what, when, and who was supposed to do what. The complete series of minutes, numbered, dated and distributed with an objection period, answers that question better than any other document. Site supervision professionals see it unanimously: the cases that settle quickly are those where the written record exists; the disputes that drag on are those where everything was said out loud.
Hence the discipline, even, and especially, when the project is going well: it is precisely because everything is fine that people stop writing, and it is in those undocumented weeks that end-of-works disputes are born.
So, what about Nodal?
Nodal does not write your minutes. It makes sure they rest on a thread that is already traced. The project moves forward by trade packages, with a visible schedule and milestones; additional works are approved as the project goes along from the client portal, through a time-stamped agreement, line by line, exactly the recording/committing border described above; and the client follows progress in their own portal, which defuses the side channels. Your weekly minutes become a consolidation of facts already dated, not a reconstruction.
And because the pipeline moves forward on proof, every step crossed leaving its trace, the project history builds, by itself, the very chronology that disputes demand: who approved what, when, and on what basis.
Article published on August 24, 2026. This overview describes a professional practice of site documentation; it does not constitute legal advice. The exact weight of a written record in litigation is assessed case by case — for an ongoing dispute, consult a construction law attorney.