Standard change templates let you turn routine, pre-approved changes into one-click requests that bypass CAB review. This guide shows you how to build the template, get it approved, and make it available for technicians to use.
Why standard change templates exist
Before standard templates, every change request went through the same CAB approval process — even routine ones like password resets or standard software installs that happen dozens of times per month. This meant change managers spent hours reviewing identical requests, technicians waited days for obvious approvals, and CAB meetings got bogged down with administrative overhead instead of focusing on risky changes. The people who suffer most are the technicians who need fast turnaround on routine work and change managers who need to focus their review time on changes that actually matter.
How standard change templates work
A standard change template is a pre-defined change request that goes through one approval cycle upfront, then becomes instantly available for technicians to implement. You create the template with all the standard details filled in, submit it for CAB approval, and once approved, it becomes a reusable pattern. When technicians need that type of change, they create a standard change from your template — no CAB review, no waiting. The template defines what's allowed (specific software versions, approved maintenance windows, authorized implementers), and the resulting changes inherit that pre-approval.
Making templates production-ready
Basic templates work for simple scenarios, but production-quality ones include automatic task generation, proper risk assessment, and built-in compliance tracking. Add task templates so each standard change creates the right implementation steps automatically. Set up periodic review schedules — most organizations review standard templates quarterly to ensure they're still valid. Include clear scope boundaries in the template description so technicians know exactly when they can use this template versus when they need a normal change request.
Before you start
- •change_admin role or equivalent
- •CAB approval process configured in your instance
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
Create the standard change template
Navigate to Change > Standard Change Catalog > Standard Change Templates and click New. Fill in Short Description and Description with specific details about what this template covers — be precise about scope so technicians know when to use it versus request a normal change. Set Type to 'Standard', Category and Subcategory to match your change taxonomy, and Assignment Group to whoever will implement these changes.
Use naming conventions like 'STD - Software Install - Adobe Reader' so templates sort logically and are easy to find.
Configure template parameters
Set Risk to the appropriate level based on your change policy — most standard changes are Low risk by definition. Fill in Justification explaining why this qualifies as a standard change (routine, low-risk, well-understood procedure). In the Implementation Plan and Backout Plan fields, write generic procedures that will apply to all changes created from this template. Leave fields like Planned Start/End Date empty — technicians will fill these when they create the actual change.
Add change tasks if needed
Click the Change Tasks tab and add any standard implementation steps that should appear on every change created from this template. Each task should have a clear Short Description, proper Assignment Group, and realistic Planned Duration. Set the Order field starting at 100 so you can insert additional tasks later without renumbering.
Submit template for approval
Change the State to 'Assess' and save the record. This triggers your standard CAB approval workflow. The template needs to go through normal change approval once — after it's approved, it becomes available for creating pre-approved standard changes. Include supporting documentation in your CAB submission explaining the business justification and risk assessment.
Set up periodic reviews
Once approved, navigate back to your template and set the Review Date field to when this template should be re-evaluated (typically quarterly or annually). Fill in Next Review Date and Review Frequency according to your organization's policy. This ensures templates don't become stale and continue to reflect current procedures.
Test template usage
Navigate to Change > Create New and select 'Standard' as the Type. Your approved template should appear in the Standard Change Template dropdown. Select it and verify that all the template fields populate correctly. Create a test standard change to confirm the workflow bypasses CAB approval and moves directly to implementation state.
Best practices
Write template descriptions with clear scope boundaries — technicians need to know exactly when they can use this template versus when they need a normal change.
Set up automatic task generation on your templates even for simple changes — it ensures consistent implementation and better tracking.
Review standard templates quarterly at minimum — outdated templates create compliance risks and operational confusion.
Use specific version numbers and configuration details in template descriptions rather than generic terms like 'software updates'.
Assign templates to specific groups that are trained on those procedures — don't make every template available to every technician.
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