Skip to main content
Service Management

Changes governed, not just tracked.

Change calendar with freeze windows, a Change Advisory Board with enforced segregation of duties, risk-based approval workflows, and full traceability from request through implementation to review.

What you can do

The controls that stop a change reaching production the wrong way.

Change calendar and freeze windows

A visual calendar of every scheduled change, with collision warnings when two changes touch the same CI or a shared service. Freeze windows block non-emergency changes during critical periods — month-end close, release weekends — scoped globally or to a category, service, or single CI.

CAB with segregation of duties

The requester of a change can never approve it, and the implementer can never be its sole approver — enforced in code, not configuration, so no tenant setting can switch it off. A single reject vote short-circuits the approval.

Quorums you can raise, never lower

Standard, Normal, and Emergency change types carry platform quorum floors (1 / 2 / 1 approvers). Workflow configuration can raise a quorum, narrow eligible approver roles, or require extra fields like a regulatory impact assessment — the Regulated preset does all three.

Transport-as-Change (SAP)

SAP transports map to change records with STMS bidirectional sync, object-level collision detection, and landscape mapping across DEV → QAS → PRD.

Test evidence that actually gates

A change model can require test evidence before implementation starts: at least one evidence item, every item passed or waived — and a waiver needs a written reason. An empty checklist blocks. Rollback plans are mandatory for Normal and Emergency changes before submission.

Post-implementation review

The PIR is captured on the change record itself, and a major-incident war room drafts one from its own timeline. Tenants that want a hard gate can make the PIR a required field on the closing transition.

Compliance relevance

How this connects to regulation

BAIT
BAIT 5 — Segregation of duties enforced in CAB approval chains.
MaRisk
AT 7.2 — Change governance with approval chains and test evidence.
DORA
Art. 8 — Change testing evidence and traceability.
Common questions

What change managers ask.

See TENSOR running on your own estate.

30 minutes, screen-shared, no slides. Bring the process you are least sure we handle and we will start there.