The heart of the panel. Ran-long and ran-short are shown as counts beside the average because 'the average hides one disastrous job inside forty fine ones'. Days lost carries an (i) when some delays were logged without a cause or a cost, so the reader knows how much of the total is missing. The top delay cause is printed under the stage name.
Also called: planned vs actual per stage · which stage runs long · stage variance table
- 1Stage logs are grouped by task type; only rows with a recorded actual count toward the averages.
- 2avgPlanned reads baseline_days first, falling back to planned_days.
- 3ranLong / ranShort / onTime are counts of positive, negative and zero variance.
- 4Delays with neither a cause nor a days impact are counted separately and excluded from the days-lost total.
- 5The Runs column reads completed/started so the denominator is always visible.
Two comments in the route carry the reasoning: on the counts, ' "Ran long" is the count that drives a conversation; the average hides one disastrous job inside forty fine ones'; and on the missing-detail counter, 'Surfaced rather than dropped: it is the measure of how much of this data can be trusted.'
- Stage duration estimates were never checked against outcomes.
- Averages concealed the frequency of overruns.
- Incomplete delay records silently understated days lost.
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 →