How it works
Prepare. Manage. Sustain. The AI drafts every step — you approve it.
A three-phase flow that mirrors how the best change teams work, with the Acclaim toolkit's readiness assessment as the lens, Block's stakeholder model for the people, and ITIL-style governance for the technical side.
01
Prepare
Log · case · impact · approach
- Log the change in plain English — the type picks its approval path (Change Manager → Sponsor → CAB, or ECAB for emergencies). Or paste your notes and choose “Draft everything” to get the case, stakeholders, comms, training and metrics in one review pass.
- Write the case for change and the vision — the co-pilot pre-fills the structured prompts from your description; you edit and confirm.
- Assess impact (1–5) and let the co-pilot score risk 0–100 with rationale, top risks and mitigations.
- Pick a playbook — ADKAR, 3-phase, Kotter, ITIL, Lewin — to pre-seed comms, training and metrics.
- Map stakeholders on agreement × trust (Block's model). People you've mapped before are suggested as you type, or bring a whole group across from a previous change.
02
Manage
Approve · communicate · train
- Submit for approval. Each approver decides in sequence with comments; the audit trail records it.
- Schedule against the change calendar — blackouts and overlapping changes on shared teams are flagged.
- Run the comms plan: audience, message, channel, preferred sender, timing — with the ready-to-send body. “Draft this week” proposes what is due next, for your review.
- Log every stakeholder conversation with a note; drag people across the grid as they move and watch the approach update.
- Mark training not run / run / completed and re-run the readiness assessment per team before go-live — quick estimate or the full 25 toolkit questions.
03
Sustain
Adopt · reinforce · prove
- Watch adoption metrics — targets vs actuals — on the dashboard and across the portfolio.
- Every time you open a change, “Since you were last here” shows what moved — stakeholder shifts, comms sent, approvals, re-checks — with a jump to each.
- Draft the weekly sponsor update from what actually happened — wins, slips, asks — then edit, copy or save it to the plan.
- Reinforce: work the engagement approach for each stakeholder type, celebrate the wins, retire the old way.
- Complete the change; it stops counting towards your band the same day and everything stays in the audit history. Export the workbook to Excel whenever you like.
Ask Gayle
An adviser who has read your change.
Gayle sits inside the workspace and answers from your live data — who's still a Detractor, which team's Knowledge score slipped, what's due this week — as well as the method behind it. Answers stream in; nothing is changed unless you act on it. Included AI allowance on every plan, or bring your own key.
ChangeOS is from the makers of ProjectPlanOS and shares its design language and its “AI drafts, you approve” rule.
you › Who on CHG-1041 haven't we spoken to in two weeks?
gayle › Three: AP clerks lead (Detractor, last contact 16 days), Procurement (Neutral, 15 days), Warehouse supervisor (Sideline Supporter, 14 days).
gayle › Suggest: floor-walk with AP clerks before Thursday's go-live comms. Want me to draft the invite?
› nothing sent until you say so