Query on Primaver Intermediate Schedule

I would step back from the Global Change altogether — the Planned date fields are the wrong lever here, and P6 will do what you are after natively.

Planned Start, Planned Finish and Original Duration are interdependent: P6 derives one from the other two. That is why it rejects combinations it considers inconsistent, and why those 302 records refuse. More to the point, even where the change succeeds you are overwriting the contractor's original durations, so any duration variance you report afterwards is meaningless.

Instead, import the Week 29 XER as its own project in the EPS and close it. Then open Week 30 and use Project, Maintain Baselines, Add, "Convert another project to a new baseline of the current project", pick Week 29, and finally Project, Assign Baselines to set it as both the Project Baseline and your primary. The baseline copy keeps Week 29's actuals and its own data date, which is precisely the snapshot you were trying to manufacture by hand.

For the weekly comparison I would then report on BL Project Start and BL Project Finish against Start and Finish, plus Variance - BL Project Finish.

Worth keeping every received XER as a separate project rather than overwriting. It costs nothing and you will want the trail if the delay argument ever gets serious.

Which columns are you comparing at the moment?

CritcalPathPress,
Here's a professional reply you can post on Planning Planet.

Thank you for your detailed explanation.

My objective is to compare the contractor's Week 29 submission (Data Date: 25-Jun-2026) against Week 30 (Data Date: 09-Jul-2026) from the client side. I receive weekly XER files but do not update the contractor's schedule.

The reason I tried the Global Change approach was that when I imported the Week 30 XER and assigned the Week 29 project as the baseline using Maintain Baselines and Assign Baselines, the baseline dates did not reflect the Week 29 status. For many activities, the baseline appeared to retain older planned dates rather than the Week 29 status dates I expected.

My intention was to create an "intermediate/status baseline" where:

• Completed activities reflected their Actual Start/Actual Finish as of Week 29.
• In Progress activities reflected Actual Start and the Week 29 forecast.
• Not Started activities reflected the Week 29 planned dates.

That is why I explored Global Change.

From your explanation, it sounds like I may have misunderstood how P6 stores baseline data. If converting the Week 29 project into a baseline should already preserve the Week 29 actuals and data date, then I clearly need to understand why that is not happening in my case.

Regarding your question, I am mainly comparing:

• BL Project Start vs Start

• BL Project Finish vs Finish

   

Have you encountered a situation where assigning a previous week's project as the baseline does not preserve the Week 29 status dates? If so, could there be a project setting or import option that causes P6 to use older planned dates instead?

This reply acknowledges their advice, explains why you tried Global Change, and redirects the discussion to the original problem: why the assigned Week 29 baseline did not reflect the Week 29 status snapshot. It is likely to elicit more targeted technical responses.