Group & Sort decides how a schedule’s activity table is organised on screen. Grouping puts activities into bands, for example by WBS, by an activity code such as area or trade, or by a field such as total float. Sorting orders the activities inside each band. P6 users know it from the Group and Sort dialog. It changes only the view, never the plan.
Worked example
Illustrative: a scheduler groups a hospital schedule first by floor (an activity code), then by trade, and sorts by start date. Each floor band shows its earliest start, latest finish, lowest float and total cost. Switching the first level to total float in 5-day bands turns the same plan into a near-critical review without editing a single activity.
Why it matters
Reviewers read schedules by area, by trade or by responsibility, not by activity ID. Group totals answer “when does Level 3 finish, and how much float does it have?” at a glance. Grouping can hide the logic, so a good review pairs it with the critical path and the longest path.
How os.construction handles it
The Planner’s Group & Sort takes up to five levels by WBS, any activity code, any UDF or any field, with intervals for numbers and dates. It shows group and grand totals aligned under their columns, and a Gantt summary bar for every band. The settings are saved in the layout.