Heavily amended contracts produce a particular kind of payment dispute. Both sides have been operating what they believe the mechanism to be, the practice has settled into a rhythm, and the document says something different from the rhythm. Unpicking that is the usual starting point for a payment and pay less notice review on this kind of contract.
The problem is not that the amendments are unfair. It is that nobody running the project day to day has read them as a mechanism, so the project operates on an assumption drawn from the standard form.
How the gap between practice and document opens
The amendments are negotiated by people who will not run the project, under time pressure, as part of a wider commercial settlement. They are then handed to a commercial team who inherit a signed contract and a start date.
That team operates the mechanism they know. Applications go in on the usual day, assessments follow in the usual week, notices are served in the usual form, and for as long as nothing is contested nobody checks.
The gap only becomes visible when a figure is refused. At that point the document reasserts itself and eighteen months of practice turns out to have no contractual basis.
Both parties are usually surprised. This is rarely a case of one side exploiting a drafting advantage; more often neither side knew what they had signed up to operate, and both discover it in the same week.
What gets amended and what it does
Payment periods, which move every deadline that follows them. Notice periods, which compress assessment. Conditions on applications, which can determine whether a cycle has started. And definitions, which change clauses without touching them.
Individually each is a small change. Together they can produce a timetable that looks nothing like the printed form, and one that is sometimes impractical to operate as written.
Where the timetable is impractical, that is worth identifying early. A mechanism that requires an assessment to be completed over a bank holiday weekend will fail eventually, and knowing that in advance allows it to be managed.
Managing it usually means starting earlier rather than negotiating a change. Once the contract is signed the timetable is what it is, and the only variable left is when you begin.
Reading the amendments as a timetable
The useful method is not to read the amendment schedule as prose but to rebuild the payment timetable from it: due date, payment notice deadline, pay less deadline, final date, with the actual periods.
Compare that with the standard form and the differences appear immediately. Compare it with what has actually been happening on the project and the exposure appears too.
Half a day of that work at the start of a project prevents most of these disputes, and almost nobody does it.
The same exercise is worth repeating whenever the contract is varied during the works, since a variation to the payment terms moves the timetable just as effectively as an amendment agreed at the outset.
The argument that follows
Disputes on amended contracts tend to be about validity rather than value. Was this a notice. Was it in time. Did the application start the cycle. Did the deduction need notifying in a particular way.
Those questions are answered from documents and dates rather than from measurement, which makes them quick to resolve and uncomfortable to lose. There is no second argument available once the dates are established.
They also tend to be decided on the first cycle examined, because the same practice was followed every month. A single procedural failure repeated twelve times is twelve failures.
That cuts both ways, which is worth remembering before taking a point. A party relying on the other side’s procedural failure may be relying on a practice both of them followed.
What to do when you are already in one
Establish the actual mechanism first, from the contract rather than from anybody’s description of it. Then build the dates for the cycles in question and compare them with what was done.
That produces a position quickly, and it frequently produces an uncomfortable one. Finding that your own practice was non compliant is better established privately than in correspondence.
Where the position is weak, the sensible response is usually to correct the practice immediately and deal with the historic cycles commercially rather than defending a procedure that cannot be defended.
Preventing the next one
At tender, read the payment amendments as carefully as the risk transfer provisions. They will be used every month on every package for the life of the contract, which is more often than most of the clauses people negotiate hard over.
Price them if they are onerous, qualify them if that is open to you, and if neither is possible, at least arrive at the project knowing what you have agreed to operate every month.
That reading belongs to tendering and procurement, and it is the cheapest point at which any of this can be dealt with.
Carrying it into the project
Once signed, the amendments stop being a legal document and become an operating manual. The timetable should be built, circulated and used by the people serving the notices.
Where staff change, the timetable should be handed over with the project, because practice travels with people and documents do not. A handover that covers the commercial position but not the payment mechanism leaves the new person operating on assumption.
Where something has already gone wrong, establishing the position before stating one is the cheap step. An initial dispute review answers whether the mechanism was operated correctly, which on an amended contract is frequently the whole question.
Money held back on a payment cycle?
A payment and pay less notice review examines one cycle end to end: the application, the notices, the dates and what the contract actually required of each party.