How-to·3 July 2026·8 min read

From 3,000 activities to one page: a Level 1 summary from a Level 3 P6 programme

Your detailed schedule is right. It's just unreadable in a boardroom. Here's the exact workflow to roll a heavyweight Primavera P6 programme up to a clean Level 1 or Level 2 summary in a few minutes — with the roll-up shown step by step, and without rekeying a single date.

Every planner knows the drill. The programme is a Level 3 monster — three, five, ten thousand activities, fully logic-linked, resource-loaded, immaculate. Then the monthly steering committee asks for "the one-pager." Suddenly you're back in the plotter room at 9pm, hand-building a summary in a slide deck, retyping dates you already have, and quietly praying nothing moved since you started.

It shouldn't cost you an evening. A Level 1 or Level 2 summary isn't a different plan — it's the same plan, viewed from higher up. The whole trick is to roll the detail up, not rebuild it. Here's the P6 view most boards never want to see, then exactly how to turn it into the page they do.

Fig 1. The Level 3 control schedule — correct, logic-driven, and completely unreadable at a glance. Everything a director needs is in here; the problem is it's in here with three thousand things they don't.

The one-pager is really a zoom level

The industry ladders schedules from Level 0 to Level 4/5 — the same programme at different altitudes:

Level 0 — a single bar or a few milestones: the whole project on one line.
Level 1 — executive summary: major phases and key milestones, board-ready.
Level 2 — a tier down: WBS- or area-level summary bars per workstream.
Level 3 — the control schedule: the detailed, logic-driven programme you run the project from (Fig 1).

So Levels 0–2 are Level 3, summarised. You don't draw them from scratch — you collapse into them. And a schedule that's built as a proper outline already knows how: every WBS parent is a summary of its children, waiting to be folded up.

Fig 2. The mechanic behind the whole trick. Fold a WBS node and Sketchedule draws one summary bar from the earliest start to the latest finish beneath it — the detail is hidden, not lost. Do it per level and the ladder appears.

The five-minute roll-up

Take a real one — the shape of an EPC capital project: engineering, procurement, six construction areas, mechanical completion, commissioning and start-up, all under a clean WBS. The directors want a single landscape page: the phases, the phase gates, and the handover milestone. Here's the version that takes five minutes instead of an evening.

Export from P6. In Primavera, export the programme as XER or Primavera XML (File → Export). No tidy-up needed — bring it exactly as it is.
Import into Sketchedule. Drag the .xer straight onto the app. It parses in your browser — nothing is uploaded, your programme never leaves your machine. The P6 WBS arrives as an outline: section headings and parent rows, with every activity nested underneath.
Collapse to the level you want. Click the collapse carets to fold thousands of activities up into their WBS parents (Fig 2). Sketchedule draws an automatic summary bar across each parent. Collapse to WBS level 2 for your Level 2; one tier higher for your Level 1. The detail stays in the file, just tucked away.
Keep the signal, hide the noise. Turn the area roll-ups into clean section bands, promote the phase gates and the handover date to milestones, and filter out anything that isn't part of the story. What's left: a handful of bars, a few diamonds, and a title (Fig 3).
Add the status story. Set the data date, fill progress to it, and add a status line so ahead/behind reads at a glance. Colour the phases by RAG, or show a %-complete pie per section. Now it's not just a summary — it's a status summary.
Brand it and ship it. Add your header, footer and logo, then export a landscape PDF or PowerPoint slide — or send a read-only link that rebuilds the whole picture in the recipient's browser. One page. Signed off.
Keep it in step next month. When the P6 is updated, hit Refresh and point it at the new file. Sketchedule re-syncs and shows you exactly what changed — dates moved, activities added, activities dropped — before you accept it. Your Level 1 tracks the real programme with a couple of clicks, not another late night.

Fig 3. The same programme as Fig 1, rolled up: four phase summary bars, the NTP / Design-freeze / Delivery / MC / Handover milestones, RAG status and the data-date line — built by collapsing, not redrawing. This is a faithful redraw of the EPC master-schedule example that ships in the app.

The whole point: you never retype a date. The summary's bars are the L3's dates, rolled up live — so when a director asks "is this current?", the honest answer is yes, and Refresh keeps it that way next month.

