Waypoint
Step 07

Use a Tollgate

In Brief — A governance forum that does not produce recorded decisions is not governing — it is meeting. This step defines five clear outcomes for every submission (Proceed, Proceed with Conditions, Hold, Return for Clarification, Decline) plus the sixth and hardest one (Stop). The decision record is the actual tollgate, not the meeting. What was decided, why, by whom, and under what conditions — written down, unambiguous, and actionable.
The Tollgate Is the Full Sequence
The governance forum meeting is the decision point — not the whole process. The tollgate sequence begins at intake and runs through four preparation steps before a proposal ever reaches the forum.

Step 3 — Intake: The front door. Work enters through one consistent process with a minimum information standard. Incomplete or unvetted submissions are returned here, not at the forum.
Step 4 — Clarify: The problem and expected outcome are defined precisely. The scope is bounded. The right type of solution is identified before a cost is attached to it.
Step 5 — Cost-Benefit: The financial and organizational case is built with honest assumptions. The investment ask for the current phase is separated from speculative future scope.
Step 6 — Prioritize: The proposal is scored against competing investments using a published model. The forum sees where the work ranks before it sees the proposal.
Step 7 — Tollgate Decision: The forum makes one of six explicit decisions, records the rationale, names the conditions and owners, and produces a decision record before the meeting closes.

Remove any step in that sequence and the decision at Step 7 is weaker. The tollgate is only as good as what enters it.
Typical duration: Recurring forum — monthly cadence is typical; standing meeting, 90–120 minutes

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 the Submission Must Contain

Every proposal that reaches the tollgate must arrive as a complete package. Incomplete submissions are returned — not held, not conditionally placed on the agenda — with specific guidance on what is missing. The review clock starts when the package is complete.

The Charter

A concise narrative stating the problem, the expected outcome in measurable terms, scope in and out, the named sponsor and delivery owner, top risks, and the budget ask for this phase only. It is the source of truth for the project. Any change to scope, investment, or governance authority returns through a gate — not through a document edit.

The Cost-Benefit Analysis

Section one covers this phase only: the investment ask, the expected return, and the assumptions underpinning both. Future phases appear as directional context, clearly flagged as not the current ask. Bundling speculative future scope into the current ask distorts the decision the forum is being asked to make.

The Requirements Baseline

What must be true for this investment to succeed — the outcome and functional requirements the forum is approving delivery against. Without it, the tollgate is approving a concept, not a commitment. The requirements baseline is what makes post-delivery accountability possible.

The Priority Score

The output of the organization’s scoring model, applied before the session. The forum uses the score as context for the decision, not as a substitute for judgment. A score without the model’s rationale is a number without meaning.

The Intake Record

The official submission confirming that the work entered through the defined front door, was reviewed for completeness, and carries a named sponsor who authorized it. Without it, the governance audit trail does not exist.

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.

Proceed

The proposal is approved to move into authorization and delivery. The investment, scope, and timeline are confirmed. The sponsor and outcome owner are named.

Proceed with Conditions

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.

Hold

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.

Return for Clarification

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.

Decline

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.

Two things make this record defensible under audit, not just useful in the moment. First, segregation of duties: the person authorizing a project should never be the person who requested it — the Authorization Checklist (T3) requires this as an explicit confirmation, not an assumption. Second, evidence retention: the Tollgate Decision Record (T5) is not filed and forgotten — it names where supporting documentation lives and how long it is kept, per your organization’s policy. Together, these two checks are what turn “we made a decision” into “we can prove what we decided, who decided it, and that the decision-maker was independent of the request.”

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

The meeting becomes a status review. The agenda fills with updates on approved work rather than decisions on proposed work. Updates are useful but they are not governance. Protect the tollgate for decisions.
Conditions are granted but never tracked. “Proceed with conditions” is the outcome governance forums most often fail to execute on. The condition is named in the room. Nobody owns tracking it. The decision record needs a condition owner, and tracking needs to be on someone’s standing agenda.
The committee exists to ratify decisions already made elsewhere. When proposals arrive pre-approved through informal executive conversations, the formal process becomes a ceremony. The governance chair needs the authority and willingness to challenge a pre-approved proposal when the evidence does not support it.
The submission bundles multiple phases into one ask. A proposal that describes a multi-phase program and requests full approval of all phases at once is not a tollgate submission — it is a negotiation. The submission must reflect the current phase only. Future phases require their own gate, their own evidence, and their own decision. Approving speculative future scope on the strength of phase one’s case is how organizations commit to things they never fully evaluated.
Specialist reviews are scheduled as conditions rather than completed at intake. Security, compliance, architecture, and data considerations should be cleared before the submission reaches the forum. Assigning a security review as a tollgate condition means the forum approved work without understanding a fundamental risk. Those reviews belong at intake — not on the other side of the decision.
Endorsement and active sponsorship are treated as the same thing. The tollgate should confirm that the named sponsor is active — engaged with the current state of the proposal, not just associated with its origin. When the tollgate approves work based on a functionally absent sponsor, authorization is likely to fail at the first real decision point.
Sponsor accountability at the tollgate has a protocol when it fails. If the named sponsor does not attend, send a written summary of the forum discussion to the sponsor within 24 hours and require written confirmation that they stand behind the recommendation before proceeding. If the sponsor cannot be reached within the defined window, the proposal is held at the tollgate — not conditionally approved, not deferred indefinitely, held. Document the reason. If the pattern recurs for the same sponsor, that is a governance-level signal that requires escalation to whoever chartered the governance model — typically the executive who authorized the governance function (a COO, executive steering committee, or board-level body). If no formal charter has been documented, the escalation goes to the most senior executive who endorsed the governance mandate. That escalation event is also a signal: the charter should exist before the next forum cycle. The governance forum does not pursue sponsors. It holds the process standard and reports what it observes.

Where the Disciplines Show Up

→ Decision Discipline: The tollgate is the purest expression of decision discipline. Who decides? Based on what authority? Against what criteria? With what record? These questions must be answered before the first meeting, not during it. The governance forum’s decision rights should be documented, understood by everyone in the room, and consistent across sessions.
→ Change & Absorption: The tollgate is the last checkpoint before work is authorized. Confirm that the change load assessment has been reviewed, that this investment does not push the receiving organization into saturation, and that a named person is accountable for adoption — not just delivery. OCM integration point: the change impact assessment should be complete before the forum convenes, not assigned as a tollgate condition. An investment whose adoption risk has not been assessed is not ready for authorization. The named adoption owner — distinct from the delivery owner — should appear on the tollgate decision record. See all four touchpoints together →
→ Enterprise Fit: The tollgate should include confirmation that architecture, data, security, and compliance reviews have been completed — not promised for later, completed. If any review surfaced a condition, that condition is attached to the tollgate outcome as “proceed with conditions” with a named owner and deadline.
→ Evidence: The decision record documents not just the outcome but the rationale — what evidence drove the decision, what was weighted most heavily, what questions remain open. Over time, the accumulation of decision records tells the organization what kinds of proposals get approved and whether the patterns are producing better investment outcomes.
→ Political: Tollgate decisions require political preparation, not just technical preparation. A decision that surprises a senior stakeholder after the meeting is a fragile decision. Political discipline means briefing key stakeholders on the decision logic before the room assembles, and ensuring the decision record captures the rationale clearly enough to survive the challenge that follows.
The Key
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

T23 — Decision Agenda

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.

T5 — Tollgate Decision Record

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.