Swimlane a programme by workstream: one wall chart, three audiences

A portfolio isn't hard to schedule — it's hard to show. Here's how to turn a flat activity list or a merged multi-plan master into a wall chart with a clean swimlane band per workstream, area or owner, drop gate curtains between the phases, and filter the same file so one deliverable serves the leadership room, the PMO and a single lane lead.

You've merged five sub-project plans into one master, or you've been handed a flat register with an "Area" column, and now someone wants "the programme on a wall." The dates are fine. The logic is fine. What's missing is a way to make a director glance at it and instantly see who's doing what, when — Engineering here, Construction there, and the gate that separates them drawn as a hard line, not left to the imagination.

That's a swimlane: a horizontal band per workstream, with every activity that belongs to it living inside its lane. It's the single most legible way to present a programme to people who don't live in the schedule. And it's a view, not a rebuild — you're grouping and banding rows you already have, not redrawing anything.

Lanes can be anything you can group by

The lane is whatever dimension your audience thinks in. On a capital job it's usually the EPC phases — Engineering, Procurement, Construction, Commissioning. On a PMO portfolio it's one lane per project. On a delivery team it's one lane per responsible person, so the wall doubles as an accountability chart: every bar sits under the name that owns it.

If the field exists on your activities — an area code, a resource, an owner, a P6 activity code, a spreadsheet column — Sketchedule can band on it. That's the important part: swimlaning isn't a special mode you have to plan the schedule around. It's a lens you drop over data you already have.

Build it in four moves

Take a real shape — a mid-size capital programme: engineering, long-lead procurement, two construction areas, and commissioning, all feeding a single handover date, with a hard "Ready for construction" gate in the middle. The board wants it on one landscape page. Here's the build.

1. Group rows into lanes. Import the master (MSP XML, P6 XER/XML, Excel or CSV — it parses in your browser, nothing is uploaded) and group by the field that defines your lanes: phase, area, sub-project or owner. Each group becomes a swimlane band with its activities nested inside, and an automatic summary bar across the top if you want the lane's overall span at a glance.
2. Set the band shading per lane. Turn on swimlane bands so each workstream gets its own full-width background stripe — faint, alternating, so the eye separates Engineering from Procurement without a single gridline. Colour the bars per lane (blue Engineering, purple Procurement, green Construction, teal Commissioning) and the chart reads itself.
3. Drop curtains at the gates. Add a curtain — a vertical band or dashed line spanning every lane — at each stage gate: "Design freeze", "Ready for construction", "Mechanical completion". The curtain cuts across all the swimlanes at once, so a phase gate stops being an invisible convention and becomes a line everyone can point at. Promote the handover date to a milestone diamond.
4. Filter to the audience. Save the full wall as one view, then use filters and saved views to cut it down. The board gets summary bars and gates only. The PMO gets every lane, RAG-coloured, with the data date and progress line. A lane lead gets their band expanded to full detail and the rest collapsed. One file, three saved views — no three separate documents drifting out of sync.

Add the status story per lane

A swimlane is the natural home for status, because status is usually owned by lane. Set the data date, fill progress to it, and drop a progress line so ahead/behind reads across every band at once — you can see instantly that Procurement is behind the line while Construction is on it. Colour each lane by RAG, or add a %-complete pie and a calculated indicator column beside the lane label, and the wall becomes a portfolio dashboard that still has real dates and real logic underneath every bar.

Why this is a gap, not a nice-to-have

Here's the honest landscape. The tools that hold the schedule and the tools that look tidy are two different families, and neither gives you a boardroom swimlane cleanly.

• Desktop schedulers can group; they can't present. The engine can group by activity code or resource and it computes the dates correctly — but a branded, alternating-band, gate-curtained landscape page that a director will actually read? That's a fight with layout settings, and it usually ends in a manual rebuild in a slide deck. Presentation was never what those tools were for.
• Cloud work-OS boards look the part but have no schedule underneath. The tidy lane-and-card boards everyone reaches for are lovely to look at and completely dateless — there's no critical path, no logic, no float, no data date. A lane on one of those is a bucket of cards, not a slice of a real programme. It presents beautifully and forecasts nothing.
• The swimlane wants both. A wall chart is only useful if it's pretty and true — legible enough for the board, and driven by dates the schedule engine actually computed. That intersection is exactly the gap: real schedule data, presented like a portfolio board.

So the one-liner: schedulers hold the dates but can't present them; work-OS boards present but hold no dates. A swimlane view needs to sit on top of the real plan and make it board-legible — which is the job.

Two ways to get a swimlane wrong

Lanes that hide the driving path

Banding by workstream can bury the critical path inside whichever lane it happens to run through. Keep the driving activities highlighted across the bands, or call the critical lane out — the board should see which workstream is pulling the end date, not just that each lane is busy.

Curtains with no gate behind them

A curtain is a promise that a real gate sits there. Anchor each one to an actual milestone or gate activity in the schedule, so when a director asks "what has to be true to cross that line?", the answer traces straight back to the plan — not to a line someone drew for tidiness.

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.