Change Advisory Boards automate the review scheduling for changes that require formal governance. This guide walks you through configuring recurring CAB meetings with the right members and change filters to route requests appropriately.
Why manual change review scheduling breaks down
Before CABs, someone manually tracked which changes needed committee review, scheduled meetings, sent agendas, and followed up on decisions. Change managers spent hours each week in email threads coordinating reviews, changes sat in limbo waiting for the next available meeting, and emergency changes bypassed governance entirely because the manual process was too slow. Platform teams that manage hundreds of changes monthly can't scale this approach.
How CAB automation works
A CAB definition combines three things: a recurring meeting schedule, a group of reviewers, and filters that determine which changes appear on the agenda. ServiceNow automatically adds matching changes to the next scheduled CAB meeting based on your criteria — change type, risk level, assignment group, or custom conditions. The CAB Workbench gives your change managers a single interface to review agendas, make decisions, and track outcomes. Start with one CAB for standard changes, then add specialized boards for different change types or business units as your process matures.
Scaling beyond basic change review
Production CAB implementations layer on approval workflows that automatically implement CAB decisions, integration with calendar systems to handle meeting conflicts, and custom change models that route to different CABs based on business criticality. You'll want separate CABs for infrastructure changes versus application changes, emergency review processes that can convene outside normal schedules, and reporting that tracks CAB decision patterns to identify process improvements.
Before you start
- •change_cab_manager role
- •Change Management plugin activated
Sourdough: ServiceNow Monitoring and Analytics
A Chrome extension for ServiceNow Admins and Developers with essential tools, analytics, graphs and monitoring features.
Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.
Step by step
Access the CAB Workbench
Navigate to Change > CAB Workbench. The workbench shows existing CAB definitions and scheduled meetings. Click New CAB Definition to create your first board. The definition establishes the recurring meeting pattern — you'll add members and filters in subsequent steps.
Configure the basic CAB settings
Set the Name (this appears in change records and notifications), select Active to enable the CAB, and choose your Time Zone for meeting scheduling. The Description field helps other administrators understand this CAB's purpose. Set Order to control which CAB processes changes first when multiple boards could apply — lower numbers run first.
Use descriptive names like 'Infrastructure CAB' or 'Emergency Review Board' rather than generic labels.
Set the meeting schedule
Configure the recurring meeting pattern in the Schedule section. Set Meeting Day (weekly meetings) or Meeting Days (multiple days per week), Meeting Time using 24-hour format, and Meeting Duration in minutes. The Next Meeting field auto-calculates based on your schedule. Enable Skip Holidays if your CAB doesn't meet during company holidays.
Define which changes appear
In the Filters section, set Change Type to specify which change categories this CAB reviews (Standard, Normal, Emergency). Add Assignment Group if this CAB only reviews changes from specific teams. Use the Condition Builder for complex criteria — risk level, CI relationships, or custom field values. Leave filters broad initially and refine based on actual change volume.
Test your filters with existing change data before activating the CAB to avoid overwhelming agendas.
Add CAB members
Click the Members tab and add Users or Groups who participate in CAB meetings. Set each member's Role (Chair, Member, Observer) which affects their permissions in the CAB Workbench. Members with Chair role can make final decisions on changes. Add email addresses for external stakeholders who need agenda notifications but don't have ServiceNow accounts.
Configure approval workflow integration
In the Workflow section, select the Approval Workflow that executes CAB decisions. The default 'Change CAB Approval' workflow handles standard approve/reject actions. For custom workflows, ensure they accept the change record and CAB decision as inputs. Enable Auto-approve changes with CAB approval if you want decisions to automatically advance the change workflow.
Test workflow integration with a sample change before processing production changes through the CAB.
Activate and verify the CAB
Save the CAB definition and verify the Next Meeting date appears correctly. Navigate to Change > CAB Meetings to see the scheduled meeting. Create a test change that matches your filters and confirm it appears in the meeting agenda. The change record will show the CAB meeting reference in the CAB section once it's added to an agenda.
Best practices
Create separate CABs for different change types rather than one massive board — infrastructure changes need different reviewers than application deployments.
Set conservative meeting durations initially and adjust based on actual agenda volume — a CAB that consistently runs over time loses member engagement.
Use groups instead of individual users for CAB membership so you can manage membership through group maintenance rather than updating every CAB definition.
Enable the 'Skip if no changes' option to avoid meeting notifications when the agenda is empty — this keeps members engaged when meetings actually matter.
Configure CAB filters to exclude changes that are auto-approved through other workflows to avoid redundant review processes.
Test Your Knowledge
Quick 3-question quiz — see how your ServiceNow skills stack up.
A list view on a table with millions of records is slow. Best fix?
Select an answer to continue