Most tools on Jira answer the delivery team's question: are we shipping? Tollgate answers the sponsor's: is the investment still on track to pay off?
Different question. Different altitude. Same Jira.
.gif)
The sponsor asks the obvious follow-up. What did that change do to the budget? Which work packages are at risk because of it? Are we still on track for the payoff?
The answer is in five places at once. Cashflow in a spreadsheet. Status in last fortnight's deck. Risks in Confluence. Decisions in meeting minutes. Delivery in Jira. None of them agree, and none of them is obviously the one that's current.
So the conversation stops. The picture was stale before it was presented, and the person in the middle is the integration layer. All that effort, and no more insight than the monthly steerco slide.
Tollgate sits on each Jira project as six tabs, plus a portfolio view across them. The picture is current because it is the place where the picture is kept — not reassembled the night before the meeting.
Cost, schedule, scope and risk each carry a RAG the registers below them derive — the honest default, before anyone has weighed in. A person can override it, because bottom-up data isn't insight until judgement has filtered it. So the override stays, on the record: the derived value sits beside it, with a name against the change and the reason for it. That's the opposite of a watermelon. The gap between what the data derived and what a person decided is out in the open, not buried under the green.
A derived status can be changed — but never quietly. The computed RAG stays on screen, with who overrode it and why — judgement, with an audit trail.
The dashboard you land on, and the one you present from. Includes a Steerco One-Pager presenter mode. Derived by the registers. Overridden on the record.
On track for what, exactly. Business problem, outcome, return expected, named sponsor and steering committee. Draft → Submitted → Approved.
Scope and budget at the unit executives think in. Baseline, forecast, actual, RAG, owner, linked Jira issues — with a phase and timeline view. Not tickets.
.gif)


Risks, Decisions and Changes. This is where the dashboard's colour starts — and where the corporate memory lives.
A register on the threat, opportunity and materialised model, sorted by impact times likelihood, with the 4Ts treatment. The governance view, not a Jira board.
Append-only corporate memory. Proposed → Approved or Rejected, separation of duties enforced. What did we approve, and when — answerable in the room.
Scope, timeline and budget change requests on the same approval pattern. Once decided, the entry is immutable. The cumulative impact is always there to point at.



Portfolio Health rolls the projects into one view. Investment Health is the deck you present from. Ask Tollgate handles the question you never anticipated.
Every project's Investment Health in one view across the whole programme. Build a Jira Plan (formerly Advanced Roadmaps) and use it as the filter — rolled up overall and by investment theme.The board-level picture.
Open Investment Health on the projector and run the meeting from it. There is no parallel slide pack to keep in sync. A branded board-deck export — one click, current data only — is on the roadmap for the exec audience who isn't in Jira. The dashboard is the deck.
A Rovo copilot for the follow-up no deck anticipated. Ask it live, in the room — scoped to this project's Tollgate data, its Jira work items and linked Confluence docs, so you can read the financial model or the technical issue below the line, not just the RAG. Available on Premium and Enterprise Jira sites. Instead of coming back to it next month.



Advanced Roadmaps and the Gantt overlay-style apps still only manage delivery — sequencing, dependencies, who is doing what when. Tollgate manages the investment outcome — whether the money is still going to land. Delivery stays in Jira, exactly where it should be.
Below the line: Roadmaps, Gantt overlays, sprint metrics. They manage how the work gets done — the delivery team's question.
Above the line: Tollgate. It manages whether the investment lands — the sponsor's question.
Built on Atlassian Forge. It reads your Jira data and keeps its own governance records separately — it can't write to or change Jira data in your projects.
It runs entirely on Atlassian Forge. No external servers, no external database, no data sent anywhere outside your Jira site. Inside your tenancy, full stop.
It reads Jira data and keeps its own governance records separately. It can't change anything in your existing projects.
No new issue types, no workflow changes, no customisations to how delivery already works. Loosely coupled — you link a Tollgate item to a Jira issue only when there's a reason to, so delivery keeps its velocity.Safe on a messy, existing Jira instance.
A few things to be straight about, because the worst beta is the one you walked into expecting a finished product.
Tollgate is fully functional right now — every tab, every register, the portfolio roll-up and Ask Tollgate. It reads your Jira and keeps its own governance records separately, so it's safe to install alongside live delivery.Install today, not someday.
It asks only for read access and keeps its records separately, so it can't change your existing projects. A sandbox is safest; production is your call. A sandbox is recommended.
Free for teams up to 10 Jira users, with a steeply declining per-user price above that. No card to start — the full gate workflow, decision record and CSV export are on the free tier.No card, no commitment.
A few features, like Ask Tollgate, don't run on a Standard licence.
/ Highlights














"I built Tollgate for the investment side of programmes, and I'm opening it to a small group who run governance for real. If that's you, I'd genuinely value your eyes on it."
— James Hallam, Softwired Digital
By registering you agree to our Privacy Policy and Terms of Service.