Free, no email required
The 30-Day Pre-Opening Cutover Checklist
40 things that have to be true before a multi-unit technology cutover — and the 9 that most teams miss.
Same 40 items, worded for your format. No form, no email, no sequence. Print it and walk it with the person who owns each item.
What's in it
Every item is counted back from the opening date. Any line where you can't name a human being and a date is a risk, not a task.
- T−30Confirm and freeze
Dates, permits, circuit IDs, scope, owners. Everything downstream inherits the errors you leave here.
- T−21Provision and stage
Hardware, imaging, key injection, merchant IDs, store records. Staged wrong is worse than not staged.
- T−14Validate
Circuit tested both directions, offline mode proven, every integration exercised one at a time.
- T−7Rehearse
Mock service at real volume, runbook published, rollback plan with a named decision-maker.
- T−1Cutover day
Go/no-go on the record, first live transaction settled before doors open, exception log manned.
- T+1 to T+7Hypercare
Written exit criteria, every day-one exception closed, defects fed into the next store's staging.
The 9 most commonly missed
If you only walk nine lines, walk these. They share a trait: each one looks complete until the day it isn't. These nine are the nine lines I walk on every call.
- Failover that isn't diverse.
Two circuits, one provider, one physical fiber path into the building. It passes every test you'll run and fails the one event it exists for.
- Key injection and merchant ID alignment.
The terminal powers on, takes a card, prints a receipt — while routing to the wrong MID. Nobody catches it until reconciliation.
- Offline mode that was assumed, not tested.
Almost every team says the system handles offline. Very few have pulled the cable in that store, on that hardware.
- A wireless survey done before fixtures went in.
Shelving, fixtures, racking and canopies change the RF environment completely. The pre-fixture survey described a building that no longer exists.
- Integrations tested as a group instead of one at a time.
Teams test "the POS" and declare victory. The downstream systems fail one at a time, starting at your busiest hour.
- Peak-load behavior.
One transaction at a quiet counter runs perfectly. A dozen at once across every station expose a queue, network or printing limit nobody wrote down.
- A rollback plan with no named decision-maker.
At 6:40 a.m. everyone on the call is waiting for someone else to say stop — so nobody does, and you open broken.
- Settlement confirmed at the terminal but not at the bank.
A batch closing successfully is not money arriving. The gap surfaces days later as a finance escalation.
- Hypercare with no exit criteria.
Store number two inherits every problem store number one had.
If you can't name an owner and a date on five of these
That's not unusual, and it's not a reflection on your team. It's what happens when a rollout is staffed by people who also have day jobs, and nobody's full-time responsibility is the date itself.
That gap is what the KeyDate Audit exists for: a fixed-scope, two-week review that returns every material risk to your opening date with an owner and a mitigation attached. Independent. No vendor commissions, ever. Find fewer than five material risks and you don't pay the second half.
Deon Coleman — 18+ years leading multi-site technology rollouts for restaurant and retail brands, including programs led inside Shake Shack, Macy's, Under Armour and Carter's/OshKosh, store cutovers across 2,200 locations for a major retailer, and venue deployments delivered at SoFi Stadium, Gillette Stadium, UBS Arena, State Farm Arena, Globe Life Field, Hartsfield-Jackson ATL and Brown University.