Community supermarket owner - first week of handing over the store checklist - tiered register passwords, three numbers reconciled every day, and the three things the owner keeps; presence fades day by day, and two weeks later three acceptance lines decide whether the handover took

You are the operations coach for the owner of a
single community supermarket. I've run this store
solo for [years running it] - register, ordering,
everything. Now I'm handing daily operations to
[handover target: a new hire / a long-time employee]
and keeping only the critical levers. My two fears:
the store falls apart on day one because they don't
know the job; or three months in I discover short
registers and supplier kickbacks. Build me a "First
Week of Letting Go" checklist from the skeleton
below, to tape up behind the register and follow
myself.

Part one - what gets handed over (for each item,
state "to what degree," and the degree must be
checkable):
1. Register: taking payment, refunds, shift-change
   cash count - handed over to "opens and closes
   the register solo"; the system's admin password
   stays with me
2. Receiving: check the delivery note, count, check
   dates, reject damaged stock - handed over to
   "verifies against the note and signs"; new
   supplier items and price changes stay with me
3. Shelving and restocking: first-in-first-out,
   fill gaps, pull short-dated stock forward -
   handed over to "works to the written standard";
   anything the standard doesn't cover, they
   photograph it and ask me
4. Scale and label printing: work off the code
   chart posted at the scale; no creating new codes -
   report to me instead

Part two - the three things the owner keeps (fixed;
nothing may be added):
1. Cash: daily takings collected and banked - they
   report the numbers, I check the numbers
2. Ordering decisions: what to order, how much,
   from whom - staff can report out-of-stocks;
   I place the order
3. Prices and promotions: every price change,
   rounding authority, giveaways - staff sell off
   the shelf tag; I set the tags

Part three - week one rhythm (one line per day):
Days 1-2: I'm in the store; they work, I watch;
correct, don't take over
Days 3-4: I'm in the store but stay out of the
register area; after close I check the three
numbers
Days 5-7: I come in for half a day; check the
three numbers plus one spot check (short-dated
pulled forward / signed receiving slips / shift
log / one random receipt recount - rotating)

The three numbers, checked every day (definitions
fixed; no inventing a fourth):
yesterday's system sales / cash counted in at
handover / bank deposit posted - if the three
don't agree, finding out why is the first thing
tomorrow morning; discrepancies never sleep
overnight

Part four - acceptance lines at two weeks (all
three must pass for the handover to count):
- Five consecutive days with all three numbers
  agreeing
- During my half-days away, no "what do I do about
  X" phone calls in normal trading hours
- Two spot checks run total, no exceptions found
Any line that fails: that block comes back to me
for one more week of shadowing, then re-acceptance

Prohibitions:
- No "build full trust" or "communicate more" -
  the checklist holds only checkable actions
- No "theft tests" layered on top of the
  reconciliation (planting counterfeit notes,
  posing as a shopper) - security comes from
  transparent daily reconciliation, not from
  entrapment; once a trap is suspected, the
  reconciliation itself stops being trusted
- The three-number definitions cannot be changed
  or extended - add a fourth and nobody checks
  any of them daily
- Don't assume roles my store doesn't have (no
  second cashier means no "cashiers cross-check"
  line)
- Every line must be judgeable as done or not done
  within one minute; anything that fails that gets
  split or cut

Why it is written this way

"The three things the owner keeps," written as a fixed list that may not grow, is the foundation of the whole checklist. The first cause of failed delegation is not employee capability - it's the owner handing over incompletely. Every small thing retained becomes one more blind spot the employee learns not to own, and the owner ends up chained to the store anyway. Cash, ordering, and pricing are where a single store's risk genuinely concentrates: cash is direct loss, kickbacks on ordering and casual markdowns are slow bleeds. Everything else in daily operations can run on process without disasters - which is exactly the calculus that makes letting go survivable.

The three daily numbers are the only safety net after handover, and they're pinned to system sales, cash counted, and bank posted - three figures from three sources that can't quietly collude with each other. A gap anywhere in the chain fails to reconcile and cannot hide. "Never sleep overnight" is discipline, not advice: once a discrepancy ages past a day, camera footage, memory, and slips all start to blur and the cost of untangling multiplies. The daily close-out also does quieter work - the employee knowing it reconciles every single day is itself the strongest rule a small store can have.

The week-one fade (watching, then staying out of the register area, then half-days) builds the ramp that handovers usually skip. The two classic failures are extremes: supervising so closely that nothing transfers, or vanishing on day one and leaving the employee to improvise in panic. The fade tells the employee help is near and tells the owner what the store looks like without them. The acceptance lines define "it took" as three checkable facts rather than a feeling - five clean reconciliation days, no rescue calls, clean spot checks. Failing a line sends one block back for another week, which is cheap; pretending it took is what's expensive.

The ban on entrapment tests deserves its own word: an owner at peak anxiety is most tempted to run fake-shopper or planted-note tests for peace of mind. These get discovered (most do), and the moment they're suspected, the genuine safety net - transparent daily reconciliation - is spent. What's left is mutual suspicion. The rule's authority comes from certainty, not surprise: every day checked, every day closed. That's security built on process, not on surveillance.

Variables