neart.ai
EcosystemStoryHow We BuildPricingBlog
Try Inspected →
neart.ai
EcosystemStoryHow We BuildBlog

Ní neart go cur le chéile

A SaltCore Group Limited company

© 2026 neart.ai · SaltCore Group Limited. All rights reserved.

Delivery & PMO

Which Metrics Tell You Your Stage-Gate Process Is Actually Working?

17 July 20254 min read

## The short answer


To know whether your stage-gate process is working, track a handful of governance-health metrics rather than just project status. The most telling are: **gate cycle time** (how long decisions take), **stop and pivot rate** (whether gates ever change direction), **conditional-pass closure rate** (whether agreed conditions get done), and **benefit-estimate accuracy** (whether the cases you approve come true). Together these show if your gates are adding assurance or just adding delay.


## Measure the process, not only the projects


Most PMOs measure project delivery — on time, on budget, on scope. Far fewer measure the *governance itself*. Yet a stage-gate process can quietly fail in ways project metrics never reveal: gates that take weeks to convene, boards that approve everything, conditions that are never closed. Governance-health metrics expose these.


## The metrics that matter


### 1. Gate cycle time


How long from a team being ready for a gate to a decision being made? Long cycle times mean governance is a bottleneck — teams idle while waiting for a board. Track the median and the worst cases. Rising cycle time is an early warning that your process is becoming a tax.


### 2. Stop and pivot rate


What proportion of gates result in something other than a straight pass? A board that passes everything is not exercising judgement. You are not aiming for a high stop rate for its own sake, but a rate of effectively zero strongly suggests rubber-stamping. This is one of the clearest signals of governance value.


### 3. Conditional-pass closure rate


When gates pass with conditions, are those conditions actually completed by their due dates? A low closure rate means conditional passes are a polite way of ignoring problems. Track open conditions and their age; ageing, unclosed conditions are accumulating risk.


### 4. Benefit-estimate accuracy


Compare the benefits and costs approved at the business-case gate with what was actually realised at closure. Persistent over-optimism tells you your gates are not scrutinising cases hard enough — and lets you calibrate future estimates.


### 5. Rework triggered after a gate


How often does work pass a gate only to be reopened because something was missed? High post-gate rework points to weak exit criteria or evidence that was not really examined.


### 6. First-time gate pass rate


The share of gates passed without being deferred or sent back. Very low suggests teams arrive unprepared or criteria are unclear; very high *combined with* a near-zero stop rate suggests the gate is too easy.


## Read the metrics together, not in isolation


No single number is meaningful alone. The interesting signals come from combinations:


- High first-time pass rate **and** near-zero stop rate → likely rubber-stamping.

- Long cycle time **and** high rework → the board is slow *and* not catching issues.

- Many conditional passes **and** poor closure → conditions are a fudge for "not ready".

- Optimistic benefit estimates **and** no stops → cases are being waved through.


## Instrument the process so the data is honest


These metrics are only useful if they are captured automatically as part of how gates run — decision dates, outcomes, conditions and their status, approved versus realised benefits. Collected by hand in spreadsheets, they decay immediately. The better approach is to make the gate process itself generate the data as a by-product. Enterprise delivery platforms, including those neart.ai builds, capture gate decisions and conditions as structured records, so governance-health metrics emerge without extra effort.


## Use the metrics to improve, not to punish


The purpose is to tune the process, not to name and shame boards. Rising cycle time might mean you need a lighter gate pack or more frequent board slots. A zero stop rate might mean stop criteria are missing. Poor benefit accuracy might mean business cases need independent challenge. Treat each metric as a prompt for a process change.


## A minimal starter set


If you track nothing today, start with three: gate cycle time, stop/pivot rate, and conditional-pass closure rate. These three alone reveal whether your governance is fast, decisive and following through — the qualities that separate real assurance from ceremony.


## Takeaway


Measure your governance, not just your projects. Gate cycle time, stop and pivot rate, conditional-pass closure and benefit accuracy together reveal whether stage gates add assurance or merely friction. Read the metrics in combination, capture them as a by-product of running gates, and use them to refine the process rather than to blame the people running it.

Related posts

Delivery & PMO

What Is Stage-Gate Governance and How Do You Run It Well?

Delivery & PMO

How Do You Run a RAID Log That Delivery Teams Actually Use?

Delivery & PMO

Earned Value Management Explained: A Practical Guide for Delivery Leaders