Put a number on lost productivity.
Overtime, stacking, and disruption quietly erode output. The measured-mile method turns that erosion into lost hours and dollars, using your own project as the yardstick.
There are three accepted ways to prove lost productivity, strongest first:
- 1. Measured mile — compare an unimpacted stretch of the job to the impacted stretch on the same work. Most defensible, drawn from your own data. This calculator uses it.
- 2. Industry studies — apply published loss factors (MCAA and similar) when no clean baseline exists.
- 3. Total cost — the weakest fallback: actual cost minus bid. Use only when the first two are impossible.
Your measured mile
The baseline is a normal, unimpacted stretch of the same work. The impacted period is the overtime or disrupted stretch you want to price.
A severe loss. This is the number claims are built on
Finding your measured mile is the hard part. POD already has it.
The measured-mile method lives or dies on clean baseline data. POD reads the daily reports and hours your team already produces, so the unimpacted and impacted periods are already recorded, ready to defend a productivity claim instead of reconstructing one after the fact.
Why measured mile wins
Both periods come from the same crew, same job, same scope. That removes the argument that the loss was your own fault, which is why courts and boards prefer it.
What erodes output
Sustained overtime, trade stacking, out-of-sequence work, and constant re-mobilization. Each one shaves output per hour, and they compound.
The math
Efficiency = impacted ÷ baseline rate. Lost hours = impacted hours × (1 − efficiency). Lost cost = lost hours × your burdened rate.
We won't invent numbers you didn't give us.
Document the loss as it happens.
POD turns the reports you already produce into a live record of hours and output, so your measured mile is captured in real time, not rebuilt under deadline.
Last updated: July 2026