Change Advisory Board (CAB)

What is a Change Advisory Board (CAB)?

A change advisory board (CAB) is a group that reviews proposed changes to IT services and systems, assesses their risk and impact, and advises whether and when they should be implemented.

Updated November 2026 · 4 min read


A change advisory board (CAB) is a group of people who review proposed changes to IT services and systems, assess their risks and impact, and advise on whether and when they should go ahead. It is a feature of IT service management and the ITIL framework, where it helps the person or group authorized to approve changes make sound decisions. A typical CAB includes representatives from operations, development, security, the service desk and the business areas affected, and meets on a regular schedule, often weekly, to review upcoming changes.

CABs exist because changes are the most common cause of incidents. The board's purpose is to make sure significant changes are planned, tested, scheduled to avoid conflicts and backed by a way to roll them back. In recent years CABs have also become one of the most debated practices in IT, because heavy approval processes can slow delivery without making it safer.

Types of Change

ITIL distinguishes three types of change, and only some of them go to a CAB:

TypeDescriptionTypical approval
StandardLow-risk, well-understood and repeatable, such as adding a user or applying a routine patchPre-approved. No CAB review for each instance.
NormalAny change that is not standard or emergencyAssessed according to risk. Higher-risk normal changes go to the CAB.
EmergencyMust be made urgently, for example to fix a major incident or security vulnerabilityAn emergency CAB (ECAB), a smaller group that can convene quickly

How a CAB Works

  1. A change owner submits a request for change describing what will change, why, the risk, the test results, the implementation and rollback plans and the proposed timing.
  2. The change is assessed and categorized. Low-risk changes may be approved without the board.
  3. The CAB reviews higher-risk changes, checking for conflicts with other changes and business events, missing testing and inadequate rollback plans.
  4. The change authority approves, rejects or defers the change, taking the CAB's advice into account.
  5. After implementation, failed or problematic changes are reviewed to improve future decisions.

Many organizations also maintain a change schedule and blackout periods, such as the weeks around year-end close or peak retail season, when non-essential changes are not allowed.

The Debate Over CABs

In Accelerate (2018), Nicole Forsgren, Jez Humble and Gene Kim reported research from the State of DevOps surveys finding that requiring approval from an external body, such as a change advisory board, was associated with lower software delivery performance, and that they found no evidence it reduced the rate of failed changes. Reviewers far from the work often lack the context to judge risk, and batching changes for a weekly meeting makes each release larger and riskier.

ITIL itself has moved in the same direction. ITIL 4, which calls the practice "change enablement," emphasizes delegating authority to the level that best understands each change and does not require a CAB for every change. Many organizations now use a hybrid model:

  • Automated controls in the CI/CD pipeline, such as tests, code review and security scans, provide evidence that a change is safe.
  • Most changes are standard or low-risk and are approved by peer review within the team.
  • The CAB focuses on genuinely high-risk changes, such as major infrastructure or cross-team migrations, and on improving the process using data on failed changes.

Change Advisory Board vs. Change Control Board

A change control board (CCB) is a related but different body, common in project management, systems engineering and configuration management. A CCB decides whether to accept changes to a project's agreed baseline, such as its requirements, scope, design or schedule, and weighs their effect on cost and delivery dates. A CAB, by contrast, advises on changes to live IT services and infrastructure. Some organizations use the names loosely, but the distinction is between changing what a project will deliver and changing systems already in operation.

An Example

Consider a hypothetical insurer whose weekly CAB reviews about 120 changes, each with a 30-minute slot booked in advance. Releases wait an average of five days for approval, and the change failure rate is 18%. The company classifies 85% of its changes as standard once pipeline checks pass, sending only database migrations, network changes and changes to core policy systems to the CAB. The board now reviews about 15 changes a week in more depth. Over two quarters, lead time for changes falls from about eight days to two, and the change failure rate drops to 9%, because the board spends its time on the changes that actually carry risk.

Common Pitfalls

  • Every change goes to the CAB, creating queues and pushing teams toward large, risky batches.
  • Rubber-stamp meetings where dozens of changes are approved with little scrutiny.
  • Members without context who cannot judge technical risk.
  • No feedback loop from failed changes into how risk is assessed.

The CAB is part of release management and the wider IT service management system, and change approval is often tested as part of IT general controls audits.