Chennai HQ · serving India, UAE, Saudi Arabia and Omaninfo@projectassure.inCall us 24/7 +91 94895 88922
Project Assure
Schedule Quality

Primavera P6 baselines explained: how to set, assign and compare them

A P6 baseline is only useful if it is saved, assigned and then left alone. Here is how to set one, read the variance it produces, and document the basis behind it.

In short

A Primavera P6 baseline is a saved copy of the approved schedule, created in Project > Maintain Baselines and made active in Project > Assign Baselines. If it is not assigned, P6 compares the project with itself and all variance shows zero. Keep the original baseline untouched, save a new copy for each approved re-baseline, and keep a basis of schedule document that records scope, calendars, assumptions, exclusions and the sources of durations.

A baseline in Primavera P6 is a saved copy of the approved schedule that P6 keeps alongside the live project, so current dates, durations and costs can be measured against the plan. To set one, save a copy of the project in Project > Maintain Baselines, then assign it in Project > Assign Baselines. Until a baseline is assigned, P6 compares the project with itself and every variance shows zero.

A baseline is only useful if it is set at the right moment, assigned consistently and then left alone. This guide covers the steps, how to read baseline variance, the mistakes that spoil reporting, and the basis of schedule document that should sit beside the baseline.

What is a baseline in Primavera P6?

A baseline records the planned start and finish dates, durations, relationships, and resource and cost assignments at the point the programme is approved. P6 stores it as an inactive copy of the project, which is why a baseline can be compared, updated or restored. Without one there is no objective answer to "are we on time?" or "are we over budget?".

A project can hold several baselines. The maximum number per project is set by the administrator in Admin Preferences (Data Limits). Baselines are used through two kinds of assignment:

  • Project Baseline: set for the project as a whole. It feeds the project-level baseline fields and, by default, earned value calculations.
  • Primary, Secondary and Tertiary user baselines: set per user. They drive the baseline bars and the BL1, BL2 and BL3 columns in layouts, so two users can see different "baseline" bars on the same project.

The first baseline is usually the original approved baseline. Later baselines are saved when an approved change or recovery programme justifies re-baselining.

How do you set a baseline in P6?

  1. Finalise and schedule the programme. Logic should be complete, durations realistic, constraints justified, and resources and costs loaded if cost or earned value will be tracked. Schedule (F9) at the agreed data date. A quality check against the DCMA 14-point assessment before baselining avoids measuring progress against a flawed plan.
  2. Save the baseline. Go to Project > Maintain Baselines, select the project, click Add and choose "Save a copy of the current project as a new baseline". Rename it so its status is obvious, for example "BL00 Original approved 01-Mar-26".
  3. Assign the baseline. Go to Project > Assign Baselines. Set the Project Baseline and the Primary user baseline, normally to the same baseline, so reports and layouts agree.
  4. Check it worked. Add BL1 Start and BL1 Finish (or BL Project Start and BL Project Finish) columns and switch on the Primary Baseline bar. On the day of baselining, baseline dates should match current dates and every variance should be zero. In later updates, variance should start to appear.

The Maintain Baselines dialog in P6 Professional also offers Update, which copies selected data from the current project into an existing baseline, for example activities added by an approved change. It overwrites baseline values, so use it only under change control and never on the original approved baseline.

How do you read baseline variance in P6?

Once a baseline is assigned, the current schedule can be compared against it in several ways:

  • Variance columns: add the BL1 variance columns for start date, finish date and duration (or the BL Project equivalents). P6 calculates variance as baseline minus current, so a negative value means the activity is later than plan and a positive value means it is earlier.
  • Bars: show the current bar and the baseline bar in different colours in the Bars dialog. Slippage is visible at a glance.
  • Claim Digger: Tools > Claim Digger compares the project with a baseline and lists added, deleted and changed activities, relationships and field values. It is the quickest way to see what changed between baseline and update.
  • Earned value: with a cost or resource loaded baseline, P6 calculates planned value, earned value and actual cost, and from them schedule variance (SV), cost variance (CV), SPI and CPI. Building and reading these is core project controls and EVM work.

