Brand a board pack: header, footer, logo and a print that matches the screen

A raw plotter dump says "planner." A considered, on-brand one-pager says "this has been signed off." The gap between the two is a header, a footer, a logo, a legend and a theme — plus one thing desktop schedulers rarely give you: a print that matches the screen exactly, with no surprise reflow. Here's how to turn a summary Gantt into an exhibit the board will actually respect.

You've done the hard part. The programme is rolled up to a clean Level 1, the phases are right, the milestones trace back to real activity IDs. Then you hit "print," and out comes a mono grid with the schedule name in 8 point at the top, gridlines everywhere, a bar chart that clearly belongs to an engineer and not a director. It's correct. It just looks like a working file that escaped, not a document anyone chose to produce.

The board notices. Not consciously — they won't say "your title block is weak" — but an unbranded, over-detailed exhibit quietly costs you authority. The chair skims it, decides it's "planner stuff," and moves on. A tidy, branded one-pager with the project name, your logo, a revision and a legend gets read. Same dates. Completely different reception.

A board pack is a designed object, not a printout

The distinction planners under-rate: the control schedule is a tool, but the board exhibit is a document. A document has a frame. It tells you, before you read a single bar, what project this is, who owns it, which revision you're holding and what the colours mean. That frame is four elements — a header, a footer, a legend and a consistent theme — and getting all four right is a five-minute job once the picture underneath is settled.

• Header — logo on the left, project (and exhibit) title centred, revision and date on the right. The reader's eye lands here first; it should answer "what am I looking at, and is it current?"
• Footer — the legend (what the bar colours, the diamonds and the data-date line mean), plus small print: confidentiality, page x of y, source file or baseline reference.
• Theme — one coherent palette and type treatment across every page, ideally your house colours, so the pack looks like it came from your organisation and not from six different tools.
• Title block — the fixed corner panel that carries prepared-by, checked-by, approved and the revision table. It's what turns a chart into a controlled exhibit.

The five-minute brand pass

Assume the summary is already built — you've collapsed the Level 3 to a clean set of phase bars and milestones. What follows is purely the presentation layer: choose how it looks, wrap it in a frame, then export it so the printed page is pixel-for-pixel the thing you approved on screen.

1. Choose a theme. Pick a theme from the gallery, or set your own palette and fonts — phase-bar colours, section-band shading, milestone symbols, background and typeface. Save it as a house theme once and every future exhibit inherits it, so your packs are consistent without re-styling each time.
2. Set the header, footer and logo. Drop your logo into the header (left), type the project and exhibit title (centre), and add the revision and date (right). In the footer, place your confidentiality line and page numbering. The header and footer are part of the layout, so they appear on screen and on every exported page — not bolted on afterwards in another app.
3. Add a legend and a title block. Turn on the legend so the colours, milestone symbols and data-date line are explained on the page itself. Add the title block — prepared / checked / approved and the revision table — so the exhibit is self-describing and controlled. No more "what does the amber mean?" from the far end of the table.
4. Export landscape, or share a link. Export a landscape PDF or PowerPoint slide sized to the page you want — the on-screen layout is the printed layout, so there's no reflow to fight. Or send a read-only link: the whole exhibit rebuilds in the recipient's browser, branding and all, with nothing installed and nothing uploaded.

Where this parts company with a desktop scheduler

None of this is a knock on the scheduling engine — the critical path, the float, the calendars all stay where they belong, in your P6 or MS Project master. The point is narrower: desktop schedulers were built to run the schedule, and their print output reflects that. It's functional. It gets the dates onto paper. It was never designed to be handed to a board.

That's why a whole ritual grew up around it — export to image, paste into slides, redraw the summary by hand, add the logo in the deck, fix the legend, and then do it all again next month when the dates move. Every step is a chance to introduce an error, and every one of them is manual.

A presentation layer collapses that ritual into a saved theme and one export. The exhibit is the branded thing — header, footer, logo, legend, revision and all — and it prints exactly as it appears. You're not screenshotting a schedule into a document; you're producing the document directly.

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 a branded board exhibit built in the app.