Skip to content
Tollgate Docs

Above the line

The single most important idea in Tollgate is a line. Above it sit the people answerable for the money — sponsors, transformation leads, programme directors, and the steering committees they answer to. Below it sit the people delivering the work. Tollgate lives entirely above the line. Almost everything else about the product falls out of that one commitment. This page explains what the line is, why it matters, and what it means in practice.

Two altitudes, two questions

Section titled “Two altitudes, two questions”

Delivery teams answer “are we building it well?” — and Jira, boards, burndowns and velocity are good tools for that. Sponsors answer a different question: “are we on track for the payoff we funded this for?”

These look adjacent, but they don’t translate into one another. Story points aren’t a yes/no. Velocity isn’t a payoff. A green sprint can sit inside an investment that drifts away from its business case. A red sprint can sit inside one that is dead on track. Executives asked their question for a decade and got answers in the delivery team’s language — outputs where they wanted an outcome.

Tollgate refuses to make that translation error. It doesn’t launder delivery signals into governance language. It takes delivery state from Jira as input and speaks above it, in the sponsor’s own vocabulary.

Why the abstractions are shaped the way they are

Section titled “Why the abstractions are shaped the way they are”

Every core object in Tollgate exists to keep the surface above the line:

  • The business case gives “on track” a destination. Without it, status is just colour.

  • The work-package abstraction exists because executives don’t think in tickets.

    A work package is a coherent slice of scope with an owner, a budget and a schedule. It is big enough to mean something to a sponsor and small enough to have resolution. It is deliberately not a Jira story (noise) and not the whole project (no resolution).

  • The derived Cost / Schedule / Scope / Risk RAGs pull status apart. A single colour would hide the disagreement.

  • The decision log and change register answer “what did we approve, and what has it cost us?”

None of these is a delivery-management feature. Each is a governance one.

The grievance underneath

Section titled “The grievance underneath”

Tollgate speaks to a quiet frustration. Executives heard for years that agile is the answer. Their reasonable question — are we on track for the payoff? — keeps coming back as story points, velocity and outcomes over outputs. Most PPM tools that sit on Jira absorbed the agile worldview and reflect it back in the same language. They fail at the exact job the executive hired them for.

This isn’t an anti-agile position. Agile is fine for delivery. Tollgate is the governance layer that agile delivery needs but doesn’t supply on its own. One caution on the framing: the sponsor-grievance pitch is for sponsors, not for the Jira admin whose sign-off you need. The tool sits alongside the delivery team’s world without disrupting it.

The line is enforced twice — editorially and by permission

Section titled “The line is enforced twice — editorially and by permission”

Good intentions alone don’t hold the line. Two mechanisms enforce it at once:

  1. Editorially, in the product. Tollgate ships a strong opinion about what earns space here.

    Below-the-line signals aren’t configuration options you can switch on. They are absent. The closed list of governance surfaces expresses this restraint as information architecture.

  2. By permission. A customer-managed governance group gates visibility.

    You can hide Tollgate from delivery teams entirely. Access control over who sees the surface reinforces the editorial discipline about what earns space. See Restrict access with governance groups.

Recommendations, not stipulations

Section titled “Recommendations, not stipulations”

Being above the line also shapes how Tollgate behaves. It guides rather than enforces. It surfaces drift, stale data and missing decisions. It doesn’t block you from saving a half-finished record, and it doesn’t email or Slack you a nag. Ageing signals appear on the surfaces the sponsor already opens, not in their inbox.

The two deliberate exceptions are the Adoption & Change quartet required at business-case submission, and the lessons entry required on a not-realised verdict. Leaving adoption out of the funding decision is the mistake most likely to sink the investment.

The restraint is a governance stance. Tools below the line nag to chase delivery. Above the line, the sponsor decides when to look.

The line in one sentence

Section titled “The line in one sentence”

Tollgate is not a PMO (project/programme management office) operations tool and not a delivery management tool. It is the above-the-line investment view: the sponsor’s surface, the presentation surface for governance. It hosts the structured conversation about whether the investment will land. To decide whether something belongs in Tollgate, ask whether it serves that conversation. If it has an authoritative home below the line, point at that home instead.

Section titled “Related reading”