Pilot rollout checklist

Source · CMS snapshot (seed) — this doc body is served from content/generated/cms-snapshot.json, not the code catalog alone. Staff path: Content Studio (:3030 /experience/sites) → Docs tab → publish doc → MCV_CONSOLE_URL=http://localhost:3030 pnpm --filter @mcv-tech/marketing-shell content:seed → rebuild :3050. Offline: MCV_CMS_SNAPSHOT_FILE=… pnpm content:seed. Category tree / nesting IA stays catalog-authored (L-DOCS); CMS overlays title / excerpt / body / updated only.

Pilot, prove, expand

This checklist describes the rollout shape we recommend to every multi-unit operator. It is deliberately conservative: the platform earns authority over your operation one proven workflow at a time. The companion essay, from pilot to portfolio, explains why nobody credible replatforms a portfolio in one move.

Before the pilot

1. Pick one bounded workflow with a real operator owner — not a portfolio, not a department, one workflow. The decision worksheet is the tool for bounding it.
2. Write the proof criteria down. What number or behavior must change for this to count as working, and by when?
3. Map system authority. Name which existing systems remain the source of record during the pilot, and for which fields.
4. Define the approval gates. Which actions in this workflow require human sign-off, and who gives it? The gate classification is at approval gates.

During the pilot

1. Run the workflow through the operator console with real work, not staged data.
2. Route exceptions to the named owner — and record how each one was resolved.
3. Leave the legacy system running. Divergence between the two records is signal, not noise.

The expansion decision

1. Review against the written criteria on the agreed date.
2. If the pilot proved out: the next brand, region, or department inherits sign-on, data boundaries, approval gates, and audit trail as-is. Expansion is configuration, not a new project — the inheritance model is described at multi-tenant architecture.
3. If it did not: you have a bounded, well-documented result — and a decision to adjust or stop that costs one workflow, not a migration.

What this page is not

This is public orientation, not a certification that any specific rollout succeeded. Live rollout status, exceptions, approvals, and evidence stay in the authenticated console.