Orpington's ERP Go Live Readiness Checklist
O R P I N G T O N T E C H N O L O G I E S
How to use this checklist
Use this checklist four to six weeks before your planned go-live date — early enough to remediate a serious gap without moving the date. Each item should be verified with documented evidence: a signed-off report, a test log, a reconciliation file — not a verbal "yes, that's done" in a status meeting.
1. EXECUTIVE SPONSORSHIP AND GOVERNANCE
8 points
☐
A single, named executive sponsor is accountable for the go-live decision — not a rotating
steering committee chair.
☐
The sponsor has personally reviewed and approved the cutover plan, not just the project
timeline.
☐
Go/no-go decision criteria are documented in writing and agreed before the decision
meeting, not debated during it.
☐
Business process owners for every affected function have formally signed off on their
area's readiness.
☐
An escalation path exists for issues discovered during cutover, with named decision-
makers reachable that weekend.
☐
Budget and contingency reserve remain available for post-go-live stabilization support, not
fully exhausted at cutover.
☐
Legal, compliance and audit stakeholders have reviewed control changes introduced by
the new system.
☐
A post-go-live governance cadence (daily standups tapering to weekly) is scheduled, not
left to be improvised.
2. CHANGE MANAGEMENT AND TRAINING
9 points
☐
Role-based training has been delivered — not generic system training — using each
department's real transactions.
☐
Training completion is tracked by name and role, with a documented plan for anyone who
has not completed it.
☐
A super-user network is identified, trained and has real authority — established weeks
before cutover, not assembled during it.
☐
Quick-reference job aids exist for the highest-volume transactions in each affected role.
☐
Communication has been segmented by role ("what changes for you"), not delivered as
generic project updates only.
☐
A help-desk or support channel specific to the new system is staffed and communicated to
all users.
☐
Adoption metrics (login rates, workaround usage, ticket themes) are defined and
dashboarded before go-live.
☐
Known process changes that will be unpopular have been explicitly acknowledged by
leadership, not glossed over.
The ERP Go-Live Readiness Checklist | Page
2
of
5