Tollgate Reviews and Benefits Tracking: Connecting the Dots
How to integrate benefit delivery data into the most consequential governance decision in the project lifecycle
The Tollgate Review Is a Decision, Not a Ceremony
The tollgate review is the most consequential governance event in the project lifecycle. It is the moment at which the organisation decides whether a project should continue to receive capital (go), be paused pending further evaluation (hold), or be terminated with remaining capital redirected (stop). This decision carries enormous financial implications. A go decision commits the organisation to continued expenditure. A stop decision recovers capital that can be deployed elsewhere. A hold decision preserves optionality while additional information is gathered.
And yet, in a remarkable number of enterprises, the tollgate review is conducted without the single most important data input: whether the project’s committed benefits are being delivered. The review evaluates scope completion, schedule adherence, budget consumption, risk status, and stakeholder satisfaction. It asks whether the project is being executed well. It rarely asks whether the project is delivering what it promised.
This omission is not a minor gap. It is a structural failure that disconnects the governance decision from the investment rationale. The project was funded because of its expected benefits. The tollgate should assess whether those benefits are materialising. Without benefit data, the tollgate can confirm that the project is running efficiently but cannot determine whether it is running productively.
Why Execution Metrics Are Not Enough
Execution metrics, scope, schedule, and budget, are necessary inputs to the tollgate review. They are not sufficient. A project can be on scope, on schedule, and on budget while simultaneously failing to deliver its committed benefits. The two dimensions of performance are related but not interchangeable.
Consider a technology platform migration that is proceeding on plan. The system is being built according to specification. The deployment timeline is holding. The budget is tracking to allocation. Every execution metric is green. But the business case projected a thirty percent reduction in processing time once the new platform is live, and early performance testing shows that the actual reduction is likely to be twelve percent. The execution is successful. The benefit is at risk.
If the tollgate review looks only at execution metrics, the project receives a go decision and proceeds to deployment. The eighteen-percent gap in processing time improvement is discovered after go-live, when it is too late to redesign the platform and the capital has been fully consumed. The organisation deployed a system that works but underdelivers by more than half on the metric that justified its funding.
If the tollgate review includes benefit data, the at-risk signal on processing time improvement is visible before the deployment decision. The governance committee can hold the project, commission a technical review, assess whether additional optimisation can close the gap, and make an informed decision about whether to proceed, adjust, or stop. The same data point that was invisible in the first scenario becomes the most important input in the second.
Integrating Benefit Data Into the Tollgate
Integrating benefit delivery data into the tollgate review requires three structural changes to the standard tollgate process. None of them is complex. All of them are consequential.
The first change is adding a benefit status section to the tollgate review package. Alongside the standard sections on scope, schedule, budget, and risk, the review package should include a summary of every committed benefit and its current delivery status. For each benefit, the summary should show the planned value at the current point in the timeline, the actual value from the most recent check-in, the status classification (on track, at risk, or exceeding), and the trend across the last three check-ins. This gives the governance committee a concise view of benefit performance that is directly comparable to the execution metrics they are already reviewing.
The second change is incorporating benefit status into the go, hold, or stop criteria. The tollgate decision framework should define explicit thresholds that reference benefit delivery. For example, a project with more than fifty percent of its committed value classified as at risk may trigger a mandatory hold pending a corrective action plan. A project with all benefits on track or exceeding may proceed with standard monitoring. The thresholds will vary by organisation, but the principle is the same: benefit delivery must be a formal input to the decision, not an afterthought that is raised only if someone in the room happens to ask.
The third change is assigning a benefit review role in the tollgate meeting. Someone at the table must be responsible for presenting and defending the benefit data. In most governance structures, this role belongs to the value realisation officer, who brings an independent perspective on benefit delivery that complements the project manager’s execution perspective. The VRO’s presence ensures that benefit data is not just included in the package but actively discussed and challenged.
The Hold Decision: Where Benefit Data Has the Highest Impact
Of the three tollgate outcomes, the hold decision is where benefit data has the most transformative impact. A go decision confirms the status quo. A stop decision, while significant, is relatively rare and usually triggered by severe execution failures or strategic changes. The hold decision occupies the middle ground: the project is not failing catastrophically, but something is wrong. The question is whether the something justifies pausing expenditure to investigate further.
Without benefit data, the hold decision relies on execution signals: schedule slippage, budget overruns, unresolved risks. These are valid triggers, but they miss the scenario in which execution is proceeding normally while benefit delivery is deteriorating. This is precisely the scenario that benefits tracking is designed to catch.
A hold triggered by at-risk benefit data creates a productive pause in which the governance committee can investigate the gap between execution performance and benefit delivery. Is the project building the right thing in the wrong way? Is the benefit target unrealistic given what execution has revealed? Are there external dependencies that need to be addressed before the project can deliver its committed value? These questions cannot be asked if the benefit data is not on the table.
The hold decision also signals to the organisation that benefit delivery is a governance priority. When project teams see that at-risk benefits can trigger a hold, the incentive to submit accurate check-ins and to flag benefit risks early increases significantly. The hold decision is not just a response mechanism. It is a cultural signal that reinforces the planned-versus-actual discipline across the portfolio.
The Stop Decision: Recovering Capital Before It Is Consumed
The stop decision is the most difficult and the most valuable governance action available at a tollgate. Stopping a project recovers the remaining uncommitted capital and redirects it to investments with higher expected returns. But stopping a project is psychologically and politically difficult. It requires acknowledging that the investment thesis was wrong, that the capital spent to date is sunk, and that the organisation is better off absorbing the loss than continuing to invest.
Benefit data makes the stop decision more defensible and more timely. When the planned-versus-actual comparison shows a persistent, widening gap between committed and delivered value across multiple check-in periods, the case for stopping is grounded in evidence rather than opinion. The governance committee is not relying on a subjective assessment of the project’s prospects. It is looking at a data-driven trajectory that shows the benefit is not materialising.
Without benefit data, stop decisions tend to happen too late, after the capital is substantially consumed and the recovery opportunity is small. Benefit tracking shifts the stop decision earlier in the project lifecycle, when more capital remains uncommitted and the redeployment opportunity is larger. The organisation does not just make better decisions. It makes them sooner, when the financial impact of acting is greatest.
This is perhaps the single most compelling financial argument for integrating benefit data into tollgate reviews. Every quarter that an underperforming project continues to consume capital because no one has the data to justify stopping it is a quarter of value destruction that was entirely preventable.
Connecting the Dots
The tollgate review is the governance mechanism that controls the flow of capital through the project lifecycle. Benefits tracking is the measurement mechanism that determines whether that capital is producing value. Connecting the two is not a reporting enhancement. It is a governance upgrade that transforms the tollgate from an execution checkpoint into a value checkpoint.
The connection requires minimal structural change: a benefit section in the review package, explicit benefit thresholds in the decision criteria, and a VRO presence at the table. But the impact is disproportionate to the effort. Go decisions are better informed. Hold decisions are triggered earlier. Stop decisions are data-driven rather than political. And every project team in the portfolio knows that benefit delivery is not just tracked but consequential.
The tollgate review without benefit data is a car with a speedometer but no fuel gauge. It tells you how fast you are going. It does not tell you whether you will reach your destination. Benefit data is the fuel gauge. And no competent driver would proceed without it.