Meeting Minutes

Definition — what it is

Meeting minutes are the formal written record of a project meeting, capturing the decisions made, the actions assigned with owners and due dates, and the items still open. In construction they are most consequential for recurring owner-architect-contractor meetings and coordination meetings, where the discussion routinely touches scope, schedule, cost, and directions that can affect the contract. Their defining property is that they are typically issued with a review-and-object window: if no one objects within a stated period, the minutes stand as the accepted record, which makes them a mechanism for establishing agreed facts and directions over time. Meeting minutes are not a transcript and not a chat log; they are a curated record of decisions and commitments, and treating them as either a verbatim recording or an informal recap defeats their purpose and their contractual weight.

Also known as: OAC Minutes, Progress Meeting Minutes, Coordination Meeting Minutes, Meeting Notes

Why it matters — what it protects

Minutes convert conversation into accountability. A decision discussed but not recorded, with an owner and a date, is a decision that quietly evaporates; the same decision captured as an action item with a name against it is one that gets chased. The running action log across successive meetings is often the most reliable list of what the project actually owes itself.

They can establish agreed facts by silence. Because minutes are usually issued subject to an objection window, an entry that goes uncontested becomes the accepted record of what was decided or directed. This is powerful and dangerous in equal measure: a favorable direction recorded and unchallenged becomes evidence, and an inaccurate entry that no one corrects can bind a party who simply did not read carefully.

They document directions that shade into changes. Owners and architects routinely give guidance in meetings that affects scope, sequence, or means and methods. Minutes that capture such a direction, with who said it and in what terms, are frequently the first evidence in a later change or claim, and minutes that omit it leave the direction as contested memory.

They are a schedule and risk instrument in aggregate. The pattern of recurring open items, repeatedly deferred actions, and decisions that never get made is a leading indicator of a project losing control of itself. Executives who read the trend in the minutes, not just the latest set, see trouble before it reaches the cost report.

Lifecycle — how it moves

1. Agenda preparation

   The agenda is built, ideally carrying forward the open action items from the prior meeting so nothing drops. Meetings run without an agenda produce minutes that ramble and miss the items that matter.

2. The meeting and note capture

   Discussion is captured with attention to decisions, directions, and commitments rather than everything said. The skill is distinguishing a decision from an opinion and a firm action from a vague intention.

3. Drafting

   Notes are turned into structured minutes: decisions stated plainly, actions with owners and due dates, open items carried with their original raise date. Drafting days later loses the nuance of who committed to what.

4. Issuance with objection window

   Minutes are distributed with a stated period to review and object. This window is the mechanism by which silence becomes acceptance, so who receives them and whether the window is clearly stated both matter.

5. Objection and correction

   Attendees review and raise corrections. Failing to read minutes carefully is a real exposure: an inaccurate entry uncorrected within the window can become the binding record.

6. Action tracking

   Assigned actions are tracked to completion across meetings. Where tracking is weak, the same items reappear meeting after meeting as 'ongoing,' which is itself a signal.

7. Retention and reference

   Accepted minutes are retained and become reference in change negotiations, claims, and closeout. Their value is entirely in later retrieval of a specific decision or direction.

Anatomy — the data it carries

Meeting identifier and type

Project, meeting series, sequential number, and type (OAC, coordination, safety). Establishes which recurring record this belongs to.

Date, time, and location

When and where, which can matter for reconstructing sequence of events and for schedule correlation.

Attendees and companies

Who was present and absent, by name and firm. Determines who is bound by the objection window and who gave any recorded direction.

Agenda / topics

The structure of the discussion, ideally aligned to standing categories so items are easy to trace across meetings.

Decisions

Plainly stated conclusions reached. The clarity here is what separates an accountable record from a vague recap.

Action items

Specific tasks with a named owner and a due date. Actions without an owner or date are the ones that never get done.

Open / carried items

Items still unresolved, with their original raise date preserved. Aging here is the schedule-risk signal.

Directions given

Instructions from the owner or design team affecting scope, sequence, or methods, recorded with attribution. Frequent first evidence in a change dispute.

Item status

Open, in progress, closed, deferred. The field that drives whether an action is actually being worked.

Objection window statement

The stated period and mechanism for raising corrections. The clause that makes silence into acceptance.

Linked records

RFIs, change events, schedule activities, and prior minutes an item connects to, so decisions stay joined to their consequences.

Author and issue date

Who prepared and issued the minutes and when, relevant to the objection-window clock.

