Standard changes that are actually standard

A standard change is a pre-authorised change with a defined procedure and a known low risk. It is not a shortcut for skipping governance when someone is in a hurry.

Why it matters

Teams need speed for repeatable, well-understood work: certificate renewals, approved firewall rule templates, routine user access patterns, catalogued environment refreshes. If every one of those goes through a full assessment board, change becomes a queue. If everything is labelled “standard” without evidence, risk hides in the volume.

Good change management protects the service and still lets predictable work move.

What makes a change standard

Before I pre-authorise a type of change, I want four things in place:

1. A written procedure people can follow without improvising.
2. Evidence that the change has been done successfully enough times to trust the pattern.
3. Clear entry criteria: when this path is valid, and when it is not.
4. A named owner who keeps the procedure current and reviews failures.

Standard does not mean unsupervised. It means the authorisation decision was made once for the pattern, not for every ticket that matches the name.

What good looks like

The catalog lists a small set of standard changes with links to the procedure, not a long menu of hopeful labels.

When something goes wrong, the failure is recorded and the standard path is paused or tightened until the procedure is fixed.

Emergency and normal changes stay available for work that does not fit the pattern. Nobody forces a risky deployment into a standard template to avoid a conversation.

Auditors and engineers can both answer the same question: why was this pre-authorised?

Common mistakes

Calling a change standard because it is “small” or “quick.” Size is not risk.

Letting the procedure drift while the ticket type stays the same. The authorisation was for a method, not a title.

Using standard change for the first attempt at something new. Prove the pattern first as a normal change.

Skipping implementation records. Even pre-authorised work needs a trail of what was done and the outcome.

Takeaway

Standard change is earned by repetition, clarity, and low known risk. Keep the label honest, and both delivery and governance move faster.