A change feed over the org's stage taxonomy: entity, change type, the name involved, the from and to values, the actor and the time. It also surfaces the most-changed stages.
Also called: stage change history · who renamed this stage · audit of my stage setup
- 1Changes are captured on the definition tables (migration 147)
- 2The analytics route reads the most recent 500 within the window
- 3The UI renders human verbs: added, removed, restored, renamed, duration changed, recoloured, reordered
A change to a shared stage template silently reshapes every future job, and there was no record of who trimmed the framing estimate or when. That made every performance number uninterpretable — an estimate cut last month looks identical to a crew that got slower. Plan changes carry a name and a time, so the analytics can be read and the setting has an owner.
- Silent changes to a company-wide template
- Performance data with no context for shifts
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 →