Stage Gate Approvals: How to Run Them Without Stalling

A stage gate approval is a formal decision at the end of a project stage: the people with authority look at agreed evidence, compare it with agreed criteria, and decide whether the work moves on. That is the whole idea. The difficulty is in the details: who is allowed to say yes, what counts as evidence, what happens when the answer is “not yet,” and how to keep all of it from turning into a queue of unanswered emails.

This guide covers the mechanics of a good gate, shows examples from product development and from media production, and explains how to track approvals so they leave a record instead of a rumor.

TL;DR

• A stage gate approval is a decision, not a status update. It needs named approvers, fixed criteria and a recorded outcome.
• Every gate ends in one of a few outcomes: go, kill, hold, recycle (send back for rework), or go with conditions.
• Match the weight of the gate to the size of the project. Applying the same rigid criteria everywhere is the classic mistake.
• Approvals only work if the evidence, the version being judged and the decision all live in one place.
• For creative and post-production teams, the gates are usually concept, script or treatment, rough cut, final cut and delivery.

Table of Contents

• What a stage gate approval actually is
• The five outcomes of a gate
• Who approves: gatekeepers, not spectators
• What a good gate review contains
• Stage gate examples
• Match the gate to the project
• Criteria that make approvals fast
• Where approvals break down
• How to run stage gate approvals step by step
• Perspective: gates are a record, not a ritual
• Tracking gate approvals in Posthive
• FAQ
• Sources

What a stage gate approval actually is

The stage-gate model splits a project into stages of work, each followed by a gate. At the gate, a review decides whether the project continues. The Project Management Institute’s research paper on product development describes Stage-Gate as the dominant process for organizing product development, intended to give interdisciplinary teams high-level charters and to support executive decisions.

You will see the same idea under several names: phase gate, stage and gate, toll gate, gate review. The vocabulary changes by industry. The structure does not: work, evidence, decision, repeat.

Two things separate a gate from an ordinary check-in:

1. The decision is binary or close to it. Someone with authority commits money or time to the next stage, or stops.
2. The criteria exist before the meeting. If the bar is invented during the review, the approval is a negotiation.

Harvard Business School research on incentives in a stage-gate process notes that many large organizations use the process to manage new product development, with project managers developing ideas while senior executives decide. That split of roles is the core of every gate: the people doing the work are not the people who approve it.

The five outcomes of a gate

A gate that can only say “approved” is not a gate. Mature processes define the full set of outcomes in advance, so nobody has to guess what a lukewarm meeting meant.

The kill option matters more than it looks. Classic research on best-practice companies, Optimizing the Stage-Gate Process, recommends rigorous go/kill decision points to bring discipline to project selection, and reports that around half of firms lack effective criteria for prioritizing projects. A gate that never kills anything is a progress bar with a meeting attached.

Who approves: gatekeepers, not spectators

The most common failure is vague ownership. Ten people are invited, everyone comments, and nobody decides. A workable setup has three groups:

• Gatekeepers make the decision. Keep the list short, usually two to five people, and define in advance whether a majority or a single owner decides.
• Contributors supply evidence: the deliverable, the budget report, the risk log, the test results.
• Observers are informed of the outcome. They do not vote.

In creative work the gatekeepers are often a mix of an internal lead and the client. A producer approves that the cut meets the brief, and the client approves that it meets the business need. If you have not written down who has which authority, you will rediscover the gap at the worst moment, usually when a late note from someone new reopens a locked cut. We cover that problem in detail in our approval matrix for rough cuts and final delivery.

What a good gate review contains

A gate review is a structured, criteria-based decision, not a routine status meeting. Status meetings answer “where are we?” Gate reviews answer “should we continue?” The distinction is worth saying out loud, because teams drift. A weekly sync that starts producing go/no-go calls without evidence is a gate with no rules. Remote and distributed teams feel this most, since the casual hallway signals are missing. A guide on remote collaboration for game audio shows how producers structure checkpoints when contributors work in different places and time zones.

A reliable gate review has five parts:

