Schedule Comparison
What changed between two programmes — where problems hide.
What it is
Comparing two schedules — current against baseline, or update to update — to see exactly what changed: dates, durations, logic, and added or deleted activities.
Why it matters
Most control failures and most disputes hide in what changed between versions. P6’s Schedule Comparison (Claim Digger) surfaces it systematically.
In practice
- Use Claim Digger / Schedule Comparison to diff two schedules rather than eyeballing them.
- Compare logic changes, added and deleted activities, duration and constraint changes — not just dates.
- Undisclosed logic changes between updates are a red flag in any review.
- Retain every issued update — you cannot compare what you did not keep.
Watch for
- Reviewing only dates and missing silent logic changes.
- No retained history to compare against.
- A baseline changed without record, defeating variance analysis.