Construction Meeting Minutes: Record, Summarise and Chase Actions With AI

Yes, if every attendee has agreed to be recorded and a person checks the draft before it goes out. A recording or live transcript goes into an AI tool, which returns minutes and an action table with owner and due date. You correct names, numbers and owners, then issue the same day.

AI writes down what was said, not what was agreed. If nobody named an owner for the scaffold alterations, the transcript has no owner to find, and a tool that guesses one is worse than a blank. The chair's read-back at the end of the meeting is the real control; the AI only saves the typing.

Follow me on Instagram@sagnikteaches

Consent first: how to ask on site and prove you did

Recording rules differ between places: some require every participant's consent, others only one party's. Do not rely on the lenient version. Ask everybody, every time, and make the asking visible.

Connect on LinkedInSagnik Bhattacharya

1. Put it in the meeting protocol. The protocol is the page every subcontractor receives at the start, or the meeting clause in the subcontract. One sentence is enough: progress meetings are recorded and transcribed to produce the minutes, and the audio is deleted once the minutes are agreed.
2. Put a line in each agenda, so a new face on site is told before they walk in.
3. Say it aloud when you press record. The transcript then carries the consent statement and the date.
4. If someone objects, stop recording for that meeting and take notes by hand. Arguing costs you more than a handwritten page.

