How many quality gates should a project have?

Enough to catch defects at the cheapest stage; few enough that overhead is justified. Typically 5–10 on a large capital project, plus automated CI gates per commit.

Who owns a quality gate?

Each criterion has a named owner; the gate as a whole has a chair (often the project director or quality lead).

Should gates be automated?

Wherever possible. Automation removes politics and accelerates feedback.

What if a gate fails?

Either rework and re-submit, or a documented waiver with executive sign-off.

Can gates slow delivery?

Poorly designed gates can. Well-designed gates accelerate delivery by preventing downstream rework.

How do agile teams use gates?

Per-commit automated gates plus per-release manual checkpoints (security, compliance, accessibility).

What is the warning sign of a broken gate?

100% pass rate or 100% block rate. Both indicate the criteria are wrong.

Which calculators on PMMilestone.org apply to Quality Gate?

For Quality Gate, the most relevant tools on the flagship platform are the Schedule Health Checker and DCMA 14-point quality assessment. They reproduce the formulas referenced in this entry against your own project data.

What is a common misconception about Quality Gate?

That quality cost only includes inspection. The cost-of-quality model includes prevention, appraisal, internal failure and external failure — and on capital projects external failure (rework, claims, defect liability) usually dwarfs the others.

Which related encyclopedia entries should I read alongside Quality Gate?

Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.

How does Dr. Hassan Eliwa's research treat Quality Gate?

Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Quality Gate is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.

How is Quality Gate defined on PMMilestone Research & Insights?

A formal checkpoint at which work is evaluated against pre-defined criteria and either passed forward, paused for rework, or stopped — preventing defects from flowing into later, more expensive stages. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.

How many quality gates should a project have?

Enough to catch defects at the cheapest stage; few enough that overhead is justified. Typically 5–10 on a large capital project, plus automated CI gates per commit.

Who owns a quality gate?

Each criterion has a named owner; the gate as a whole has a chair (often the project director or quality lead).

Should gates be automated?

Wherever possible. Automation removes politics and accelerates feedback.

What if a gate fails?

Either rework and re-submit, or a documented waiver with executive sign-off.

Can gates slow delivery?

Poorly designed gates can. Well-designed gates accelerate delivery by preventing downstream rework.

How do agile teams use gates?

Per-commit automated gates plus per-release manual checkpoints (security, compliance, accessibility).

What is the warning sign of a broken gate?

100% pass rate or 100% block rate. Both indicate the criteria are wrong.

Which calculators on PMMilestone.org apply to Quality Gate?

For Quality Gate, the most relevant tools on the flagship platform are the Schedule Health Checker and DCMA 14-point quality assessment. They reproduce the formulas referenced in this entry against your own project data.

What is a common misconception about Quality Gate?

That quality cost only includes inspection. The cost-of-quality model includes prevention, appraisal, internal failure and external failure — and on capital projects external failure (rework, claims, defect liability) usually dwarfs the others.

Which related encyclopedia entries should I read alongside Quality Gate?

Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.

How does Dr. Hassan Eliwa's research treat Quality Gate?

Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Quality Gate is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.

How is Quality Gate defined on PMMilestone Research & Insights?

A formal checkpoint at which work is evaluated against pre-defined criteria and either passed forward, paused for rework, or stopped — preventing defects from flowing into later, more expensive stages. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.

Quality · Letter Q

Quality Gate

A formal checkpoint at which work is evaluated against pre-defined criteria and either passed forward, paused for rework, or stopped — preventing defects from flowing into later, more expensive stages.

By Dr. Hassan Eliwa, PhD · Founder of PMMilestone.org and PMMilestone.com · Updated 2026-06-26

Definition

A quality gate is a formal checkpoint in a delivery process at which work is evaluated against a defined set of pass/fail criteria before it proceeds to the next phase. Gates exist at architectural reviews, design freezes, code-promotion stages, commissioning hand-offs, regulatory inspections, and executive go/no-go decisions. They embody the same principle as jidoka: catch problems where they are cheapest to fix.

Why It Matters

Without gates, defects flow downstream and compound. A design error caught at the design gate may cost a day to fix; the same error caught at commissioning may cost millions. In software, a security vulnerability caught at the pre-merge gate costs minutes; the same vulnerability in production may cost reputation and regulatory exposure.

Anatomy of a Good Gate

