Snapshot Versioning
Unlimited named plan snapshots — any snapshot can serve as baseline, forecast checkpoint, status record, or what-if scenario; the active baseline is a designation, not a separate column set.
Baseline management is one of the most operationally frustrating aspects of traditional scheduling tools. Most tools provide a limited number of baseline slots — often five or ten — and storing a new baseline means either using an empty slot or overwriting an existing one. Teams that need more historical snapshots than available slots end up maintaining external files, copying fields to custom columns, or simply accepting that some historical records will be lost.
Self-Contained Snapshots
ProjectXL snapshots are self-contained records of the complete plan state at the moment of capture. They are not pointers to current table data — they are independent records that preserve the full planning state including schedule activities, network structure, assignments, non-labor cost plans, and other governed table content. Because they are independent, they are immune to changes in the live plan. A snapshot taken six months ago accurately reflects what the plan looked like six months ago, regardless of how much the plan has changed since.
Active Baseline as a Designation
The active baseline is a designation applied to one snapshot at a time, not a separate set of columns that data must be explicitly written into. This means the baseline is always a specific named snapshot — a record with a date, a description, and full historical content — rather than an unnamed set of column values. Teams that need to rebaseline apply the designation to a new snapshot and the previous baseline remains in the archive unchanged, still accessible for comparison.