Construction payment verification
Pay for the work you can prove.
A contractor claims 90% complete. The site evidence shows about 67%. SiteProof AI checks every progress claim against geotagged evidence and deterministic rules before a naira moves, and keeps the proof.
AI observes. Rules verify. Professionals decide.
ABC Construction Ltd
First Floor Masonry
- Claimed
- ₦18,500,000
- Progress claimed
- 90%
- Analysis estimate
- 67%
Contractor claims 90% completion while verified estimate is 67%.
What SiteProof AI does
In plain terms, before the detail.
SiteProof AI is a verification platform for people who pay contractors against progress. When a contractor claims a percentage of a milestone, your site engineer captures evidence on a phone, and SiteProof works out how much of the claim the evidence actually supports.
It does this in the open. The server fingerprints and inspects every file, an analysis reads what is visible, and a set of fixed rules checks location, timing, duplicates, quality, quantities and documents. Anything the rules cannot settle goes to a named reviewer.
What comes out is not a score to trust. It is a decision with its proof: an exact payment recommendation, a sealed evidence pack and an audit trail that shows who decided what, and why.
Watch a contractor claim become a defensible payment
A 1:40 recording of the real interface on the Nova Heights sample project: capture, server inspection, analysis, rules, the reviewer’s decision, the exact payment recommendation, the sealed evidence pack and the portfolio view. No sound needed.
1 of 9 · A claim arrives
Claim CLM-0042 · Nova Heights
ABC Construction Ltd: First Floor Masonry
- Amount claimed
- ₦0
- Progress claimed
- 0%
- Quantity claimed
- 1,152 of 1,280 m²
Submitted by Amara Eze (QS). Inspection scheduled, evidence checklist copied for the masonry stage.
ABC Construction Ltd claims 90% of First Floor Masonry: ₦18,500,000. Submitting it schedules the inspection.
A claim arrives. ABC Construction Ltd claims 90% of First Floor Masonry: ₦18,500,000. Submitting it schedules the inspection.
Played live from the real screens and engine, on sample data with fictional people. The analysis estimate is simulated.
Claims arrive as promises. Payment needs proof.
A progress claim is a percentage and an invoice. Behind it sit site photos on someone's phone, a measurement sheet, a bill of quantities and a schedule. Teams stitch these together by hand, under time pressure, to answer one question: is this much really built? When they cannot, they pay on trust, or argue about it afterwards without a record.
From claim to defensible payment
Four stages, with a clear owner for each. The model observes, the rules verify, and a person decides.
1.Capture
Site engineers follow a checklist and capture geotagged photos and measurement sheets from a phone. The server records what the files really contain, not what the device says.
2.Observe
An analysis model reads the evidence and reports what it sees: estimated completion, measured quantities, visible defects. It never decides anything.
3.Verify
Up to thirteen deterministic rules check location, timing, duplicates, quality, quantities and documents. The same evidence always gives the same result.
4.Decide
A named reviewer decides what is verified. The payment recommendation is calculated from that, exactly, and a manager approves it.
See it work on a real scenario
Nova Heights, Lagos. This is the verification engine and payment formula running in your browser, not a mock-up. Only the analysis estimate is simulated.
Claim CLM-0042 · Nova Heights
First Floor Masonry · ABC Construction Ltd
- Amount claimed
- ₦18,500,000
- Progress claimed
- 90%
- Analysis estimate
- 67%
Contractor claims 90% completion while verified estimate is 67%.
The rules, check by check
- Required evidencePass
- LocationPass
- TimingPass
- Duplicate imagesPass
- Photo qualityPass
- Analysis confidencePass
- Progress claimed vs observedFail
- Quantities vs BOQFail
- Document consistencyPass
- Visible defectsPass
- Schedule alignmentPass
Computed live by the same deterministic engine the product uses. Same evidence in, same result out, every time.
Your decision
The analysis said 67%. A reviewer counted the north wing and verifies 69%. Drag to try other values.
Between 0% and the 90% claimed.
- Recommended payment
- ₦14,183,333
- Withheld from the claim
- ₦4,316,667
₦18,500,000 × 69% ÷ 90%. Calculated exactly, to the kobo. A person approves the amount; SiteProof never moves money.
What you get on every claim
Evidence, checks and a decision in one place, then a record you can hand to anyone.
Claim created
Quantity surveyor · 09:02
Claim submitted, inspection scheduled
Quantity surveyor · 09:05
Evidence captured and processed
Site engineer · SiteProof · 14:40
Analysis completed, verification run
SiteProof · 14:42
Verified at 69% of 90%
Reviewer · 10:15
Payment of ₦14,183,333 approved
Project manager · 11:30
Progress claimed vs observed
Contractor claims 90% completion while verified estimate is 67%.
FailSeverity: CriticalQuantities vs BOQ
Contractor claims 1152 m2 of Sandcrete blockwork (MASONRY-01) while 860 m2 (75%) is evidenced.
FailSeverity: HighRequired evidence
All 6 required evidence items were provided.
PassLocation
All 6 geotagged photos were taken within 150 m of the site.
PassTiming
All 6 timestamped photos were taken within 72 hours of submission.
PassDuplicate images
No duplicate photos found among 6 fingerprinted files.
Pass
Built for everyone who needs the truth about progress
Developers and owners
Is the progress I am paying for actually built?
See the claimed figure beside what the evidence supports, with the money at risk and the proof behind every number.
Quantity surveyors
Which claims need my judgement, and why?
A ranked review queue, checks that explain themselves, and a recommendation that follows from the progress you verify.
Project managers
What needs me this week?
Exceptions first: high-risk claims, quality flags, projects behind schedule, and payments waiting for approval.
Site engineers
What exactly do I need to photograph?
A stage-specific checklist on a phone, with clear guidance, and nothing to fill in about the files themselves.
Finance teams
What am I allowed to pay, and who approved it?
An approved amount, the verified progress it came from, the person who decided, and a sealed record to file.
Lenders and auditors
Can I check this without taking anyone's word?
A read-only evidence pack through an expiring link: evidence, checks, decisions and the audit trail.
Move from trusting claims to verifying them
| Today | With SiteProof AI |
|---|---|
| Percent complete is whatever the contractor says | Claimed progress sits beside what the evidence supports |
| Photos live on phones and in chat threads | Evidence is captured against a checklist, fingerprinted and stored privately |
| A QS eyeballs the pictures, if there is time | Fixed rules check location, timing, duplicates, quality and quantities every time |
| Disputes are settled from memory | Every decision has a named person, a reason and a timestamp |
| The payable amount is negotiated | The recommendation is exact arithmetic on the verified progress |
| Proof is a folder of files | A sealed evidence pack you can print, share and check later |
Built so the answer can be defended
Tamper-evident evidence
Every file is hashed on arrival. Evidence packs are frozen and sealed with a fingerprint, so nothing can be quietly changed.
A complete audit trail
Every action, by a person or the system, is recorded in an append-only log that cannot be edited or deleted.
Shareable proof
Generate a read-only evidence pack, print it as PDF, or share an expiring, revocable link with a developer, lender or auditor.
AI never approves a payment. It cannot: the verdict comes from rules, the decision comes from a named person with the right role, and the recommended amount is plain arithmetic on the verified progress. Access is limited by role and by project, and each organization's data is isolated by the database itself. Read how security works, including what is not built yet.
Start with one project.
We are working with a small group of developers, quantity surveyors and project managers on early pilots. Pricing is agreed per engagement.
- 1
Tell us about your projects
A short conversation about how claims are verified today and where it hurts.
- 2
Run one live project
We set it up together and you verify real claims alongside your current process.
- 3
Decide with evidence
Compare what the evidence showed with what was claimed, and decide whether to expand.
Questions teams ask first
Does the AI approve payments?
No, and it cannot. The analysis only reports what it sees. The verdict comes from deterministic rules, the decision comes from a named person with the right role, and the recommended amount is arithmetic on the verified progress. A manager approves it, and SiteProof never moves money.
Is the AI real today?
SiteProof AI is a pilot-stage product. Capture, evidence integrity, the verification rules, review, payment recommendation, evidence packs and the audit trail are built and tested. The analysis step reads evidence through a strict, pluggable interface; the current build ships a simulated analysis provider for demonstrations, and a vision model is connected behind the same interface without changing the rules or the human decisions.
How is the payment recommendation calculated?
Claim amount × verified progress ÷ claimed progress, using exact integer arithmetic in kobo, rounded once at the end and never above the claim. Example: ₦18,500,000 claimed at 90%, verified at 69%, gives ₦14,183,333.33.
Can a contractor game it?
No system removes fraud risk, but this one makes it harder and leaves a record. Photos are fingerprinted and compared across claims, capture location and time come from the file rather than the device, quality is measured, and anything that does not hold up is flagged for a person to judge.
Who can see what?
Access is by role and by project. Site engineers, quantity surveyors and reviewers see the projects they are assigned to; owners and finance see all projects. Payment figures are limited to the roles that need them. The database enforces tenant separation itself.
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.