How to Get More Out of Your P6 Schedule Comparison

Comparing two versions of a Primavera P6 schedule is one of the most routine tasks in construction project controls — and one of the most underestimated. Most schedulers know how to run a basic comparison. Fewer get everything that a thorough comparison can tell them.

This post walks through what a complete schedule comparison should cover, what to focus on in the output, and how to make sure the results are actually useful to the people who need them.

Start With What Changed — Activities First

The most obvious starting point is the activity list. A comparison should tell you:

• Which activities were added since the last update
• Which activities were removed
• Which activities were modified — and exactly which fields changed

For modified activities, you want before-and-after values for every changed field: dates, durations, float, status, percent complete, constraint type, and WBS assignment. A list that just says "Activity A1050 changed" is not useful. You need to know what changed and by how much.

When reviewing activity changes, pay particular attention to changes in activity type — a task-dependent activity becoming a level of effort, for example, can have significant implications for how the critical path is calculated.

Logic Changes Are the Most Important Thing to Check

Here is a truth that experienced schedulers know: the most consequential schedule changes are often not to dates at all. They are to logic.

A predecessor relationship that gets modified, removed, or replaced can shift the critical path without any date on any activity obviously moving. A new finish-to-start link gets added and suddenly a string of activities that used to run in parallel are now sequential. None of this shows up in a simple date comparison.

A thorough schedule comparison looks specifically at the relationships table — not just the activity list. For every modified, added, or removed relationship you want to see:

• The predecessor activity ID and name
• The successor activity ID and name
• The relationship type (FS, SS, FF, SF)
• The lag value before and after

Change Inspector's Relationships tab shows exactly this for every changed predecessor-successor link, flagging additions, removals, and lag modifications separately.

Float Movement Tells You About Schedule Health

Float values — total float and free float — are one of the most information-rich signals in a schedule comparison. Looking at how float changed between two updates tells you:

• Which activities are moving toward the critical path
• Where schedule compression is occurring
• Whether overall schedule health is improving or deteriorating

An activity that had 30 days of total float in the baseline and now has 8 days has consumed 22 days of buffer. That might be expected. Or it might be a warning sign that deserves attention before the next update cycle.

Change Inspector's Float Consumption analysis (in the Health Check module) shows the top activities by float consumed between two files, with before-and-after values and a warning flag for any activity that transitioned from positive float to critical between the two schedules.

Check Schedule Options — Not Just Activities

One thing many schedulers overlook is that two XER files from the same project can produce different results not because the schedule changed, but because the schedule calculation settings changed.

If the float type changes, or if Retained Logic switches to Progress Override, or if the critical float threshold shifts — any of these can cause apparent changes in float and dates that have nothing to do with actual project progress.

Change Inspector's Schedule Options tab compares the P6 calculation settings between two files — retained logic, float type, critical float threshold, data date, and nine other settings — and flags any differences at the top of the tab. This is the first thing to check when you see unexpected float or date changes in the Activities tab.

Make the Output Useful to Your Audience

A comparison report that only the scheduler can interpret is only half a solution. Depending on who needs the information, you may need the output in different forms:

• For the project team: a summary of the most significant changes, organized by WBS, with plain-English explanations of what shifted and why
• For the owner: a formatted report showing all changes against the approved baseline, organized and color-coded, with a clear executive summary
• For subcontractors: a targeted report showing changes to their scope only
• For claims documentation: a comprehensive, record of every change, formatted for attachment to a Time Impact Analysis or forensic schedule review

Change Inspector exports comparison results to Excel with color-coded formatting, organized by change type, suitable for all of these purposes without manual reformatting.

How Often Should You Run a Comparison?

Every schedule update should be compared against the previous update. Not just when something seems wrong — every time. The value of schedule comparison is cumulative: you build a running record of how the schedule has evolved, which gives you the context to spot patterns that a single comparison would miss.

A subcontractor whose milestone slips two days in each of six consecutive updates has a 12-day problem that no individual comparison would flag as significant. The pattern only becomes visible when you look across all the updates.

Use the Schedule Log in Change Inspector to catalog every schedule file in chronological order, record metadata for each update, and then run comparisons across any two files in the log. The running record is there when you need it — for a monthly report, or a claims situation six months down the line.