Evidence-Backed
Every finding is supported by activity-level schedule evidence.
Pathizer vs. Manual XER Review
If your team already compares XER files by hand, you know the method works — and what it costs in specialist hours every data date. Pathizer runs the same read deterministically, on every update, with the evidence trail built in.
Run it against a review your team already finished — and compare the reads.
Task By Task
Compare two XER updates
Export both files, diff activities in spreadsheets, and reconcile added, deleted, and modified rows by hand.
The engine compares every update pair automatically — activities, relationships, durations, and constraints.
Trace float erosion to paths
Chase total float activity by activity and rebuild the float paths that matter from memory and filters.
Float movement is mapped to phase and float paths on every update, with erosion flagged before it hits zero.
Identify what drove the movement
Correlate logic edits, duration changes, and progress by inspection — and hope nothing was missed.
Driver attribution ranks the activities and logic edits that carried the movement, each with a confidence level.
Separate progress from revisions
Manually distinguish what the work did from what the scheduler changed — the hardest call in any review.
Half-Step Analysis makes the split explicit: progress-related impacts versus schedule revisions, update by update.
Assemble evidence for review
Screenshot, annotate, and file the backup by hand so conclusions can be defended later.
Every finding is source-linked to its XER rows automatically — the evidence ledger builds itself as you review.
Write the executive narrative
Draft the update story from scratch for the owner meeting, every single cycle.
An evidence-backed narrative drafts itself from the schedule record; your team edits and owns the language.
Repeat next data date
Start over. Quality depends on who does the review and how much time they have that week.
The same deterministic methodology runs on every update, every project — inspectable and consistent.
Manual review typically costs hours of senior scheduler time per update pair, and the depth varies with the week. The engine runs the full read on every update — your team spends its time on judgment, not reconciliation.
What Stays Yours
Every finding is supported by activity-level schedule evidence.
Visualize phase paths, float paths, and schedule logic.
Measure delay, recovery, and impact in days.
Built for project controls, accountability review, and executive decisions.
Upload the same update pair your team already compared and see what the engine reads — free, on your own schedule record.