Failure modes — how it breaks

Recap instead of record

The minutes narrate the discussion but never crisply state what was decided or who owns what. Everyone leaves with a different understanding, and the document that was supposed to settle it settles nothing.

Actions without owners or dates

An action is recorded as 'coordinate the ceiling heights' with no name and no date. It belongs to everyone and therefore no one, and it reappears unresolved at the next meeting and the one after.

Directions omitted or softened

The owner directs a change in the field during the walk, but the minutes record it as a topic 'discussed' rather than a direction 'given by,' with attribution. When it becomes a change claim, the strongest contemporaneous evidence is missing or diluted.

Objection window ignored

An inaccurate or unfavorable entry is issued, no one reads carefully, and the window closes. The erroneous record now stands as accepted, and correcting it later means arguing against a document you effectively agreed to by silence.

Open items never age out

Carried items lose their original raise date each time they roll forward, so a problem that has been open for four months looks the same as one raised last week. The aging signal that should trigger escalation is erased.

Minutes issued too late

Minutes arrive days or weeks after the meeting, by which point the objection window is meaningless and the actions have already gone stale. The record loses both its accuracy and its accountability function.

Metrics — how it is measured

Issuance timeliness

Days from meeting to issued minutes. Late issuance guts both the objection window and the action-tracking value.

Action closure rate

Share of assigned actions closed by their due date. The core accountability metric across the meeting series.

Open item aging

Days each carried item has been open, from its original raise date. The leading indicator of a project accumulating unresolved decisions.

Action attribution completeness

Share of actions with both a named owner and a due date. Measures whether the minutes actually assign accountability.

Objection / correction rate

Frequency of corrections raised within the window. A very low rate can mean minutes are accurate or that no one is reading them.

Repeat-item frequency

How often the same item recurs across meetings unresolved. A direct measure of whether decisions are actually being made.

The AI shift — what actually changes

Conversational

The stack of minutes becomes a searchable decision record. You ask what was decided about a specific interface, when a particular direction was given and by whom, or which action items assigned to a subcontractor are still open, and get an answer assembled across the whole meeting series with the specific minutes cited rather than a manual re-read.

Generative

Drafting shifts from typing up notes to editing a structured draft: from meeting notes or a recording, a model produces minutes with decisions stated plainly, actions extracted with candidate owners and due dates, open items carried forward with their original raise dates, and any owner direction flagged for attribution, which the author confirms and issues.

Orchestrated

The minutes stop being a standalone document. Carried open items are reconciled against the prior meeting so nothing drops, action items are linked to the RFIs, change events, and schedule activities they concern, recorded directions that touch scope are surfaced as potential change events, and the objection-window clock is tracked so acceptance is deliberate rather than accidental.

Autonomous

The routine motion runs continuously: agendas are assembled from the prior meeting's open items, draft minutes are produced with actions and owners extracted, aging on carried items is tracked from the original raise date, action-owner reminders are issued and escalated, and directions with scope implications are flagged, while the accuracy of the record, the attribution of directions, and any change decision remain human.

Prompts — put it to work

Tool-agnostic and copy-ready. Adapt the specifics — thresholds, contract windows, cost codes — to your own project before you run them.

Conversational — Finding a specific decision buried across months of meetings.

Search our project meeting minutes across the whole series and answer precisely: what has been decided or directed about the lobby ceiling height and the coordination of ductwork above it. Give me each relevant entry with its meeting date, whether it was a decision or a direction, who made it, and its current status, in chronological order. Then tell me whether the record is consistent or whether later minutes contradict earlier ones, and flag any direction that touches scope but was never converted into a change.

What good output looks like: A chronological trace of the decisions and directions on the topic with dates, attribution, and status cited, plus an explicit note of any contradiction or unpriced scope direction.

Follow-ups:

• Which of these entries went uncontested within their objection window and now stand as accepted?
• List the still-open action items on this topic and who owns them.
• Draft a change event for any scope direction that was never priced.

Generative — Turning a recording or rough notes into issuable minutes.

Produce formal meeting minutes from the attached notes for this week's owner-architect-contractor meeting. Structure them by our standing agenda categories. State each decision plainly. Extract every action item with a candidate owner and a due date, and mark where the owner or date is unclear so I can confirm. Carry forward the open items from last meeting's minutes, preserving each item's original raise date. Separately flag any statement that reads as a direction from the owner or architect affecting scope, sequence, or methods, and record it with attribution. Include the standard objection-window statement.

