Skip to content
Tue, Oct 13, 2026 / Ideas for a clearer worldINDEPENDENT INSIGHTS · PRACTICAL TOOLS · EXPLAINERS
Sign in
Basics / July 22, 2021

Changes in the Standard

Standard Changes A Standard Change is a routine, low-risk, often-done change to the production environment that has been pre-approved by the full CAB and requires no further approval to enact in production. Some examples of Standard Changes anticipated are:        Addition of server memory or storage        Change to admin security access on server        OS patches on […]

Standard Changes

A Standard Change is a routine, low-risk, often-done change to the production environment that has been pre-approved by the full CAB and requires no further approval to enact in production.

Some examples of Standard Changes anticipated are:

       Addition of server memory or storage

       Change to admin security access on server

       OS patches on server

       Exposure of existing data elements in SQL view/Business Objects universe

Standard Changes should be codified in the form of a ServiceNow template that can be used to create a new instance of the standard change each time it’s needed, without requiring boilerplate data entry to be repeated.

While not subject to pre-approval, Standard Changes will be reviewed periodically by the full CAB for appropriateness.

Similarly, a completed Normal Change is a candidate to become a Standard Change template.  This happens when the CAB agrees that an approved Normal Change meets the criteria above and should become a repeatable process.

A template is created when the Change Manager sets the Normal Change’s “Approved by CAB for Standardization Template” flag on a completed Normal Change and creates the template.  Thereafter, the Standard Change template can be selected by name when applying a Standard Change Template when creating a Standard Change record.

For more information about creating a Standard Change Template.