Snack stall cashier - rush-hour order-accuracy checklist - three-point read-back on taking the order, special requests parked on a physical marker, three rules for mid-flight changes, every item done inside five seconds

You are a stall-operations trainer. At rush hour we take 20
straight minutes of nonstop orders, shouted in and called out -
one wrong order tangles everything behind it. Build "no wrong
orders" into a checklist taped inside the cart.

Usage constraints, stated up front: holdable with one hand,
scannable in one glance, every action done inside 5 seconds.
Items that fail any of the three do not appear on the list.

1. Taking the order (every single order)
□ Three-point read-back: item + quantity + special request
  (spice level / no cilantro or scallion / to-go or eat here)
  - "2 skewers, mild, to go" is enough; no pleasantries
  attached
□ Park the special request on something physical the same
  second: swap the marker skewer (e.g. mild always gets the
  [red] skewer), or sticker / mark the box - a request that
  lives in your head counts as not taken
□ When a group orders, take the order from one designated
  speaker only: anything added by others gets redirected to
  "tell it to the person ordering" - two voices on one order
  is how orders break

2. Handing off (every single order)
□ Match the marker, not the face: pick up by the special-
  request skewer; on number-called pickups, say "number +
  item" both - calling only the number roughly doubles the
  grab-it-wrong rate
□ To-go orders get the item initials and number written on
  the bag; only eat-here orders go by shout - identical bags
  sorted by shouting is the wrong-order disaster zone

3. Changes and interruptions (the messiest moment)
□ Mid-order changes: only items not yet on the grill or in
  the fryer can be changed; anything already cooking gets
  "that one's already going, it can't come back" - align
  this line with the owner before your first shift
□ Rush-chasers get progress only, never new orders: "three
  ahead of you" - absorbing new orders while fending off
  chasers is the single biggest source of fresh mistakes
□ When you catch your own wrong order mid-rush: call it out
  to the owner on the spot - "number X went wrong" - do not
  quietly remake it; quietly remade orders become one
  untraceable gap in the evening's count

Fixed footer line on the sheet: this list guards accuracy,
not speed - sacrifice the read-back to speed and one wrong
order costs you three orders' worth of time.

Rules:
- No "stay focused" / "be careful" items - they cannot be
  executed
- Every action is concrete enough to say what the hands are
  doing, one line each
- No new paper forms - nobody writes at rush hour; marking is
  done with skewers, stickers, and where things get placed

Why it is written this way

The enemy of an accuracy checklist isn't carelessness, it's the rush itself: across 20 nonstop minutes, any process that requires stopping to think gets abandoned on the spot. That's why the usage constraints come first - one hand, one glance, five seconds - they are the test of whether the list survives its first evening rush. A checklist with "strengthen verification awareness" on it becomes a piece of decorative tape on the third day and nothing more.

"Parking the request on something physical" is the load-bearing action of the whole sheet. Spice levels and exclusions that live only as spoken words make a wrong order a matter of time - an overloaded brain at rush hour is physiology, not attitude. Color-skewers, stickers, and box marks all do the same thing: externalize memory onto objects. "Mild always gets the red skewer" costs zero attention and gives handoffs a physical source of truth. Matching markers instead of faces is the same logic - faces misremember, skewers don't.

The three mid-flight rules get their own section because the messiest rush moment isn't volume, it's mutation: changes, chases, and add-ons all crowd into the same window. "Chasers get progress, not new orders" looks like turning away business, but it's protecting the cashier channel - the moment taking payments doubles as fending off chasers, new orders come in incomplete and the error rate jumps, costing more time than the one or two orders declined. "Call out your own wrong order, never quietly remake it" leaves the evening count a way to reconcile: a secretly remade order matches on neither the payments side nor the handoff side, and by month end it's just an unexplainable gap.

The footer - "this list guards accuracy, not speed" - is a disclaimer written to both the owner and the cashier: the moment an accuracy checklist gets used as a speed tool, the read-back is the first thing sacrificed, precisely because it's the most time-consuming item. Printing the priority beats explaining it ten times during training.

Variables