Product
Changes
Typed change requests with CAB approval, conflict-aware scheduling, and questionnaire-scored risk assessment.
Change calendar showing scheduled changes and conflicts
Product screenshot coming soon
Change types and lifecycle
Not every change carries the same risk, so changes are typed from the start and move through a full lifecycle.
Standard, normal, and emergency types
Each change is typed at creation, which drives which approval and scheduling rules apply to it.
Full lifecycle tracking
From Draft through Implemented to Closed, every change carries an explicit, auditable state history.
Pre-approved standard templates
Routine, low-risk changes can run from a pre-approved template that bypasses the CAB approval step entirely.
Approval and risk
Changes that need sign-off go through a CAB workflow with quorum rules and a visible, questionnaire-driven risk score.
CAB approval with quorum
Change Advisory Board approval workflows enforce a minimum number of approvers before a change can proceed.
Separation of duties
The person who requests a change cannot also be the one who approves it.
Questionnaire-scored risk assessment
A structured risk questionnaire produces a visible risk bar on the change record, replacing gut-feel risk calls.
CAB approval workflow with quorum status
Product screenshot coming soon
Scheduling and conflicts
The change calendar catches scheduling problems before they become outages.
Conflict detection
Overlapping change windows and configuration-item awareness flag conflicts before a change is scheduled.
Freeze / blackout windows
Configured freeze windows block scheduling during blackout periods and surface a clear reason why.
Risk bar and scheduling conflict warning on a change request
Product screenshot coming soon
Implementation and review
Every change carries a plan for how it will go — and how to back out if it doesn't.
Implementation and backout plans
Changes record both the implementation plan and the backout plan before work begins.
Structured post-implementation review
Closing a change captures a structured post-implementation review rather than leaving the outcome undocumented.
Related
See it running on your tenants.
Get a walkthrough of incidents, changes, the customer portal, and the MSP admin console — tailored to how your service desk works today.