A scrolling list of change entries, each tagged by entity (stage or checkpoint), with the verb, the old value struck through, the new value, the stage it belonged to, and the date. Also a most-changed ranking and a total change count in the tile row.
Also called: who changed the stage setup · stage edit history · why did my durations change · plan change log
- 1Every edit in the Stages tab writes a change row with entity, change type, names, from and to values, actor and time.
- 2The panel lists up to 500 changes in the window, newest first.
- 3Change types are rendered as verbs: added, removed, restored, renamed, duration changed, recoloured, reordered.
- 4Added and removed rows carry colour-coded tags.
The heading's (i) explains the diagnostic use: 'Every edit made in the Stages tab. Useful when performance shifts: a stage that suddenly runs over may simply have had its estimate cut.' It is the second of the two questions the route deliberately keeps apart from performance.
- Configuration changes were invisible when interpreting a performance shift.
- Nobody could tell when or by whom a stage estimate was altered.
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 →