The deadline passes. Concrete gets poured, the prestart runs on time, and nothing on site signals that anything has changed. Legally, though, the position shifted the moment the window closed. A payment claim that goes unanswered converts into a debt, and every offence available the day before is gone the day after.
Security of Payment deadlines do not announce themselves. There is no alarm, no site notice, no line in the daily report. Teams that know this respond correctly. Teams that discover it after the fact are already managing consequences.
What follows maps four failure modes that compound under Australian Security of Payment legislation. Each one is survivable alone. They rarely arrive alone.
Failure Mode 1: The Clock That Starts on Its Own
In New South Wales, a respondent has up to 10 business days to serve a payment schedule. In Queensland, the window is up to 15 business days. Those periods are the statutory maximums. A contract can set a shorter period, but it can never set a longer one. Miss either deadline and the full claimed amount converts from a disputed claim into a statutory debt.
Every offence closes with that deadline. Backcharges, defects, set-offs: all become unavailable once the period expires without a response. Recent NSW authority confirms the statutory limit runs from actual service of the claim, and a contractual deeming provision cannot extend it.
From that point, the contractor can file the amount as a judgment debt and suspend works after proper notice. Interest accrues on the unpaid amount in the meantime. The respondent is no longer disputing a claim; they are trying to recover money already treated as owing.
Most project teams find out through a letter or an adjudication application two to three weeks later. In several cases that have gone to lawyers, that letter was the first time anyone at a senior level knew a claim had been received.
The statutory framework is structured so that the respondent pays first and disputes later, at their own cost. That sequencing is deliberate, and it holds regardless of whether the claim was unexpected or the relationship seemed cooperative.
Failure Mode 2: The Claim That Looks Like Paper
Payment claims regularly arrive at a general inbox, projects@ or admin@, alongside a concrete docket and a toolbox talk reminder. The subject line reads Progress Claim 14, or simply Invoice attached. Nothing in the presentation signals a statutory consequence.
The person who opens that email is working through a full inbox on a busy day. The claim looks like routine correspondence, and that is precisely where the risk sits.
There is a second layer. The contract usually specifies where and how a claim must be served, and the contractor does not always follow that method.
Before the deadline can even be argued, there may be a dispute over whether the clock started at all. That preliminary argument alone has cost more than the underlying claim on projects I have seen reach a lawyer.
Failure Mode 3: The NSW to Queensland Border Crossing
The timing difference between the two states is what most practitioners know first. In practice, it is also the least dangerous distinction. Three other differences catch experienced people who cross the border carrying habits built in the wrong jurisdiction.
1. Any invoice can be a payment claim
In Queensland, a payment claim no longer needs to state that it is made under the Act. Any written request for payment can start the clock, with no specific wording required. Practitioners who learned the process in NSW often wait for language that never appears. By the time they realise it, the clock has already started.
2. NSW provides a secondary window. Queensland does not.
In NSW, missing the schedule is not immediately fatal. The contractor must first serve a notice of intention to apply for adjudication, which gives the respondent five business days to lodge a late schedule.
In Queensland, no such window exists. A missed schedule makes the respondent immediately liable for the entire claimed amount as a payable debt, with minimal grounds for dispute.
3. Failing to respond is a separate statutory offence in Queensland
In Queensland, failing to lodge a payment schedule is an offence under the Building Industry Fairness Act. The respondent can be fined for not responding, separately from owing the claimed amount.
Both states share the same broad legislative intent. The mechanics differ enough that assuming consistency between them is a reliable way to make the wrong call. Experienced practitioners are more exposed here than beginners, because they have enough confidence in their existing habits to stop verifying the rules before applying them.
Failure Mode 4: The Schedule That Won the Deadline and Lost the Adjudication
Serving a payment schedule within the deadline resolves only part of the problem. At adjudication, the respondent is confined to the reasons stated in that schedule. Grounds known at the time but omitted from the schedule are not available later.
Defects the site team identified, backcharges in preparation, liquidated damages being calculated: if none of those appear in the schedule, the adjudicator will not consider them. The rule is codified, with no discretion.
Every valid ground should be included at the outset: scope disputes, defects, rates, quantities, contractual time bars. The schedule sets the ceiling on what can be argued at adjudication. Anything omitted from it is permanently unavailable in that proceeding.
A deficient schedule has a recognisable profile. It is issued on day nine of a ten-day window, written by whoever was available that evening. The scheduled amount sits below the claim without detailed justification. The reasons read: Amount not substantiated. Works incomplete. Rates not agreed. Generic language, often copied from the previous month.
There is no item-by-item breakdown, no clause reference, no supporting calculation. Adjudicators routinely give no weight to reasons framed as under assessment or on account without supporting figures.
A schedule written that way stops the automatic debt conversion, but it does not survive adjudication. When the contractor submits forty pages of measured quantities and the respondent's schedule offers three sentences of generic reasoning, the outcome is rarely in doubt.
The practical standard is to write the schedule with adjudication already in mind. Every reason should be specific enough to develop into a substantive argument if the matter proceeds. A schedule prepared under time pressure with no supporting detail will stop the debt, but it will not hold at the next stage.
The Excuse That Does Not Hold
When lawyers eventually become involved, the account from the respondent's side tends to follow the same outline: conversations were ongoing, the relationship was good, both sides were working through it, and the contractor knew there were issues with the claim.
None of that appears in the statutory process. The legislation operates on documents that were served, not on phone calls, site meetings, or email threads that did not constitute a formal response.
On the other side, the contractor's commercial team may be engaged in exactly those conversations while their contracts team separately counts down the response period. The two tracks do not necessarily share information, and the deadline runs regardless of what is happening in the relationship.
What the respondent said in those conversations and what they actually served in response are two separate records. In nearly every case that has gone badly, the spoken record was extensive and the served record was empty.
A second common excuse runs the other way: the claim was inflated, rates were doubled up, items were claimed twice, so it would not survive scrutiny and did not need a formal response.
That reasoning inverts the actual risk. Case law confirms that even imperfect or overstated claims carry full statutory consequences if left unanswered. The amount that goes unscheduled is the amount that converts into a debt. An inflated claim left without a response becomes an inflated debt. The correct response to a poorly substantiated claim is to answer it quickly and in detail.
The Fix, and Why It Keeps Failing
The structural answer is straightforward. One named person owns the claims mailbox, with a named deputy to cover leave. When a claim arrives, the response date is recorded somewhere the whole team can see, treated with the same discipline as a concrete pour booking.
Open claims belong on the project meeting agenda. Thirty seconds is enough: what is open, who holds it, when it falls due. A whiteboard in the site office handles this without any software.
Where the arrangement degrades is in maintenance, not setup. In week one, the register is clean. By week six, a pour cycle is running, two people are on leave, a redesign is moving through the engineer's office, and the register has not been updated in nine days.
No one decided to stop. The register was displaced every day by something with a more immediate visible consequence. Sites reward production. A claims register updated on a Friday generates no visible result and earns no recognition.
Feedback from a missed SOPA deadline arrives months later, sometimes more than a year after the event. By then, the people responsible may no longer be on the project, and the connection between the original lapse and the current cost is too distant to drive any behavioural change.
The register also tends to live in one person's spreadsheet. When that person resigns, the system goes with them. Process knowledge and open-claim tracking do not transfer automatically to the next person.
The discipline needs to be embedded in a process that continues regardless of who is carrying it on any given week. A system that depends on individual consistency will eventually meet a week where that consistency is unavailable, and on a live construction site, that week arrives regularly.
What This Means for Your Next Claim Cycle
Each of the four failure modes shares one characteristic: the cost on the day is zero, and the cost months later can be substantial. Around 70% of Australian construction companies report late payments each year, and the average dispute value reached AU$33 million in 2022. A missed deadline with no immediate signal is not a missed deadline with no consequence.
The fix itself is not complicated. What makes it difficult is durability. A system built around named individuals and visible deadlines holds until the named individual is tired, absent, or off the project. On a live site, that situation arises regularly.
Based on projects where this has gone wrong, the starting position I would take is: assign the mailbox to a named person and a named deputy, publish the response date to the whole team the day a claim arrives, and put open claims on the weekly agenda before the next claim lands. Beyond that, the industry needs a monitoring arrangement that tracks deadlines independently of individual capacity. Building a register durable enough to survive staff turnover and a heavy pour week is the work that determines whether these four failure modes remain a recurring problem or a manageable one.
Alexios Kavallaris is the founder of Gnosis, a contract administration platform built for civil engineers working under AS 4000 and NZS 3910. He has spent 27 years in civil infrastructure across Greece, England, New Zealand and Australia, including eight years on New Zealand's Waikato Expressway programme, and is a 2020 Engineering Science Award recipient (KuDos).