"But P6 already does summary bars" — yes, and that's the point

If you're a planner, you spotted this three figures ago: P6 collapses the WBS and draws summary bars natively. Group, summarise, filter, print — it's all there, and it's computed off the real schedule engine. Sketchedule doesn't replace any of that, and it isn't trying to.

The gap was never summarising — it's everything after it. A collapsed P6 layout is functional, not board-ready, which is exactly why planners still rebuild the summary in a slide deck at 9pm. Here's where the two actually part company:

Presentation, not just print. A branded single landscape page — logo, header/footer, clean typography, RAG stoplights, conditional symbology, curtains, a status line — is painful to coax out of P6. There's a whole cottage industry (P6-to-PowerPoint converters, Visualizer, manual rebuilds) precisely because native presentation is weak. That page is Sketchedule's entire job.
Compose the story, don't just fold the tree. A real Level 1 often isn't a clean WBS collapse — you want these six phases, merged and reordered, a couple hidden for commercial reasons, a callout added, a gate curtain drawn. P6's summary is rigid to the WBS structure; a presentation layer lets you build the picture you actually want to show.
Anyone can open it. P6 is heavyweight and licensed. The director who has to read the summary — or the bid partner who wants to tweak it — usually can't open a P6 layout at all. Sketchedule runs free in a browser, and a read-only link rebuilds the whole picture for someone with no P6 and nothing installed.
What-if without touching the master. Nudge the summary for a scenario slide, or compare two versions, without editing your live control schedule.

So the honest one-liner: P6 can summarise; it can't present. Sketchedule is the presentation front-end for the plan P6 already computes — a companion to the scheduling engine, not a replacement for it.

Where the source of truth stays. A summary bar here is the min-start / max-finish of its children — a picture, not a re-run of the network. Critical path, float and logic still live in P6; Sketchedule presents them. That division is deliberate: keep P6 as the engine, and stop hand-rebuilding its output for the boardroom.

Three ways to get the summary wrong

Burying the critical path

A roll-up that hides which phase is driving completion is decoration, not a schedule. Keep the driving path visible at summary level — highlight the critical phase bar, or call it out. The board should see where the risk sits, not just when the project ends.

Milestones that don't trace back

Every diamond on the one-pager should map to a real activity ID in the Level 3. When a director asks "where does that date come from?", you want a one-word answer, not a five-minute hunt through the detail.

Rolling up dirty inputs

A summary bar inherits the span of its children. If a child sits on the wrong calendar, or progress hasn't been brought to the current data date, the summary quietly lies. Roll up clean inputs and the picture is honest by construction.

Level	What it shows	How you get there in Sketchedule
L0	Whole project on one line / a few key dates	Collapse to the top WBS node, or a milestone-only view
L1	Major phases + key milestones (board)	Collapse to WBS level 1; promote gates to milestones; add data date + RAG
L2	WBS / area summary bars per workstream	Collapse to WBS level 2; section bands per area
L3	The detailed control schedule	The imported P6 file, fully expanded — your source of truth

Key takeaways

A Level 1/2 summary is a zoom level of the Level 3 — collapse into it, don't rebuild it.
Import the P6 XER/XML, collapse the WBS, and the summary bars draw themselves — no dates rekeyed.
Dress the story with a data date, RAG and milestones, then export a one-page PDF/PPT or a read-only link.
Refresh from the updated P6 each period — the board view tracks the real programme in a couple of clicks.
Keep the critical path visible and every milestone traceable to an activity ID, or the summary misleads.

Try it on your own programme

Open Sketchedule in a browser — free, no install, nothing uploaded. Drop in an XER and roll it up.

Start free →Open the EPC example

← BlogAll articles Try it →Open the EPC master-schedule example

Primavera and P6 are trademarks of Oracle Corporation; Microsoft Project is a trademark of Microsoft Corporation. Sketchedule is an independent product and is not affiliated with, endorsed by or sponsored by Oracle or Microsoft. Figures are illustrative, drawn in Sketchedule; Fig 3 is a faithful redraw of the EPC master-schedule example that ships with the app.