Every revision kept,
so a slip can be measured rather than argued.
The schedule handler reads a programme export as the dated revision it is: activities, logic, baselines and progress. Revisions are kept side by side, so movement between them is a measurement.
LLX-HANDLER-SCH · R3 · 5 formats
Three things a printed bar chart loses.
Activities and logic
Predecessors, successors and lags are read as relations, so the critical path can be recomputed rather than trusted.
Baselines and progress
Baseline dates and actual progress are read separately, which is what makes a comparison possible at all.
Every submitted revision
Each revision is stored as its own dated version with its digest, instead of overwriting the last.
The questions programmes usually decide.
How much an activity moved
Two revisions are compared activity by activity: dates, durations and logic changes are listed.
Delay analysisWhen the critical path changed
The driving path is recomputed per revision, so a shift is dated rather than asserted.
Critical pathWhether progress matches the record
Reported progress is read against the correspondence and records for the same dates.
SubstantiationRead in place, in the format it arrived in.
The file is never converted or re-saved. It is read where it lies, and the handler records a SHA-512 of the bytes it read — so a passage cited today can be replayed against the same file years from now.