1. A fixed agenda. Deliverables reviewed, criteria scored, decision, actions.
2. Pre-circulated evidence. Reviewers read before the meeting, so the session is for judgment, not presentation.
3. Scored criteria. Scorecards make “is this good enough?” less subjective. The best-practice research above recommends them for judging projects objectively at gates.
4. A recorded outcome. One of the defined outcomes, with a date, names and any conditions.
5. Owned follow-ups. Every condition has a person and a deadline.

Keep it short. If a review needs ninety minutes of explanation, the evidence pack was not ready, and the right outcome is probably “recycle.”

Stage gate examples

Product development

The classic five-stage model runs: scoping, building the business case, development, testing and validation, and launch, often with a discovery step before stage one. Each gate asks a different question:

• Gate 1, idea screen: Does this fit our strategy, and is it feasible enough to scope?
• Gate 2, second screen: Is the business case credible after early research?
• Gate 3, go to development: Are the definition, budget and plan solid enough to commit real resources?
• Gate 4, go to testing: Does the product meet its specification so far?
• Gate 5, go to launch: Do test results, production readiness and launch plans support release?

Notice that the cost of a wrong “go” rises at every gate. Early gates are light and fast. Late gates deserve the most scrutiny.

Government IT

Public agencies use gates too. The U.S. Department of Health and Human Services publishes a stage gate review practices guide as part of its Enterprise Performance Life Cycle, a framework meant to strengthen IT governance through disciplined investment and project management. It is a useful model if your clients are institutions that expect documented decisions.

Video and post-production

Media projects rarely call them gates, but they have them. A typical documentary, commercial or branded series moves through these checkpoints:

Each row has a different bar. At the rough cut, you are approving structure and story, not color or music. If the client signs off on structure and then asks to restructure at fine cut, the gate has failed. Our posts on dailies review and the first deliverable sign-off checklist show how to make the early gates stick.

Localization and versioning

If the same asset ships in several languages, you need gates per language, not one gate for the master. A translated script can be approved while a dubbed version is still in review. A workflow like multilingual content production shows how language files can be packaged for review before delivery, and the same principle applies to captions and subtitles: each language version is its own deliverable with its own approver.

Match the gate to the project

Stage-gate is better understood as a framework you adapt than a template you copy. The PMI white paper discusses Robert Cooper’s view that the process should be flexible, which is why leading practitioners scale it to the project. A three-day social edit and a six-month brand film should not share the same gate paperwork.

A simple scaling rule:

• Small projects (days): Two or three light gates. One approver. Checklist, not scorecard.
• Mid-size projects (weeks): Four or five gates. A named client approver and an internal approver. Short scorecard.
• Large projects (months): Full gates with evidence packs, formal outcomes and a recorded decision log.

The mistake to avoid is bureaucracy that outweighs the risk. If a gate takes longer than the work it governs, people will route around it, and then you have no process at all.

Criteria that make approvals fast

Fast approvals come from clear criteria, not from pressure. Write criteria that a reviewer can check without asking you a question.

Weak: “The cut feels right.”

Strong: “Runtime is within 60 seconds of the brief. All approved script points appear. Legal lines are on screen for at least four seconds. Audio levels pass the platform spec.”

A good criterion is:

• Observable: a reviewer can check it against the deliverable.
• Specific to the stage: it does not drag in later-stage concerns.
• Agreed in advance: it is in the brief or statement of work, not invented in the review.
• Tied to a decision: if it fails, the outcome is recycle or hold, not just a comment.

Tie revision limits to the same logic. When the statement of work says two included rounds, each round is a gate with a defined scope. We walk through this in revision rounds and SOW rules and in the two-round creative approval workflow.

Where approvals break down

These are the failures we see most often in creative and production teams.

Approvals in email threads. The decision exists, but it is spread across forty messages. Six weeks later nobody can say which version was approved.

Unclear version. The client approves “the cut,” but there were three cuts that week. An approval without a version reference is worth very little.

Silent approvers. A gatekeeper who does not respond holds the project hostage. Set a deadline in the gate definition and state what happens at expiry: deemed approved, escalated, or on hold.

Scope creep dressed as feedback. Late stakeholders add requests that belong to an earlier gate. The fix is to log them as change requests with a cost, not as notes.

