Bubble tea order-taking six-point checklist - drink, size, sugar, ice, toppings, destination; compressed to three questions at peak, with the cup sticker read-back as the final gate before sealing

You are an operations supervisor for a bubble tea shop.
Produce a printable order-taking checklist to post beside
the register screen.

Structure (order it by the real sequence of taking an
order, not by importance):

Section 1, six points on every order:
□ Drink - what the customer said maps to a menu name;
  size and hot/cold variants count as different drinks
□ Size - medium or large; state our default size first
  [blank to fill]
□ Sugar - state our default sugar level first [blank
  to fill]; if the customer does not specify, use the
  default and repeat it back
□ Ice - for hot drinks this point becomes temperature
□ Toppings - "no topping" must be confirmed too; never
  treat skipping the question as a default no
□ Destination - for here or to go + name or number

Section 2, peak three questions (queue longer than 3):
□ Sugar and ice in one sentence ("Regular sugar and
  ice okay?")
□ Any toppings?
□ For here or to go?

Section 3, read-back rules:
□ Single drink: turn the screen toward the customer
  for a visual confirm
□ Two drinks or more, or any modification: read the
  whole order back verbally

Section 4, assembly-side second check (the final gate
before sealing):
□ Read the printed cup sticker aloud - drink / size /
  sugar-ice / toppings / destination - all matching
  before the lid goes on
□ Delivery tickets: compare the sticker against the
  platform ticket side by side

Section 5, miss recovery (2 minutes at close each day):
□ For every remake or modified order today, log which
  of the six points was missed
□ Count weekly: whichever question was missed most
  moves to first position in next week's peak three

Format:
- Fits on one A5 sheet, checkboxes as □
- The peak three questions boxed separately, visually
  distinct from the six points
- Miss recovery as a compact table row at the bottom,
  sized for one week

Constraints:
- No "be careful" / "double-check everything" attitude
  lines - only actions and sequence
- Do not decide our default size or sugar for us -
  leave blanks; defaults differ by brand, and a wrong
  pre-filled default is worse than none
- Do not grow the list past six points: six is the
  upper bound a cashier can actually ask during a
  rush; add a seventh and the whole sheet gets
  abandoned

Why it is written this way

Ordering by the real sequence instead of importance matters because a checklist is read aloud line by line, not memorized - importance ordering suits training material, sequence ordering suits something taped beside a screen. Drink first, destination last: a cashier who scans the sheet has effectively taken the order without mentally re-sorting anything.

"'No topping' must also be confirmed" gets its own line because half of all remakes come from "I assumed they didn't want any" - treating a skipped question as a default is the most invisible form of order error. For the same reason, defaults are left blank for the shop to fill: brands default to different sugar levels, and a checklist that pre-decides the default has planted a systematic error inside the process.

The peak three questions are a compression of the six points, not a separate list, so the switch is instant when the queue grows. Three rather than four or five puts "askable" ahead of "complete": at peak, this checklist's enemy is not error but the queue - three questions fit in the time available, which is the only reason staff will keep using the sheet.

Miss recovery turns a static checklist into a self-correcting process. Log one line per remake - which question was missed - and after two weeks the data speaks: if sugar dominates, next week's first question is sugar. Without the recovery loop the sheet is one more piece of paper on the wall; with it, the checklist's content evolves to match this store's actual error pattern.

Variables