Construction & real estate
Turning site photographs into a progress record
A developer whose site engineers reported progress as percentages in a weekly message, supported by photographs that were never linked to anything. Billing disputes were routine because progress claims could not be evidenced.
Illustrative scenario — not a named client engagement
Before
- Progress self-reported as a single percentage per package
- Photographs stored in messaging apps and lost within weeks
- Variations agreed verbally on site
- Client reporting assembled manually each Friday
System shape
- Quantity-based progress with mandatory evidence capture
- Variation requests with cost, time and approval trail
- Document intelligence over drawings and site correspondence
- Programme view of slippage across every live site
Approach
Process Audit
Mapping how quantities were actually measured on site versus how they were billed, and where the two diverged.
System Blueprint
Progress modelled against measured quantities and checkpoints rather than free-text percentages, with evidence required at each checkpoint.
Working Prototype
One site, one package type, mobile capture with offline tolerance — deployed in under three weeks.
Build & Integrate
All active sites, variation workflow linked to the commercial record, and automated weekly client packs.
Signals we would measure
Targets agreed before the build, not claims made after it.
Time between site event and system record
Variations captured at occurrence versus at billing
Disputed claim value as a share of certified value
Hours spent assembling client reporting
Sound familiar
Most of these start with one spreadsheet nobody trusts.
If any part of this resembles your operation, a Process Audit will tell you exactly where the leverage is.