Plans change. Keep the receipts.
Every NeoGantt chart keeps an automatic version history you can restore from, plus named iterations you save when a plan is agreed. Each new iteration lists what moved, what was added and what was removed since the last one, so the update email is half-written before you open it.
One is automatic. The other is on purpose.
Automatic history
While anyone edits, NeoGantt saves a snapshot of the chart, at most once every five minutes. The latest 200 are kept. Open History, pick one and restore it.
It’s the safety net for the afternoon a colleague deletes a phase by accident, and it costs you nothing until then.
Iterations
A named checkpoint you save yourself: “v1, agreed at kickoff” or “v2, scope change”. Each records who saved it and when, and is never pruned.
Expand any iteration and NeoGantt lists what changed since the one before it. Every iteration can be restored too.
The email you'd otherwise have to write.
- “Content & brand assets supplied” extended by 7 days (ends 29 Jan 2027)
- “Visual design” moved +7 days (now 8–19 Feb 2027)
- “Design approved” moved 15 Feb 2027 → 22 Feb 2027 (+7 days)
- Added task “Extra copy round” (1–5 Feb 2027)
- Renamed “Go live” → “Go live (phase 1)”
- “Wireframes” progress 80% → 100%
- Removed task “Print brochure”
The summary covers tasks, milestones and groups that were added, removed or renamed, dates that were moved, extended or shortened, and progress changes.
It’s plain text, so it pastes straight into an update email or a status report. Day counts in the summary are calendar days, even on a chart that counts durations in working days.
Tracking schedule changes on a live client project
- At kickoff you build the plan with the client and save an iteration: v1, agreed at kickoff. That’s the version everyone said yes to.
- Three weeks in, the client’s content arrives late. You extend their task, push design back a week and leave a comment on the design approval milestone explaining why. Comments are visible to everyone viewing the chart, including the client on the share link.
- You save v2, content delay. Its summary lists every date that moved. You paste it into your update, and the share link already shows the new plan.
- Two months later, someone asks why launch slipped. You open History and there it is: what was agreed, what changed, when, who saved it, and the comment saying why.
What the summary leaves out
It’s built to answer “what moved?”, so it ignores changes that don’t affect the schedule. Restoring an iteration still brings everything back.
- Added, removed and renamed items
- Moved, extended and shortened dates
- Progress changes
- Colour changes
- Row order, and tasks moved between groups
- Client-task flags
- Comments, which keep their own thread on each task
Version history questions
How far back does version history go?
Automatic history keeps the most recent 200 snapshots of each chart, taken at most every five minutes while someone is editing. Iterations you save by name are kept for good.
Can I undo a restore?
Yes. Restoring an old version is an edit like any other, so ⌘Z (Ctrl+Z on Windows) puts the chart back the way it was.
Is an iteration the same as a baseline?
No. NeoGantt doesn't draw planned-versus-actual bars on the chart. An iteration is a saved copy of the plan you can compare against, restore, or read the change summary for.
Make your first chart
Free for one person with up to 5 charts. No card, nothing to install.