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
- Confirm project, data date, completion condition, and options before F9.
- Preserve the schedule log and compare the result with the prior accepted calculation.
- Never move the data date or alter options only to obtain a preferred finish.
The data date separates fact from forecast
Actual starts and finishes should be supported history on or before the data date; remaining work should be forecast forward. Invalid progress on the wrong side of the line is a status-quality defect, not something the scheduling engine can fix automatically.
Options change the answer
Out-of-sequence handling, critical-activity definition, float basis, multiple-float-path settings, open-project treatment, and calendar behavior can change dates or interpretation. A formal submission should retain the settings and schedule log.
Run a controlled P6 schedule calculation
Use this procedure for formal baselines, updates, and analytical copies.
Menu path: Tools > Schedule (F9)
Before you start
- Native backup or controlled working copy
- Approved data date
- Documented scheduling options
- Named completion milestone
Confirm the project set
Close unrelated projects or document every open project and external relationship included in the calculation.
Verify: The scheduling dialog lists only the intended project set.
Set the data date
Enter the agreed cutoff for each open project.
Verify: The date matches the reporting period and status evidence.
Review Options
Inspect out-of-sequence behavior, critical-activity definition, float calculation, lag calendar, external-project treatment, and multiple-float-path settings.
Verify: Options match the approved schedule basis or the analytical purpose.
Enable the log
Select Log to File and use a controlled filename containing project ID, data date, and purpose.
Verify: The output path is known and writable.
Schedule
Run the calculation and read every warning before accepting the result.
Verify: The log records the intended data date, settings, activity counts, and exceptions.
Validate the output
Inspect finish milestones, longest path, negative float, open ends, invalid progress, and changes from the prior calculation.
Verify: Every material change has an identifiable input or status cause.
Field-ready control
F9 calculation record
- Intended project set only
- Approved data date
- Options recorded
- Completion milestone named
- Schedule log saved
- Warnings dispositioned
- Finish and path changes reconciled
- Native result retained
Common questions
Why did the finish change when I only changed a scheduling option?
Options affect how P6 handles out-of-sequence work, float, criticality, lag calendars, open projects, or other calculation conditions. Treat options as controlled model inputs.
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.
Schedule a projectOracle · checked 2026-08-01Scheduling projectsOracle · 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