Construction Meeting Minutes

Construction meeting minutes are the written record of what a group of people agreed to at a project meeting — not a summary of who talked about what. On an Australian development, many meetings happen across the life of a project: site meetings, design coordination, control group, safety, and handover. Every one of those meetings produces decisions, instructions and open items, and if the record of those items isn't captured properly, disputes months later come down to memory versus memory.

This is general information, not legal, tax or financial advice.

What are construction meeting minutes, and why are they a contract record rather than a note-taking exercise?

Minutes exist to create a shared, dated account of what a meeting decided — who raised an item, what was agreed, who owns the follow-up, and by when. That's different from a personal note pad or a set of dot points someone emails around afterwards. A note-taking exercise records impressions. A contract record records facts the project can rely on later: this item was raised on this date, this person was given this action, and this is the status as at this meeting.

That distinction matters because minutes often become evidence. If a delay, an instruction or a disputed scope item is ever tested under the contract — in an extension-of-time assessment, a variation claim or a formal dispute — the first place anyone looks is the contemporaneous record. Minutes that read like a diary of conversation are far less useful than minutes that show a tracked item moving from raised to closed.

Which meetings on an Australian development actually need minuting?

Not every conversation on a project needs formal minutes, but several recurring meeting types do because decisions made in them carry contractual or safety consequences. The site or progress meeting — usually held weekly or fortnightly between the client side and the head contractor — is where program, quality and open issues get tracked meeting to meeting. Design coordination meetings, held with the architect and consultant team, resolve interface issues before and during documentation, and those resolutions often change scope or cost.

A project control group or client-side meeting deals with higher-level decisions — budget, program milestones, and approvals that sit above the contractor's day-to-day — and needs its own record separate from the site meeting. Safety and WHS consultation meetings are their own category: SafeWork NSW and Safe Work Australia both name regular team meetings and toolbox talks among the ways an employer can meet its duty to consult workers, so what was said and who attended is worth recording. And a handover or practical completion meeting closes out defects, outstanding items and final documentation, which makes its minutes the reference point for the defects liability period that follows.

What must each minute entry contain to be useful later?

A minute entry that will still be useful in six months needs six things: an item number that persists meeting to meeting rather than resetting each week, the date the item was first raised, a plain description of the issue, a named owner (a person, not just "the contractor"), a due date, and a current status — open, closed, or carried forward. Miss any one of these and the entry degrades into a sentence buried in a paragraph that nobody can search for later.

The persistent item number is the one people skip most often, and it's the one that matters most. If item 14 from March becomes item 3 in April's minutes because last month's closed items were deleted, nobody can trace an issue's history without reading every set of minutes in order. A stable register — where closed items stay visible with a closed status rather than disappearing — is what turns minutes from a weekly document into a running project record.

How do minutes differ from a site diary and an RFI?

A site diary is a daily, single-author record of conditions and events on site — weather, labour, progress, incidents — created contemporaneously by whoever is responsible for keeping it that day. Minutes are different: they record what a group agreed at a specific meeting, with multiple attendees who each had the chance to object to what was written down. A site diary is one person's account; minutes are the meeting's account.

An RFI is different again — a formal request for information or clarification on a specific technical point, raised and answered through its own numbered register with its own response. An RFI might be raised in a meeting and noted in the minutes, but the minute entry isn't the RFI. If the question and its formal answer only exist as a line in a set of minutes, the project has lost the audit trail an RFI is meant to create.

Who issues the minutes, and what does the "no objection" convention mean?

On most projects, whoever calls and chairs the meeting is responsible for issuing the draft minutes afterwards — the client-side project manager or superintendent for a site meeting, the architect for a design meeting, the meeting organiser for a control group meeting. Draft minutes go out to every attendee with a chance to review them. Standard form contracts such as AS 4000-1997 and AS 2124-1992, published by Standards Australia, don't typically set out a rigid minutes procedure of their own — the "no objection" practice sits alongside the contract as a convention, not a clause within it.

The convention works like this: attendees are given a period to flag anything they believe is wrong, missing, or recorded incorrectly, and if nobody raises an objection within that window, the minutes stand as the agreed record of the meeting. The exact period is whatever the meeting or the project sets, and it varies from project to project. The point of the convention is that silence isn't neutral. If you disagree with what's in the draft, you need to say so in writing before the window closes, not months later when the item resurfaces in a claim.

How are minutes used later in an extension-of-time or variation argument?

Because minutes are dated and created close to the event they describe, they carry weight as contemporaneous evidence — the same reason a site diary does. If a contractor later lodges an extension-of-time claim for a delay, the earliest written record of that delay being raised is often a site meeting minute, not the formal EOT notice itself. A minute that shows the delay was flagged on the date it happened supports the contractor's case. A minute that shows nothing was said for weeks undermines it.

The same applies to variations. A change discussed and apparently agreed in a design coordination meeting isn't a variation until it's formally directed and priced — but the minute recording that discussion is often the first piece of evidence either side points to when arguing about what was actually instructed, and when. This is exactly why minuting an instruction casually, without following it up with a formal direction, creates risk rather than removing it.

What format keeps minutes useful across a whole project?

The format that holds up over a twelve-month build is an item register, not a narrative document. Instead of "minutes of meeting held on 4 March" written as paragraphs of prose, the useful version is a table: item number, date raised, description, owner, action, due date, status. Each meeting updates the same table — closing items that are done, adding new ones, and carrying open items forward with their original number intact.

A narrative record might be easier to write in the moment, but it's much harder to use six months later when someone needs to answer a simple question: when was this first raised, and who was supposed to action it? A register answers that in one line. A paragraph of meeting prose makes you read the whole document to find out.

What are the most common failures in how minutes are kept?

A handful of habits are responsible for most of the pain. Writing minutes as narrative prose instead of a tracked action list is the biggest one — it reads well once and becomes useless the moment someone needs to find an item three months later. Renumbering items from scratch each meeting is a close second, because it destroys the ability to trace an issue's history across the project.

Leaving an item without a named owner is another common failure — "the contractor to review" isn't an owner, it's a hope. Circulating draft minutes late, after the next meeting has already happened, defeats the purpose of the "no objection" window entirely. And the failure with the biggest downstream cost is minuting an instruction that should have been issued as a formal direction or variation — recording that a decision was made in a meeting doesn't make it contractually binding, and treating it as though it does is how informal conversations turn into unresolved scope disputes.