Schedule Levels of Detail
One project, five altitudes — the same schedule shown from the executive's 30,000-foot milestone view down to the foreman's daily task list, all rolling up from one network. Levels are about presentation; classification is about maturity. Built on AACE 37R-06.
Why one schedule needs many views
This is different from classification (last lesson). Class is about a schedule's maturity; levels are about presentation — how much of a (given) schedule you show. A single mature schedule can be rolled up or drilled down across all five levels at once.
The five levels
Tap a level to see who it's for, what it contains, and what it's used for.
Level explorer
ExploreTap a level to see who it's for, what it contains, and what it's used for.
Milestone summary
The whole project on one page: major milestones and key phases. For executives and owners who need the big picture and headline dates — not how the work gets done.
| Level | Name | Audience | Shows |
|---|---|---|---|
| 1 | Executive / master | Executives, owner | Key milestones & phases — one page |
| 2 | Management summary | Senior PM, sponsors | Major areas/systems by phase |
| 3 | Project control | Project team | The control baseline — CPM with logic |
| 4 | Execution | Supers, leads, subs | Detailed activities by area/discipline |
| 5 | Detail / short-interval | Foremen, crews | Daily/weekly tasks, lookaheads |
All levels roll up from one schedule
The single most important principle: the levels are views of one network, not separate documents. Level 5 detail rolls up into Level 4, which rolls up into Level 3, and so on. Done right, you maintain detail in one place and summarize upward — the executive's milestones and the crew's lookahead are always telling the same story.
Get the altitude right
Choosing the level isn't about taste — it's about the decision the reader has to make. A useful way to think about it:
| If the reader needs to… | Show them |
|---|---|
| Decide go/no-go, report to the board | Level 1 — milestones |
| Track major areas and interfaces | Level 2 — summary |
| Manage the baseline, run delay analysis | Level 3 — control CPM |
| Coordinate trades and work fronts | Level 4 — execution |
| Run the crews this week | Level 5 — short-interval / lookahead |
Ten things to remember
- Levels of detail = the same schedule at different zoom levels, one per audience.
- Levels (presentation) ≠ classification (maturity) — don't confuse the two.
- Level 1 = milestones for executives; Level 5 = daily tasks for crews.
- All levels roll up from one network — never maintain disconnected summaries.
- Disconnected levels = multiple versions of the truth — the schedule that drifts.
- Match detail to the decision — too much buries; too little starves.
- Level 3 (control) is the anchor — the baselined CPM analysis runs against.
- Summarize upward (1–2), elaborate downward (4–5) from the control schedule.
- Use WBS / coding to roll up cleanly — the structure that makes summarizing automatic.
- Level 5 lookaheads drive the field — short-interval planning off the same baseline.
Glossary
- Level 1 (master)
- Executive milestone summary — the whole project on a page.
- Level 3 (control)
- The baselined CPM the team manages and analyses against.
- Level 5 (short-interval)
- Daily/weekly task and lookahead detail for the crews.
- Levels of detail
- A hierarchy of views (L1–L5) of one schedule, from milestones to daily tasks.
- Lookahead
- A short-window (e.g. 3–6 week) detailed forecast of imminent work.
- Roll-up
- Summarizing detailed activities into higher-level bars via WBS/coding.
- Summary schedule
- A higher-level view — sound only if it rolls up from the working schedule.
- WBS coding
- The structure that lets one network present cleanly at every level.