Upload a baseline programme and the progress updates that followed it. The tool compares each update against the one before, measures how far the completion date moved in every window, identifies which activities drove that movement and why, and flags where more than one independent path slipped at the same time. Windows analysis and as-planned versus as-built, with float erosion tracking and candidate concurrency detection.
Analysis Support Only: Outputs from this tool are analytical decision support based on the schedules uploaded. They are not a legal opinion or a substitute for expert witness evidence in dispute, adjudication or arbitration. Independent expert review recommended before use in any commercial or contractual context.
↑
Drop your XER files here
Select the baseline and every update you want included. Files are sorted automatically by data date. Everything is processed in your browser — no programme data is uploaded.
Files Loaded
The earliest data date is used as the baseline unless you set another. Remove any update you do not want in the analysis.
#
File
Data Date
Programme
Activities
Completion
Role
Analysis Settings
Adjust these before running if your programme does not use an eight hour day, or if you want near-critical paths included.
—
Total Slip (Days)
—
Updates Analysed
—
Windows
—
Delay Drivers
—
Concurrency Flags
Summary
Narrative generated from the movement measured between your updates.
Slip Against Baseline
Cumulative movement of the completion date across every update supplied.
Completion Date Movement
Days later than the baseline completion date, measured at each data date.
Window Analysis
Each window compares two consecutive updates. Own movement is the part of an activity's slip not inherited from a predecessor. Beyond float is the part of that slip the activity had no float left to absorb. Individual figures will not always sum to the movement in the completion date, because where several paths slip at once only the governing path drives completion.
Largest Delay Contributors
Movement beyond available float, summed across every window, so an activity that slipped repeatedly ranks above one that slipped once.
Delay Beyond Available Float
Top contributing activities across the full period analysed.
Activity
Name
WBS
Days
Windows
Causes Recorded
Float Erosion
Activities that lost the most total float between the baseline and the final update. Float loss frequently precedes a path becoming critical.
Activity
Name
WBS
Baseline Float
Final Float
Eroded
As-Planned vs As-Built
Activity
Name
State
Planned Start
Actual Start
Start Var
Planned Finish
Actual Finish
Finish Var
Dur Var
Want Expert Review?
Have your analysis reviewed by an expert, add professional narrative and sign off the report. Direct senior expertise — no account managers, no junior staff.