Schedule Levels 1 to 5
Last reviewed 9 September 20262,528 words11 min read
L1 to L5, and who reads which
🟩 In one line — Schedule levels are five layers of the same plan, from a one-page milestone chart (Level 1) to a daily crew list (Level 5); the contract baseline is almost always Level 3, Levels 1 and 2 are rolled up from it in P6 rather than maintained separately, and Levels 4 and 5 are built with the people doing the work.
👤 Who this is for — Juniors who keep hearing "Level 3" without a definition, and mid-level planners writing a programme submission where the client spec says one thing and the contract says another. You should already know what a WBS is and what a CPM network does.
First, let's be honest about why this page exists
"Level 3" is the most-used and least-defined phrase in planning. A client's project manager says "we want a Level 4 programme" and means "more detail than the last one." A contractor submits 14,000 activities and calls it Level 3 because that's what the spec asked for. A director opens the 6-page Level 2 and says "this isn't a programme, where's the logic?" Everyone is talking past each other because they think level means activity count. It doesn't. A schedule level is defined by who uses it and what decision it supports.
Getting it wrong costs real money in two directions. Submit too much detail as your baseline and you'll spend the next three years updating 14,000 lines every month, every trivial slip becomes a reportable variance, and the client's reviewers get to comment on your foreman's Tuesday. Submit too little and your programme can't carry a delay analysis, because the delayed work is buried inside a 120-day bar called "MEP Installation Tower."
🟨 The standard — what "good" looks like
AACE RP 37R-06 (Schedule Levels of Detail — As Applied in Engineering, Procurement and Construction) is the reference. It defines Levels 1 to 5 by purpose, audience and typical content, and it is explicit that levels are about hierarchy and use, not line count. It also draws the important line: Levels 1–3 are typically planner-produced and integrated in one CPM model; Levels 4–5 are execution tools built by field supervision from the Level 3.
AACE RP 27R-03 (Schedule Classification System) is a different axis and is routinely confused with 37R-06. 27R-03 classifies schedules by maturity of project definition (Class 5 concept through Class 1 detailed), parallel to the cost estimate classes in RP 18R-97. A Class 3 schedule and a Level 3 schedule are not the same thing. Say "Level" for detail, "Class" for maturity.
GAO Schedule Assessment Guide, Best Practice 5 requires the schedule to be traceable horizontally (logic across the network) and vertically (summary dates consistent with detailed dates). Vertical traceability is the technical name for "your Level 1 must roll up from your Level 3, not live in PowerPoint."
FIDIC 1999 Cl 8.3 asks for a programme showing the order and timing in which the Contractor intends to carry out the Works, with a supporting report on methods and resources. FIDIC 2017 Cl 8.3 is more prescriptive about programme content and supporting report — it is describing a Level 3 network with method and resource narrative. NEC3 and NEC4 Cl 31.2 list what the programme must show: order and timing, float, time risk allowance, method statements and resources — again a Level 3 with a Level 4-type method layer underneath.
DCMA 14-Point doesn't name levels, but its metrics (High Duration at 44 working days, Metric 8; logic and float tests) presuppose an activity-level Level 3 network. Run it on a Level 2 and everything fails; run it on a Level 5 and it's meaningless.
🟢 Rule to remember: the level is set by the reader and the decision, not the row count — and every level above 3 must be produced from Level 3, never beside it.
How it actually works
Here is the hierarchy as it is actually used on Gulf projects. Activity counts are for a mid-size building or plant, purely indicative.
| Level | Common name | Who reads it | Typical form | Indicative size | Who produces it |
|---|---|---|---|---|---|
| 1 | Executive / Milestone summary | Board, client executives, lenders, authority | One page of bars and milestones | 10–30 lines | Planner, rolled up from L3 |
| 2 | Management summary | Project director, client PM, consultants | Bars by phase and area, key interfaces | 50–300 lines | Planner, rolled up from L3 (hand-built at tender) |
| 3 | Project control / CPM baseline | Planner, construction manager, client reviewers, delay analysts | Full logic network, resource loaded, calendars, constraints | 500–5,000 activities | Planner with discipline leads |
| 4 | Detailed working / look-ahead | Superintendents, section engineers, subcontractors | 4–6 week window, zone by zone, crew level | 2–5 tasks per L3 activity in the live window | Construction team, planner supports |
| 5 | Daily / hourly task list | Foremen, permit coordinators | Daily plan, hour-by-hour in shutdowns | Per crew, per day | Foremen and supervisors |
Level 3 is the schedule. Everything else is a view of it or an extension of it. On a typical building in the UAE, a Level 3 activity is a discrete piece of work in one zone, one trade, with a duration between about 5 and 44 working days. "Slab formwork, Level 14, Zone A — 3 days" is Level 4 territory. "Structure Level 14 — 7 days" is a healthy Level 3 activity. "Superstructure Tower — 210 days" is Level 2.
Levels 1 and 2 in P6 are layouts, not projects. Use View → Group and Sort to group by WBS and collapse to the level you need. For Level 1, flag milestones with an activity code (Enterprise → Activity Codes → "Report Level" = L1) and apply a filter. Print with a one-line-per-WBS layout and the summary bars come from the detail underneath. The moment someone builds a separate Level 1 in Excel or PowerPoint, the dates diverge within a month — and the diverged version is the one the director shows the client.
Level 4 has three practical homes. Steps inside the Level 3 activity (Activity Details → Steps) — good for repetitive work, keeps one file. A separate P6 project with a small number of links back to the Level 3 — good when a subcontractor runs their own detailed programme. Or a controlled Excel look-ahead that quotes the Level 3 activity ID on every row. Any of the three works. What doesn't work is a Level 4 with no traceability, because then nobody can tell whether the look-ahead is ahead of or behind the baseline.
Level 5 belongs to the field. In a shutdown, Level 5 is the schedule — hour-by-hour, and the planner lives in it. On a building, it's the foreman's daily allocation and the planner should see it, not write it.
Consistency across disciplines matters more than depth. A Level 3 where civil is broken to pour-by-pour and MEP is one 90-day bar per floor is not a Level 3. It's two schedules stapled together, and the critical path will run through the civil work simply because that's where the logic is.
📜 Which level is the contract programme
Read the spec and the conditions together. Most ADNOC-type or Aramco-type specifications explicitly require a Level 3 CPM baseline, resource loaded, with a Level 4 ninety-day or six-week look-ahead updated weekly. Building contracts under FIDIC often say nothing about levels, in which case Cl 8.3 (either edition) is asking for what the industry calls Level 3, plus the supporting report.
Do not submit a Level 4 as the contract baseline, even if the client asks for it. Explain that the baseline is the instrument for measuring delay and change; the look-ahead is the instrument for running the site. Merging them means every re-sequencing decision a superintendent makes on a Wednesday becomes a "departure from the baseline" and a letter. Under NEC, where the Accepted Programme is revised regularly (Cl 32), this is slightly less painful, but the principle holds: the Accepted Programme should be at the level where the Project Manager can judge practicability (Cl 31.3), not at the level where they can redirect your gangs.
🟥 Where people go wrong
- Believing level equals activity count. A 200-activity Level 3 for a substation is fine. A 6,000-activity Level 3 for a refinery unit is fine. The test is whether each activity is a single trade in a single location with a duration you can measure progress against — not whether you've hit a number somebody once mentioned in a meeting.
- Submitting a Level 4 as the baseline to look thorough. It impresses at the first review and then destroys you monthly. Updating 12,000 activities means statusing gets delegated, quality drops, and the client's reviewers now have twelve thousand things to comment on.
- Maintaining Level 1 and 2 outside P6. The director's PowerPoint milestone chart is edited by hand for the board meeting. Three months later it shows a completion date the P6 file hasn't shown since February. When the claim comes, that slide is disclosed.
- A Level 3 with one phase left at Level 2. Commissioning is the usual victim: "Testing and Commissioning — 90 days" on a data centre where T&C is the project. If a phase is where the risk is, it needs the same granularity as the rest.
- Confusing AACE Class with AACE Level. A tender programme can be a Class 4 (early definition) and still be built to Level 3 detail in the areas that matter. Reviewers who conflate the two will ask why your "Class 3" has 40-day activities.
- Uneven granularity across disciplines. Civil at pour level, MEP at floor level, façade as one bar per elevation. The float and criticality you report is then an artefact of where you bothered to put logic.
- No coding to support roll-up. If milestones aren't coded and the WBS doesn't reflect the reporting structure, producing the Level 1 becomes a manual job every month, which is exactly how the separate PowerPoint version gets born.
⚖️ When you're challenged
"The spec says Level 3. Why do you only have 1,400 activities?" "Level 3 is defined by content, not count — AACE 37R-06 is clear on that. Every activity here is one trade in one zone with a measurable quantity, durations are all inside 44 working days, and the network passes the DCMA checks. If there's an area you'd like broken down further, tell me which one and I'll show you the Level 4 behind it."
"Can I have the Level 1 by tomorrow morning?" "You can have it in twenty minutes. It's a layout on the same file, so the dates will match what we submitted last month exactly. I'd rather not hand-draw one, because then it stops matching."
"Why does the six-week look-ahead show a different sequence from the baseline?" "The look-ahead is Level 4 — it's how the site is executing Level 3 activities this month. The Level 3 dates and logic haven't changed; the superintendent has split Zone A into two pours to suit the pump position. Each look-ahead line quotes the Level 3 ID, so you can trace it."
"The client wants the Level 4 as the baseline. They're paying." "We can give them the Level 4 as an attachment every week. If it becomes the baseline, every weekly re-sequencing becomes a formal departure and the delay measurement gets buried in noise. That doesn't help them either. The spec asks for Level 3 as the baseline and a Level 4 look-ahead — that's the right split."
📄 Related pages
- WBS Structure Design — the WBS is what makes Level 1 and 2 roll up without effort
- Activity Duration Limits — where the 5–44 day Level 3 band comes from
- Weekly Report and Look-Ahead — Level 4 in practice; three-week and six-week windows
- Milestones and Key Dates — coding milestones so Level 1 is a filter, not a drawing
- Tender Programme — Level 2 built top-down before you have a Level 3
- Shutdowns and turnarounds — the one sector where Level 5 is the contract schedule
- Client schedule specifications — how owner specs phrase the level requirement
- DCMA 14-point assessment — the checks that presuppose a Level 3 network
✏️ Worked example
A 24-storey residential tower with a 3-level podium, Dubai. Structure is flat slab, table formwork, target floor cycle of 7 working days on a 6-day calendar. This is how "Structure Level 14" looks at each level.
| Level | What appears | Duration shown | Where it lives |
|---|---|---|---|
| 1 | Milestone: "Tower Structure Topped Out" | Single date | Filter on activity code L1 |
| 2 | Bar: "Tower Superstructure L4–L24" | 21 floors × 7 days = 147 working days | WBS summary, collapsed |
| 3 | Activity: "Structure L14" with FS link from L13 and to L15; separate activity "Structure L14 — Post-tensioning stress" | 7 days | The baseline network |
| 4 | Zone A columns (2d), Zone B columns (2d, SS+1), Table forms shift (2d), Slab rebar (3d), MEP sleeves and embeds (2d), Pour (1d) | Overlapping within the 7 days | Steps on the L3 activity, or the weekly look-ahead |
| 5 | Tuesday: 14 fixers Zone A slab, 6 carpenters strip L12 Zone B, pump booked 05:00 Thursday | Daily | Foreman's whiteboard and daily report |
Activity counts across the whole tower:
| Level | Lines | Comment |
|---|---|---|
| 1 | 14 | Milestones only, including 3 contractual |
| 2 | 160 | Phase × area summaries |
| 3 | 2,350 | The contract baseline, cost and manhour loaded |
| 4 | ~240 live at any time | Six-week window; roughly 5,800 over the project life |
| 5 | Per crew, per day | Never in P6 |
Notice that the Level 2 duration of 147 days is not typed anywhere. It is the sum of 21 Level 3 activities. When Level 17 slips two days because of a pump breakdown, the Level 2 bar moves, the Level 1 milestone moves, and the director's chart is correct without anyone touching it. That is what vertical traceability means in practice, and it is the whole argument for building levels down from one file.
📖 References
- AACE International RP 37R-06, Schedule Levels of Detail — As Applied in Engineering, Procurement and Construction
- AACE International RP 27R-03, Schedule Classification System
- AACE International RP 18R-97, Cost Estimate Classification System (for the Class/Level distinction)
- GAO Schedule Assessment Guide (GAO-16-89G), Best Practice 5 — horizontal and vertical traceability
- FIDIC Conditions of Contract for Construction 1999, Cl 8.3; FIDIC 2017, Cl 8.3 (check against your copy)
- NEC3 ECC Cl 31.2, 31.3; NEC4 ECC Cl 31.2, 31.3, 32
- DCMA 14-Point Assessment, Metric 8 (High Duration)
- Oracle Primavera P6 Professional User Guide — Group and Sort, Activity Codes, Activity Steps
From the field
Experience from working planners. Unreviewed — read it as experience, not guidance.
Add what you know about schedule levels 1 to 5. What worked, what the consultant pushed back on, what you would do differently next time. A paragraph is plenty.
Contributors get their name and one link on the site — your own templates, course or consultancy. We take nothing and hold nothing.
Add your experience