Change requests that reach CAB ready.
CAB workflow, auto-generated templates, testing checklists, and back-out plans — built in, not bolted on. Raise CRs for software, infrastructure, and operational changes in the same platform you use for work orders.
CRs reach CAB with half the fields missing.
- ✕CR raised by email — no standard fields, half missing
- ✕CAB approval via Slack DM — no audit trail, no timestamp
- ✕Testing plan written from scratch every time (when written at all)
- ✕Back-out plan: "we'll roll back if needed"
- ✕Client CRs tracked in a separate spreadsheet per account
- ✕No link between the CR and the software version being deployed
Template auto-fills. CAB approves. Evidence is automatic.
- ✓Change type auto-generates the right template — no blank fields reach CAB
- ✓CAB approval chain configured once — approvals timestamped in the record
- ✓Testing checklist built into the CR — sign off each step before CAB review
- ✓Back-out plan is a required section, not an afterthought
- ✓Client CRs scoped to client assets — all accounts in one platform
- ✓CR links directly to the software version record in Software Asset Management
Structured approval. Not a Slack thread.
Each change request routes through a configurable CAB approval chain. Approvers receive notifications, record their decision, and the full approval history is permanently attached to the CR — timestamped, named, and exportable for audit.
- Configurable CAB chain per change type — standard, normal, and emergency flows
- Each approver receives a notification with the full CR detail
- Approval, rejection, or conditional approval — all options with notes
- Full audit trail: who approved, when, and what they reviewed
Pick the change type. Get the right form.
Standard, normal, and emergency changes each need different levels of scrutiny. When you select a change type, AssetOS auto-generates the correct template — pre-populating required sections, testing steps, and the right CAB approval chain. No blank fields. No forgotten back-out plans.
- Standard: pre-approved procedure, minimal fields, fast-tracked CAB
- Normal: full template — testing, back-out plan, business justification, full CAB
- Emergency: expedited form, reduced fields, post-implementation review auto-scheduled
- Custom templates configurable per team or client without engineering involvement
Every CR has a back-out plan. No exceptions.
Testing checklist and back-out plan are required sections on every normal and emergency CR — not optional fields that get skipped. Technicians sign off each testing step individually. The rollback procedure is captured and reviewed by CAB before approval is granted.
- Testing checklist with step-by-step sign-off — each step timestamped
- Back-out plan includes rollback owner, rollback procedure, and verification steps
- Testing status visible to CAB approvers before they vote
- Failed testing step halts CAB review — prevents incomplete changes reaching production
CR links to the version. Version shows the CR.
When a CR covers a software deployment, link it directly to the version record in Software Asset Management. The CR inherits the asset context — affected service, current production version, deployment environment. The software asset record shows open CRs in a dedicated tab.
- Link any CR to one or more software asset version records
- CR auto-inherits affected service and environment from the linked version
- Software asset record shows "Change Requests" tab — see every CR for that software
- Close the loop: CR approval → deployment logged against the version automatically
CRs and work orders. One platform.
Why operations teams manage maintenance and change together.
Built for the people who own the change process.
Stop chasing approvals across four channels.
CAB approval chain runs in the platform. Approvers get notified, vote with notes, and the audit trail builds itself. No more Slack DMs that disappear.
Raise CRs for every customer you support.
CRs scoped to each customer's assets, with their CAB contacts as approvers. No spreadsheet per account, no email threads per customer.
Every CR is audit-ready by default.
Approval timestamps, testing sign-offs, and back-out plans are captured automatically — not reconstructed before an audit. Export the full CR history as PDF in two clicks.
Common questions
What is the difference between a change request and a work order?
Work orders cover routine and reactive maintenance — assign to a technician, execute, close. Change requests cover formal modifications to systems, software, or infrastructure that need CAB approval, a testing plan, and a documented rollback before work begins. AssetOS manages both in the same platform.
How does CAB approval work in AssetOS?
Each CR routes through a configurable approval chain. You define the CAB members per change type (standard, normal, emergency). Each approver receives a notification, reviews the full CR including testing status, and casts their decision with optional notes. All decisions are timestamped and attached to the record.
Can we use AssetOS as an MSP raising CRs for client systems?
Yes. CRs are scoped to the assets you look after for each customer, with that customer's CAB contacts as approvers, and the change history filters by customer.
Is change request management available on all pricing plans?
Change requests are available on the Professional and Enterprise plans. Start a free trial to explore the full platform — no credit card required.
CRs that reach CAB complete, every time.
Start a free trial. Raise your first change request in under five minutes — no credit card required.
No credit card required · Cancel any time