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
- Build separate layouts for distinct operating and review questions.
- Disclose filters, baselines, grouping, timescale, and data date on formal outputs.
- Protect global and shared layouts; experiment in personal copies.
Design from the review question
A status-collection layout needs actual and remaining fields. A logic layout needs predecessors, successors, relationship types, lags, constraints, float, and trace logic. A baseline layout needs current and assigned baseline bars and variance columns. One overloaded layout rarely serves all three well.
Filters are disclosure items
Filters change which activities exist on screen and in many prints or exports. Name filtered layouts clearly, show filter criteria, and retain an unfiltered reconciliation view.
Create a controlled review layout
Start with a copy of a governed template and save under clear ownership.
Menu path: View > Layout > Save As; View > Columns / Group and Sort / Filters / Bars
Before you start
- Defined review purpose
- Required field list
- Approved code and baseline conventions
Copy the template
Open the closest governed layout and use Save As before changing it.
Verify: The new layout name states purpose and owner.
Choose evidence columns
Add identifiers, WBS/codes, status, dates, durations, float, constraints, and baseline variance needed for the question.
Verify: Every displayed metric has enough context to interpret it.
Group and sort
Use View > Group and Sort By > Customize to create a reproducible hierarchy and order.
Verify: Summary bands reconcile to the intended WBS, phase, area, or responsibility.
Apply and disclose filters
Create named filters with explicit criteria and test them against an unfiltered count.
Verify: The displayed population and excluded records are understood.
Configure bars and time
Add current, baseline, actual, remaining, and critical bars as appropriate; set a readable timescale and data-date line.
Verify: Bars reconcile to the corresponding table fields.
Save and test
Save the layout, reopen it, and test it with another project or user if it is intended for sharing.
Verify: The layout reproduces the same question without hidden personal settings.
Field-ready control
Professional layout check
- Purpose and owner in name
- Required identifiers visible
- Active filters disclosed
- Grouping and sort reproducible
- Baseline assignment verified
- Bars reconcile to columns
- Data date and timescale readable
- Global template not overwritten
Common questions
Can a layout change schedule data?
Most layout settings only change presentation, but editable columns allow data changes and some drag operations can modify dates or durations. Use read-only review practices and personal copies where appropriate.
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.
Group and sort a tracking layout using custom settingsOracle · 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