Use cases

One dashboard, four people who need it.

Tollgate gives each person on a project the part of the picture they answer for, inside the Jira project they already open. Pick yours below.

Book a demoSee how it works

Choose your view

Each person on a project answers for part of the picture.

Project manager

Project manager. You answer for time, cost, scope and risk.

Read the project manager view
Sponsor

Sponsor. You want to open one page and know where the project stands.

Read the sponsor view
Delivery lead

Delivery lead. You want project tracking that leaves your Jira alone.

Read the delivery lead view
For project managers

Report from the plan, not from a rebuilt pack.

The plan, the status and the registers live in the project, so the pack never has to be rebuilt.

You keep the plan in work packages: dates, budget, actual, forecast and percentage complete. You set the Cost, Schedule and Scope status each period and write the commentary beside it.

Tollgate shows its calculated status next to yours and keeps the last four periods as dots. The timeline and the S-curve draw themselves from the same work packages, so there is one set of numbers.

Editing a status card in Tollgate: set the status, write the commentary, calculated status beside it

Before

A spreadsheet for the budget.

A document for the risks.

A pack that takes the evening before the meeting.

After

Update the work packages as the work moves.

Set the status and write the commentary beside it.

On meeting day, open the dashboard.

See how it works
For delivery leads and Jira admins

Your Jira stays as it is.

Tollgate adds no issue types or schema changes and asks nobody to re-key delivery data, so your Jira admin has nothing to reconfigure.

Many project tools need Jira restructured before they work: new issue types, new hierarchy levels, workflows your team has to learn. The restructure lands on your team.

Work packages are Tollgate's own records. They link to your Jira issues and add no issue types. Your workflows, boards and sprints are untouched. Tollgate runs on Atlassian, with no external servers and no external database.

Tollgate work packages register linked to Jira issues, with no new issue types
See how it works
For PMO leads

Every project reports the same way.

One layout, in Jira, next to the work, instead of each project manager's own template.

Each project has the same dashboard, the same plan structure and the same three registers. A PMO lead reading one project can read the next. The project managers keep the content current, and the structure is already there.

Same dashboard

Overall status, project brief, and Cost, Schedule and Scope cards on every project.

Same plan structure

Work packages with dates, budget, actual, forecast and percentage complete.

Same three registers

Risks and opportunities, decisions and changes, kept next to the plan.

Small projects and large ones

With a budget or without one.

For mid-market technology teams running multi-million-dollar programs on Jira who need investment governance without an enterprise PPM suite.

Some projects have a funded budget, and some have a team and a date. The S-curve covers both. With a budget it shows earned value. Without one it shows planned against actual percentage complete. The timeline draws itself from the work package dates in either case.

No logos yet. Tollgate is new, and we won't invent customer stories. The quickest way to judge it is to run one of your own projects through it. Book a demo and bring one.

Work packages

The one set of numbers both charts read from.

Timeline

Drawn from the work package dates, with or without a budget.

S-curve

Earned value with a budget; planned against actual percentage complete without one.

See how it works

See your project on the dashboard.

Thirty minutes, a live project, no deck.

Book a demo
Read the docs