A progress claim is the single document that decides whether a construction subcontractor gets paid this month or waits another six weeks for an adjudicator to sort it out. In New South Wales, Queensland, Victoria and every other Australian state, security of payment legislation gives subcontractors and head contractors a fast, structured pathway to get progress claims paid, provided the claim itself is drafted correctly. Get the reference date wrong, leave out the statutory notice wording, or submit unsupported variations, and a claim that should have been paid inside 15 business days ends up stuck in an adjudication process that costs both sides time and legal fees. For a mid-sized Sydney fit-out contractor running six live sites, that delay is not an abstract risk. It is $180,000 sitting in accounts receivable while the bank asks when the next payroll run clears.
Why progress claims trip up construction businesses
Most disputes over progress claims in Australia do not come down to whether the work was actually done. They come down to paperwork. The Building and Construction Industry Security of Payment Act 1999 (NSW) and its interstate equivalents set out specific requirements for what counts as a valid payment claim: it has to identify the construction work, state the amount claimed, and in most jurisdictions include a statement that it is made under the relevant Act. Miss that statement and a respondent can argue the claim never triggered the statutory timeframe at all, resetting the clock and buying weeks of delay. Add in variations that are not clearly tied to an approved instruction, reference dates that do not match the payment schedule in the head contract, or supporting documents that arrive in a separate email three days later, and what should be a routine monthly claim turns into a dispute an adjudicator has to untangle. None of this requires bad faith on either side. It is simply hard to keep fifteen or twenty active contracts consistent when claims are drafted by whoever has ten minutes free on a Friday afternoon.
Missing or incorrect statutory notice wording required under the applicable Security of Payment Act
Reference date that does not align with the payment schedule set out in the head contract
Variations claimed without a clear link to an approved instruction or scope change
Supporting documentation such as photos, timesheets and delivery dockets sent separately instead of attached to the claim itself
Claim served on the wrong entity or address, which can invalidate the statutory notice entirely
How Claude helps draft SOPA-aware progress claims
This is a drafting and consistency problem before it is a legal one, and it is exactly the kind of task Claude handles well once it is set up properly. We build the workflow around the contract itself: the head contract, the variations register and the payment schedule template all go into a project Claude has access to, so every claim it drafts references the correct clause numbers, the correct statutory wording for the state the project sits in, and the correct reference date. Claude pulls together line items from timesheets and delivery dockets, matches them against approved variations, and flags anything that is not yet backed by a signed instruction before the claim goes out, rather than after a respondent disputes the payment schedule. For a Brisbane civil contractor we set this up for, claim drafting time per site dropped from roughly two hours to twenty minutes, and the rate of claims disputed purely on drafting grounds fell close to zero over the following quarter.
In practice the setup takes a few sessions. We import twelve months of existing progress claims so Claude can learn the head contractor's preferred format and the specific quirks of each contract before it drafts anything new. From there, each new claim starts as a structured brief covering site name, claim period, works completed and variations to include, and Claude turns that into a claim document with the correct statutory notice, an itemised scope, and a one-page supporting evidence summary attached. Nothing goes out without a human sign-off; the aim is to remove the blank-page problem and the risk of a missed clause, not to automate away the judgement call on what to claim. Builders and subcontractors across Sydney, Melbourne and regional Queensland are all working under slightly different variants of the same security of payment framework, so the underlying legislation reference has to be swapped per state, and Claude keeps that mapped against each project's jurisdiction automatically.
What accurate claims are worth
The commercial case is straightforward once you put a number on adjudication. A contested progress claim that goes to adjudication under a state Security of Payment Act typically costs each party somewhere between $3,000 and $15,000 in adjudicator fees and legal input, on top of the working capital tied up while the dispute runs. A construction business issuing forty progress claims a year that gets even three of those disputed purely on drafting technicalities is looking at $20,000 to $45,000 in avoidable costs, before counting the cash flow hit of payment sitting six to eight weeks longer than it should. Getting the claim right the first time is cheaper than winning the argument about it later, and it is far cheaper than writing off variations because nobody can reconstruct the paperwork trail three months after the work was done.
If progress claims are eating more admin time than the actual construction work, we can set up a Claude-based drafting workflow against your existing contract templates in about two weeks. Book a session to walk through how a Claude-first progress claims process would work for your NSW, Victorian or Queensland projects.
