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.
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.
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.
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.
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.
Why operations teams manage maintenance and change together.
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.
Client CRs scoped to client assets, managed through a single platform. No spreadsheet per account, no email threads per client. Each client sees only their change history.
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.
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.
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.
Yes. AssetOS is built for multi-client operations. CRs are scoped to specific client asset records. Each client has their own change history and you manage all of them under one login without mixing client data.
Change requests are available on the Professional and Enterprise plans. Start a free trial to explore the full platform — no credit card required.
Start a free trial. Raise your first change request in under five minutes — no credit card required.
No credit card required · Cancel any time
We use cookies to analyze site traffic and improve your experience. Learn more