Construction Progress Meeting Minutes Template: Decisions, Delays and Commitments

A construction progress meeting minutes template should preserve what the team can act on: verified status, constraints, decisions, commitments, and unresolved questions. It should not become a transcript of every comment or a substitute for required contractual notices and technical records.

The strongest minutes distinguish fact, report, decision, and action. That separation helps readers understand what happened and what authority exists for the next step.

Set the record context before the discussion

Give every issue a traceable identity: project, contract or work package, meeting number, date, time, location, chair, minute-taker, attendees, apologies, distribution list, and linked agenda. State the revision status and correction deadline.

Record roles or organizations where useful, but collect only necessary personal information. Mark who had authority to make particular decisions. Attendance alone does not imply agreement with every statement.

Carry forward the agenda version and supporting-document cutoff used for the meeting. If a late schedule, drawing, or report was discussed, identify it explicitly instead of silently treating it as part of the original pack. This lets an absent recipient understand which evidence informed a decision and prevents a later revision from being mistaken for the document actually reviewed.

Copyable construction progress meeting minutes template

Project / contract:
Meeting number / date / location:
Chair / minute-taker:
Attendees / apologies / distribution:
Previous minutes and open actions:
Progress by area, trade, or milestone:
Look-ahead activities and dependencies:
Delays, disruptions, and constraints:
Design information, RFIs, and submittals:
Site access, logistics, and interfaces:
Safety and environmental items / formal references:
Quality, inspections, testing, and defects:
Proposed changes and formal process status:
Decisions and authority:
Actions — owner — due date — status:
Next meeting / correction deadline:

Use persistent item numbers so recurring issues can be followed without rewriting their history.

Reconcile previous actions first

Review each open action as complete, open, blocked, superseded, or transferred. Require evidence or a clear explanation. “Ongoing” is not a useful status unless the next deliverable and date are stated.

For a durable ownership model, use the action item form guide.

Record progress with an evidence basis

Organize progress by area, system, trade, or schedule activity. State what was completed, the reporting period, and the source: installed quantities, accepted milestones, inspection records, or another agreed method. Avoid unsupported percentages.

The construction daily report template provides day-level evidence; the progress meeting should synthesize it rather than duplicate every shift detail. Note any disagreement about measurement and assign a route for resolution.

Capture look-ahead work and dependencies

For the next period, record planned activities, required information, access, materials, predecessor work, inspections, and responsible parties. Separate a forecast from a commitment. A useful line reads: “Cable tray installation planned for Level 2 on 23 July, dependent on work-area release and RFI-014 response.”

Do not bury dependency dates in narrative. A table makes gaps visible:

Describe delays neutrally and precisely

Record time, location, affected activity, observed condition, source of the reported cause, immediate impact, mitigation, and next decision. When responsibility is disputed, attribute the statement: “Contractor reported access was unavailable” rather than declaring a proven cause.

Do not make entitlement, liability, or extension-of-time conclusions unless the authorized process has done so. Link formal notices and schedule analyses. Minutes may provide evidence but may not satisfy contract-specific notice requirements.

When several constraints affect the same activity, keep them separate until their relationships are established. Restricted access, missing information, unavailable labour, and late material may overlap without sharing one proven cause. Record the time window and mitigation for each. This gives planners usable evidence and prevents a convenient meeting summary from hardening an untested causal story into the project record.

Track design information and approvals accurately

List RFIs, submittals, drawings, samples, and decisions by reference and revision. Use precise states such as draft, submitted, under review, approved with comments, rejected, or issued. “Discussed” is not “approved.”

If work proceeds under an interim instruction, identify the authority, scope, limits, and formal follow-up required. Avoid paraphrasing a technical instruction in a way that changes its meaning; link the controlled source.

Separate quality and safety records from summaries

Minutes can note inspections, defects, observations, or incidents and assign follow-up. They should not replace controlled inspection, test, nonconformity, incident, medical, or safety records. Reference those systems only to the extent authorized.

The construction site inspection checklist helps structure observations, while the construction punch list template supports closeout defects. Escalate urgent hazards immediately instead of waiting for the next meeting.

Record changes without implying approval

Give each proposed change a unique identifier, description, origin, affected scope, information needed, owner, and current formal status. Separate a request, technical assessment, commercial review, and authorized instruction.

A conversation may identify a possible change, but it does not necessarily approve cost, time, or scope. State “proposed,” “under review,” or “authorized” only when supported by the project’s defined authority.

Where temporary direction is necessary, record its limits: affected location, permitted duration, maximum quantity, safety conditions, and the event that ends the instruction. Link the follow-up document required to confirm, replace, or withdraw it. A bounded interim decision is easier to supervise and less likely to be repeated elsewhere as though it were a project-wide standard.

Write decisions and actions as different records

A decision is an authorized choice. An action is future work. Capture both explicitly:

Decision D-07: Site manager approved use of the north delivery route from 08:00–10:00 on 22 July, subject to the current logistics plan.
Action A-24: Logistics lead to circulate the route notice by 16:00 on 21 July.
Review trigger: Reassess if the façade delivery schedule changes.

Use a decision log template for choices that need lifecycle tracking beyond one meeting.

Convert an authorized progress discussion into a structured draft. Kuno can support consented capture and draft notes; accountable project professionals must verify every commitment, status, date, and technical statement. Explore Kuno

Review, correct, and distribute responsibly

Before distribution, check names, item references, quantities, dates, decisions, owners, and links. Flag disputed wording rather than silently choosing one version. Give recipients a defined correction period and preserve approved revisions according to project rules.

Corrections should show what changed and why. For a material correction, issue a revised record with a revision marker rather than editing the distributed copy invisibly. If parties disagree, preserve the neutral core fact, attribute the competing positions, and identify the formal resolution route. The minute-taker should not decide a technical or contractual dispute through editorial wording.

Use the how to write meeting minutes guide for editing discipline and the meeting follow-up guide for the action cycle. Restrict sensitive commercial, security, personal, and incident information to authorized recipients.

Example concise minutes entry

Item 4.3 — Level 2 ceiling sequence
Status: Framing completed in rooms 2.14–2.19. Ceiling closure has not been authorized.
Constraint: Above-ceiling inspection IR-066 remains pending.
Decision: Room 2.18 remains open until inspection outcome is issued.
Action: Field engineer to confirm inspection time by 08:30 on 20 July.
Owner: J. Patel, field engineering.
Formal record: IR-066; no approval or delay entitlement inferred from this minute.

This structure lets a reader distinguish current fact, restriction, decision, and next action without reconstructing the whole conversation.

Final publication check

Confirm that every open item has one owner, every date is unambiguous, every approval has authority, every technical source has the correct revision, and every sensitive detail has a legitimate audience. If the minutes conflict with a controlled document, escalate and correct the record.

Make minutes concise enough to use and precise enough to trust. Record only with appropriate authorization and notice, then keep a responsible human in control of review, corrections, formal notices, and distribution. See Kuno for progress notes