Skip to content
Tollgate Docs

The dashboard is the deck

New users often look for the export button — the one that turns the dashboard into a deck for the steering committee. In Tollgate you don’t need it: the dashboard is the deck. This page explains why presenting live is a design principle rather than an omission, and what it means for how you run a meeting.

The night-before ritual

Section titled “The night-before ritual”

Here’s the workflow Tollgate is built to end. A PM spends the evening before a steering committee reassembling a status pack. They copy numbers out of Jira and paste a RAG (red/amber/green) table into PowerPoint. They update a slide someone made last quarter and chase the latest risk list out of Confluence. The deck is stale the moment it’s saved, because the data moved on while the PM built the slides. And it’s a parallel artefact the PM must maintain beside the real picture.

That ritual is pure duplication. The PM becomes the integration layer between five systems and a slide master, every reporting cycle, forever.

The natural endpoint of minimal duplication

Section titled “The natural endpoint of minimal duplication”

Tollgate’s whole premise is a single surface where the governance-relevant picture is kept, not reassembled. Follow that premise to its conclusion and the deck disappears. If Tollgate already holds the current case file, the case file is the thing you present. There’s no deck to export because there’s nothing to re-create.

The PM keeps the picture current through the week — five minutes here, ten there. The resulting Investment Health view goes on the projector. Keeping the case file current is the only data-entry cost, and it replaces the night-before scramble entirely.

This is why the Health surfaces are presentation-grade by default. Typography, information density, contrast and visual hierarchy must hold up projected to a room of executives, not merely read well in a browser tab. Presentation quality isn’t a polish layer applied at the end. It’s the default state of the surface, because the surface is the deck.

Live beats static, especially under a follow-up

Section titled “Live beats static, especially under a follow-up”

A static deck has one fatal weakness in a steering committee: the follow-up question it doesn’t have a slide for. “What did we decide about that change in Q2? What’s the cumulative budget impact? Which work packages are at risk because of it?” With a deck, the answer is “I’ll have to come back to you on that” and the conversation stalls.

Presenting live, the path from “I’m presenting” to “I’m answering a question” is one click or one prompt. Jump to the Risks, Changes or Decision log register. Or put a plain-language question to Ask Tollgate and get an answer from current data, in the room. The meeting doesn’t stall because the case file is right there, whole and current — not flattened into whichever slides someone anticipated.

The line we hold

Section titled “The line we hold”

This principle has a sharp edge, and it’s worth being explicit about it. The point of Tollgate is that you present the live case file, not that you author a separate deck alongside it. A slide editor, or a template that re-flows the dashboard into a separate authoring surface, would recreate the night-before ritual. Anything that turns into “produce the deck for me” replaces the signature use case instead of serving it.

The test is a question. When a customer asks how to produce the deck, the answer is to open the dashboard — not instructions for building one.

What this means for you

Section titled “What this means for you”
  • Keep the picture current through the week. Don’t build a deck for the meeting.
  • Present from Investment Health (one project) or Tollgate Portfolio (across a portfolio).
  • Answer follow-ups by jumping to a register or asking Tollgate — not by anticipating every question in advance.
Section titled “Related reading”