Construction Meeting Minutes: Template & Best Practices

Construction runs on meetings — weekly progress meetings, coordination meetings, owner-architect-contractor (OAC) meetings, pre-construction meetings. But a meeting without good minutes is a meeting whose decisions evaporate the moment everyone walks out. Meeting minutes are what turn a conversation into a record and a set of commitments. This guide gives you a construction meeting minutes template and the best practices that make minutes actually useful.

Why meeting minutes matter

Meeting minutes do more than record what was said. They document decisions — so there's no argument later about what was agreed. They assign accountability — action items with owners and due dates turn discussion into commitments someone is responsible for. And they create a record — of who agreed to what and when, which matters when a decision made in a meeting later becomes relevant to a dispute. Minutes are the difference between a meeting that moves the project and one that just fills an hour.

Construction meeting minutes template

Header: project, meeting type, date, time, location, and prepared by.

Attendees: who was present, their company/role, and who was invited but absent.

Agenda / topics: the items discussed, ideally following a consistent agenda.

Discussion summary: for each topic, a brief factual summary of what was discussed — not a transcript.

Decisions made: decisions reached, stated clearly and unambiguously.

Action items: the heart of good minutes — each with a description, an owner, and a due date.

Open items: anything unresolved and carried to the next meeting.

Next meeting: date, time, and location.

Best practices for useful minutes

Focus on decisions and actions, not transcription. Nobody needs a word-for-word account. What matters is what was decided and what happens next. Capture those crisply and skip the play-by-play.

Assign every action item an owner and a due date. An action item without a name attached is nobody's job. "Someone should follow up" is not a commitment; "Sarah to confirm steel delivery by Friday" is.

Carry forward open items. Track unresolved items meeting to meeting so nothing quietly disappears. A recurring "old business" section keeps them visible until closed.

Distribute promptly. Minutes sent the same day, while the meeting is fresh, get read and acted on. Minutes sent a week later are archaeology.

Be factual and neutral. Minutes are a record, not advocacy. State decisions and actions objectively, since they may be referenced later.

Minutes and the field record

Meeting minutes capture decisions and commitments; your daily reports capture what actually happens in the field. Together they tell the full story of a project. A decision recorded in Tuesday's OAC minutes, and its execution documented in that week's daily reports, form a complete, connected record. When action items from a meeting play out on site — or don't — your daily documentation is where that shows up.

BuildLog keeps your field record consistent and connected to the decisions being made in meetings. Document the day's work, delays, and directions on site, and when a meeting commitment or decision affects the field — a change directed, a schedule agreed, an action promised — the daily record captures how it actually unfolds. It works offline and exports branded PDFs, keeping everything searchable in one place, with a free tier to start.

Frequently asked questions

What should construction meeting minutes include? Header details, attendees, topics discussed, decisions made, action items with owners and due dates, open items carried forward, and the next meeting details.

How detailed should meeting minutes be? Focused, not verbatim. Capture decisions and action items clearly; summarize discussion briefly. A transcript buries what matters.

Why are meeting minutes important in construction? They document decisions, assign accountability through action items, and create a record of what was agreed — which prevents disputes and keeps commitments from being forgotten.

---

Keep the field record that meetings depend on. Try BuildLog free.