A month's money on a construction contract turns on a handful of dates. Not on the quality of the work, not on the strength of the argument, and not on who is right about the valuation. On dates. Most people in the industry know the pay less notice is one of them. Fewer have noticed that their own application is another, and that getting it wrong can leave them with nothing at all.
I say this with some feeling, because the payment regime under the Construction Act is the single most powerful tool a sub-contractor has, and the single most common way I see it wasted is by a business that understands the other side's deadlines perfectly and ignores its own. So here is the timetable, in order, and then a recent decision that shows what happens when both parties treat it as optional.
The timetable, in order
Every payment under a construction contract runs on the same spine. The contract fixes a due date and a final date for payment. Between them sits a sequence of notices, and the Act is precise about who serves what and when.
- The payment notice. The payer, or the person the contract names to do it, must give a payment notice "not later than five days after the payment due date", stating the sum it considers due and the basis on which that sum is calculated. Many contracts instead make the payee's application serve as that notice, which is why the application itself has to be served on time and in the right form.
- The default notice. If the payer's notice is not given when it should be, the Act lets the payee serve its own notice in default, and that notice then fixes the sum. Where the application already stands as the payee's notice, the application does the job.
- The pay less notice. If the payer intends to pay less than the sum notified, it must say so in a pay less notice served not later than a prescribed period before the final date for payment. The period is whatever the contract sets. Several JCT forms use five days. Where the contract is silent, the Scheme provides seven. The notice has to state the sum the payer now considers due and the basis of that calculation.
- The final date for payment. By this date the Act says "the payer must pay the notified sum (to the extent not already paid)". The notified sum is whichever of the above notices last validly fixed it.
That is the whole machine. Four dates, three notices, one sum. Everything else in a payment dispute is commentary.
The missed pay less notice, and the limit of it
The consequence most people know is the one at the end of the chain. If the payer does not serve a valid pay less notice in time, the notified sum stands and must be paid in full by the final date, whatever the payer thinks the work is worth. This is what the industry calls a smash and grab, and an adjudicator will enforce it without looking at the valuation at all, because the Act does not ask them to.
It is worth being clear about what that does and does not achieve. It does not decide what the work was worth. It decides who holds the money while that argument happens. The payer who has missed its notice has to pay first and may then start its own adjudication to establish the true value. Pay now, argue later, as the saying goes. For a sub-contractor that is a very good position to be in, because cash in hand changes every negotiation that follows. It is not a final answer, and anyone who treats a smash and grab as one is going to be surprised by the second adjudication.
Four dates, three notices, one sum. Everything else in a payment dispute is commentary.
When both sides are late, nobody wins
Now the decision, because it cuts the other way. In Liberty Roofing (East Midlands) Ltd v Midleton Developments (Church Street) Ltd, decided in the Technology and Construction Court in Manchester on 27 March 2026 and so far unreported, a roofing sub-contractor and its contractor had a contract based on the JCT Short Form Sub-Contract with a schedule setting specific dates for applications and notices.
For two payment cycles the sub-contractor served its applications late. The contractor then served its payment notices late as well, and served no pay less notices. The sub-contractor adjudicated. The adjudicator accepted that the documents were late, but treated them as fixing the notified sums anyway, and awarded the sub-contractor the amounts in them.
The court refused to enforce the decision. The Act only treats a notice as fixing the notified sum where it is given "pursuant to and in accordance with a requirement of the contract", and a notice served after the contractual date is not. As reported, the court held that the timing of the applications was fundamental to the payment provisions the parties had agreed, and that neither a late application nor a late payment notice can create a notified sum. The sub-contractor's fallback argument, that the parties had carried on as if the late documents were valid and it would be unfair to let the contractor say otherwise, did not succeed either. The test was simply whether the documents had been served in accordance with the contract. They had not. So there was no notified sum, and nothing for the adjudicator to award.
Read that again from the sub-contractor's side. It did the work. The contractor did not pay. The contractor also failed to serve its own notices properly. And the sub-contractor still walked away from the enforcement hearing with nothing, because its own application had been a few days late and, under the schedule it had signed up to, a late application was not an application at all.
Bespoke schedules change the dates
The detail that sank that claim was the schedule of dates. Standard forms set their notice periods by reference to the due date and the final date. A great many sub-contracts, particularly bespoke and heavily amended ones, replace that with a calendar: application by this date, notice by that date, and so on through the year. Where that is done, the calendar is the contract, and the Act's test of whether a notice is valid becomes whether it was served in accordance with those dates.
That has a practical consequence that is easy to miss. A sub-contractor who is used to applying "about the end of the month" is, under a schedule, applying late every time it misses the stated day. It may get away with it for cycle after cycle because the payer carries on paying. Then one month the payer stops, the sub-contractor reaches for the Act, and discovers that it has nothing to reach with. Read the schedule before you sign it. Diarise every date on it. Treat the application date as a hard date, because the court will.
Form, not just time
Time is the first requirement. Content is the second. A payment notice and a pay less notice each have to state the sum the server considers due and the basis on which it has been calculated. The courts have tended to look at substance over form and to read a notice as a reasonable recipient would, which helps a party whose notice is imperfect but clear. It does not help a party whose notice is missing, or late, or sent to the wrong person. Nor does it rescue an application that is really an invoice with a number on it and no indication of how the number was reached.
So the application needs the sum, the basis, the right addressee, and the contractual form, on the contractual date. Get those four things right every month and the regime works for you. Miss any of them and you are relying on the payer being more careless than you are, which is not a strategy.
The sub-contractor did the work, the contractor did not pay and served nothing in time, and the sub-contractor still walked away with nothing. Its own application was late.
What good looks like
The businesses that get paid on time and win the arguments when they do not have a short list of habits:
- They map the payment timetable for every contract at the start: due dates, application dates if scheduled, payment notice dates, pay less dates, final dates. Then they diarise all of them.
- They treat their own application date as a deadline, not a target, and they serve in the form and to the person the contract names.
- Every application states the sum and shows the basis of calculation, so it can stand as a notice if the payer serves nothing.
- They check, on the day, whether a payment notice and a pay less notice have arrived, and whether each is valid in time and content.
- Where the payer has missed a notice, they act on it promptly rather than letting the next cycle muddy the position.
- They keep every notice, every application and every date in one place, so the file tells the story without anyone having to reconstruct it.
None of this is difficult. It is the discipline of serving the right document on the right day, every month, when nothing seems to be going wrong. The month something does go wrong is the month that discipline pays for itself.
The dates are the whole game
The payment regime is the fairest piece of construction law we have. It gives a sub-contractor a mechanism that does not care how big the other party is or how good its lawyers are. It cares about dates and documents. That is its strength, and it is also the catch: it holds you to exactly the same standard it holds them to. Serve on time, in form, every month, and the Act is on your side. Serve late and you may find, as a roofing contractor found in Manchester this year, that the Act is not on anybody's side at all.
This is the timetable Defender Platform is built around. It reads the payment provisions and any schedule of dates in your contract, puts every application, notice and final date on one calendar, and tells you the day a notice is due or the day one has not arrived. Software or a wall planner, the rule does not change: the dates are the whole game.