Standard Change
A pre-authorised class of change whose risk controls are automated and evidenced, so it does not need per-instance approval.
Traditional change management approves each change individually. Continuous delivery makes hundreds of changes. The two are reconciled not by exempting engineering from governance but by moving the approval up a level: a class of change is assessed once, its controls are agreed, and instances that demonstrably meet those controls are pre-authorised.
The assessment covers what the pipeline proves — tests, scanning, contract verification, progressive rollout with automated rollback — and what evidence each run emits. Once agreed, a conforming change proceeds without a board, and the evidence is available if anyone asks.
This is usually a better outcome for both sides than either party expects. Risk functions get continuous evidence rather than a meeting minute, and often better controls than the previous process had. Engineering gets to deploy. What makes it fail is trying to argue the controls are unnecessary rather than demonstrating that they are automated: the standard change route is earned by evidence, and the evidence has to be real.