Drafted minutes.
Meeting notes turned into structured, formal minutes — decisions, actions, owners, deadlines — in the project’s own format, for the chair to review and issue. The hours after every progress meeting come back.
Whoever holds the pen holds the record. Whoever fails to correct it accepts it.
Last updated
Zepth Core module
Construction runs on meetings — and the minutes are not a courtesy summary. They are contemporaneous records that surface in claims and arbitration years later, often as the only written trace of what was agreed, instructed or acknowledged.
Whoever takes the minutes controls the record. Whoever fails to correct them accepts it.
Minutes are admissible contemporaneous business records, and a clean set with no recorded objections is powerful evidence of what was decided and who acknowledged what. The Society of Construction Law’s Delay & Disruption Protocol puts contemporaneous records among its core principles, and progress-meeting minutes sit alongside the site diary as the primary written account of what the project knew, and when.
But the mechanism with real teeth is quieter than that, and most teams never think about it until it is too late: deemed acceptance.
Many contracts and project procedures deem minutes approved unless a party objects in writing within a defined window — commonly by the next meeting, or within a stated number of days. The windows vary; the principle does not. Silence becomes assent. Two years later, in a dispute, the record shows you agreed — because you did not write the correction letter.
Decisions, not discussions. Good minutes separate four things: decisions made, instructions given, information shared, and actions assigned — with an owner and a date on every action. Verbatim transcription is an anti-pattern, and so is vagueness. “Delay was discussed” is useless in a claim. “Contractor notified two-week delay to Level 3 slab due to late structural revision; Engineer acknowledged” is a record. One of those sentences is worth money and the other is worth nothing, and they take the same amount of time to write.
Whoever holds the pen shapes the narrative. The scribe decides whether an exchange reads as “contractor raised concern” or “engineer acknowledged delay” — and those are very different sentences in an arbitration bundle. Convention gives the chair the pen, usually the consultant in a consultant-administered contract. Sophisticated contractors never let one-sided minutes stand: they issue written corrections within the window, every time, and keep their own contemporaneous notes. Meeting after meeting of unchallenged adverse minutes builds the other side’s contemporaneous record — and that is the one the tribunal will prefer.
Attendance and authority are part of the record. Who was present, and at what level of authority, determines whether an “agreement” recorded in the minutes binds anyone at all. The attendance register is what defeats the later argument — we weren’t there, or he had no authority to agree to that. It is a column, and it costs nothing, and people leave it out.
Carry-forward discipline. Un-actioned items carry forward with their original dates visible, not silently re-dated to look fresh. Quietly dropping items is how obligations evaporate, and it is rarely deliberate — it is just what happens when the person typing wants a shorter document. Numbered items, referenced by meeting, section and item, make the trail citable years later.
The safe rule runs in both directions, and it is worth stating carefully because the honest version is more useful than the confident one.
On the one hand: anything in minutes that looks like an instruction or a variation should be followed by a formal instruction or a written confirmation under the contract’s own machinery. A mention in the minutes rarely satisfies a contractual notice requirement, particularly where the contract directs that notice be given to a named person in a specified form. Relying on a line in the minutes is how contractors do work they never get paid for.
On the other hand: courts have, in some circumstances, given signed minutes and progress reports instructive or notice effect. So neither side gets to assume that minutes are legally inert.
The practical advice is the same whichever way the law lands in your jurisdiction, which is why it is worth following: treat a directive line in minutes as a trigger to request or issue the formal document — and write every line as if it might one day be read aloud in an arbitration. Because it might.
Actions recorded without owners or dates simply do not close, and the issues resurface later as delays with no accountability trail attached to them. Inaccurate minutes left unchallenged inside the objection window are deemed accepted, and a position is surrendered by nobody in particular, on a day nobody remembers.
A directive buried in minutes and treated as a real instruction produces the worst outcome of all: the work gets done, and the payment is refused for want of a formal instruction.
And then there is the chronic failure, the one almost every project has: minutes that read like a summary of a conversation. Pleasant, fluent, and useless to the one audience that will ever read them closely — a tribunal.
Minutes are structured by design rather than by discipline. Decisions, instructions, information and actions are distinct record types, so the difference between them survives the typing. Every action carries an owner and a deadline, and open items carry forward automatically with their original dates intact.
Attendance is logged with roles. Distribution and the objection window are tracked, so the deemed-acceptance clock is visible rather than discovered afterwards. And every minute item can link to the RFIs, instructions, submittals and programme items it references — which is what turns the minutes from prose into navigable evidence.
The record says what was decided, not what was discussed — which is the difference between an asset and a summary.
The deemed-acceptance clock is visible and tracked, so a position is never surrendered by silence.
Actions carry owners and dates and carry forward with their original dates, so obligations cannot quietly evaporate.
Minutes link to the RFIs, instructions and programme items they reference — navigable evidence rather than prose.
Decisions, instructions, information and actions are distinct — because merging them is what makes minutes useless in a claim.
No unassigned items. An action without an owner is a sentence, and it closes like one.
Open items roll to the next meeting carrying the date they were first raised — visibly, so age cannot be laundered.
The register that defeats “we weren’t there” and “he had no authority to agree to that”.
Distribution logged and the deemed-acceptance clock shown, so silence is a decision rather than an accident.
Every item can reference the RFI, instruction, submittal or activity it concerns — minutes as evidence you can navigate.
The first agenda item is the register of open actions from last time, with their original dates. Not a tour of opinions — a review of what was promised.
Decisions, instructions, information, actions. Keeping them apart in the record is what makes the record usable, and it is the step that gets skipped.
A named owner and a date, on every single one. An action without an owner is a sentence, not a commitment, and it closes at roughly the rate you would expect.
Minutes distributed to attendees with the objection window tracked. Deemed acceptance runs whether or not anyone is watching it, so it is better to be watching it.
If the minutes are wrong, say so in writing before the window closes. Every time it matters. This is the single cheapest piece of claims defence available on any project.
Meeting notes turned into structured, formal minutes — decisions, actions, owners, deadlines — in the project’s own format, for the chair to review and issue. The hours after every progress meeting come back.
Every commitment made in the room becomes a tracked action, and aging items are drafted into the next agenda’s carry-forward automatically. Nothing evaporates because nobody typed it up.
Lines that read like instructions or variations are flagged for formalisation under the contract. This closes the minutes-as-instruction trap from both sides: the contractor gets the formal instruction it needs, and the consultant does not accidentally issue one.
Discussion items are linked to the records underneath them — “the Level 3 delay in item 12.3.4” connects to the activity and the RFI it actually concerns. Minutes stop being prose and become evidence you can navigate.
The engineer’s judgment stays in charge; the AI removes the latency and the blind spots.
Open-action registers by owner, meeting and age, with closure rates and carry-forward history showing original dates. Distribution and objection windows are tracked per issue, so the deemed-acceptance clock is a report rather than a surprise. Exportable for governance reporting — and, when it matters, for the claim.
They are admissible contemporaneous business records, and under deemed-acceptance procedures they can bind you by silence. They rarely substitute for a formal contractual notice or instruction — but tribunals read them closely as evidence of what the parties knew and acknowledged, and when.
Read the full answerUnder most project procedures they are deemed accepted once the review window closes — conventionally by the next meeting, or within a stated number of days, though the window varies by contract. The discipline is simple and unglamorous: correct in writing, within the window, every time it matters.
Read the full answerBy convention the consultant chairs and minutes formal progress meetings on consultant-administered contracts, while the main contractor records its own coordination meetings. Whoever does not hold the pen should keep their own notes and use the correction mechanism — routinely, not only when something looks bad.
Usually not: formal notice and instruction requirements are separate, and are often directed to a named person in a specified form. But courts have in some circumstances given signed minutes and progress reports contractual effect, so neither side should assume minutes are inert. Treat a directive line in minutes as a trigger to request — or issue — the formal document.
Read the full answerAttendance with roles and authority. Decisions. Instructions given. Actions with owners and deadlines. Carry-forward items with their original dates. And precise records of any acknowledged delay or impact. Leave out editorial commentary and verbatim debate — neither helps, and both dilute the parts that do.
Owners, deadlines, automatic carry-forward, and a review of open items as the first agenda point rather than the last. Actions without owners have completion rates that embarrass everyone involved, which is why the owner column is not optional.
Read the full answerRelated answers
Terms defined here
Zepth is the construction project delivery platform — it runs construction, procurement and asset management on one record, and does the work: reading the drawings, reviewing the submittals, matching the invoices and flagging the risks, with a human sign-off on anything consequential.
A short, tailored walkthrough on your real workflow — no generic demo.