Learning Center
Measured Mile Analysis for Loss of Productivity
The measured mile is the standard technique for proving a loss of productivity claim -- the excess labor hours a disruption cost a crew, as distinct from a schedule delay claim measured in days. It works by comparing the same crew’s own actual productivity rate during an unimpacted stretch of the project against its rate during the impacted stretch, then converting that gap into excess labor hours.
Productivity, Not Schedule Delay
A disruption doesn’t always push the finish date. Out-of-sequence work, trade stacking, excessive change-order volume, or repeated re-mobilization can all make a crew work far less efficiently -- burning more labor hours to install the same quantity of pipe, pour the same volume of concrete, or pull the same length of cable -- without ever consuming float or moving the critical path. That inefficiency is real money, but it’s invisible to a pure schedule analysis. Measured mile analysis exists specifically to quantify it, in labor hours, independent of whatever the schedule shows for time.
Why the Project’s Own Data Beats a Benchmark
Estimating manuals and published industry productivity studies can put a number on how many hours a task should take, but they describe a generic crew under generic conditions. A measured mile comparison uses two periods from the same project -- ideally the same crew, the same equipment, the same scope of work, and the same general site conditions -- with the disruption in question as close to the only variable that changed. That’s what makes the comparison persuasive: it isn’t asking a fact-finder to accept an outside rate as fair, it’s asking them to believe the crew’s own recorded performance on the same job, before and after.
Worked Example: A Pipe-Installation Crew
A crew installing underground pipe works cleanly for its first four weeks. Starting in week 9, the electrical subcontractor begins pulling conduit through the same trench line out of sequence, forcing the pipe crew to repeatedly stop, shift equipment, and rework sections it had already prepared. Weeks 1–4 become the unimpacted period; weeks 9–12, while the trade stacking is active, become the impacted period.
| Period | Week | Feet Installed | Labor Hours | Hours / Foot |
|---|---|---|---|---|
| Unimpacted | Week 1 | 100 ft | 80 hrs | 0.80 |
| Unimpacted | Week 2 | 100 ft | 80 hrs | 0.80 |
| Unimpacted | Week 3 | 100 ft | 80 hrs | 0.80 |
| Unimpacted | Week 4 | 100 ft | 80 hrs | 0.80 |
| Impacted | Week 9 | 70 ft | 84 hrs | 1.20 |
| Impacted | Week 10 | 60 ft | 72 hrs | 1.20 |
| Impacted | Week 11 | 65 ft | 78 hrs | 1.20 |
| Impacted | Week 12 | 55 ft | 66 hrs | 1.20 |
| Unimpacted | Total | 400 ft | 320 hrs | 0.80 |
| Impacted | Total | 250 ft | 300 hrs | 1.20 |
The Calculation
- 1. Unimpacted-period rate
- 320 labor hours ÷ 400 linear feet = 0.80 hours per foot. This is the measured mile -- the crew’s own baseline rate before the disruption began.
- 2. Impacted-period rate
- 300 labor hours ÷ 250 linear feet = 1.20 hours per foot -- the same crew, same pipe, installed 50% less efficiently while the conduit crews were stacked into the same trench.
- 3. Excess rate
- 1.20 − 0.80 = 0.40 excess hours per foot attributable to the disruption.
- 4. Excess labor hours
- 0.40 excess hours per foot × 250 feet (the impacted-period quantity) = 100 excess labor hours caused by the trade stacking during weeks 9–12.
Picking a defensible unimpacted period is the hardest part of a measured mile analysis -- and the first thing the other side will attack. Claims Digger’s schedule comparison shows exactly when out-of-sequence work, added activities, or logic changes actually appeared across a project’s schedule updates, so you can point to the specific weeks where a given disruption genuinely wasn’t yet present -- and build your measured mile baseline on solid ground. See how it works.
Frequently Asked Questions
- Is a measured mile analysis the same as a schedule delay analysis?
- No. A schedule delay analysis measures time -- how many days a project finished late and which activities drove that. A measured mile analysis measures lost labor productivity -- how many extra labor hours a crew burned doing the same scope of work, whether or not that inefficiency ever pushed the finish date. The two frequently accompany the same disruption event, but they answer different questions and are usually presented as separate heads of damage.
- What makes a period qualify as the "unimpacted" baseline?
- It has to be genuinely comparable to the impacted period in everything except the disruption itself -- same crew composition and experience level, same equipment, same general working conditions and scope of work, ideally on the same project. A period that looks unimpacted on the surface but was itself affected by a different problem will understate the excess hours, or invite a challenge that undermines the whole analysis.
- What if the project never had a clean unimpacted period?
- This is the technique's main practical limitation. When no representative unimpacted stretch exists on the project itself, analysts sometimes fall back to a comparable period from a similar project, an industry productivity study, or an estimate built from first principles -- but each of those substitutes external data for the project's own actual performance, which is exactly the strength a true measured mile analysis is built on. They're generally treated as a less persuasive fallback, not an equivalent alternative.
- Does the measured mile technique only work for labor hours?
- Hours per unit of work is the most common metric because labor cost is usually what's actually in dispute, but the same before-and-after comparison works with any consistent productivity measure -- units of equipment output per shift, for example -- as long as the same metric is tracked the same way in both the unimpacted and impacted periods.
Part of the Claims Digger Learning Center. Related reading: Pacing delay explained · Full glossary