Schedule history and undo#

Every change to your schedule is saved automatically. Owl building the plan, an imported Primavera P6 or Microsoft Project file, a status update, a duration you nudged by hand: each one is written to the Schedule History as a snapshot. That history gives you three things:

• Undo and redo (⌘Z / ⇧⌘Z) for your own last changes.
• A complete record of how the plan got where it is, with a roll back to any earlier point.
• Named revisions — the versions that matter, such as the update you submitted to the owner each month, kept apart from hundreds of everyday edits.

Note: You never have to save. Every edit creates a snapshot, so the history is always complete and you can always step back.

Undo your last change — ⌘Z#

Press ⌘Z (Ctrl+Z) or click the undo arrow at the left of the schedule toolbar to undo your last change. ⇧⌘Z (Ctrl+Shift+Z or Ctrl+Y) redoes it. Hover the arrow to see what it will undo, for example Undo CO_001 name (⌘Z).

Undo only touches your own changes, never a teammate's. Changes Owl made when you asked it count as yours. On a shared schedule, you can undo your mistake without wiping out what someone else did in the meantime.

• An undo reverses the fields your change touched and leaves everything else as it is now. It is saved as a new snapshot (change type Undo), so the history still shows both the change and its undo.
• If someone has since changed the same field, Owl refuses the undo rather than overwrite their work. The arrow is greyed out and its tooltip says why.

To go back further than a few steps, or to undo a whole batch of changes, roll back from the history instead.

Open the Schedule History#

In the project tree, click Schedule History. It opens as a tab.

1234561Open Schedule History from the project tree.2Switch between All changes and your named Revisions.3The timeline: newest first, grouped by day. Each row is a snapshot with its time, summary, version number and who made it.4What changed: the exact fields this snapshot changed.5Roll back here re-opens this plan as the live version.6Name version turns this snapshot into a named revision.

Read the timeline#

The left side is the timeline, newest at the top and grouped by day. Each snapshot shows:

• When it happened.
• What changed — a short summary (Schedule update, Undo DPMC_FINAL remaining duration and % complete, or a revision's name).
• Which version it is (v114, v113, …). Versions count up, so a higher number is more recent.
• Who made it — you, a teammate, or Owl when the agent did the work.

The top row, Current — live working version, is where you are now. It also tells you which version is the baseline.

Switch the view at the top:

• All changes — every snapshot. Busy days collapse to Show 9 more edits from Sep 15.
• Revisions — only the versions you named (below).

See what a snapshot changed#

Click any snapshot to open it on the right: its version, its change type, the current baseline, and a What changed list of the exact fields that moved, old value to new. Click Show Gantt to see the whole schedule as it stood at that moment.

121The field that changed: DES50_003's percent complete, 84 → 100.2Show Gantt draws the whole schedule as it was at this version. Expand and collapse it like the live one.

Name the versions that matter#

A schedule goes through hundreds of edits, but a handful of versions really count: the plan you submitted, each monthly update, Rev 3. Give those a name and they become revisions you can find, compare against, and point people to.

1. Select the snapshot in All changes.
2. Click Name version at the bottom of the detail.
3. Enter a Name (September update, Rev 1) and, if you like, a Note, then click Save name.

1231The name everyone will see.2An optional note: who it went to, why.3Save name.

Named versions show their name in the timeline and appear under Revisions. Open one there and the detail shows Changes since the revision before it, so you can see exactly what moved between two submissions.

12341Revisions lists only the named versions.2Each revision with its version, date and note.3Changes since the previous revision.4Rename changes the name.

Heads up: People may already refer to a revision by its name, so Rename asks you to type RENAME REVISION before it changes the name. Remove name, in the same dialog, turns it back into an ordinary snapshot and also asks for a typed phrase.

Tip: When you import a status update, Owl offers to name the version it creates. See Import your schedule.

Roll back to any snapshot#

Found a change you want to reverse — a bad bulk edit, an import that went sideways, a scenario merged by mistake? Select the snapshot from before it and click Roll back here. Owl re-opens that plan as your live working version.

Rolling back is reversible. Your current schedule isn't thrown away; it's kept as a snapshot at the top of the history, so you can roll forward to it again.

Related: Set as baseline (next to Roll back) makes a snapshot your plan of record: the plan that EVM and variance analysis measure against. Owl asks you to confirm first.

What to do next#

• Record progress — every status update you make in Track progress and collaborate lands here as a snapshot.
• Compare against the plan of record — set a baseline, then watch cost and schedule drift on the EVM dashboard.