What good output looks like: Issuable minutes with crisp decisions, attributed actions and owners, correctly carried open items with original raise dates, and directions flagged for attribution, with unclear owners marked for confirmation.

Follow-ups:

• Reconcile the carried items against last meeting's minutes and flag anything I dropped.
• Rewrite the flagged directions with precise attribution of who directed what.
• Generate the action-owner reminder list once I have issued these.

Orchestrated — Keeping the action log honest across systems.

Reconcile our meeting-minutes action log against the rest of the project. For every open action item, check whether it is actually being worked in the system where it lives: actions about information requests against the RFI log, actions about scope or cost against the change log, actions about sequence against the schedule. Flag any action marked in progress in the minutes with no corresponding activity anywhere, any action that has recurred across three or more meetings, and any recorded owner direction that should have generated a change event but did not. Return the reconciliation tied to the specific minutes entry and the record it should connect to.

What good output looks like: A reconciliation that exposes actions marked in progress with no real activity, chronic repeat items, and unconverted directions, each tied to the minutes entry and the system it should link to.

Follow-ups:

• Draft escalation notes for the actions recurring across three or more meetings.
• Open change events for the directions that were never converted.
• Which owners are consistently missing their action due dates?

Autonomous — Standing policy for running the meeting-minutes process.

Operate our meeting-minutes process continuously under these rules. Assemble each agenda from the prior meeting's open items, preserving their original raise dates. From the meeting notes, draft minutes with decisions stated plainly and actions extracted with candidate owners and due dates, and present them to the chair for confirmation before issuance. Track the objection window on issued minutes and remind attendees before it closes. Track action items to closure, reminding owners before due dates and escalating overdue and thrice-repeated items to the project manager. Flag any recorded direction that appears to affect scope. Never issue minutes without the chair's confirmation, never treat an uncontested entry as a settled fact for a claim without a human review, and never open or price a change on your own; route all attribution and change decisions to a human with your reasoning.

What good output looks like: Timely draft minutes and a tracked action log with a short human exception queue, where issuance, attribution, and change decisions always require a person, fully audited.

Follow-ups:

• Show me this week's overdue actions, repeat items, and objection-window deadlines.
• Which recorded directions are you flagging as possible unpriced changes?

Get the full Construction AI Prompt Catalog — every prompt in the library in one document.

Maturity — locate yourself honestly

0. Level 0 — Informal notes

   Someone jots notes that may or may not circulate. Decisions and actions live in memory and email, and nothing is carried forward reliably.

1. Level 1 — Structured minutes

   Minutes are drafted and issued with an objection window and an action list, but tracking across meetings is manual and inconsistent.

2. Level 2 — Tracked and linked

   Open items are carried with original raise dates, actions are tracked to closure, and items link to RFIs, changes, and the schedule.

3. Level 3 — Assisted

   Minutes are drafted from notes or recordings with actions and owners extracted, directions flagged, aging tracked, and cross-system reconciliation surfaced.

4. Level 4 — Operated

   Agenda assembly, drafting, objection-window and action tracking run within guardrails, while accuracy, attribution, and change decisions stay human.

Common questions

Are meeting minutes contractually binding?

They are not a contract, but they can carry real contractual weight, especially when issued subject to an objection window. An entry that records a decision or direction and goes uncontested within the stated period is commonly treated as the accepted record of what happened, and it becomes evidence in a change or claim. That is exactly why reading issued minutes carefully and correcting errors within the window is not optional.

How detailed should minutes be?

Detailed enough to capture every decision, action, and direction with clarity, but not a transcript. The goal is a curated record of what was concluded and who owns what next, not a play-by-play of the conversation. A useful test is whether someone who missed the meeting could tell exactly what was decided, what they now owe, and by when, without needing to have been in the room.

What should I do if issued minutes are wrong?

Raise a correction in writing within the stated objection window, referencing the specific entry and stating the accurate record. Silence within that window is commonly treated as acceptance, so letting an inaccurate or unfavorable entry stand because it seemed minor is how a party ends up bound by something they never actually agreed to. The correction should be as specific as the entry it fixes.

Do minutes replace formal notice or an RFI?

No. Recording a direction or an issue in minutes documents that it was discussed, but it generally does not satisfy a contractual notice requirement, authorize a change, or resolve a question the way an RFI answer does. If a direction given in a meeting affects scope or cost, it should be converted into the proper instrument — a change event or an RFI — and not left to live only inside the minutes.