What it is
A ranked bar list rolled up across the whole window: 'Weather — 12.5d · 7×', 'Material delivery — 8d · 3×'. Causes come from the structured delay-reason codes recorded on stages, so they aggregate cleanly rather than being free text.
Also called: delay causes totalled · days lost by reason · biggest cause of delay
See it
How it works
- 1Per-stage cause totals are summed across all stages into one map.
- 2Rows are sorted by days lost descending and bar width is scaled to the largest.
- 3Each row shows days to one decimal and the number of occurrences.
- 4The section renders only when at least one stage has a recorded cause.
Why we built it
Delay reasons were being captured on stages already; without a rollup they stayed one job's story. Totalling them turns 'we always get weather' into a number of days per season that can be planned against.
The problem
- Delay causes were recorded but never aggregated.
- Seasonal or supplier patterns were invisible at the job level.
Sound familiar?
What you get
The top cause of lost days across the business is named and quantified.
Supports concrete decisions — lead times, buffers, supplier changes.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →