Published 2 October 2026 · Online guide
Agree the programme boundaries
Define the business processes, entities and modules in scope before committing to a rollout plan. Identify process owners and decision rights. Distinguish standard configuration from custom development, and record dependencies on finance, procurement, supply chain and reporting. A shared scope baseline makes trade-offs visible.
Govern data and change
Assign ownership for master data, migration rules and reconciliation. Test representative transactions across process boundaries rather than validating modules only in isolation. Document how scope changes affect cost, schedule, training and support. Establish who can approve a change and how the updated baseline is communicated.
Prepare cutover and adoption
Set acceptance criteria for integrations, data reconciliation and business readiness. Rehearse cutover with named responsibilities, stop criteria and recovery options. Plan role-based training and support for the transition. Confirm the handover arrangements for defects and operational issues.
Working checklist
Maintain a scope baseline, decision log, dependency register, migration plan, reconciliation evidence, test plan and cutover runbook. Review open risks at agreed decision points. Use objective acceptance criteria instead of assuming that installation means business readiness. These controls support planning and oversight; delivery time, cost and business outcomes depend on the actual programme and are not guaranteed by a checklist.
General planning guidance. Adapt the framework to your systems, business requirements and applicable obligations.
Explore related technology insights