One schedule, three audiences — build exec, PMO and site views from one file

The board wants a one-page summary. The PMO wants the RAG and the earned-value numbers. The site lead only cares about their workstream, in full. Most teams answer that by keeping three separate schedules — and three schedules drift apart the moment the programme moves. Here's how to serve all three from a single file, with named views you save once and switch between in a click.

You know the failure mode because you've lived it. Monday morning, three requests land: the steering pack, the portfolio review, and "can you just send me the mechanical bit." So you carve the master into a boardroom slide, a PMO tracker and a filtered extract — three artefacts in three tools. By Thursday the programme has moved, and now three things are out of date instead of one. Someone quotes a stale handover date in a meeting. Everyone blames "the plan."

The mistake is treating each audience as a different schedule. It isn't. It's the same programme seen at a different altitude and through a different filter. Build the file once; then save the exec, PMO and site views as named lenses onto it. Switch, export or share-link each independently — but there is only ever one set of dates underneath.

Why three files always drift

A separate boardroom deck, a PMO spreadsheet and a site extract feel efficient the day you make them. The trouble is that each one is now a copy, and copies have to be maintained by hand. When an activity slips, you have to remember to touch all three — the slide, the tracker, the extract. Miss one and you've published a contradiction: the exec pack says June, the site plan says August, and nobody knows which is real.

This is the category tax. Screenshot-and-paste into slides, cloud work-OS boards rebuilt from the schedule, desktop presentation add-ins that snapshot a moment in time — they all fork the plan. The instant you fork it, you own the reconciliation forever. The fix isn't better discipline about updating three things; it's refusing to have three things. One file, and every audience reads a saved view of it.

Build once, then filter and collapse to each audience

The whole method rests on two controls you already have: outline collapse (which altitude — how much of the WBS is folded up into summary bars) and row filters (which slice — which activities are in scope at all). Combine them and you can carve any audience's picture out of the one file without deleting a single row.

• Exec = collapse hard, filter nothing. Fold the WBS up to Level 1 so each phase is a single summary bar, promote the gates to milestones, and you have the boardroom one-pager.
• PMO = collapse to Level 2, show the numbers. One tier lower — area summary bars per workstream — with RAG stoplights, %-complete pies and the EVM columns (CPI / SPI) switched on.
• Site = filter to one workstream, expand fully. Filter rows to Workstream = Mechanical (or an owner, a WBS branch, a tag), leave the detail expanded, and the site lead gets exactly their scope at full depth.

Nothing is destroyed to make any of these. The exec view still contains every activity — they're folded, not gone. The site view still contains the whole programme — the other workstreams are filtered out of sight, not removed. Clear the filter, expand the outline, and you're back to the full master in one click.

Save each as a named view, then export or share-link it

Once you've dialled a lens in, you don't want to re-dial it every month. Save it. A saved view stores the whole configuration — the filter, the outline collapse level, the visible columns, the RAG and EVM toggles, the theme — under a name. Then the three audiences become a dropdown: Exec, PMO, Site — Mechanical. Switch between them in a click, on the same file, live against the same dates.

1. Build the master once. Import the real programme — MS Project (XML), Primavera P6 (XER/XML), Excel or CSV — so the full logic-driven schedule lives in one file. It parses in your browser; nothing is uploaded. Get the WBS, calendars and progress right here, once.
2. Filter and collapse to the audience. For the exec, collapse the outline to Level 1 and promote gates to milestones. For the PMO, collapse to Level 2 and switch on RAG stoplights, %-complete pies and the EVM columns (CPI / SPI). For the site lead, apply a row filter — Workstream = Mechanical, an owner, a WBS branch or a tag — and leave the detail expanded.
3. Save the view with a name. Save each configuration as a named view: Exec — Board, PMO — Portfolio, Site — Mechanical. The filter, collapse level, columns and toggles all travel with the name. Switching audiences is now a single click, not a rebuild.
4. Export or share-link each independently. From any view, export what suits its audience — a landscape PDF or PowerPoint one-pager for the board, an Excel extract or tracker for the PMO, a PNG for the site's toolbox talk — or send a read-only share link that opens exactly that view in the recipient's browser, nothing installed. Each audience gets its own artefact; all of them read the one file.

Because a share link carries the schedule inside it (encrypted, nothing uploaded), the board partner, the PMO analyst and the site lead each open their view without a P6 licence and without anything installed. Three recipients, three tailored pictures, one file behind all of them.

The one-file app view

Here's how the whole thing looks in the app — the master with a workstream column, a section band per phase, automatic summary bars, milestones, a data date and the saved-view switcher up top. Flip the View dropdown and the exact same grid reshapes into the exec, PMO or site picture.

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.