Use a Tollgate
What’s Actually Happening
The meeting happened. People presented. Questions were asked. There was discussion. Someone said something that sounded like a decision. The meeting ended.
Three days later, the project team is operating as if approval was granted. The sponsor believes a condition was attached that has not been met. Someone in the governance forum thinks the item was deferred for another cycle. The EPMO has no record of what was actually decided because nobody wrote it down.
A tollgate is not a meeting. It is a decision point with a defined structure, defined authority, and a defined record of what was decided, by whom, based on what, with what conditions and next steps. The meeting is the vehicle. The decision is the destination. If the meeting ends without a recorded decision, the tollgate did not function.
Why This Step Exists
Because organizations need a moment where the question changes from “should we consider this?” to “do we commit to this?”
Everything before the tollgate is preparation. The intake established the minimum information. The clarification defined the problem and the outcome. The CBA made the financial and tangible case. The prioritization model evaluated the proposal against competing investments. All of that work exists to give the governance forum what it needs to make a responsible decision.
The tollgate also creates accountability. A decision recorded with rationale, owner, and conditions is a decision the organization can be held to. An implicit approval granted in a meeting where everyone interpreted the outcome differently is not a decision — it is a future conflict waiting to surface.
What Good Looks Like
Every proposal that reaches the tollgate receives one of five explicit outcomes before the meeting ends. Decided, recorded, and communicated in the session.
The proposal is approved to move into authorization and delivery. The investment, scope, and timeline are confirmed. The sponsor and outcome owner are named.
The proposal is approved, but specific conditions must be met before work begins or before a defined milestone. The conditions are written down. An owner is named for each. A deadline is set.
The proposal is not ready for a decision but is not being declined. Something specific is missing. The submission returns to the requester with explicit guidance on what is needed and when.
The proposal raises questions that cannot be resolved in the current session. Different from Hold in that this outcome is about the quality of the submission, not the completeness of it.
The proposal is not approved. The rationale is recorded. The requester receives a specific, honest explanation. If the underlying problem is real, the declination should acknowledge it and note what would need to change for a resubmission.
A sixth outcome exists but is rarely acknowledged explicitly: Stop — an existing project is being terminated. The investment is no longer worth continuing. This is the hardest outcome for most governance forums to produce and the most important for the credibility of the governance model.
How to Do It
Structure the meeting so that decision-making is the purpose and presentation is the preparation. Before the session, every governance forum member should have reviewed the proposal. The session is not for reading documents aloud. It is for clarifying questions, surfacing disagreements, and making a decision.
Open each agenda item with the same structure: what are we deciding, what is the recommendation, what are the open questions? Give the sponsor two to three minutes to present updates. Then open for questions. Then move toward a decision.
The governance chair is responsible for calling the decision. When the discussion has covered the material adequately, the chair names the outcome they believe the forum is converging on and asks for confirmation or objection.
Record before closing each agenda item: the decision outcome, the rationale in two to three sentences, any conditions with owners and deadlines, who was in the room, and the next action with owner. This record takes five minutes to produce and prevents weeks of confusion.
What Breaks When You Skip It
Work begins without a clear decision. The project team proceeds on the assumption that the presentation went well and approval was implied. Each party acts on their interpretation of a conversation that produced no shared record.
Over time, a governance forum that does not produce clear, recorded decisions trains the organization to treat the forum as a presentation theater rather than a decision authority. Leaders stop bringing their real problems to the forum because nothing useful happens there. The forum continues to meet. But it no longer governs anything.
The Gotchas
Where the Disciplines Show Up
The tollgate is not complete until the decision, the rationale, the owner, and the next condition are recorded and communicated. The meeting is not the tollgate. The record is the tollgate.
You know this step is working when people in the organization start citing previous tollgate decisions as precedents — without being prompted. The decision record is being read, referenced, and used to make the next decision better.
The Artifacts
A structured meeting agenda listing each proposal with: the recommended outcome, open questions from the pre-read, and expected time for discussion. Signals that the meeting’s purpose is decisions, not presentations.
Produced during or immediately after each session: outcome, rationale, conditions with owners, attendees, and next actions for every item reviewed. The official record of what the governance forum decided.