DataTerminology.comNEW
Also known as: Phase Gates, Stage Gates, Quality Gates
Formal checkpoints in a lifecycle where stakeholders review evidence and authorize progression.
DESCRIPTION
Approval gates control risk by requiring evidence and sign-off before advancing to the next stage. In data and ML, gates validate data quality, privacy, model risk, and deployment readiness. Effective gates are lightweight, automated where possible, and tied to objective criteria. They align teams, prevent regressions, and enforce compliance. Overly heavy gates can slow delivery and should be balanced with continuous delivery practices.
ALTERNATIVE DEFINITIONS
Wikipedia
The phase-gate process is a project management technique in which a project is divided into distinct stages, or phases, separated by decision points (known as gates).
Introduces the concept of stages separated by decision gates.
Project Management Institute
A phase-gate is a governance structure that uses review points to evaluate performance and decide whether to continue, modify, or stop a project.
Positions gates explicitly as governance checkpoints for decisions.
RELATED TERMS
Change Request Process Governance Policies SDLC CAB Releasing Data Contracts Risk Assessment Impact Analysis Segregation of Duties
COMPETING TERMS
RELATIONS
- Broader: Approval Process
KNOWLEDGE AREAS
Data Management Collaboration Testing & Validation Software Engineering MLOps
TARGET AUDIENCE
Data Governance Manager DevOps Engineer MLOps Engineer Data Architect Chief Information Officer Enterprise Architect AI Product Manager
EXTERNAL SOURCES
- Wikipedia - Phase-gate process
- Google SRE - Release gates via SLOs
- Microsoft - Azure Pipelines approvals
TOP QUESTIONS
What is the purpose of Approval Gates in data and ML workflows?
To ensure quality, safety, and compliance by verifying objective criteria—like data tests, privacy checks, and model risk—before promotion.
Category: Purpose
How do you avoid Approval Gates slowing delivery?
Automate evidence collection and checks, use risk-based gates, and focus on objective, easily measured criteria.
Category: BestPractice
What evidence is typical for an Approval Gate?
Test results, data quality reports, lineage and impact analysis, security/privacy assessments, and rollback plans.
Category: Requirements
How do Approval Gates relate to CABs?
Gates are checkpoints; Change Advisory Boards may review high-risk changes at those points and authorize progression.
Category: Governance
Are Approval Gates compatible with Continuous Delivery?
Yes, when gates are automated and lightweight, enabling fast feedback while retaining control for critical risks.
Category: Opinion
What are common mistakes with Approval Gates?
Subjective criteria, manual reviews for low-risk changes, and unclear ownership lead to bottlenecks and inconsistency.
Category: Mistakes
How do you measure gate effectiveness?
Track lead time impact, change failure rate, escaped defects, and compliance findings to balance speed and safety.
Category: Metrics
Where should gates be placed in a data pipeline?
Before production deployment, schema changes, critical transformations, and releases that affect SLAs or regulated data.
Category: Design
Who approves at an Approval Gate?
Designated approvers such as product owners, data stewards, SREs, security/privacy officers, or change managers, depending on risk.
Category: Roles