Catching a stage-of-completion mismatch before it hits the claim file
A stage-of-completion mismatch rarely shows up on day one. It shows up at month nine, after a fire or a wind event, when the adjuster pulls the contractor's last progress report and the numbers don't square with what's standing on the lot. By then the gap is a coverage argument, not a data point.
Catching the mismatch months earlier, while the policy is still active and the file is still boring, is the fix.
Where the mismatch comes from
Builder's risk progress updates come from one source: the contractor, reporting on their own job. The super who signs off on the monthly draw isn't always the one who walked the slab, and a busy project team fills out the form between everything else it's doing that day. "60% complete" means whatever the person filling out the form decided it means that day. Framing might be up on three of four buildings and the form reports the project as a whole. A weather delay in March doesn't make it onto the April report because nobody updated the template.
None of that is fraud. All of it is exposure sitting on a policy that was priced against a completion curve nobody is actually checking.
The usual underwriting response is a site visit, which works and also costs a trip, a schedule, and a contractor who knows the inspector is coming two weeks out. A desk audit of invoices tells you what was billed, not what's built. Neither one runs often enough to catch drift between visits.
A repeatable check against the self-reported number
What closes the gap is a second, independent read of the site that doesn't depend on the contractor's form at all. Imagery, read monthly, gives you footprint and structure progress as it exists on the ground on a fixed date, regardless of what the draw request says. Put that next to the reported percentage and a mismatch stops being a surprise at claim time and becomes a line item you flag in month four: reported 55%, imagery shows framing not yet closed in, follow up with the GC before the renewal, not after the fire.
The same read also catches the things a progress percentage doesn't mention at all. A footprint that's expanded past the permitted plan. A site that looks unsecured in October when the policy assumed fencing and lighting were in from the start. None of that is a contractor lying on a form. It's just not on the form.
It's a monthly habit built on repeat very-high-resolution imagery (≤0.5 m ground sample distance, satellite or aerial, standard RGB), delivered as an overlay on the site map so it sits next to the policy file instead of in a separate report nobody opens. Builder's Risk Monitor builds that read for exactly this use: stage of completion, footprint change, and visible site security, checked against the contractor's own number every month the policy is in force.
What to do with a mismatch once you see one
A single month of disagreement between the imagery read and the self-reported percentage isn't automatically a problem. Weather, a delayed material delivery, a reporting lag: there are ordinary reasons a GC's number runs a little ahead or behind. What matters is whether the gap holds for two or three cycles running, or whether it's widening. That's the pattern worth a call to the insured, an adjustment to reserve, or a note in the file before renewal, rather than a dispute after a loss.
If you underwrite course-of-construction risk and the only progress number in the file is the one the contractor wrote down, that's worth changing before the next large loss makes the point for you. Get a monthly, independent read of stage of completion filed against the policy from month one.