For example, if Activity A has a baseline finish of Monday 1 June and a current finish of Monday 15 June, on a five-day calendar with no holidays the finish variance is -10 days. P6 reports variance in working time, not calendar days.

What are the common baseline mistakes in P6?

These errors are common even among experienced planners, and each one undermines reporting:

MistakeConsequenceHow to avoid it
Baseline saved but not assignedP6 compares the project with itself, so all variance is zeroAssign it in Project > Assign Baselines and check the baseline columns
Updating or overwriting the original approved baselineThe approved plan is lost and true variance cannot be shownKeep the original untouched and save a new copy for each re-baseline
Project Baseline and user baselines pointing at different versionsReports, layouts and users disagree on what "baseline" meansAgree one convention, label baselines clearly and record which is assigned
Restoring and editing a baselineThe baseline no longer represents the approved planTreat baselines as frozen records of the approved programme
Baselining without resources or costsNo planned value, so no SV, CV, SPI or CPILoad resources and costs before baselining if earned value is required

Why keep a basis of schedule document with the baseline?

A baseline shows what the plan was. A basis of schedule document explains why. Keep one version-matched to each baseline, recording the scope covered and the WBS, the calendars used (working week, shifts, holidays and any weather allowance), the key assumptions on sequence, access, productivity and procurement, the exclusions, and the sources of durations such as estimates, productivity rates, subcontractor input or historical data. Note the data date, the baseline name and the reason for any constraints. When a delay is disputed or a re-baseline is challenged, this document is what makes the baseline defensible.

When and how should you re-baseline in P6?

Re-baseline when the approved plan has genuinely changed, for example through an approved scope change or a formally accepted recovery programme. Re-baselining to hide delay destroys the record of performance. Good practice:

  • Never delete the original baseline. Keep it for historical comparison.
  • Save a new baseline copy with a clear name and date, for example "BL01 Rebaseline 01-Jan-27", and assign it as the Project Baseline and Primary baseline.
  • Record the reason, the approval and the date in a change log, and issue a revised basis of schedule.
  • Use Claim Digger, or keep the original as a Secondary baseline, to show the effect of the change against the original plan.

Set baselines carefully, assign them consistently and leave the original alone. With a sound baseline and its basis of schedule, progress, delay and cost can be reported and defended. An independent reviewer such as Project Assure checks baseline assignment and baseline-versus-update changes as part of a schedule review.

FAQ

Common questions

What is a baseline in Primavera P6?
A baseline is a saved copy of the approved schedule, stored by P6 as an inactive copy of the project. It holds planned dates, durations, relationships, resources and costs, and is the reference for measuring progress and variance.
How do I set a baseline in Primavera P6?
Go to Project > Maintain Baselines, click Add and save a copy of the current project as a new baseline. Then go to Project > Assign Baselines and set it as the Project Baseline and Primary baseline, and check that the baseline columns show matching dates.
What is baseline variance in P6 and how do I see it?
Variance is the baseline value minus the current value, reported in working time, so a negative finish variance means the activity is later than plan. Add the BL1 finish date variance column, show the baseline bar, or use Tools > Claim Digger to list changes.
Can I have multiple baselines in one P6 project?
Yes. The maximum per project is set in Admin Preferences, and each project has one Project Baseline plus Primary, Secondary and Tertiary user baselines. Keep the original for history, label each baseline clearly and record which one is assigned.
Why does every baseline variance show zero in P6?
Usually the baseline was saved but never assigned, so P6 is comparing the project with itself. Assign it in Project > Assign Baselines; on the day of baselining zero variance is expected, but it should change after the first update.
Chennai city skyline at dusk under a vivid pink and violet sky

Bring this discipline onto your programme.

Every insight comes from live mandates. A principal replies within one working day.