You have read half of this contract.

You have read half of this contract

Ask a site team what the contract requires and you get a fluent answer. Complete the works. Provide the security. Submit the programme. Keep the records, run the safety system, take care of the works until handover. Clause 4 is long, and most contractors know it line by line, because somebody audits them against it every week.

Now ask the same team what the employer promised. The room goes quiet, and somebody says “to pay us”.

The contract has a whole clause for the other side. Six sub-clauses in the Red Book, each one a dated, specific duty with a consequence attached — and on most projects nobody's read them, which means nobody notices when one's missed.

Access is a date, not a courtesy

Sub-clause 2.1 turns site handover into a dated duty rather than a favour. The employer has to let you onto every part of the ground and hand over control of it, by whichever date the Contract Data sets. Two separate words doing separate jobs: getting in is one thing, being in charge of what you find is another.

Three things follow that people miss. The right doesn't have to be exclusive — the employer can have others on site alongside you unless the contract says otherwise. Where the employer is handing over an existing foundation or structure, the timing and manner come from the Specification. And the employer may hold access back until the Performance Security has arrived, which makes that piece of paperwork worth chasing on day one rather than week three.

Note where the date lives: the Contract Data. That is the document Week 2 put fourth in the priority stack and told you to read first. This is what it looks like when that advice earns its keep.

The clause that asks whether they can pay

Sub-clause 2.4 is the most under-used protection a contractor has, and it exists because the employer's ability to fund the job isn't something you're expected to take on trust.

The employer's financing arrangements are supposed to be set out in the Contract Data. If the employer intends a material change to them — or has to make one because its own financial position moved — it must give you a notice immediately, with supporting particulars.

And you can ask. Four situations open the door: a single variation instruction priced above ten percent of the Accepted Contract Amount; variations accumulating past thirty percent of it; payment not arriving under sub-clause 14.7; or you becoming aware of a material change that nobody notified. On the million-dollar job in this site, that first threshold is a $100,000 instruction and the second is $300,000 of accumulated change.

Once asked, the employer has twenty-eight days to produce reasonable evidence that funding is in place and being maintained for the part of the price still to be paid.

Assistance, and the papers you cannot get yourself

Sub-clause 2.2 covers the things only the employer can realistically obtain: copies of the country's laws where they are not readily available, and permits, permissions, licences or approvals required by those laws.

This one rarely produces a dispute on its own, and it produces a great many delays. A permit nobody chased isn't a dramatic breach; it's four weeks of a piling rig standing still while two organisations each assume the other is dealing with it. Which is exactly the situation the next clause was written for.

The notice you send before anything goes wrong

Sub-clause 1.9 works differently from everything this track has covered so far, and the difference is the point.

It asks for a notice to the Engineer as soon as a missing drawing or instruction starts to threaten progress — not once harm has been done, but while it is still only probable, and while the reasonable time for issuing the thing has not yet run out. The notice names the document, explains why it matters and when it is needed, and puts a size on the disruption that will follow if it arrives late.

Read the tense. Nothing has gone wrong yet. This is a notice you send while there is still time for somebody to fix the problem, and the best possible outcome is that the drawing arrives and the notice never matters again.

Compare it with Week 1's notice of claim, which is entirely retrospective: an event happened, and you have twenty-eight days to protect the money. One preserves a right after the damage. The other tries to prevent the damage. The second is cheaper, quicker to write, and far less often sent.

What happens when they do not deliver

Obligations without consequences are wishes, so it is worth knowing where the escalation actually goes.

Sub-clause 16.1 lets the contractor suspend work, or slow it down, where the employer fails on financial arrangements, fails to pay under 14.7, or fails to comply with a binding agreement, a final and binding determination under 3.7, or a DAAB decision — provided the failure amounts to a material breach.

The route is deliberately slow. You give a notice, and the notice must state that it is given under 16.1 — the same labelling rule sub-clause 1.3 imposed in Week 1. Then not less than twenty-one days pass. Only then may you suspend, and only until the default is put right.

This is a serious step and it isn't the first move in a payment argument. But knowing the ladder exists changes how the earlier conversations go, because everybody in the room can count to twenty-one.

Practical insight

Build the other list. It takes an afternoon and almost nobody has one.

Go through Clause 2 and sub-clause 1.9 and write down every employer duty with three columns beside it: what is promised, when it is due, and where the date came from. Most of the dates will come from the Contract Data, and any blank you find there is worth raising now rather than in month seven.

Then put the access dates on the programme as constraints rather than assumptions. If your Schedule Week 11 logic says piling starts on a date the employer has not committed to, your programme is telling you something the contract doesn't support.

Keep a live list of drawings and instructions you are waiting on, with the date each becomes critical. That list is the raw material for a 1.9 notice, and if you maintain it honestly you'll send fewer claims later.

And check one thing today: does anybody on your team know what the Contract Data says about the employer's financing? On most projects the honest answer's no, and it is the first question worth having an answer to when a large variation lands.

Key takeaways

✔ The contract is two lists. Contractors know Clause 4 by heart and often haven't read Clause 2 at all.

✔ Sub-clause 2.1 makes access and possession a dated obligation, with the date in the Contract Data — and it need not be exclusive to you.

✔ The employer may withhold access until the Performance Security is received, which makes that a day-one task.

✔ Sub-clause 2.4 requires the employer's financing to be detailed in the Contract Data, and a material change to be notified immediately.

✔ Four triggers let you request evidence of funding — a variation over ten percent, accumulated variations over thirty, non-payment, or an unnotified change. The employer then has twenty-eight days.

✔ Sub-clause 1.9 is forward-looking: it is sent when a missing drawing is likely to cause delay, and it says what, why, by when, and how much.

✔ Sub-clause 16.1 allows suspension after a notice that identifies itself as such, and not less than twenty-one days — but only for a material breach.

What's coming next

Obligations tell you what each side owes. Instructions are how one side changes what the other is doing, and that is where the money starts moving. The problem is that a great deal of what arrives on site looks like an instruction and is not one: a comment on a drawing, an email from somebody without authority, a verbal direction at a Thursday walkround, a marked-up sketch handed over at the tea hut. Next week we look at what actually counts as an instruction under the contract, who is allowed to give one, and what to do with the ones that do not qualify.