Desktop P6 Professional workflow. Menu labels are aligned with Oracle’s current Version 26 help; older 24.x deployments may show minor wording or privilege differences.
Key takeaways
- Create and assign baselines as two separate controlled steps.
- Verify bars, columns, variance fields, and earned-value baseline settings after assignment.
- Never update, replace, or restore a governing baseline without approval and an audit record.
Creation is not assignment
Project > Maintain Baselines stores a copy or converts another project. Project > Assign Baselines selects the project baseline and primary, secondary, and tertiary comparison baselines. Verify the bars and variance columns after both actions.
Protect the yardstick
Updating an in-progress baseline can overwrite selected project or activity data. Preview changes, preserve a backup, record approval, and understand which calculated dates are not directly updated. Re-baselining and updating a baseline are governance decisions, not routine file maintenance.
Create and assign an accepted baseline
Perform the quality and approval gates before creating the record in P6.
Menu path: Project > Maintain Baselines; Project > Assign Baselines
Before you start
- Approved native schedule
- Approval record and date
- Baseline naming convention
- Maintain Baselines privilege
Preserve the accepted file
Retain the exact native schedule and approval record outside the editable current project.
Verify: Checksum, filename, project ID, and approval date are recorded.
Create the baseline
Choose Project > Maintain Baselines > Add and save a copy of the current project as a new baseline.
Verify: The baseline appears with a descriptive name, type, and creation date.
Name and classify
Rename the generated baseline and assign the organization’s baseline type.
Verify: The name identifies purpose, approval, and date without ambiguity.
Assign it
Choose Project > Assign Baselines and set project and primary comparison baselines; assign secondary or tertiary only for a defined purpose.
Verify: The intended names appear in every assignment field.
Display and reconcile
Add baseline bars and variance columns to a controlled layout.
Verify: Sample activities and contractual milestones match the accepted native file.
Lock the record
Restrict privileges and enter the baseline in the change-control register.
Verify: Later edits require documented authorization and can be audited.
Field-ready control
Baseline control gate
- Exact approved file retained
- Approval record linked
- Baseline created and named
- Project and primary baselines assigned
- Bars and variance columns verified
- Earned-value baseline setting checked
- Privileges and change control confirmed
Common questions
Can an in-progress baseline be updated?
P6 supports selective baseline updates, but that is a consequential governance action. Preview the exact changes, preserve the prior baseline, obtain authorization, and verify the result. Creating a new controlled baseline is often clearer.
Sources and scope
Follow the reference trail.
This guide is original educational commentary. Kairos reference records identify the source organizations, editions and scope behind this guidance. The original publishers retain their publications and rights.
Create a baselineOracle · checked 2026-08-01Assign baselines to projectsOracle · checked 2026-08-01Update a baselineOracle · checked 2026-08-01Primavera P6 Professional User Guide, Version 26Oracle · checked 2026-08-01Schedule Assessment Guide: Best Practices for Project SchedulesU.S. Government Accountability Office · checked 2026-08-01