Claims that argue for themselves

A progress claim argues for itself when every quantity on it points to a record that already exists: the installed quantity to installation entries with photos, the material on site to goods receipts, the accepted work to inspection verdicts, and the previous quantity to the last certified invoice rather than to a cell someone carried forward. Built this way, the claim is not a document you defend; it is a summary of facts the client's engineer can check line by line. Two practices do most of the work. Derive the previous quantity from the last invoice, so the same quantity can never be claimed twice. And attach the evidence when the claim line is built, from the records, not weeks later from a folder.

Deriving previous quantities

The classic failure: the payment application is a spreadsheet, the "previous" column is copied forward from last month, a row is inserted, the columns shift, and one line is claimed twice. The consultant finds it, and every other line on the claim is now suspect. The remedy is structural. Previous quantity is not a column anyone types; it is the sum of what was certified on prior invoices for that line, computed at the moment the new claim is built and again when it is locked. Double-claiming then requires forging an invoice, not nudging a cell.

The claim grid

One row per BOQ line, one column per payment stage (delivered, installed, inspected, or whatever the contract defines). Previous, this period and cumulative for each. The cumulative can never exceed the line's claimable quantity, and the claimable quantity is the contract quantity as revised by approved variations.

Evidence that belongs on the claim

Goods receipts for material-on-site lines: the receipt number, date, quantity and the QC decision.
Installation entries for installed quantities: dates, quantities per zone, and the photos stamped with name and time.
Inspection verdicts for work claimed as accepted: the request reference, the date, the code.
Variation approvals for any quantity above the original line: who approved, when, and the agreed quantity.

Evidence attached at build time is cheap; evidence assembled at dispute time is expensive and incomplete. The claim should be able to print its own supporting file.

Variations, omissions and the revised value

A claim is measured against the revised contract, not the original. Approved additions raise the claimable quantity on the affected lines; omissions reduce it, and the record must be able to hold a negative. The over-billing check — is the cumulative claim above the contract value? — must use the revised value, or every project with an approved variation trips the check for the wrong reason.

The practice

Claim only against an approved budget. A claim built on unsigned numbers is an argument waiting to happen.
Never type the previous quantity. Derive it, and re-derive it at lock.
Attach the receipt, the entry, the inspection at the moment the line is built.
Record every deduction — advance recovery, retention, tax — as a ladder on the claim, so the certified figure is reproducible.
Keep every revision of a claim. A revised claim replaces the old cycle; it does not erase it.

How Muthari OS handles this. Claims are a grid of BOQ lines by payment stage. Previous quantities are derived from prior invoices and re-derived after the claim is locked, so the same quantity cannot be claimed twice. Goods receipts and work inspection records are linked to the claim as evidence automatically. Claims are blocked until the budget is approved, and the check is repeated at lock. The deduction ladder — value of work done, advance recovery, retention, VAT — is recorded on the claim; certification carries due-date clocks; payments are recorded against the invoice; revised claims keep the old cycle in history. Approved remeasures, including omissions as negative quantities, revise the claimable quantity, and a derived revised contract value feeds both the over-billing check and the claim header. Honest limit: a claim above the revised contract value raises a warning rather than a refusal, and variation quantities are valued at the BOQ rate in the claim today.

Book a free demo See the whole system →