How to prepare construction site meeting minutes with Claude
Organize meeting notes, separate observations from decisions and review the Word minutes. A method, fictional example and link to the Claude skill.
By Educasium
Download and install the Claude site minutes skill →
Useful site meeting minutes let readers trace what was observed, decided and requested. Claude can organize notes and prepare a Word document. The quality still depends on the information supplied and the review: a well-written sentence is not evidence that a decision was made.
This guide is for architects and site coordinators who want a repeatable AI-assisted method, from note-taking to circulating the signed document. It complements, without replacing, our guide to the structure and legal weight of site-meeting records, which details the 8 expected sections and the distribution list. Download buttons and installation steps are on the CR de chantier skill page.
Summary
- Prepare facts before requesting a draft
- What the CR de chantier pack contributes
- Draft the minutes step by step
- What the 8-day objection deadline actually changes
- Turn notes into statements you can verify
- Review the Word file before circulation
- Continue at the next meeting
- What we observe among site supervisors
- When this skill is not enough
- Train to make your records more reliable
- Frequently asked questions
Prepare facts before requesting a draft
Reliable minutes are prepared before Claude is even opened: the list of attendees and absentees, decisions actually made, observed issues and their dates. This step cannot be delegated to the AI, because it depends on what happened on site, not on how elegantly it can be phrased.
Identify the project, meeting date and participants. Separate attendees, absentees and people who sent apologies. Add notes by trade, explicit decisions, observed issues and announced dates. If previous minutes exist, identify the file and whether it is a draft or an approved version.
What to gather before writing
A complete attendance list, raw or dictated meeting notes, the previous minutes when they exist, and any photo references form the minimum base. Without it, Claude can only turn an incomplete text into a better-written incomplete text: the readability gained does not make up for the missing information.
Wording that should not become certainty
Preserve uncertainty in the source wording. “The contractor reports 60% progress” is not the same as a verified measurement. Requesting a repair does not establish that it was accepted or completed. For a photograph, provide a reference and description without assuming the image will be embedded in the document. Attendance mentioned for “next week” is not a firm date until a contractor has confirmed it in writing.
What the CR de chantier pack contributes
The skill organizes notes into eight fixed sections — general information, participants, progress by trade, decisions, issues, planning, photographic references and distribution — so nothing is lost in the formatting. It does not guess missing facts and does not replace a cumulative tracker for issues left open across several meetings.
This pack is separate from the ChatGPT training kit, which combines a thirteen-part Word template with a seven-tab Excel register for cumulative tracking. If you work with ChatGPT rather than Claude for a one-off record, our method for preparing site-meeting minutes with ChatGPT applies a similar logic from your notes and the previous minutes. The Claude skill covered here prepares one-off minutes; it is not itself a cumulative action register — for that ongoing tracking, the defects tracking table is the appropriate companion tool.
Install once, then work with your notes
Native installation makes the skill available in Claude: download it from the CR de chantier skill page. Attaching the portable version supplies text but does not install it. If the skill is already enabled, send the notes and ask Claude to use it. The official Claude guide explains skill management. Its file creation feature supports requesting a downloadable Word document. The skill does not, however, check the accuracy of a declared progress percentage or decide whether an issue should be closed: those checks remain the site supervisor's responsibility.
Draft the minutes step by step
Drafting itself follows a fixed order that separates gathering, structuring and review — five steps that, followed in order, reduce the risk of missing information or turning an assumption into an established fact.
Step 1: Gather the notes and previous minutes. Collect the meeting notes, even raw or dictated, along with the last approved record and its status. Name files with their date to avoid confusing versions.
Step 2: Ask Claude to structure the notes by trade. With the skill enabled, send the notes and request a first structuring pass by technical trade, without approving the final text yet.
Step 3: Separate observations, decisions and actions in each section. An observation records what was seen, a decision records an explicit agreement, an action describes remaining work with an owner and deadline when known.
Step 4: Fill uncertain fields rather than guessing them. When information is missing — a date, an owner, the basis of an announced percentage — ask that the field stay marked as pending confirmation rather than filled with a plausible guess.
Step 5: Request the Word file and review it before circulation. Explicitly ask for a downloadable .docx, open it, and compare every section against the original notes before sending it to contractors and the client.
What the 8-day objection deadline actually changes
The wording “after 8 days without written objection, the record becomes contractual” does not come from the NF P 03-001 standard itself: this standard, which governs private construction contracts, does not list site-meeting records among the contractual documents. The binding force of that deadline comes from a clause the parties must have inserted into the contract; without it, a contractor's silence does not amount to automatic acceptance, even though courts do give the document real evidential weight.
What general law provides without a clause
Article 1120 of the Civil Code states that “silence does not amount to acceptance, unless the law, usage, business relationships or particular circumstances provide otherwise.” A contractor who does not respond to a record is therefore not deemed to have accepted it, unless the contract contains the 8-day clause, or established professional usage and business relationships let a judge find tacit acceptance.
| Situation | Effect of the contractor's silence | What must be checked |
|---|---|---|
| Contract contains the 8-day clause | Record deemed accepted once the deadline passes, absent written objection | Actual presence of the clause in the CCAP or contract documents |
| No clause, but established usage or business relationships | Tacit acceptance possible, assessed case by case by a judge | History of exchanges and habitual practice between the parties |
| No clause and no established usage | Silence carries no acceptance value (Article 1120 of the Civil Code) | Written objection remains possible beyond 8 days |
| Written objection received within the deadline | The disputed point stays open regardless of the clause | Written trace of the objection and its receipt date |
This mechanism is covered in depth in our guide to the structure and legal weight of site-meeting records, which draws in particular on Le Moniteur's construction-law brief on site-meeting records. Claude can reproduce the 8-day wording if it appears in your template, but it cannot verify that your contract actually contains the clause giving it that force: that check remains human.
Turn notes into statements you can verify
Every point raised in a meeting must be classified before approval: an observation, a decision and an action carry different weight, and conflating them in the final record presents a mere reported statement as an established commitment.
Classify each point before approving its wording: an observation records a reported condition; a decision records an agreement; an action describes work to do. Add owners and deadlines only when known. Where sources conflict, ask for the disagreement to remain visible until clarified.
The following example is fictional and written to explain the method. This table is not a generated or tested Claude output.
| Received note | Working wording | Information still needed |
|---|---|---|
| Structure reported 60% complete | Contractor reports structural progress of 60% | Basis for that assessment |
| Damp on ground floor | Damp reported on the ground floor | Cause, affected trade and corrective action |
| We will attend on Friday | Attendance discussed for Friday | Exact date, committed contractor and scope |
Do not turn the final line into a dated commitment automatically. Establish which Friday was meant and who agreed to attend. Similarly, an issue disappearing from the latest notes does not justify closing it.
Review the Word file before circulation
The generated file remains a draft until it has been fully reviewed: comparing every section against the original notes, checking names and dates, and opening the Word file itself to spot broken layout are three separate checks that no partial review replaces.
Compare the document against the notes point by point. Check names, dates, percentages, recipients and photo references. Confirm that unknown information remains identified. Open the file in Word to inspect split tables, ambiguous empty rows and inconsistent numbering.
The pack reference file may contain wording about objections within eight days, whose exact scope is detailed above: it only applies automatically if your contract contains the matching clause. Have contractual wording reviewed before circulation. Keep the draft status explicit until the responsible person approves the content.
Continue at the next meeting
Archiving the approved version separately from the draft avoids mixing, meeting after meeting, what has been settled with what is still under discussion.
At the next meeting, supply that version and the new notes, clearly naming reference files. Ask for new points to be distinguished from historical ones. Do not assume that a document downloaded to your computer is available in a new conversation.
What we observe among site supervisors
In our exchanges with architects and site supervisors following long-running projects, the friction point is almost never understanding what a record should contain: the eight-section structure is usually well known. What costs time is formatting after a sometimes-long meeting, and checking that no issue carried forward for weeks has slipped through. That is a formatting and vigilance task, not a lack of rigour — exactly what a well-structured document can lighten, without ever replacing the human decision on what was actually said during the meeting.
When this skill is not enough
A well-structured record does not resolve everything at stake on a site. A disagreement between the client and a contractor over actual progress is not settled by better formatting: it calls for an on-site contradictory check, or even an outside opinion.
A project with many issues left open for months is better served by a defects tracking table than a string of standalone records, otherwise an old issue gets buried in the volume. A one-off visit outside a planned meeting calls for a site visit report, lighter than the full record covered here. Finally, a disputed contractual clause calls for a legal professional, not a rewording.
Train to make your records more reliable
Setting a method once is not enough: you also need to adapt it to every site without losing time or missing an issue carried forward for weeks. 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.
Training 100% fundable via OPCO/FIFPL. Qualiopi-certified programme. To structure your site-meeting records and contractual 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.
Frequently asked questions
Claude returns only text: what should you check?
Check skill activation and file creation first, then explicitly request a downloadable .docx rather than a plain text preview. A useful test means opening the document and comparing it against the original notes, rather than merely asking Claude whether it knows the skill. If the file still will not download, restart the conversation and check the installation before resending your notes.
Must the skill be installed for every meeting?
No, not for a skill that stays installed and enabled in your Claude account: it is the project data that needs updating, not the skill itself. The practical page provides the native pack and a first test scenario; then use your own validated notes, meeting after meeting. Reinstalling only becomes necessary after a pack update or a fault reported in the conversation.
Does a record prepared with AI have the same value as one written by hand?
Yes: nothing in French law makes a record's value depend on how it was drafted — what matters is its content, its distribution and, where applicable, the contractual clause that gives it binding force after the objection deadline. A record prepared with Claude therefore carries neither more nor less weight than one typed directly in Word, provided it has been reviewed and approved by the responsible person before circulation. It is the rigour of the content that protects the architect, not the tool used to format it.
What should you do if a contractor does not react within the stated deadline?
If your contract contains the 8-day clause, the absence of a written objection within that time in principle makes the record contractual on the points it mentions, but keep proof of the date it was circulated to the contractor concerned. If the contract does not contain that clause, the lack of reaction alone is not enough to establish acceptance under Article 1120 of the Civil Code, and an objection remains possible beyond 8 days absent particular circumstances recognized by a judge. When in doubt, have a legal professional confirm that your contract actually contains the clause before treating a point as definitively settled.