Every clock in this contract is somebody's Tuesday.

Every clock in this contract is somebody's Tuesday

Twenty weeks of clauses, and the one thing never assembled is the calendar.

Every obligation in this track happens on a date or inside a window. They sit in the conditions in the order a lawyer would organise them, which is not the order they arrive in. Put them back into time, and the year has a shape that is a great deal easier to manage than the book is to read.

It also makes something obvious. Jobs rarely lose money on the difficult decisions. They lose it on periods that expired while everybody was busy.

The month before anybody builds anything

Three contractual deadlines land inside the first four weeks, and not one of them involves construction.

The performance security is due within twenty-eight days of the letter of acceptance. Week 5 noted the sting that sits in sub-clause 2.1: the employer may withhold access to the site until that security has been received. A delay in a bank's paperwork becomes a delay to the works, and it belongs entirely to the contractor.

The DAAB members are appointed jointly within the period the Contract Data states — twenty-eight days from the same letter if it states nothing. Week 18 made the point that on most projects this never happens: the period passes, and nobody notices it existed.

The initial programme goes in within twenty-eight days of the commencement notice, prepared in the software the Specification names, carrying everything Week 11 listed.

And one task with no deadline at all: reading the Contract Data. It is the highest-value hour of the job, it sets most of the numbers above, and nothing in the contract requires anybody to open it.

What recurs

Then the job settles, and two cycles run alongside each other.

The monthly one is payment. A statement after each period, an interim certificate within twenty-eight days, the money within fifty-six — and, as Week 12 established, both clocks run from the day the Engineer receives the statement, not from the day the certificate is issued. The second period contains the first rather than following it, so a slow certificate buys the employer nothing.

The second cycle is the programme, and it is event-driven rather than calendared. A revised programme falls due whenever the current one stops reflecting actual progress or becomes inconsistent with the contractor's obligations. The Engineer then has twenty-one days to respond to an initial programme and fourteen to a revision, and silence in either window is a deemed no-objection.

That cuts both ways. A programme nobody objected to is the Programme, and the employer's people are entitled to rely on it — including the revision submitted quietly to paper over a slip.

The clock nobody starts

Then there is a third cycle, and it has no rhythm at all.

Every time something happens that might carry time or money, a twenty-eight day period starts. The fully detailed claim falls due eighty-four days after the same moment, not eighty-four days after the notice — so a notice served on day twenty-seven leaves fifty-seven days for the rest of it, not another twelve weeks.

Both run from awareness: the day the party became aware, or should have become aware. Week 10 spent an article on what that second half does to a start date nobody wrote down.

This is the cycle that empties margins, because nothing external triggers it. The statement is prompted by the month ending. The revised programme is prompted by the Engineer asking. Nothing whatsoever arrives to tell you that a twenty-eight day clock started on a wet Tuesday in March.

The end that arrives twice

Completion is not one date either, and the tail is longer than most teams staff for.

The application for the taking-over certificate can go in up to fourteen days ahead of the date the contractor judges the works ready for handover. The certificate itself releases the first half of the retention from Week 15.

Within eighty-four days of the date of completion, the statement at completion is due with its supporting documents.

Then the defects notification period runs — a year, typically — and within twenty-eight days of the last of those periods expiring, the performance certificate is issued. That releases the second half of the retention, and the performance security itself comes back within twenty-one days of the same certificate.

And within fifty-six days of that certificate, the draft final statement.

Read those last two together. The document that closes the money falls due about a year after the site emptied, on a job whose team dispersed at handover.

What twenty weeks reduces to

A track this long risks leaving the impression that contract administration is a specialism. It is not. Four documents carry most of it, and every one of them fits on a page.

The clock list from Week 10: the periods that end a right, the ones that run in the contractor's favour, and the rest that are only procedure. Pinned somewhere people can see it.

The blanks sweep from Week 15: every empty field in the Contract Data, and what the conditions do instead. Some switch a mechanism off entirely; some substitute a default nobody chose.

The three names from Week 6, and the address from Week 1. Who is allowed to instruct, and where a notice actually has to arrive before it is a notice.

And the other side's list from Week 5: every employer obligation, its date, and the document that date came from.

Where this track started

Week 1 opened on a rock worth $48,450, a clause that said the ground was the employer's risk, and a contractor who paid for it anyway — because a site engineer sent an email that was never a notice, and nobody counted the days.

Everything since has been the machinery around that single failure. Which provision governs, who may instruct, what a notice must say and where it must go, how long there is, what records make an entitlement provable, and who decides.

The net margin on that job was $48,163. One unwritten letter cost more than the entire profit, and none of the engineering was wrong.

That is the argument of this track, and it survives any change of contract form. Being right is not the job. Staying entitled is.

Practical insight

Build the calendar for the job you are on now, in whatever tool your team already opens every day.

Start with the fixed dates: security, DAAB, initial programme, first statement. On a running job most of them have passed, which is itself worth knowing — an unappointed DAAB is a gap, not a non-event.

Then add the recurring rows: statement, certificate, payment, and the review window that opens every time you submit a revised programme.

Then the tail, now, even though it feels absurdly early. Taking over, the eighty-four days to the statement at completion, the defects period expiry, the performance certificate, the fifty-six days to the draft final statement, both retention releases and the return of your bonds. The people who would have remembered will have gone.

And add one weekly item that is not a date at all: is there anything open that we became aware of, or should have become aware of, more than three weeks ago? That single question is the difference between the contract working for you and the contract simply happening to you.

Key takeaways

✔ Three deadlines land in the first month — performance security, DAAB appointment and initial programme — before anybody has built anything.

✔ Access to the site can be withheld until the performance security arrives, so treat a banking delay as a construction delay you own.

✔ Diarise payment as one clock, not two: certificate at twenty-eight days, money at fifty-six, both counted from the day the Engineer receives the statement.

✔ The programme cycle is event-driven, and the Engineer's silence — twenty-one days on the initial, fourteen on a revision — is a deemed no-objection.

✔ Watch the third cycle yourself, because nothing triggers it: the twenty-eight days and the eighty-four both run from awareness, not from the notice you served.

✔ Put the tail in the calendar on day one: eighty-four days to the statement at completion, the defects period, then twenty-eight and fifty-six days to the performance certificate and the draft final statement.

✔ Keep four pages on the desk: the clock list, the blanks sweep, the three names and the address, and the other side's obligations.

What's coming next

Track 4 ends here. You can find the provision that governs, serve a notice that survives, keep records that make an entitlement provable rather than arguable, and follow the money from application to bank account. What none of that tells you is what the entitlement is worth. Track 5 is Claims & Delay Analysis, and it starts exactly where this one stops: a preserved right, a programme that can be re-run, and the question this track has deliberately never answered — how much?