Skip to content
ELFBRIX

Subcontractor payment claim checks

Never pay for work that isn't done, and never miss a response deadline. Every sub's claim is checked against their contract and what's actually on site.

ELFBRIX elf handling subcontractor payment claim checks for construction

Hours back

3

hours a week back, typically

How it runs

What we build, step by step.

This is the usual shape. Yours gets built around how your team actually does the job.

  1. 01

    Claims logged as they land

    Each sub's claim is pulled from email and logged with the date received and the date your response is due.

  2. 02

    Checked against the contract

    Every line is compared with the subcontract breakdown, approved variations and what's already been paid.

  3. 03

    Checked against the site

    The percentage claimed is compared with the latest daily reports and photos, and any gap is flagged.

  4. 04

    Paperwork chased

    Missing statutory declarations, payment statements or insurance certificates are requested before the claim can be paid.

  5. 05

    Response drafted

    A draft payment schedule with each adjustment and the reason for it, for the PM to check and send.

Runs inOutlookProcoreCompanyCamGmailGoogle Sheets

Shown with software we see a lot. If your team uses something else, we build it into that instead.

Built for your business

Same job, different business. We build yours.

Two firms in the same trade rarely run a job the same way. Different software, different steps, different people signing off. We build it for your business, around how your team actually does the job.

  • Your steps

    Built around the order your team already works in, odd exceptions included.

  • Your software

    Runs inside the tools you already pay for, set up the way you use them.

  • Your rules

    Your wording, your limits, your sign-offs. Nothing generic goes out in your name.

You sign off

Your team keeps the final say.

The project manager approves every amount and signs every payment schedule. It never knocks back a claim on its own.

What it's worth

What those hours add up to.

3 hours a week, over 46 working weeks, is 138 hours a year. At $50 an hour, that’s

$6,900

back in the business, every year.

Typical, not promised.

Before and after

The job, before and after.

How it runs today

Claims land in the PM's inbox at month end. Each one gets checked against the subcontract, the variations register and whatever the site manager remembers, usually late at night. Overclaims slip through, and a claim that sits too long can leave you owing the full amount.

What we build

  • Claims logged as they land
  • Checked against the contract
  • Checked against the site
  • Paperwork chased
  • Response drafted

A month in

Claims are checked within days of landing, overclaims get caught with the photos to back it up, and no response deadline passes by accident.

FAQ

Does it know the payment claim rules where we work?

Yes, once we set it up with the response times that apply to your contracts. It counts down from the day each subcontractor claim lands. Anything disputed still goes to your lawyer.

What if the site manager disagrees with the percentage?

The site manager wins. The claim check shows the gap between what the sub claimed and the site photos, and the site manager or project manager makes the call.

Next step

Bring this one to a free live build.

Thirty minutes on subcontractor payment claim checks. We build its elf with you, live, and you keep it.