Recipe Consistency Checklist

Daily and per-shift workflow the sous chef and line leads run to keep plates consistent across stations, shifts, and locations. Covers spec-card adherence from receiving through plating, plus the line check and tasting cadence that catch...

Use this workflow
1

Receiving and Ingredient QC

  1. Check delivery against the PO and invoice
  2. Verify case counts and weights at the door
  3. Inspect produce, protein, and dairy for spec
  4. Probe-temp incoming TCS items
  5. Log delivery acceptance status
  6. Date-label and FIFO-rotate into the walk-in
2

Spec-Card Prep and Mise en Place

  1. Pull today's prep list against par sheet

    • Pull pars off the count sheet from last night's close. Cross-check against forecasted covers in Resy or OpenTable — Friday and Saturday almost always need a 1.3x bump on garde-manger items that prior pars don't reflect.

  2. Weigh prep batches on a calibrated scale

    • Use grams for anything under a pound; ounces drift fast on a scale that hasn't been calibrated this month. Verify the scale tare with a 100g check weight before each prep block.

  3. Build batch sauces to the spec card

    • Spec card lives in the prep binder; do not improvise from memory. The most common drift source is the line cook who's made the demi 200 times eyeballing the wine reduction — by Saturday the dish tastes different than Tuesday.

  4. Portion proteins into individual servings

    • Steaks, chops, and fish portions are weighed individually and stacked on quarter sheets between parchment. Tolerance is ±0.25 oz from spec — anything outside that goes to staff meal or family pre-shift, not to the line.

  5. Label every prep container with date and initials

    • Day-dot or masking-tape label: item, prep date, use-by date, prepper's initials. An unlabeled container is treated as unknown and discarded — no exceptions, even at the end of a slammed prep shift.

3

Pre-Service Line Check

  1. Walk every station with the sous chef

    • Sauté, grill, garde, fry, pastry. At each station, line cook presents pars, sauces, and proteins. Sous tastes the four heaviest-volume sauces and the day's vinaigrette before the line check is signed off.

  2. Taste and approve batch sauces

    • Salt, acid, and viscosity against the reference notes on the spec card. If a sauce is off, it gets corrected on the spot or 86'd before doors open — sending an off-spec sauce to service is the single biggest source of guest complaints in the comp ledger.

    Collects list
  3. Confirm 86 list and low-par items

    • Anything 86'd or running short gets posted in the POS (Toast, Square, Aloha) and called out in the pre-shift lineup. Servers cannot sell what the line cannot fire — sounds obvious, but it's the most common in-shift comp source.

  4. Re-batch or pull items flagged in line check

    • If line check flagged a batch sauce or component as off-spec, the chef de partie remakes it before service. Document what was pulled, why, and the corrective action taken — this is the audit trail that catches recurring drift on a specific station or shift.

    Collects paragraph
4

Service Execution

  1. Fire tickets to spec-card cook times

    • Cook times on the spec card are the standard, not a suggestion. Expediter calls fires based on table course timing; line cooks hit the spec time, not 'when it looks done.' Variance from spec-card time is the leading indicator of plate-to-plate inconsistency.

  2. Plate to the photo card at the pass

    • Laminated photo card lives at the pass for every menu item. Expediter compares each plate to the card before it leaves — sauce placement, garnish position, protein orientation. This is what keeps Tuesday's plate looking like Saturday's plate.

  3. Spot-check portion weights mid-service

    • Pull two random plates per hour at the pass and weigh the protein. Drift typically shows up between 7:30 and 9:00 PM when the line is in the weeds — that's when the cook starts hand-portioning instead of using the pre-portioned stack.

    Collects image
  4. Log every comp, void, and remake

    • Every comp gets a reason code in Toast or Aloha — overcooked, undercooked, wrong dish, allergen, off-flavor, presentation. The comp ledger is the truth source for which station or which dish needs intervention; without reason codes, you're just paying for theft and drift with no signal.

5

Post-Service Review and Training

  1. Review comp and remake reasons with the line

    • 15-minute post-service huddle. Pull the comp report from the POS, walk through every remake by station, name the spec-card section that was missed. Avoid blame — name the spec, name the gap, assign the fix.

    Collects list
  2. Schedule a re-training session for the affected station

    • If the post-service review flagged a recurring drift — same dish remade three nights running, same station miscounting portions — schedule a 30-minute pre-shift re-train at that station. Sous demos the spec, line cook executes, sous tastes and signs off before the cook is cleared back to the line.

  3. Update the spec card if a recipe has evolved

    • If the executive chef has tweaked a dish — new technique, new ingredient sub, new garnish — the spec card and photo card both get updated, dated, and re-printed for the prep binder. Verbal-only updates don't survive a Saturday night.

  4. File the night's line-check log

    • Line-check log, comp report, and any corrective-action notes go into the daily ops folder (R365, MarginEdge, or the GM's shared drive). The week's logs feed Monday's leadership review — drift trends only show up over a 7-day window, not a single night.

    Collects signature