RoostRoost Flow
Change control without the meeting
Roost Flow is ITIL-style change enablement, made asynchronous: design the approval workflow once on a canvas, then let requests route themselves through manager and CAB gates — with risk graded, plans attached, and every decision on the record.
Design the gauntlet on a canvas
The workflow builder is drag-and-drop on a real canvas: drop stages, approval gates, action tasks, and branch steps straight onto an edge and the chain re-links itself. Start from the seeded ITIL templates — Standard, Normal, Major, Emergency — or build your own from scratch.
Branching that routes itself
Branch steps read the request's priority and risk level and send it down the right path — urgent hotfix to the short lane, high-risk change through the full CAB. Forward-only by construction, so cycles can't happen.
Versioned and pinned
Publishing snapshots the workflow into an immutable version. In-flight requests stay pinned to the version they started on — editing a template never rewrites history. Undo/redo, live publish validation, and a leave guard keep drafts safe.
The request rides the map
Every request renders its own live progress canvas: green for passed, a pulsing amber ring where it stands now, vote tallies on the gates, and the rejection path traced in red when one was taken.
Approvers that resolve themselves
Gates route to named people, to reusable groups like CAB and ECAB, or dynamically to the requester's manager. Approval rules: any one voice, everyone, or N-of-M quorum. Out-of-office? Approvals delegate automatically.
Approvals on your time
No weekly change meeting. Approvers get a personal queue with a pending badge, see the full risk assessment and plans inside the decision dialog, and the request advances the moment the rule is met.
Risk graded before anyone votes
Impact × likelihood on a 3×3 matrix produces the risk level, displayed everywhere the change appears — and branch steps can route on it, so a high-risk change takes the long way around.
Plans, not vibes
Implementation, rollback, test, and downtime plans as structured markdown sections. Workflows can refuse submission without a rollback plan — the gate that prevents the 2 a.m. scramble.
A calendar that says no
Planned changes land on the change calendar next to freeze windows. Raise a request into a freeze and Roost warns you before the CAB has to.
Rejection with a path back
A rejected gate can terminate the request or send it back for rework — as a fresh attempt, with the failed one preserved untouched in the record.
An audit log that can't be edited
Every transition, vote, and comment is an append-only audit event, exportable as CSV per request. Closed changes carry a post-implementation review verdict — successful, with issues, or failed — feeding an honest success rate.
Templates and recurring changes
Request templates pre-fill title, plans, risk, and workflow. Recurring schedules raise and submit routine changes on cadence — monthly patching that files itself.
Email where it matters
Approvers are notified when a gate activates, requesters when a verdict lands, and slow gates get a nudge after 24 hours. Sign-in itself uses emailed one-time codes.
Linked to the work — and the fallout
Tie a change to a board card, or spawn one at creation. If a change causes an incident, the incident links back — and the change wears it, feeding the change failure rate.
Put your next risky change through a real gate
Seeded ITIL workflow templates mean your first change request can go through review today.
Roost is in beta — access is invite-only while we build.