Construction meeting minutes template (Word, free)
Last updated
This construction meeting minutes template follows the order of a typical weekly site meeting or progress meeting: safety first, then progress against the programme, delays and weather, requests for information, submittals, change orders, quality and inspections, payments, and an action list numbered across meetings so that action 14.03 can be cited in meeting 20. Attendees are listed by company, because on a construction project who said something matters contractually.
Download the Word file, copy the plain text, or read the example: meeting fourteen on a primary school extension.
Word file (.docx), free and without signing up. Opens in Google Docs and Pages too.
What’s in the template
The minutes open with these details:
- Project
- Contract reference
- Meeting number
- Date
- Time
- Location (site office)
- Chair
- Minutes taken by
- Present (name, company, role)
- Apologies
- Distribution
Then the body follows the meeting in this order:
- 1. Previous minutes — Record that the previous minutes were accepted, or list the amendments requested in writing and by whom.
- 2. Safety — Always first. Record facts and the status of any investigation; do not record opinions about fault.Incidents and near-misses since last meeting: · Toolbox talks held: · Inductions this period: · Inspections and observations: · Outstanding safety actions:
- 3. Progress against programme — Compare with the current approved programme. Record the figures and the critical path position, not the discussion of why.Planned percent complete: · Actual percent complete: · Activities completed this period: · Activities planned next period: · Critical path status: · Days ahead / behind programme:
- 4. Delays and weather — Record days lost this period and cumulatively, the cause, and any notice given under the contract.Days lost to weather this period / cumulative: · Other delay events and cause: · Notices given (date, clause if known):
- 5. Requests for information (RFIs) — Open RFIs with the date raised and the date a response is due. Overdue responses are a delay record.RFI no.: · Subject: · Raised: · Response due: · Status:
- 6. Submittals and samples — Every submittal in review, with its status.Submittal: · Submitted: · Status (approved / approved as noted / revise and resubmit / rejected):
- 7. Change orders and variations — Each change with its cost and time effect and its approval status. A change discussed is not a change approved; record who approves and whether they have.CO no.: · Description: · Cost: · Time: · Status (raised / priced / approved / rejected):
- 8. Quality and inspectionsInspections held and results: · Non-conformances open: · Hold points upcoming:
- 9. Design and information — Current drawing register revision and any information the contractor is waiting for.
- 10. Commercial and paymentsProgress claim no. and period: · Amount claimed / certified: · Retention held: · Payment due date:
- 11. Procurement and subcontractors — Long-lead items, deliveries expected, subcontractor start dates.
- 12. Actions and next meeting — Number actions as meeting number dot item: 14.01, 14.02. Carry open actions forward under their original number.
At the end: action items and open rfis and submittals, as tables you can keep across meetings.
The template
Download it as a Word file, or copy the text version into your own document.
Construction Site Meeting Minutes Project: Contract reference: Meeting number: Date: Time: Location (site office): Chair: Minutes taken by: Present (name, company, role): Apologies: Distribution: 1. Previous minutes [Record that the previous minutes were accepted, or list the amendments requested in writing and by whom.] 2. Safety [Always first. Record facts and the status of any investigation; do not record opinions about fault.] Incidents and near-misses since last meeting: Toolbox talks held: Inductions this period: Inspections and observations: Outstanding safety actions: 3. Progress against programme [Compare with the current approved programme. Record the figures and the critical path position, not the discussion of why.] Planned percent complete: Actual percent complete: Activities completed this period: Activities planned next period: Critical path status: Days ahead / behind programme: 4. Delays and weather [Record days lost this period and cumulatively, the cause, and any notice given under the contract.] Days lost to weather this period / cumulative: Other delay events and cause: Notices given (date, clause if known): 5. Requests for information (RFIs) [Open RFIs with the date raised and the date a response is due. Overdue responses are a delay record.] RFI no.: Subject: Raised: Response due: Status: 6. Submittals and samples [Every submittal in review, with its status.] Submittal: Submitted: Status (approved / approved as noted / revise and resubmit / rejected): 7. Change orders and variations [Each change with its cost and time effect and its approval status. A change discussed is not a change approved; record who approves and whether they have.] CO no.: Description: Cost: Time: Status (raised / priced / approved / rejected): 8. Quality and inspections Inspections held and results: Non-conformances open: Hold points upcoming: 9. Design and information [Current drawing register revision and any information the contractor is waiting for.] 10. Commercial and payments Progress claim no. and period: Amount claimed / certified: Retention held: Payment due date: 11. Procurement and subcontractors [Long-lead items, deliveries expected, subcontractor start dates.] 12. Actions and next meeting [Number actions as meeting number dot item: 14.01, 14.02. Carry open actions forward under their original number.] Action items Action no. | Raised (meeting) | Action | By (company) | Due | Status Open RFIs and submittals Ref. | Subject | Raised | Due | Status
Minutes as contract records
Site meeting minutes are different from most minutes because they may be read in a dispute. If a delay claim or a change order is contested a year later, the minutes are often the only contemporaneous record of when an issue was first raised, what each party said about it and when information was promised. For that reason they stay strictly factual: what was reported, what figures were given, what was agreed and by whom.
Check your contract for what it says about minutes. Many forms of contract treat them as a record, not as an instruction; an action in the minutes does not by itself vary the works or extend the time. Instructions and notices usually have their own mechanism and the minutes should record that one was issued, not substitute for it.
Silence on circulated minutes
A common convention on construction projects is that minutes circulated and not challenged within a stated period, often a week or by the next meeting, are taken as an accurate record. Whether that convention binds anyone depends on the contract and on what was agreed at the first meeting, so state the rule in the minutes themselves and check your governing documents. In practice it means every party should read the minutes within days and put any correction in writing. A correction raised verbally at the next meeting, after the period, is harder to rely on.
What to record for every change, delay and RFI
- Changes: the number, a one-line description, who requested it, the cost and time effect as priced, and the approval status with the approver named.
- Delays: the event, the date it started, the days claimed, whether notice was given and when. Record the contractor's position and the client representative's position separately if they differ.
- RFIs: the number, date raised, date response due, and whether an overdue response is holding up work on site. The gap between due and answered is what a delay claim is built on.
- For each, the meeting number in which it was first raised, so the history can be traced.
What to leave out and common mistakes
- Opinions about fault. "The architect's late response caused the delay" is a claim, not a record. Write the dates and let them speak.
- Instructions. If the client's representative instructs a change in the meeting, minute that an instruction was given and that it will be confirmed through the contract's process.
- Restarting the action numbering each meeting. Actions carry their original number until closed.
- Mixing the programme discussion with the progress figures. Record the figures, then any agreed recovery measure, then stop.
- Issuing the minutes late. If the convention is acceptance by silence within a week, minutes issued ten days later have defeated their own purpose.
Who chairs and who takes the minutes
On many projects the client's representative, architect or project manager chairs and issues the minutes; on others the main contractor does. Whoever issues them should be named in the contract or agreed at the first meeting and recorded. Each company present should be listed with its representatives, because the minutes may later be used to show that a party was present when something was raised.
Example: filled-in construction meeting minutes
What the template looks like once it’s been used. The organisation and people are made up.
Minutes of site meeting no. 14, Alder Grove Primary School extension
Project: Alder Grove Primary School, two-storey classroom extension
Contract reference: WSD-2025-118
Date: Thursday 7 May 2026
Time: 10:00 am to 11:20 am
Location: Site office
Chair: Nicola Brandt, project manager, Pell & Marsh Architects
Minutes taken by: Nicola Brandt
Present: Nicola Brandt (Pell & Marsh Architects), Dermot Corrigan (Corrigan Build Ltd, site manager), Aiden Walsh (Corrigan Build Ltd, quantity surveyor), Sunita Rao (Westbrook School District, facilities manager), Greg Holloway (Tarrant Structural, engineer)
Apologies: Paul Nkemelu (Westbrook School District, finance)
Distribution: All present, apologies, project file. Minutes are taken as accepted unless corrections are received in writing within seven days.
1. Previous minutes
Minutes of meeting 13 (30 April 2026) accepted. One correction received from Aiden Walsh on 4 May: item 13.7, CO-06 value is $14,800 not $14,300. Corrected and reissued.
2. Safety
One near-miss on 2 May: an unsecured ladder slipped on the first-floor slab, no injury. Investigated by the site manager; ladder tagging reinstated and a toolbox talk on ladder use held on 4 May. No reportable incidents. Toolbox talks: two (ladders; working near the school boundary during school hours). Inductions: four, for the roofing subcontractor. Site inspection by Corrigan Build's safety adviser on 5 May: no major findings. Outstanding: replacement of the damaged hoarding panel by the playground gate, Corrigan Build, by 11 May.
3. Progress against programme
Planned 58% complete; actual 54%. Steel frame complete and signed off by Tarrant Structural on 28 April. Roof decking 70% laid. Blockwork to first floor 40%. Next period: complete roof decking, start roofing membrane, continue blockwork, first-fix electrical to ground floor. Critical path runs through roof watertight, currently forecast 29 May against a programme date of 22 May. Project is four working days behind programme.
4. Delays and weather
Three days lost to rain in the period 20 to 24 April (cumulative 9 days this year). Corrigan Build gave written notice of delay on 27 April citing weather. Dermot Corrigan stated that two of the four days behind programme are attributable to the overdue response to RFI-031 (see item 5). Nicola Brandt noted the client's position will be given in writing once the RFI is closed.
5. Requests for information
RFI-031 (door hardware schedule, raised 14 April, due 28 April): overdue. Nicola Brandt to issue the schedule by 11 May; Corrigan Build confirmed door frames cannot be ordered without it. RFI-033 (invert level of foul drain at manhole F3, raised 1 May, due 15 May): Greg Holloway to respond by 12 May. RFI-032 closed on 30 April.
6. Submittals and samples
Window samples: approved 1 May. Roofing membrane data sheet: revise and resubmit, the submitted product does not match the specified fire rating; resubmission due 12 May. External brick sample panel: inspection arranged for 14 May with Sunita Rao.
7. Change orders
CO-06 (additional surface drainage at the east boundary, $14,800, no time effect): approved by Westbrook School District on 1 May. CO-07 (relocate electrical switch room to avoid existing services, priced $23,500 and five working days): priced and with the client; Sunita Rao expects a decision by 14 May. CO-08 (raised today): client request for an additional external tap by the playground; Corrigan Build to price by 14 May.
8. Quality and inspections
Steel frame inspection 28 April: passed. Blockwork cavity inspection, ground floor: one non-conformance (NC-04, missing cavity tray at the north window), rectified and reinspected 5 May, closed. Upcoming hold point: roof deck before membrane, Tarrant Structural to inspect on 48 hours' notice.
10. Commercial and payments
Progress claim no. 13 for the period to 30 April: claimed $438,000, certified $412,000 on 5 May. Difference relates to materials on site not yet invoiced. Retention held to date $186,000. Payment due 2 June under the contract terms.
12. Next meeting
Thursday 14 May 2026 at 10:00 am, site office.
Open RFIs and submittals
| No. | Decision | Outcome |
|---|---|---|
| 1 | Minutes of meeting 13 accepted as corrected (CO-06 value) | Accepted |
| 2 | CO-06 additional surface drainage, $14,800 | Approved by client, 1 May 2026 |
| 3 | CO-07 switch room relocation, $23,500 and five days | With client, decision due 14 May |
Action items
| No. | Action | Owner | Due |
|---|---|---|---|
| 1 | Issue door hardware schedule in response to RFI-031 (action 13.04, carried) | Nicola Brandt, Pell & Marsh | 11 May 2026 |
| 2 | Resubmit roofing membrane data sheet with the specified fire rating (14.02) | Dermot Corrigan, Corrigan Build | 12 May 2026 |
| 3 | Decision on CO-07 switch room relocation (14.03) | Sunita Rao, Westbrook School District | 14 May 2026 |
| 4 | Price CO-08 external tap (14.04) | Aiden Walsh, Corrigan Build | 14 May 2026 |
Tips for construction meeting minutes
- Issue the minutes within two or three working days and state the correction period in the distribution line of every set.
- List attendees by company and role every time, even when it is the same people. The minutes may be read by someone who does not know who Dermot is.
- Record both parties' positions on a delay as positions, with the date each was stated. Do not resolve the disagreement in the minutes.
- Keep RFI and submittal registers as attachments and minute only the items that changed or are overdue.
- Use the action numbering meeting.item from the first meeting onward, and never reuse a number.
- Photograph the whiteboard or the marked-up programme used in the meeting and file it with the minutes.
Related templates
- Project meeting minutes template — The weekly status record: where each workstream stands, which milestones moved, what changed on the risk log and what was decided.
- Safety committee minutes template — The monthly safety committee record: incidents, near-misses, inspections, hazard reports and a corrective actions register that stays open until verified.
- Project kickoff meeting template — The one meeting where scope, roles and how the project will communicate are written down before anyone starts work.
- Business meeting minutes template — A simple, professional format for any business meeting: agenda items with discussion, decision and action, and next steps.
- All meeting minutes templates
Or let the notes write themselves
A template helps when you’re the one typing. If you’d rather not be, an AI note taker can draft the summary and action items for you. Most send a bot into the call; QuietNote captures from your own computer instead, so nothing joins the meeting and you decide when capture starts. It’s in private beta. Whatever you use, read the draft before you send it, and tell attendees you’re recording where the rules require it.
Questions
What should construction meeting minutes include?
Project and contract reference, meeting number, attendees by company, acceptance of the previous minutes, safety, progress against the programme, delays and weather, open RFIs, submittals, change orders with their status, quality and inspections, payments, procurement and a numbered action list carried from meeting to meeting. Record figures and agreements, not discussion.
Who takes minutes at a construction site meeting?
It varies by contract. Often the client's representative, the architect or the project manager chairs and issues the minutes; on some projects the main contractor does. Whoever it is should be agreed at the first meeting and recorded, since the party that holds the pen has some influence over the record.
Are construction meeting minutes legally binding?
Generally minutes are a record of what was said, not a contract document, and an action in the minutes does not by itself instruct a change or extend time. They can still carry weight as contemporaneous evidence in a dispute, which is why parties correct them promptly. What status they have depends on your contract, so check it rather than assume.
How soon should site meeting minutes be issued?
Within a few working days, and in any case before the next meeting. Many projects adopt a convention that minutes not challenged within a set period, such as seven days, are accepted as accurate. That convention only works if the minutes arrive in time for people to read them.
What is the difference between a site meeting and a progress meeting?
The terms overlap. A site meeting is usually the weekly meeting at the site office covering everything from safety to payments. A progress meeting sometimes means the same thing and sometimes a monthly meeting with the client focused on programme, cost and changes. The template covers both; drop the sections that do not apply.
Can an AI note taker be used for construction site meetings?
It can capture the discussion and draft the action list, which helps when the chair is also taking the minutes. Because these minutes may be relied on in a dispute, the issued version should be checked by the chair against the registers for every figure, date and status, and all parties should be told at the start if the meeting is recorded.