Substantiation is revenue — what every unbacked claim line costs you on a Tier 1 job

Your crew worked a 10-hour shift on Tuesday. You paid them for it on Thursday — every hour, at the right rate, because Fair Work doesn't wait for anyone to certify anything. Three weeks later the head contractor's certifier looks at that line on your progress claim, can't find a signed docket behind it, and certifies it at zero.

The work happened. The wages are gone. The revenue isn't coming — at least not this month, and maybe not at all.

That's not a paperwork problem. That's the gap between the amount you earned and the amount you actually collect, and on a Tier 1 or government-backed job it's wider than most subcontractors think.

The seat you're in

When you claim up to a Tier 1 head contractor — especially on anything public-sector — you're claiming into a machine built to scrutinise every dollar. Their certifier has reporting obligations of their own. Nothing gets certified on trust. If a line isn't backed at the moment you submit, it doesn't get paid; it gets queried, deferred, or knocked out.

And "approved by default" — the rule that turns a missed certification window into an automatic full approval — protects them, not you. (We covered how that clock works in the Security of Payment piece.) As the claimant, you don't get the benefit of the doubt. You get the burden of proof.

Unsubstantiated revenue doesn't disappear in one clean hit. It leaks four ways, and they stack:

1. Knock-backs. The certifier issues a payment schedule for less than you claimed — a line cut, a variation zeroed, standby time disallowed. Pending evidence you don't have.
2. Deferral. Some of it you can re-claim next period once you've reconstructed the backing. But that's revenue arriving 30 to 60 days late — working capital you're now funding yourself.
3. Permanent loss. The signature you never got on the day. The docket that lived in the ute and is gone. The verbal variation nobody wrote down. You can't reconstruct it, so you write it off.
4. Re-work and relationship cost. The hours your team spends chasing, rebuilding, and re-submitting evidence — and a certifier who starts treating all your claims as suspect because the last three needed correcting.

“

Wages don't wait. Claims do.

For materials and plant, an unpaid line often still sits on supplier terms — the cash hasn't fully left you yet. Labour is different. You've already paid it.

• Wages run weekly or fortnightly. Non-negotiable.
• The matching claim is monthly, then 30–60 day terms, then conditional on substantiation.

So a knocked-back labour line isn't deferred revenue sitting neutral on a ledger. It's cash that left your account weeks ago with nothing coming back to meet it. You've financed the Tier 1's project out of your own payroll. Do that across a few cost codes every month and you're effectively lending money, interest-free, to the contractor above you — without ever deciding to.

A worked example

Illustrative numbers — not benchmarks. Your mix will differ.

A civil subcontractor submits a monthly progress claim of $420,000. The certifier knocks back $35,000 — about 8% of the claim — across three lines: dayworks dockets that weren't signed, a variation claimed before written approval came through, and plant standby with no record of the hours.

Trace that $35k through the four leaks:

The $9k write-off alone is margin you'll never see again — and it's not a one-off. Repeat 8% leakage on a monthly claim across a 12-month job and the permanent losses alone run into six figures, before you count what financing the deferrals cost you.

None of this is because the work wasn't done. It's because the work wasn't backed at the moment it was claimed.

What "substantiated at submission" actually means

The fix isn't more diligent chasing after a knock-back. It's that every line is already backed when you hit submit. For each claimed line, the certifier should be able to pull:

• the signed docket — labour and plant, charged to a cost code, signed by site
• the approved variation — written instruction in hand before it's claimed, not after
• the supplier invoice for materials
• photos and time records for standby, delay, and disruption

Attached at submission. Not promised, not "coming". The certifier has nothing left to query, so there's nothing to defer, write off, or argue.

Where tectm fits

tectm is built so the substantiation exists before the claim does:

• Dockets are priced and signed at capture — contract-aware rates applied on the day the work happened, charged to a budget line, signed off on site. The backing is created when the cost is, not reconstructed at month-end.

That pricing isn't a black box. It's the same 7-step engine you can drive yourself right here — change the rate, the hours, the day, and watch the bands resolve:

• Variations are approved before they're claimable — so a variation can't land on a claim ahead of its written instruction.
• The claim-substantiation engine checks every line against its docket backing before you submit — and flags anything thin while you can still fix it, not after the certifier already has.

The result is the same one the worked example was missing: a claim where every line carries its own evidence, so the certified amount matches the claimed amount, and the cash you've already spent on wages actually comes back.

Substantiation isn't compliance. It's collection. Every line you can back is a line you get paid for — and on a Tier 1 job, that's the whole margin.

Book a demo to see how tectm builds the substantiation packet as you go, so every claim lands fully backed.