Before
Project completion: Mon 12:00
Alice
- PreparationMon 09:00–Mon 11:00
Ben
- ReviewMon 11:00–Mon 12:00
Understanding / Activity & forecast history
The date moved. Keep the explanation.
Activity records meaningful saved changes. Forecast history records meaningful observations of the schedule. Together with actual work, they help explain the gap between the original plan and what happened.
Understand the model ↓See the worked example →What changed, when and who changed it.
Administrators can review organisation activity, filtering by project, person, category and date. New meaningful edits include compact before-and-after details for work, assignments, effort, calendars, prerequisites and commitments.
Unchanged saves, page views and unsaved What If exploration do not manufacture planning activity. Older events show only information that was recorded at the time.
What the forecast looked like.
Scheduling saves capture meaningful forecast observations, including relevant inputs, allocations, dates and deadline risk. Identical recalculations do not create another observation. Baseline, original and latest records provide different reference points.
The current Why this date explanation describes the live plan. Forecast history and contributing changes help explain movement around recorded observations; they are not a complete replay of every instant.
History is evidence, not a general undo button.
Recorded actual intervals describe work that happened. Forecast observations describe estimates at particular points. One should not be substituted for the other.
History begins with the information actually captured. It does not reconstruct unrecorded plans or restore every historical state. Ordinary edits cannot be undone through the history view.
A FICTIONAL SCHEDULING STORY
The person who wasn’t interrupted
Before
Alice prepares the work from 09:00 to 11:00. Ben reviews it from 11:00 to noon.
The change
Alice takes a committed one-hour export fix at 10:00. Ben’s calendar, estimate and assignment stay unchanged.
After
Project completion: Mon 13:00
Alice
- PreparationMon 09:00–Mon 10:00
- Interruption · Customer export fixMon 10:00–Mon 11:00
- PreparationMon 11:00–Mon 12:00
Ben
- ReviewMon 12:00–Mon 13:00
Example assumptions. Monday 19 October 2026. Both people work 09:00–18:00 without breaks in this isolated example. One explicit stage dependency connects preparation to review.
THE CONSEQUENCE
Preparation finishes at noon. The finish-to-start dependency prevents Ben reviewing it at 11:00.
THE REVISED PLAN
Ben reviews from 12:00 to 13:00. His work moved because its prerequisite moved, not because someone edited his task.
Work, time and consequences.
Explore the connected product ↗Register your interestComing in a later release · registration is not open yet