What is a Quality Gate?

What is a Quality Gate?

A quality gate is a formal decision checkpoint embedded in the product development lifecycle. At a gate, a cross-functional team examines documented evidence — test results, design reviews, requirement traceability matrices, risk registers — and makes a binary decision: the product meets the criteria to advance, or it does not. Unlike a progress meeting or a status update, a gate has teeth. A product that fails a gate does not move forward.

The concept originates in the stage-gate methodology developed by Robert Cooper in the 1980s, which divided product development into discrete stages separated by gates. Each stage has a defined purpose — concept development, feasibility, detailed design, validation, launch. Each gate has defined entry requirements (what must be true before the review can even occur) and exit criteria (what must be demonstrated before advancement is permitted). The PLM systems that manage product development today are built around this logic, implementing gates through lifecycle state transitions that require authorized approvals before an object can change state.

Quality gates are not bureaucratic overhead. They are the principal mechanism by which organizations prevent the compounding cost of late-discovered defects. A manufacturing defect costs roughly ten times more to fix than a design defect, and a field defect costs ten times more than that. A gate that catches a structural analysis gap at the design review stage prevents an expensive tooling rework, a program delay, and a potential field failure — all in a single decision.

Why Quality Gates Matter in PLM

PLM systems are, at their core, systems of record and workflow control. They do not merely store product data; they govern how product data moves through the lifecycle. Quality gates are the governance checkpoints at which PLM enforces the rules an organization has agreed to follow. Without gate enforcement inside PLM, design teams can release incomplete configurations to manufacturing, manufacturing can begin tooling before design is stable, and suppliers can receive drawings that have not yet been approved. The PLM system becomes a filing cabinet rather than a control system.

In regulated industries — aerospace, defense, medical devices, automotive safety systems — quality gates are not optional. They are required by quality management frameworks such as ISO 9001, AS9100, APQP (Advanced Product Quality Planning), and ITAR-regulated programs. Gate records, including who approved what and when, become part of the regulatory submission package. PLM systems that manage gate approvals electronically with audit trails are a compliance prerequisite, not a luxury.

Common Use Cases

• Concept gate (Gate 1): Before significant development resources are committed, a concept gate reviews market requirements, technical feasibility, and business case. The PLM system ensures that a requirements baseline exists and has been reviewed before any design work begins.
• Design freeze gate: Before manufacturing engineering begins tooling design, a design freeze gate confirms that the product geometry and bill of materials are stable and approved. PLM enforces design freeze by restricting modification rights on released configurations.
• Manufacturing readiness gate: Before first article inspection or production ramp, a manufacturing readiness gate validates that the MBOM, work instructions, and process plans have been released and that quality control plans are in place. PLM and MES records provide the evidence trail for this decision.

Related Concepts

• What is PLM? — the system of record within which quality gates are defined and enforced
• Engineering Change Management in PLM — the formal process that governs changes after a gate has been passed, including design freeze violations
• What is PLM Lifecycle Stages — the phases between gates and how PLM manages transitions across the full product lifecycle

Frequently Asked Questions

What is the difference between a quality gate and a design review?

A design review is a collaborative examination of the design itself — engineers discussing whether the architecture is sound, whether requirements are met, whether risks are understood. A quality gate is a governance decision that follows from a review: given the evidence from the design review (and other sources), does this product meet the criteria required to advance? The gate is the decision; the review is one input to it. Many programs conflate the two, which produces design reviews that never actually stop anything from advancing.

What happens when a product fails a quality gate?

A failed gate returns the product to the current phase with a documented list of deficiencies that must be resolved before the gate can be attempted again. The program plan absorbs the delay. This is painful in the short term but far cheaper than discovering the same deficiencies during manufacturing qualification or, worse, in the field. Failed gates are the most cost-effective form of quality intervention available — the earlier in the lifecycle a problem is caught, the cheaper it is to fix.

How do PLM systems enforce quality gates?

PLM systems enforce quality gates through lifecycle state management and workflow controls. An object — a document, a part, a BOM — can only transition from one lifecycle state to the next when an authorized approver signs off and required conditions are met. Some PLM platforms support rule-based gate automation: a design release gate might require that all associated test reports are in an approved state before the release workflow can proceed. Without PLM enforcement, quality gates become suggestions rather than controls.