Industry·10 June 2026·6 min read

One wall, every project: the portfolio swimlane chart your leadership room reads

Every project in your portfolio has its own plan, its own planner and its own file. What the leadership room actually wants is one thing: a single wall that answers "where is everything?" at a glance. Here's how to merge several plans into one master swimlane chart — a lane per project, phase summary bars, key milestones, portfolio gate curtains and RAG — and keep it current with a refresh, not a rebuild.

You know the Monday-morning scene. The portfolio review starts, and someone has spent Sunday night stitching together five status slides — one per project, each in a slightly different template, none of them lining up on the same timescale. Project C's "on track" is against a plan nobody has seen since March. The programme director stares at it and asks the only question that matters — are we going to hit the year-end gate across the board? — and the slides can't answer it, because no single view shows all five projects on one timeline.

That view exists, and it's not a slide deck. It's a portfolio wall: one lane per project running left-to-right across a shared calendar, each lane rolled up to its handful of phase bars and milestones, with the portfolio's gates drawn straight across every lane. It's the canonical "where is everything" picture — and you build it by merging the plans you already have, not by hand-copying dates into a fresh chart.

Fig 1. The move that makes a PMO wall possible: import each project's plan — whatever tool it lives in — and stack them as swimlane bands on one shared calendar. Five files become five lanes on a single page.

Why a wall, and why the usual tools can't draw it

The reason the portfolio review keeps defaulting to a slide-per-project deck is that nothing in the standard kit produces a clean cross-project wall. Desktop schedulers are built to run one plan brilliantly — critical path, float, resource levelling — but they don't present several plans, side by side, on one branded page; you end up screenshotting each and pasting into slides. Cloud work-OS boards go the other way: they'll happily stack a dozen projects into swimlanes, but the "dates" are card fields somebody dragged, not schedule dates rolled up from a real network, and there are no phase summary bars, no data date, no proper gate curtains.

A portfolio wall needs both halves: the real schedule dates and roll-ups of a scheduler, and the clean, one-page, multi-lane presentation of a board. That's exactly the seam a presentation front-end sits in — it reads the real plans, rolls each to summary level, and lays them out as lanes you can actually put on the wall.

The lane is the unit. A portfolio wall isn't a giant merged schedule — it's a set of independent plans presented together. Each lane keeps its own dates; the wall just aligns them on one timescale and draws the gates that cut across all of them. Nothing about merging into the view changes the underlying plans.

Building the wall in five moves

Say you run a capital-programme office with five live projects — a mix of P6 and MS Project files, plus one that's still tracked in a spreadsheet. Here's the workflow that turns that pile of files into a single leadership-room wall, and keeps it current next month.

Import and merge the plans. Bring each project into one document: drop in the P6 XER/XML and MS Project XML files, and paste or map the spreadsheet columns for the Excel one. Everything parses in your browser — nothing is uploaded. You now have all five programmes in a single master view, each arriving as its own outline.
One lane per project. Turn each imported plan into a swimlane band — a labelled horizontal track for Project A, B, C, D, E (or one band per workstream, if that's how leadership thinks). The bands stack down the page; the calendar runs across the top, shared by all of them.
Roll each project to summary + key milestones. Collapse every lane to its top phases so an automatic summary bar spans each project, and promote each project's handful of make-or-break dates to milestones — the gate approvals, the handovers, the go-lives. The detail stays in the file; the wall stays readable (Fig 2).
Draw the gate curtains + RAG. Add portfolio curtains at the shared gates — the year-end stage gate, the funding checkpoint — as vertical bands cutting across every lane, so you can see at a glance which projects clear each gate and which don't. Then colour each lane's status with RAG stoplights driven by its own data, and drop a data-date line so "as at today" is unambiguous.
Share and print the wall. Add a legend, header and logo, then export a landscape PDF or PowerPoint for the room — print-matches-screen — or send a read-only link that rebuilds the whole wall in the recipient's browser, with nothing to install.

Fig 2. Each project rolls up the same way: collapse the WBS and Sketchedule draws one summary bar from earliest start to latest finish, then you promote the two or three milestones that matter. Do it per lane and every project reads as a single tidy row on the wall.

The order matters. Merge first so everything shares a timescale; then roll up, because a lane you can't read is worse than no lane at all. A portfolio wall lives or dies on being scannable in ten seconds — one bar and a couple of diamonds per project, gates cutting across, and the eye immediately lands on the lane that's about to miss.

Fig 3. The portfolio wall, built in Sketchedule: a grid panel of five project lanes with Start / Finish / % columns, phase summary bars on a month axis, milestone diamonds and handover flags, the year-end gate curtain cutting across every lane, RAG stoplights per project and the dashed data-date line. This is the "where is everything" view the leadership room reads in ten seconds.

What the wall tells you that the deck can't: read down the gate curtain in Fig 3 and Project C's summary bar runs past it while its RAG dot is red — that project is the one that misses the year-end gate, and the whole room sees it at once. No slide-flipping, no reconciling five timescales in your head.

Keeping the wall current — refresh, don't rebuild

A portfolio wall is only useful if it's honest this month, not last month. The trap is that "one master view built from five files" sounds like five times the maintenance. It isn't — because each lane stays linked to its source file.

When a planner updates Project C in P6 and re-exports, you hit Refresh on that lane and point it at the new file. Sketchedule shows a diff preview first — what changed, what's added, what's now obsolete — before you accept it. The summary bar re-spans, the milestones move, the RAG re-evaluates, and the gate curtain instantly shows whether the update pushed that project across the gate. Five quick refreshes and the wall is current, with a clear audit of what moved since last period.

Fig 4. Refresh a lane from its updated source and Sketchedule previews the diff — changed, added, obsolete — before you apply. You see exactly what moved, and whether it changed the project's standing against a portfolio gate, before it hits the wall.

Where the detail lives. The wall is a presentation of five plans, not a replacement for them. Each project's detailed, logic-driven schedule stays in P6 or MS Project — that's the source of truth the planners run the work from. The wall reads those files, rolls them to summary, and presents them together; it never edits the master.

Key takeaways

A portfolio wall is several plans presented together — one swimlane per project on a shared timescale, not one merged mega-schedule.
Import and merge P6, MS Project, Excel and CSV plans into one master view, then roll each lane to a summary bar + key milestones so the wall stays scannable.
Gate curtains cut across every lane and RAG per project make "who misses the gate?" a ten-second read.
Refresh each lane from its updated source with a change / add / obsolete diff — the wall tracks reality without a rebuild.
Desktop schedulers can't present a clean cross-project wall; cloud boards lack real schedule dates and roll-ups. Each project's detail stays in P6/MSP.

Build your portfolio wall

Open Sketchedule in a browser — free, no install, nothing uploaded. Drop in your project files and stack them into lanes.

Start free →Browse examples

← BlogAll articles Next →Swimlane a programme by workstream

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.