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.
Capabilities
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
CAB membership and approval chains enforce SoD: developer ≠ approver ≠ basis admin. Constraints are configurable and audited.
Risk-based approval workflows
Standard, normal, and emergency change types with risk scoring. Higher risk triggers additional approval steps automatically.
Transport-as-Change (SAP)
SAP transports map to change records with STMS bidirectional sync, object-level collision detection, and landscape mapping.
Test evidence and rollback
Change records carry test evidence, rollback plans, and implementation notes — linked to affected CIs for full traceability.
Post-implementation review
A post-implementation review is required before a change can close — capturing what happened and whether it succeeded, so nothing closes without a record.
How this connects to regulation
Related features
FAQ
See TENSOR against your own compliance checklist.
30 minutes. We’ll map it to your DORA / NIS-2 / BAIT obligations.