N NoBullshit.wiki 中文

Hotpot restaurant field supervisor - inspection finding grading and recheck SOP: Class A stops the line on the spot, Class C never gets a corrective sheet

Works with:Claude / GPT-4 classCategories:Hotpot RestaurantLevel:Intermediate Updated

You are the supervisor-system designer for a chain hotpot brand.
Turn the grading and recheck process for inspection findings into
an archivable SOP.

Part 1 - Grading (three fixed grades, each with a locked
disposition)

Class A (food safety and compliance, handled on the spot)
- Triggers: sample retention missing or log broken; expired or
  spoiled product present in the working area; thawed stock
  re-frozen; staff with expired health permits on shift
- Disposition: stop-sale + seal + photographic evidence on the
  spot; written report up the chain the same day. Class A has
  no "deadline" - only on the spot

Class B (structural execution drift, deadline + recheck)
- Triggers: broth output off the reference sample; repeated
  peak-hour sauce-bar stockouts; cleaning collapse (ranges,
  pots, accumulated grease); equipment running sick (refrigeration
  out of spec and still in use)
- Disposition: the corrective sheet must carry three elements -
  what changes / how it is verified / recheck date. Missing any
  one, the sheet is not issued

Class C (experience items, demonstrate + observe)
- Triggers: service kit (apron, phone bag, hair tie) not offered
  proactively; unfamiliar recommendation and answer scripts;
  slow but not collapsed table clearing
- Disposition: no sheet. Demonstrate once on the spot, log it
  in the visit record, observe in passing next visit - writing
  C up is how C drowns B

Part 2 - Recheck rules
- Recheck scope: every prior Class B item plus spot checks of
  adjacent areas for the same class of problem (last time the
  sauce bar; this time also glance at prep stock for the broth
  push). Never a full re-inspection - a recheck verifies "did
  it change," and re-inspecting everything dilutes the focus
- Recheck evidence: each B item verified per the sheet's stated
  method (photos / logs / on-site measurement); a verbal
  "fixed" does not count
- Repeat escalation: the same Class B problem failing two
  consecutive rechecks escalates - company stores to the
  regional manager and into the store manager's review;
  franchise stores into the brand's contract channel. The
  supervisor stops pushing alone - pushing what cannot be
  pushed, over and over, rots the supervisor's credibility
  and the problem together

Part 3 - Documentation
- Banned words on corrective sheets: "strengthen," "pay
  attention," "emphasize," "continue" - any occurrence bounces
  the sheet back for rewrite. Every item must be verifiable:
  what to look at, what state counts as passing
- Visit records list A / B / C separately; C entries record
  facts only, no appraisal

Part 4 - Discipline
- Grading addresses problems, not people: no employee names on
  sheets, only posts and observed conditions
- When the supervisor is unsure of the class (A-like or
  B-like), grade up, never down
- This SOP contains no appraisal or penalty schedules - those
  belong to HR and the contract

Constraints:
- The three-grade frame and its dispositions are bound tight;
  no "use judgment" clause - judgment is exactly what this
  grading exists to eliminate
- No regulation citations - triggers are phrased per the
  brand's food-safety standard; local regulatory requirements
  govern the specifics

Why it is written this way

The heart of the grading is protecting Class B. Write everything up and the store goes desensitized to corrective sheets, real structural problems drowning in a pile of "didn't offer the apron" - a sheet's gravity is diluted by its count. Not writing up Class C looks like lightening the store's load, but it actually clears the road for B: paperwork drops, and every sheet that does get issued carries weight. It is equally a constraint on the supervisor - issuing sheets is the lowest-effort action, it looks like managing, and it spreads the supervisor's own attention thin too.

Rechecks covering only the prior items target the supervisor's most common failure: conducting the recheck as a fresh inspection. Inspect everything every time, "discover" new problems every time, and every problem lives only as long as the supervisor's three minutes of attention - the remediation loop needs narrow, deep rechecks, not broad, shallow repeat inspections. The definition is written into the rules: a recheck answers "did it change," not "let's have another look."

"Strengthen / pay attention / emphasize / continue" are banned because those four words are the commonest legal escape on corrective sheets: an item reading "strengthen sample management" cannot be verified as changed or not, and turns into one-word-against-another later. Every item must translate into "what to look at, what state passes" - an item that won't translate means the supervisor hasn't decided what they want yet, and shouldn't issue the sheet.

The escalation channel admits the supervisor's power boundary: a problem two rounds of pressure can't move sits outside the supervisor's authority, and pushing it anyway spends their credibility along with the problem. Writing "when to let go, and to whom" into the SOP makes letting go a process step instead of a dereliction.

Variables

Variable Notes
Class B deadlines Days allowed - tier by problem type (cleaning from 3 days, output from 7), one schedule across the whole region, never store-by-store pricing
Recheck interval The "date" in dated recheck - 7 to 14 days suggested; closer and the fix hasn't landed, farther and the focus has dissolved

store inspectionsremediation loopgrading