12 · Progress Claims

Get paid for what you have actually built.

Raise interim payment certificates straight from measured progress — previous, this period and cumulative — with retention, advance recovery and approved variations handled, and every claim gated and branded before it leaves the building.

From progress to certificate

The IPC, without the spreadsheet.

Progress is measured against the WBS, the claim is built from that measurement, and the numbers carry straight through to certification.

Measure progressProgress is recorded against the WBS — percentage, quantity or milestone — by the people who did the work, not re-estimated later.

→

Draft the claimThe claim assembles itself from that measurement: previous, this period and cumulative on every line, in the format your QS expects.

→

ApproveThe claim goes through the approval rule for its value. Nothing moves until the signatures are in, and the numbers freeze as approved.

→

Certify & issueRetention, advance recovery and approved variations are applied on the certificate, it issues on your letterhead, and the ERP receives the change-set.

📑

Previous / this / cumulative

Every line shows what was claimed before, what is claimed now, and the running total — the format your QS expects.

💰

Retention & advance

Retention held and released, advance payment recovered — calculated on the certificate, not on the side.

🔄

Variations included

Approved variations flow into the claim so the contract value always reconciles.

Controlled, like everything else

Gated, versioned, branded.

A claim is a controlled document: it needs approval before issue, it freezes on submission, and the certificate carries your identity.

✅

Gated approval

Role-based approval before a claim can be certified or sent.

📄

Branded certificate

Your logo, entity details and TRN on every issued document.

📜

Full history

Every revision of every claim, kept and comparable.

IPC built from measured progressThe claim is generated from what was actually measured against the WBS, so the certificate and the site record can never drift apart.
Retention, advance recovery and variationsRetention held and released, advance payment recovered, approved variations folded in — all calculated on the certificate, not on the side.
Gated approval before issueNothing reaches the client until the right people have signed. The approval is recorded against the claim, with the numbers frozen as approved.
Branded, traceable certificateIt issues on your letterhead with your entity details, and every line traces back to the measurement and the contract value it came from.
Writes back to the ERP on completionOnce certified, the revenue and receivable go to the ERP as a change-set. BuildOrch prepares and approves; the ERP transacts.