Pre-defined, measurable criteria — not opinions in a meeting.
Clear ownership of each criterion.
Evidence required for each criterion — test reports, peer reviews, signed checklists.
A documented escalation path for waivers, with executive sign-off.
Time-bounded review — not an indefinite hold.

Real-World Construction Example

A $310M data centre adopted nine formal quality gates from design through commissioning. Each gate had a 30–80 item checklist signed by the owner, contractor, and independent commissioning agent. At gate 5 (electrical pre-energisation), two undersized transformers were caught; rework cost $180k but avoided a multi-month delay that would otherwise have appeared during black-start testing.

Real-World IT Example

A regulated payments platform implemented automated quality gates in its CI/CD pipeline: lint, unit tests, integration tests, security scan, license scan, performance regression, accessibility scan. Each commit had to clear all seven before merging. In the first year, the gates blocked 1,400+ defects, with an estimated avoided remediation cost of over $1.8M.

Common Mistakes

Subjective criteria. "Looks good" is not a gate.
Rubber-stamp gates. A gate that always passes is decoration.
No waiver process. Real projects need a documented route around exceptional cases.
Too many gates. Gates have overhead; place them where the cost-of-defect curve is steepest.
Gates without authority. A gate the project director can override informally is not a gate.

Expert Tips

Automate every gate criterion that can be automated.
Make gate results visible on the project dashboard — transparency drives behaviour.
Trend gate pass-rates over time as a leading indicator of process health.
Pair gates with Definition of Done for daily-level enforcement.
Review gate criteria at retrospectives; they should evolve with the project.

Practical Lessons Learned

The most effective gates are unambiguous and binary. Anything requiring judgement degrades into politics.
Resistance to gates is almost always a sign that the criteria are wrong, not that gates are wrong.
Healthy gates have a non-zero block rate. A gate that has never failed is not a gate.

Key Takeaways

Quality gates catch defects where they are cheapest to fix.
Good gates have measurable criteria, owners, evidence, and a waiver process.
Automate gates wherever possible.
Healthy gates block real work occasionally; gates that always pass are decoration.
The principle applies equally to construction phase gates and CI/CD pipelines.

Related Encyclopedia Entries

Frequently Asked Questions

How many quality gates should a project have?
Enough to catch defects at the cheapest stage; few enough that overhead is justified. Typically 5–10 on a large capital project, plus automated CI gates per commit.
Who owns a quality gate?
Each criterion has a named owner; the gate as a whole has a chair (often the project director or quality lead).
Should gates be automated?
Wherever possible. Automation removes politics and accelerates feedback.
What if a gate fails?
Either rework and re-submit, or a documented waiver with executive sign-off.
Can gates slow delivery?
Poorly designed gates can. Well-designed gates accelerate delivery by preventing downstream rework.
How do agile teams use gates?
Per-commit automated gates plus per-release manual checkpoints (security, compliance, accessibility).
What is the warning sign of a broken gate?
100% pass rate or 100% block rate. Both indicate the criteria are wrong.
Which calculators on PMMilestone.org apply to Quality Gate?
For Quality Gate, the most relevant tools on the flagship platform are the Schedule Health Checker and DCMA 14-point quality assessment. They reproduce the formulas referenced in this entry against your own project data.
What is a common misconception about Quality Gate?
That quality cost only includes inspection. The cost-of-quality model includes prevention, appraisal, internal failure and external failure — and on capital projects external failure (rework, claims, defect liability) usually dwarfs the others.
Which related encyclopedia entries should I read alongside Quality Gate?
Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.
How does Dr. Hassan Eliwa's research treat Quality Gate?
Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Quality Gate is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.
How is Quality Gate defined on PMMilestone Research & Insights?
A formal checkpoint at which work is evaluated against pre-defined criteria and either passed forward, paused for rework, or stopped — preventing defects from flowing into later, more expensive stages. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.

Quality Gate

Definition

Why It Matters

Anatomy of a Good Gate

Real-World Construction Example

Real-World IT Example

Common Mistakes

Expert Tips

Practical Lessons Learned

Key Takeaways

Related Encyclopedia Entries

Related Research Articles, Case Studies & Tools

Frequently Asked Questions

People also ask

Which book goes deeper than this entry?

Which calculator on PMMilestone.org applies here?

Where is this in the glossary?

Which learning track covers this end-to-end?

Related Entries

Further reading on PMMilestone.org