Fresh supermarket cashier - shift-handover till reconciliation SOP, over/short in tiers, never "cashier pays the difference"

You are a cashier-operations consultant for a fresh-food supermarket.
Write an archivable SOP for shift-handover till reconciliation.
Principle to align on first: the first goal of a reconciliation
system is not zero errors - it is errors surfacing onto paper.
What's hidden below the line is more dangerous than what's written
on it.

Input I will give you:
- Shift pattern (how many shifts, handover times)
- Float amount and change fund
- The small-amount tier line (see variables)
- Whether the POS can print per-shift: subtotal, refunds, price
  overrides, discounts

SOP structure:

1. The handover itself (fixed moves, face to face):
1. The outgoing cashier prints the shift subtotal - not the day
   total; the shift boundary is where responsibility divides
2. Float counted face to face and signed; till sealed and tagged
3. The incoming cashier re-verifies subtotal against cash in
   drawer - verification is not ceremony; any objection is raised
   at this step, after which the drawer is the incoming cashier's
   responsibility
4. Difference computed: counted - (subtotal - float) = over or
   short

2. Over/short handled in three tiers (actions fixed per tier):
- Small (at or below the tier line): log it, no pursuit, no
  repayment. Log fields: shift, amount, likely cause (checkbox:
  change error / abandoned transaction / coupon / scale-item
  override). Small variances pay off in the monthly aggregate,
  not in the single ticket
- Large: the outgoing cashier runs the fixed three-step
  self-check, in order - reprint and re-add the subtotal; review
  the shift's refunds; review scale-item overrides and discounts.
  Still unexplained after three steps -> duty supervisor, whose
  handling and logging spots the SOP names
- Pattern (escalation tier): the same cashier short across
  consecutive shifts, cumulative past a threshold (both lines in
  variables) -> referred to the store's standing process. Note:
  this tier is judged in the monthly aggregate, never at the
  handover itself - the handover logs, it does not diagnose
  patterns on the spot

3. Paperwork and filing:
- Reconciliation log column definitions: date / shift / cashier /
  subtotal / counted / difference / cause checkboxes / self-check
  result / signatures
- Refund and override vouchers filed by shift - every over/short
  investigation lives or dies on them
- Who runs the monthly aggregate and what they look at: per-
  cashier difference distributions, patterns only, never single
  tickets

Do not:
- Write "shorts are made up by the cashier" - flat repayment
  rules drive errors underground: staff quietly cover their own
  shorts, small variances vanish from the record, and the first
  visible event is the big one. That trade is how a control
  becomes a blindfold
- Write "count carefully" or "verify thoroughly" - adjectives
  with no moves in them don't enter an SOP
- Fill in the tier lines or thresholds for me - they stay
  variables
- Add any paperwork beyond "both parties sign; each keeps a
  copy" - every extra form costs execution rate

Why it is written this way

The design origin is stated up front: the enemy of a reconciliation system is concealment, not error. Cash variances form a pyramid - a broad base of small ones, a rare point of large ones - and the base is what makes the point explainable (a genuine pattern announces itself in the base first). A store that makes cashiers repay shorts buries its own pyramid: cover-your- own-short becomes habit, the paperwork glows clean, and the real problem compounds invisibly.

"Log small, no blame" only works paired with "aggregate monthly, look for patterns": a single small short isn't worth chasing, but the same cashier short across consecutive shifts isn't random anymore. Logging at handover and pattern-judging monthly is a deliberate separation - judging patterns at the handover is both impossible (no aggregate data in hand) and corrosive (every handover becomes mutual surveillance).

The fixed three-step self-check (reprint, refunds, overrides) is the cheap lane for large variances: most overs and shorts come from a missed refund or a scale-item override, and the three steps locate most of them without a supervisor. Lanes must be cheap or they go unused - a system where every variance waits for a manager ends up with no variances reported.

The ban on "cashier repays the difference" leads the prohibitions because it's the default clause in most drafted versions of this SOP - and the most fatal: it trades the system's information function for a zero-sum transfer. Of everything in this SOP, that one line needs the least explaining.

Variables