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 method. Download buttons and installation steps are on the skill page linked to this article.
Prepare facts before requesting a draft
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.
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.
What the skill contributes
The CR de chantier pack contains instructions and a reference with eight sections: general information, participants, progress by trade, discussions and decisions, observations and issues, planning, photographic references and distribution. This structure organizes information; it does not supply missing facts.
This pack is separate from the ChatGPT training kit, which combines a thirteen-part Word template with an Excel register. The Claude skill prepares meeting minutes; it is not itself a cumulative action register.
Install once, then work with your notes
Native installation makes the skill available in Claude. 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.
Turn notes into statements you can verify
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
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 contains wording about objections within eight days. We do not present this as a general legal rule: its applicability to your project has not been established. Have contractual wording reviewed before circulation. Keep the draft status explicit until the responsible person approves the content.
Continue at the next meeting
Archive the approved version separately from the draft. 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.
Claude returns only text: what should you check?
Check skill activation and file creation, then explicitly request a downloadable .docx. A useful test means opening the document and comparing it with the notes, rather than merely asking Claude whether it knows the skill.
Must the skill be installed for every meeting?
Not if it remains installed and enabled. Update the project information instead. The practical page provides the native pack and a first test scenario; then use your own validated notes.