The application served too early

Payment under a construction contract runs on a cycle. Each period has a due date, and the statutory clock for notices runs from that due date. An application for payment has to sit within that structure. If it does not, the timing failure can be as damaging as a missing figure.

The application belongs to a period

Every application relates to a particular payment period and the due date for that period. It is a claim for the value of work up to a valuation point, put forward so that it becomes the notified sum for that cycle. That link between the document and the period is what gives the application its effect.

Break the link and the effect goes with it. An application that does not clearly attach to a period, or attaches to the wrong one, is not doing the job the payment mechanism expects of it.

Served too early

An application served before the period it relates to has begun, or before the point in the cycle the contract allows, can be ineffective. If it is premature it may not trigger the payment mechanism at all, in which case no notified sum arises from it. The contractor is left thinking a claim is running when nothing is.

The safer reading in some cases is that a premature application does not simply vanish but takes effect in the next cycle, once the period it should have addressed comes round. Either way the contractor loses the timing it wanted. The sum it expected to be payable now is not payable now.

The wrong date

A misdated application carries the same risk. If the document points at a due date that does not match the cycle, the recipient cannot tell which period is in play, and the mechanism cannot attach the claim to the right point. The result is the same family of outcomes: no notified sum, or a notified sum a cycle later than the contractor intended.

The document has to name its period

Because so much turns on the period, the application has to make plain which one it covers. A reasonable recipient should be able to read the document and know, without guessing, the period it relates to and the due date it is aligned with. Ambiguity here is not a small defect. It goes to whether the document works at all.

The Technology and Construction Court has dealt with timing and validity disputes of this kind, and the direction of travel is consistent: a document that leaves the recipient unsure which period it addresses is on weak ground. The principle is more useful than any single set of facts. Say which period the application covers, and align it with the correct due date.

Counting from the due date, not the valuation

A related trap sits in the arithmetic of the cycle. The statutory payment days run from the due date, not from the date the work was valued. It is easy to slip into counting from the valuation date because that is the date the surveyor is working to, but the Act ties the notice deadlines and the final date for payment to the due date.

Count from the valuation and every downstream date drifts. The payment notice deadline moves, the pay-less deadline moves, and the final date for payment moves with them. An application built on the wrong anchor puts the whole cycle out of step even when the application itself is served on time.

The check before it goes in

• Has the period this application relates to actually begun?
• Does the document state which period it covers, without ambiguity?
• Is it aligned with the correct due date for that period?
• Are the downstream dates counted from the due date, not the valuation date?

If all four hold, the application is anchored where it should be and the notified sum it claims can arise in the cycle intended. If the first or third fails, the claim may be ineffective now, or may only bite a period later.

Why the discipline is worth it

The payment cycle is unforgiving about timing precisely because so much depends on it. An application is a claim to a sum that becomes payable on a defined date, and that only works if the document sits in the right period against the right due date. Serve it early or misdate it and the contractor risks discovering, too late, that the cycle it was counting on never started.