How it works
Eight steps from a claim to a defensible payment.
The path of one claim
- 1
A claim is entered
Quantity surveyor or project manager
The contractor's claim is recorded against a milestone: percentage complete, amount, and the quantities claimed for each BOQ item. Submitting it schedules the site inspection and copies the right evidence checklist.
- 2
Evidence is captured
Site engineer
On site, the inspector works through the checklist: exterior, interior, key structural elements, materials, the BOQ sheet and the measurement sheet. Each file is uploaded straight to private storage.
- 3
The server inspects every file
SiteProof
Each file's fingerprint, type, capture time, location and quality are derived from the bytes. A file that is not what it claims to be is rejected.
- 4
The evidence is analysed
Analysis provider
An analysis model reads the evidence and reports what it sees: estimated completion, quantities, defects, figures on documents. It is never shown the claimed progress or amount, and its answer is validated against a strict schema.
- 5
The rules verify
Verification engine
Up to thirteen deterministic checks run, then a verdict, a risk score and the financial exposure are calculated. A missing or failed analysis can never produce a verified claim.
- 6
A professional decides
Reviewer
Claims that need judgement go to the review queue. The reviewer decides what is verified and explains why; the payment recommendation follows from that.
- 7
Payment is approved
Project manager or owner
The recommended amount, or a justified different amount, is approved. The claim is marked approved for payment.
- 8
The proof is kept
SiteProof
An evidence pack seals the whole record. It can be printed or shared, and the audit trail shows every step in order.
Three roles that never blur
The reason the result can be defended is that nothing does another's job.
The analysis observes
Does
- Reads the photos and documents
- Reports estimated completion, quantities, defects and figures on documents
- States how confident it is
Never
- Sees the claimed progress or amount
- Decides a status, a verdict or a payment
- Gets its answer accepted without strict validation
The rules verify
Does
- Run up to thirteen deterministic checks
- Produce a verdict, a risk score and the financial exposure
- Explain every result in plain language
Never
- Use a model's free text
- Give different answers for the same evidence
- Mark a claim verified when the analysis is missing
Professionals decide
Does
- Verify, partly verify, reject or ask for more
- Override a check, with a recorded reason
- Approve the payment amount
Never
- Decide a claim they captured themselves
- Skip the note when they depart from the analysis
- Change the audit trail afterwards
The checks
Up to thirteen. Invoice and delivery-note checks run only when those documents are provided. Each result carries a plain-language reason built from measured values.
Required evidence
Was every required photo and document provided?
Compares what was captured with the checklist for the stage. Missing required items fail the check.
Location
Was the evidence captured at the project site?
Measures the distance between each photo's own GPS and the project site, and flags devices that disagree with the file.
Timing
Was the evidence captured recently and consistently?
Compares capture times with the submission time and flags old photos and inconsistent clocks.
Duplicate images
Is any photo reused from another claim or inspection?
Exact fingerprints and perceptual hashes are compared across the organization's earlier evidence.
Photo quality
Are the photos sharp, bright and large enough to judge?
Measures sharpness, brightness and resolution against minimums.
Analysis confidence
How sure is the automated analysis?
Low confidence fails or warns, so uncertain readings never pass silently.
Progress claimed vs observed
Does the claimed completion match what is visible?
Compares claimed progress with the estimate. Only over-claiming beyond the project's tolerance counts against the claim.
Quantities vs BOQ
Do measured quantities match what the contractor claims?
Compares quantities seen in the evidence with the quantities claimed for each BOQ item.
Document consistency
Do the measurement and BOQ sheets agree with the claim?
Reads figures from the documents and compares each with its own reference.
Invoice
Does the invoice total match the claim amount?
Runs only when an invoice is provided.
Delivery note
Does the delivered quantity support the invoice?
Runs only when a delivery note is provided.
Visible defects
Are there defects that affect the work claimed?
Weighs credible defects by severity.
Schedule alignment
Is the visible work at the stage the milestone expects?
Compares the stage visible in the evidence with the milestone's stage.
Stop paying on trust.
Set up a workspace, add a project and load the Nova Heights demo to walk the whole flow in minutes, or try the live demo first.