Run the change in one place, then hand it over cleanly

You already know how to run change. The question isn't method — it's the apparatus around it: the version-controlled decks, the stakeholder spreadsheet only you understand, the readiness story you reconstruct from memory for every steering committee, and the handover that leaves the client with a zip file they never open. ChangeOS is built to carry that apparatus for you, and to hand it over as something the client can actually run.

Why run it in a system at all

Because the value you add is judgement, and judgement is easy to lose in administration. When readiness, the stakeholder map, the comms plan and the decision record all live in one place and update each other, you spend your hours reading the situation and deciding what to do — not rebuilding the picture. The co-pilot drafts the case, the plan, the risk score and the week's comms in your client's sponsor's voice; you edit and approve. It's leverage, not autopilot.

Evidence, not anecdote, at the steering committee

• Readiness measured per team and re-checked over time, so you can show movement rather than assert it.
• An anonymous participant pulse and a comprehension check — how ready people feel, and what they actually understood — reported by group, never by individual.
• A recorded, attributed go/no-go at each gate, with the readiness evidence captured by value at the moment you decided, so the record can't drift later.
• A branded report the client keeps — your logo, your findings — that reads like the work you did, because it is.

The diagnostic for a change you've inherited

Half the engagements that reach a consultancy are already in trouble. The Assess stage is a time-boxed diagnostic for exactly that: capture one-to-ones (what a source tells you in confidence is never attributed to them in any report or export — only that accounts differ, and with what confidence), reconstruct a timeline marked asserted, corroborated or documented, and decide at a gate whether to proceed. If it's a relaunch, link it to the failed attempt so the history, the drift and the cynicism are carried across rather than forgotten.

Partner-only notes that stay yours

You hold things the client shouldn't see — the sponsor who's privately wavering, the stakeholder who's the real blocker. Partner-only notes are never visible to the client and never transfer at handover; they move to your practice's private vault. The confidentiality your work depends on is built in, not a discipline you have to maintain by hand.

A clean handover — and a client who can keep going

When the engagement ends, you review exactly what the client will see, then transfer ownership of the workspace. They inherit a living change — readiness history, stakeholder map, the plan, the decision record and its conditions to verify in Sustain — not a static deliverable. You choose whether to keep the billing relationship or hand it to the client. The work you did stays usable after you've gone, which is the difference between a report and a result.

A folder of decks is a record of what you did. A transferred workspace is a capability the client keeps — and it's a far better advertisement for the next engagement.

Every change makes the next one sharper

Closed changes contribute a de-identified outcome — no names, no notes, no free text — to an anonymous benchmark: what tends to land, at what readiness, for which kinds of change. Across a practice running many changes, that's a compounding asset you can bring to the next client, honestly.