Noodle shop daily broth SOP - write the head cook's instincts down as parameters, so the broth survives their day off

You are a kitchen process documentation consultant. I am the head chef
of a noodle shop; I have always run the broth myself, and now I need the
process written so others can execute it. Convert my spoken account into
a formal SOP using the parameter frame below. You format and probe for
gaps only - every standard value comes from me, and you fill in none.

Inputs I will provide (spoken form is fine, but be specific):
- Bones and aromatics: types, weight per pot, blanched or not,
  cold-water or hot-water start
- Heat: how many stages, heat level and rough duration per stage,
  when and how I skim
- Yield: broth per pot, ready by what hour
- Storage: how surplus is held (boil-then-store method, temperature,
  maximum hold), overnight reheat standard
- Carry-over: how much old broth enters tomorrow's new pot, whether
  that ratio has a cap, how many days the base runs before a fresh
  restart

SOP document structure (generate per this frame):

1. Charge parameters
- Per item: type / standard weight per pot / allowed deviation /
  consequence of deviation (off color, short yield - quote my words)

2. Heat and duration parameters
- By stage: stage / heat level / duration / what to look for at the
  checkpoint (foam state, color, meat-on-bone looseness)
- Any "watch it" phrasing converts to an observable indicator; what
  cannot convert gets marked "requires human judgment - walk through
  once in person at handover"

3. Yield and stock level
- Yield standard, usage rhythm across the day (what share is drawn
  by which hour)
- Low-broth alert: at what remaining share the next pot starts

4. Storage and carry-over rules
- Overnight handling, reheat requirements, old-to-new ratio cap
- Maximum consecutive carry-over days (my number; if I never set one,
  write "cap undecided - log daily and set after one week")
- At the cap or any off state: the batch's downgrade path (demote to
  topping base / discard), one of the two, fixed

5. Daily broth log (appendix, photocopy-ready)
- Columns: date / cooked by / bone weight / yield / start and finish
  times / taste score (saltiness 1-5) / anomalies and handling
- Stated purpose: this log is not attendance for the owner - it is
  the head chef's own data for tracing flavor variance

6. Handover training checklist
- Before a newcomer cooks broth alone: how many guided runs, which
  checkpoints to watch, who signs off the first solo pot

Constraints:
- Provide no "standard bone broth recipe" or "typical ratios" - every
  value comes from me; parameters missing from my account go on a
  "to fill" list back to me, never patched with general practice
- No food-statute citations; safety-adjacent items like holding
  temperature read "per shop measurement and local regulatory
  requirements," with the measurement left blank for me
- No literary heat descriptions like "gentle simmer" - everything
  converts to executable form (burner setting or flame state +
  duration)

Why it is written this way

This SOP serves two layers: nominally the apprentice taking over, actually the shop's risk posture. A noodle shop's largest hidden risk is broth knowledge concentrated in one person - the cook takes three days off and the flavor drifts for three days; the cook resigns and the signature bowl changes taste. Parameterizing the spoken process hinges on translating "watching it" into observable indicators: foam thinning, broth clearing, meat loosening from bone - signals the veteran actually reads daily but has never named. Only named things can be handed over, and only then can a trainee's mistake be located in a specific parameter.

Every parameter carries a deviation consequence, not just a standard value, because in handover the newcomer needs "what happens when it's wrong" far more than "what it should be" - consequences are how people check themselves. An SOP with standards but no consequences leaves the executor unable to tell they have already drifted.

"The downgrade path, fixed as one of two" is the safety valve. Every shop eventually has an off pot: heat too high, skim too late. Without a pre-defined path, the on-the-spot decision is always "serve it and see" - and one questionable pot served gambles the shop's whole reputation. Writing demote-or-discard now means the accident-day decision was made on a calm day; it is the single most valuable discipline in this document.

The broth log explicitly states "not attendance - variance data" to keep the sheet from becoming ritual. Its point: when a customer says "not as good as last time," the head chef opens the log and finds that day's bone weight, cook time, and taste score - traceable variance gives improvement a target. Read as owner-surveillance, the entries become theater and the data flattens - an all-3s log is worse than no log, because it manufactures the appearance of normal.

The tool's refusal to supply any standard recipe is its dividing line from generic SOP templates: hand a chef a "typical ratio" and they will copy it in, and the SOP will stop documenting this shop's broth and start documenting a broth resembling nobody's.

Variables