Rubber stamps. If every gate passes, the criteria are too soft or the evidence is not examined. Track your recycle rate. Zero is a warning.

Uniform rigidity. One heavy process for every project. See the previous section.

How to run stage gate approvals step by step

1. Define the stages and gates before kickoff. Put them in the project plan and the contract.
2. Name gatekeepers per gate, with a backup for each.
3. Write criteria for each gate and share them with the client at the start.
4. Set an evidence pack. List exactly what must be submitted: the deliverable, notes resolved, budget and schedule status, open risks.
5. Lock the version under review. Reviewers see one version, with a clear number.
6. Set a response window. For example, two business days, with an escalation path.
7. Run the review. Score criteria, choose the outcome, record conditions.
8. Log the decision with date, approver, version and outcome.
9. Close the actions before the next gate opens, or carry them as explicit conditions.
10. Review the process after the project. Which gates caught problems? Which were noise?

If you want to test a lighter version first, our approval tracking workflow is built to be validated in a single week, and the seven-step creative ops workflow shows how the pieces fit together.

Perspective: gates are a record, not a ritual

We build Posthive for teams that deliver media, so we see approvals from the unglamorous side: the file, the version and the signature. Our view is simple. A gate is only as good as the record it leaves. The meeting is the least important part.

Most approval pain in post-production is not disagreement. It is ambiguity about which version was approved, by whom, and against what. That is why we built the workspace around version management, task and deadline tracking, client feedback and approval tracking, and secure delivery in one place. When the cut, the notes and the sign-off sit together, a gate becomes a quick decision instead of an archaeology project.

We also think clients should own their deliverables and versions, and that gatekeepers should never be rationed by a seat count. That is why every plan includes unlimited free seats: your client, your producer and your editor can all be in the review without anyone paying per person. If the person who must approve cannot get in the room, you do not have a gate.

Our advice to any team: start with fewer gates than you think you need, write the criteria down, and make the version under review impossible to confuse.

— Lorenz

Tracking gate approvals in Posthive

If your gates currently live in email and shared drives, Posthive gives you one workspace for projects, versions, deadlines, review and client approvals, with plugins for NLEs and Google Calendar integration so review dates land where people already look. Each plan includes unlimited free seats, so clients can approve directly. Pro is $49 per month and Enterprise is $99 per month; see Posthive pricing for what each tier includes, or start from the Posthive homepage.

FAQ

What is the difference between a stage gate and a phase gate?

In practice they are the same idea. Both split a project into stages or phases with a formal review between each one. Some organizations reserve “stage-gate” for the product innovation model with its specific five stages, and use “phase gate” for general project phases, but the mechanics of work, review and decision are identical.

Who should approve at a stage gate?

A small group of named gatekeepers with authority over the budget and the scope of the next stage. Keep the group to a few people, define whether one owner or a majority decides, and separate them from the team that did the work. In client projects, include one client signatory so approval is binding.

How long should a gate review take?

As short as the evidence allows. If reviewers read the evidence pack in advance, most reviews are a short decision meeting. Lighter projects can run a gate as an asynchronous approval with a response deadline and no meeting at all.

What happens if a project fails a gate?

It does not have to be the end. The outcome is usually recycle, meaning rework the stage and return, or hold, meaning pause until a constraint lifts. Kill is reserved for cases where the business case no longer works. Record the reason in every case so the next review has context.

Do stage gates slow down creative work?

They can if applied rigidly. Scaled to the project, they usually save time, because the criteria are agreed up front and late changes get caught at the stage where they are cheapest to fix. Use light gates for small jobs and reserve formal reviews for decisions that are costly to reverse.

Sources

• Project Management in Product Development, PMI
• Optimizing the Stage-Gate Process: What Best-Practice Companies Do
• Incentives in a Stage-Gate Process, Harvard Business School
• Stage Gate Review Practices Guide, U.S. Department of Health and Human Services

Recommended

• Two Round Creative Approval Workflow for Production Teams
• One Week to Validate Your Approval Tracking Workflow for Creative Managers
• Approval Matrix: Who Can Sign Off on a Rough Cut or Final Delivery?
• Checklist First Deliverable Sign Off for Project and Creative Leads