Construction meeting minutes template for site and PCG meetings

A construction meeting minutes template for site and PCG meetings has to survive being opened twice: once as the minutes for the meeting that just happened, and again as a register you scroll through months later looking for when something was first raised. This one is built to do both from the same row. Search construction meeting minutes template word and most results promise a document you can type over in Word; what you can actually download here is a CSV and a PDF, because a register that has to reconcile against a variation number and an RFI number is a spreadsheet with fields, not a page of prose with a letterhead.

One row of the download is one action from one meeting, and it carries that meeting’s standing sections with it — attendees, apologies, safety, programme, RFIs, variations, claims — so the export is a flat action list with nothing separated from its context. Open the CSV and the meeting 14 header repeats on every action from that meeting: the date, who chaired, who was there, what safety covered, and where the job sat against the programme. That repetition is not padding. An action list on its own tells you what to do; the standing sections beside it tell you why, and a filtered or sorted view loses nothing because the context travels with the row rather than sitting in a separate sheet.

It is written for whoever chairs and minutes a site or project control group meeting: the client-side project manager, the superintendent, or the architect running a design meeting. Whether you searched for a construction meeting minutes template, a project meeting minutes template construction teams can run a register from, or a construction meeting minutes sample to check your own format against, the fields are the same twenty this page tables below.

Background on why minutes are treated as a contract record rather than a note-taking exercise, and on the “no objection” convention that lets a circulated draft stand as agreed, is in construction meeting minutes.

The meeting details block — project, meeting type, meeting number, date and time, location, chair, minutes taken by — is the header that repeats on every action from this meeting. Keep the numbering separate per series: site meeting 14 and a PCG meeting are different sequences, and mixing them is how a meeting number stops meaning anything.

The people block — attendees, apologies — names people and organisations, not roles. Recording who sent an apology matters as much as recording who attended, because an action assigned to someone who was not in the room is the first thing anyone challenges later.

The standing sections — safety, programme, RFIs, variations and claims — are pulled from their own registers, not from memory. RFIs closed or still open since the last meeting come from the RFI register, and variations raised or directed come from the variation register. In the demonstration meeting, RFI-041 closed on 13 August and VO-12, submitted 14 August, was still awaiting the superintendent’s direction — both numbers pulled straight off their own registers rather than retyped from memory.

The action block — item number, action, owner, due date, status, next meeting — is the part the minutes exist to produce. “Issue the superintendent’s direction on VO-12, or reject it with reasons” is item 14.6 in the demonstration record, owned by the superintendent and due 2026-08-27, ahead of the next meeting on 2026-09-03. One named owner and one date, every time — an action with neither is an action nobody is holding.

An owner that is not a person. “The contractor to review” is not an owner, it is a hope. A company cannot be chased for an update; a named person can, and naming them is what makes an action list something other than a wish list.

Circulating the draft too late. If the draft minutes go out after the next meeting has already happened, the review window the “no objection” convention depends on has already closed before anyone had a chance to use it.

Treating a meeting note as a direction. Recording that something was agreed in a meeting does not make it a formal instruction or a variation. A decision that changes scope, cost or time needs its own numbered variation, issued in writing, and the minutes should say that it was issued rather than stand in for it.

Restating numbers from memory. Writing that “the RFI closed a while back” instead of pulling the actual number and date off the RFI register is how a project ends up with two versions of the same fact — one in the register, one in someone’s recollection of the meeting.