What moved since last month — answered in writing.
Drop each month’s XER — the app recognises it as an update of the same P6 project and files it automatically. Four trend charts and a written narrative explain the movement.
One project, filed monthly — automatically.
The library matches updates by P6 project id, then project name, then file name. One update per data date; re-imports replace cleanly instead of duplicating history.
Four charts, one story: where the finish is heading.
Every monthly update becomes a data point — the drift is visible long before it becomes a claim.
Written by the app, ready for the meeting.
“Forecast finish moved +9 days (14-May → 23-May). Driving the movement: A1030 ‘Pile caps zone 2’ slipped +11d on the critical path. Entered the critical path: A2210, A2230.”
Prove what slipped, when and why.
Baseline-vs-current finish variance, slipped activities ranked by an impact score, WBS slippage, missed actuals, CPLI and BEI — traced update by update, exportable as evidence.
Delay drivers ranked by impact — finish variance, float and flags per activity.
Honest scope: this is window-by-window observational analysis across your updates — it does not build TIA fragnets. That limit is documented in the pricing FAQ, not hidden in fine print.
Any two XERs, diffed for the record.
For ad-hoc questions outside the monthly cycle: compare any two exports directly, then take the CSV with you.