Subcontractors track progress claims by keeping four records connected: the contract scope (the BOQ), measured physical progress against that scope, the cumulative amount claimed to date, and the amount the client has actually certified. A progress claim — also called a payment application or interim application — is the periodic statement of the value of work completed. Tracking it properly means being able to show, for any line of the contract, how much was executed, how much was claimed, and how much was certified — and to explain every difference between those three numbers.
The terms, untangled
Progress claim, payment application, interim application — different names for the same document: the periodic statement of the value of work executed, submitted to the client or main contractor for payment. The name varies by region and contract form; the mechanics do not.
Payment certificate — the response. The client or their quantity surveyor reviews the claim and certifies the value they accept for payment. It is rarely equal to the claim.
Cumulative and period values — claims are normally cumulative: the total value of work done to date, minus what was previously certified, gives the amount due this period. This is why a single wrong number carries forward into every future claim until someone finds it.
Why spreadsheet tracking breaks
Most subcontractors start with a spreadsheet, and most spreadsheets fail the same way — not loudly, but by slowly disconnecting the numbers that must stay linked:
- The claim file is a copy of last month’s copy. Formulas drift, rows get inserted on one sheet but not another, and nobody can say which version is true.
- Claimed and certified values live in different files — or the certificate simply overwrites the claim, destroying the record of what was originally asked.
- Physical progress lives with the site team, the claim lives with the office. The claimed percentage and the site’s real percentage quietly diverge until the client’s QS points it out.
- When the client certifies less than claimed, the difference is absorbed instead of tracked. Value that should have been resubmitted next month is simply forgotten.
- Extra work gets typed into original scope lines, because that is the easy place to put it — and the entitlement trail is gone.
None of these are calculation errors. They are record-keeping failures: the four records that must stay connected — scope, progress, claimed, certified — drift apart because nothing forces them to stay linked.
The workflow that works
A controlled claim process is not complicated. It is five habits, kept in one structure:
1. Fix the baseline
The contract BOQ — items, quantities, rates — is the reference for everything that follows. Every claim line points back to it. Extra work is added as separate, named items with their own descriptions, never mixed into original quantities.
2. Measure progress against the baseline
Physical progress is recorded weekly, against the same BOQ structure, by the people who see the work. Not a separate tracker with its own logic — the same items, the same units.
3. Derive the claim — don’t invent it
The monthly claim is produced from the progress record: cumulative value of work done, minus what was previously certified. If the claim needs a meeting to reconstruct what happened, the tracking has already failed.
4. Record the certificate as its own record
What the client certifies is entered alongside the claim, never over it. The gap between claimed and certified is not noise — it is the list of items to explain, correct, or resubmit.
5. Reconcile and carry forward
Executed, claimed, and certified stay as three linked, separate values per item. What was rejected or under-certified is visible and goes back into the next claim deliberately, not by luck.
Frequently asked questions
What is the difference between a progress claim and a payment application?
They are the same document under different names. “Progress claim” is common in the UK, Australia, and much of Europe; “payment application” or “pay app” is common in the US; “interim application” also appears in contracts. All of them mean the periodic statement of the value of work completed, submitted for payment.
What is the difference between a progress claim and a payment certificate?
The claim is what the subcontractor asks for; the certificate is what the client or main contractor accepts for payment. The two rarely match. They should be kept as separate records, because the gap between them — what was claimed but not certified — is exactly what needs to be explained, corrected, or resubmitted.
How often are progress claims submitted?
Usually monthly, as set by the contract. Physical progress, however, should be measured more often — typically weekly — so that the monthly claim is produced from an existing progress record instead of being reconstructed from memory at the end of the month.
Should extra work be included in a progress claim?
Yes, but as separately identified items with their own description and approval trail. Extra work merged silently into original contract quantities is the fastest way to lose entitlement: the client cannot certify what they cannot see, and the subcontractor can no longer prove what was original scope and what was added.