Agenda line:
This meeting will be recorded and transcribed so the minutes and action list can be produced. The audio is deleted once the minutes are agreed. Tell [chair's name] before the start if you object.

Opening statement (say it as the recording starts):
It's [date], this is the weekly progress meeting for [project]. I'm recording and transcribing so I can write the minutes and the action list. If anyone objects, say so now and I'll stop and take notes by hand.

The software helps but does not replace this. Microsoft Teams has a meeting-policy setting (explicit recording consent) that makes participants give their consent before they are recorded or transcribed, and Google Meet tells everyone on the call that notes are being taken (a pencil icon appears) while asking the organiser to say so as well. Those prompts reach people on a screen. They do nothing for the foreman sitting at the table who never opened the call, so your spoken statement still matters.

Subscribe on YouTube@sagnikteaches

Know when to pause. Valuations, claims and anything personal are better off the record: say "pausing the recording for the commercial item" aloud, pause, and minute only the outcome. If a recording involves phone calls, people joining from other places or members of the public, ask a solicitor first.

Which meetings to record, and which to leave alone

Recording suits meetings whose output is a list of actions: the weekly progress meeting, the subcontractor coordination meeting, a pre-start meeting and design-team meetings. The value sits in who agreed what, and a transcript can be searched later when somebody remembers a promise differently.

Leave it off for valuation negotiations, claims, disciplinary or performance conversations and anything where people need to speak freely before positions are fixed. Take notes by hand in those, or write down only the agreed outcome afterwards. A useful habit is to split the commercial item into its own short meeting, so the progress meeting can be recorded from start to finish without pausing.

Choose a recording route that survives a noisy cabin

Most site meetings happen in a cabin with a kettle, a radio and three conversations at once. Pick the route that suits where you meet and the subscriptions your firm already holds. Prices and caps below were read from the vendors' pages in November 2026, so check them before you buy.

Whichever route you choose, the room matters more than the software. Put the phone or conference speaker in the middle of the table, not by the door. Switch off the radio and the kettle. Ask people to give their name and company the first time they speak, and keep a printed attendee list so names can be matched afterwards. Send a short vocabulary list with the agenda (subcontractor names, product names, grid references) so you can paste it into the prompt. The comparison of AI note-takers for small teams covers the wider field, and whether note-takers are safe for client calls covers where the audio goes.

If some attendees join remotely, run the meeting as an ordinary call with one laptop in the cabin and let the call's own notes or recap tool do the listening. People on the call are normally told on screen when recording or notes start (Google Meet shows a pencil icon, for example), which helps with consent, but the people in the room still need your spoken statement. Use a single microphone for the room: two open microphones in one cabin produce echo and doubled words in the transcript. Attendees joining from other places raise the legal question again, so keep the same rule. Ask everyone, and ask a solicitor if the rules may differ for people in different places.

From transcript to action table: prompt, sample and fixes

The prompt does most of the work, and its most important rule is the one that stops guessing: an action's owner and date must come from the transcript, or the field says "TBC".

You are writing minutes for a construction progress meeting. Use ONLY the transcript below.

1. Attendees: names and companies exactly as stated. If a name is unclear, write [unclear].
2. Decisions: one line each. Use "agreed" only if someone said it was agreed. Otherwise write "discussed".
3. Action table with columns: No. | Action | Owner (person and company) | Due date | Transcript time.
   - Owner and due date must be stated in the transcript. If either is missing, write "TBC - not stated". Do not infer.
   - Meeting date is Thursday 11 March, so "Tuesday" means 16 March and "Friday" means 12 March, unless a date is spoken.
4. Information items: noted but not actioned.
5. Questions for the chair: unclear names, numbers that could be misheard (for example fifteen and fifty), and any action with no owner.

Vocabulary: [subcontractor names, product names, trade terms, grid references]
Previous actions still open: [paste action log rows]

TRANSCRIPT:
[paste]

An illustrative six-line extract from a transcript:

[00:41:12] Chair: Scaffold alterations to the east elevation, who's picking that up?
[00:41:20] Voice: We'll sort it before the plasterers start.
[00:41:31] Chair: Dryliner, can you confirm the board delivery for the first floor?
[00:41:38] Dryliner foreman: Tuesday morning, fifteen pallets.
[00:42:05] Chair: Electrician, first fix on level two is Friday the nineteenth, yes?
[00:42:11] Electrician: Friday, yes, if the ducting's finished.

Illustrative output, trimmed:

Questions for the chair, also illustrative: who owns the scaffold alterations; is "fifteen pallets" right, or was it fifty; who finishes the ducting and by when. This is the output you want, because the assistant declined to invent an owner for item 1 and turned the ducting remark into a question rather than an action. What you would still fix: add the missing action for the ducting once someone accepts it, and check the pallet count against the delivery note. In a transcript, number pairs that sound alike are the commonest quiet error, so any figure that drives a delivery or a date gets checked against your own notes.

The vocabulary line is worth filling in properly, because it is the cheapest fix for a mistranscribed site. An illustrative list for a mid-sized refurbishment:

Vocabulary:
Companies: [groundworks sub], [dryliner], [electrical sub], [scaffolder], [client's name]
Terms: DPC, DPM, noggin, soffit, fascia, screed, first fix, second fix, RFI, as-built
Locations: east elevation, level two, plant room, riser 3, loading bay
Products: [board type], [ductwork system name]

Without a list like this, a tool can mangle terms such as DPC or a subcontractor's trading name. With it, names and terms tend to come back spelled the way your team writes them, though you still check the first few meetings.

A minutes template for a progress meeting

A reusable template keeps meetings comparable and gives the assistant a fixed shape to fill. This one suits a weekly progress meeting on a small or medium job. The right-hand column is the instruction to carry into the prompt.

The variations row earns its place. A polite nod at the end of a discussion is easy to summarise as agreement, and an unrecorded extra is how a job loses money quietly. Minuting the word "discussed" until someone says "agreed" costs nothing, and the tutorial on turning meeting notes into tasks shows how the same rule keeps task lists honest.

Read-back, correction and same-day issue

Before anyone leaves, the chair reads the action list aloud and each owner says yes. It takes three minutes and replaces the guessing the AI would otherwise do. After the meeting, work to a timetable so the minutes are out while people still remember the meeting. An illustrative day:

• 11:30 meeting ends; recording stops; audio stays on your device.
• 11:45 transcript ready; paste it into the assistant with the prompt.
• 12:00 draft back. Check names against the attendee list, numbers against your notes and owners against the read-back.
• 12:20 corrected, saved as Rev A.
• 13:00 issued by email, with the action table in the body and the full minutes attached.

Subject: Minutes and actions, progress meeting 14, [project]

Hello all,

Minutes and the action list from today's meeting are attached (Rev A). Actions due before the next meeting are in the table below.

If your meeting protocol allows it: please reply within three working days with any corrections. Otherwise these stand as the record.

Next meeting: [date, time, place].

[your name]

Whether silence counts as acceptance depends on your meeting protocol and contract, so state the rule in the protocol rather than in the email alone. If corrections arrive, issue Rev B and keep both versions. Keep the audio only until the minutes are agreed, then delete it as you said you would.

Send the minutes to everyone who attended and to anyone who holds an action but was absent, plus the client and designers if your protocol says so. Name files so they sort in order, for example Minutes-14-RevA-11Mar.pdf, and keep the minutes, the issue email and (until agreed) the audio in one folder per job.

Chasing actions between meetings

Minutes without chasing are a record of who promised what, not a tool for getting it done. Keep one action log in a sheet, with the columns number, action, owner, company, due date, status, last chased and notes. Illustrative log as at 18 March:

Each week, filter for rows that are due within two working days or overdue, then paste them into the assistant grouped by owner and ask for one short reminder per person. Use the rows only, so there is nothing to invent:

Write a short reminder email to ONE person from the rows below. Under 90 words, courteous and specific. List each action with its number, due date and days overdue. Ask for a date if overdue. Do not mention payment, delays to other trades or contract terms.

Owner: Groundworks foreman
Rows:
43 | Book the drainage inspection | due 12 Mar | 6 days overdue

A fair escalation rule is the second miss: the first overdue action goes to the top of the next agenda, and the second goes to a phone call and a note in the minutes. Keep the chasing aligned with how you already follow subcontractors, as in the tutorial on chasing subcontractors and progress updates, and feed the day's events into the daily report so the two records agree.

Where AI minutes go wrong on a building site

• Overlapping voices. Speaker labels drift when three people talk at once, so a remark gets attributed to the wrong company. Check speaker names against the attendee list, and ask people to say their company when they first speak.
• Trade vocabulary. Terms such as damp-proof course, noggins and soffits turn into near-homophones. The vocabulary list in the prompt prevents most of it.
• Nods and thumbs-up. Agreement given by gesture never reaches the transcript. The chair says "agreed" aloud.
• Soft language. "We'll have a look at it" becomes "agreed to carry out". The prompt's rule on "discussed" versus "agreed" is there for this.
• Numbers and dates. Fifteen and fifty, the fourteenth and the fortieth, a weekday read as the wrong week. Verify any figure that triggers an order or a deadline.
• Side conversations. A joke or a personal remark can land in the summary. Delete it.

None of these is rare. They are the reason the draft is a draft, and the reason the read-back and the twenty-minute check are in the timetable.

Here is a realistic mistake and how it shows up, as an illustration. The draft minutes say the dryliner "agreed to complete the first floor by Friday". The dryliner's reply to the issued minutes is one line: "I said Friday if the boards arrive Tuesday." The site manager opens the transcript at the time stamp in the action table, hears the condition, and issues Rev B within the hour with the dependency written into the action. Without the transcript-time column, the two would argue from memory. Without same-day issue, the objection would arrive after the delay it describes.

What it costs a small firm, and the time it takes

Take six meetings a month at 90 minutes each. That is nine hours, or 540 minutes, comfortably inside Otter Pro's 1,200 monthly minutes. The binding limit is the 90-minute cap per meeting, so one long pre-start meeting breaks it. Otter Pro on annual billing is $8.33 a month, which is $99.96 a year. Business at $19.99 a month is $239.88 a year and covers four-hour meetings.

The cheapest route is usually the subscription your firm already holds. If your firm has an eligible Google Workspace edition or Google AI plan, Take notes for me costs nothing extra. If your people already hold Teams Premium or Microsoft 365 Copilot licences, intelligent recap does too. For anything involving client confidences, compare each vendor's privacy terms before you choose, because they differ.

As for time, measure rather than assume. Write the minutes by hand for three meetings and note how long each takes. Then use the AI route for the next three, including the twenty-minute check and the read-back. The difference between the two sets of timings is your real saving, and it will be specific to your meetings and your typing speed.

Site meeting recording and minutes questions

Do I need everyone's consent to record a site meeting?

Treat the answer as yes. Recording laws vary, and asking everyone removes the question. A visitor who arrives late, such as a building inspector or a supplier's representative, has not heard your opening statement, so repeat it when they sit down. If one regular attendee objects every week, take their items first, minuted by hand, and start recording once they have left. Ask a solicitor before relying on any lighter rule.

Which is better for site meetings, Otter or Teams?

It depends where the meeting happens. For a meeting in the site cabin, a phone running Otter, or Google Meet's in-person notes, needs nobody to dial in. If the meeting is already on Teams, intelligent recap needs a Teams Premium or Microsoft 365 Copilot licence and transcription switched on. Pick the route your people will actually start every week.

Can AI minutes be relied on if there is a dispute later?

Minutes can be referred to later, so accuracy matters more than speed. An AI draft nobody has read is the weakest version. A chair-checked action table, issued the same day with a stated window for corrections, is far stronger. Keep the agreed minutes and the issue email together, and ask your solicitor how your contract treats meeting minutes.

How long should I keep the audio recording?

Set a rule and tell attendees, for example deleting the audio once the minutes are agreed and keeping the minutes themselves. Shorter is safer because recordings can capture commercial discussion and personal remarks. If a dispute is brewing, check with your solicitor before deleting anything.

Further reads

• Architect Meeting Minutes: Record, Summarise and Issue Same Day With AI — The design-side version of the same minutes routine
• How Much Does an AI Note-Taker Cost per Seat? — What note-takers cost per seat across the main tools
• AI Tools for Construction Project Management: RFIs, Logs, Reports — RFI and action logs that feed from the minutes
• Can AI Write Toolbox Talks? What a Competent Person Must Check — Toolbox talks: another short site meeting AI can draft
• Construction Handover Pack Checklist: Gather the Paperwork With AI — Handover meetings need the same owners-and-dates discipline
• AI for Electrical Project Management: Diaries, RFIs, Snag Lists — Site diaries and RFIs alongside the minutes
• AI Automation for Construction Companies: Daily Logs to Invoices — Six paperwork steps from dictated daily log to progress invoice, one tool each, with a ten-person firm's costs, sums and who signs what.
• AI Software for Construction Scheduling: Programme Updates After Delays — One small job walked through a late delivery and two weather days: what the assistant does, what you calculate yourself, and what you tell each sub.
• AI Tool for Construction Planning: Pre-Start Checklist and Long-Lead Items — A 42-item pre-start checklist for small construction jobs, with prompts for scope, long-lead order-by dates and a risk register you actually review.
• AI in the Construction Field: Photos, Voice Notes and Punch Lists — Site crews take the photo and say one sentence; AI turns the captions into trade-by-trade punch lists and daily logs that the foreman reviews at the desk.
• ChatGPT for General Contractors: 10 Prompts for Bids, Subs and Updates — Ten prompts for bid screening, scope sheets, sub chasing and client updates, each with a sample output and a check before sending.
• How to Use AI in a Construction Company: Estimator, PM and Office — What estimators, project managers and office staff should each hand to AI, who reviews the output, and where figures and contract wording go wrong.
• AI in Construction Projects: Weekly Early-Warning Flags for Cost and Delay — Paste weekly progress notes, thresholds and last week's flags into an AI assistant, then check each flag before it reaches the risk register.
• ChatGPT for Construction: Eight Office Jobs With Worked Examples — Eight office jobs a small construction firm can give ChatGPT, each with a worked example, a check step and the jobs to keep human.
• How Is AI Used in Construction? Site Jobs and Office Jobs Compared — A small firm's site-versus-office split for AI in construction, with a worked week and a rule for which jobs to try first.
• Best AI for Engineering Firms: Proposals, Specifications, Minutes — How a small engineering firm can reuse past bids in proposals, draft specification first drafts and issue minutes faster, with no AI in stamped calculations.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Otter pricing page and privacy policy (read November 2026); Microsoft Learn pages on Teams intelligent recap and meeting recording policies; Google Meet help page for Take notes for me.