Daily Prep & Production Plan (station-by-station)
Complete station-by-station daily and weekly prep template that aligns forecasted covers and menu mix with prep quantities, par levels, batching, timing, carryover rules, and end-of-day yield checks. Includes instructions for linking to forecast data and quick updates during service.
Daily Prep & Production Plan — Station-by-Station
Purpose: Make the right amount of food at the right time. This template turns your forecast and par rules into clear station tasks, timing, batching notes, and end-of-day yield checks so service stays smooth and waste is minimized.
How to use this template
- Start with the forecast summary for each service period (breakfast, lunch, dinner, late night).
- Identify the top menu items that drive prep volumes and enter them in the "Top Drivers" section.
- For each station, fill the Station Prep Table with forecasted quantities, par levels, batch sizes, timings, carryover rules, and yield expectations.
- Assign owners (lead cook, prep cook) and check start/finish times. Share the plan with the shift team before service.
- During service, update actual usage and adjust carryover or top-up prep as needed; capture adjustments in the shift notes area for handover.
Forecast summary (by service period)
Record forecasted covers and expected % mix for high-volume items. Use absolute numbers where possible.
- Service: Lunch
- Forecasted covers: 120
- Expected busiest hour: 12:30–13:30
- Notable events or reservations: Private party (20) from 18:00
Top 10 items driving prep
List items likely to consume the most time/volume/ingredients so they get priority in prep sequencing and batching.
- Chicken salad — forecast 60 portions
- Margherita pizza — forecast 40
- French fries — forecast 90
- ... (fill remaining items)
Station Prep Table (use one row per menu item or prep task)
Copy this table for each station (Cold, Hot, Fry, Grill, Pastry, Beverage, Garde Manger, Prep).
| Station | Item / Prep Task | Forecast Qty | Par (on-hand target) | Prep Qty (planned) | Batch Size | Start Time | Finish Time | Hold Time / Temp | Yield % (est.) | Carryover Rule | Owner | Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Cold | Chicken salad (portioned) | 60 | 20 | 80 | 20 portions/batch | 08:00 | 09:00 | ≤2 hrs, 41°F | 90% | Keep up to 20 for next service if <48 hrs | Jane | Hold chilled, rotate FIFO |
Timing & batching notes
Guidance to choose batch sizes and start times:
- Batch size should align with equipment capacity and service cadence. Avoid batches so large they sit beyond the safe hold time.
- Schedule high-labor or long-cook items earlier but keep a small rolling buffer for top items to react to demand spikes.
- Flag cross-station dependencies (e.g., grill needs finished proteins from sous station at :15 past each hour).
Carryover rules (examples)
Clear rules reduce overproduction and confusion at shift handover. Examples:
- Prepared items that safely hold ≤48 hours: keep up to Par for the next service; log date/time and initials.
- Made-to-order components (e.g., sauces) carry over only if cooled and labeled with batch yield.
- Perishable ready-to-eat items: do not carry over beyond end-of-day unless explicitly refrigerated and approved by manager.
End-of-day yield & reconciliation checks
Quick checks to validate how prep matched actuals and to fine-tune future plans.
- Record actual used quantity vs. planned for top 10 drivers.
- Calculate actual yield: (usable quantity after prep ÷ raw input) × 100.
- Note discrepancy reasons (over-forecast, unexpected event, spoilage, portion inconsistency).
- Adjust par and batch sizes for the next similar service period if variance >10%.
Instructions for linking to forecast data
Where possible, connect the "Forecast Qty" column to your sales or forecasting tool so daily numbers populate automatically. If integration isn't available, export the day's forecast to CSV and paste the key numbers into this table.
Recommended fields to import: date, service period, menu item ID, forecasted qty, expected peak hour, reservations. Use item-level historical sales to calculate a baseline and apply modifiers for events, weather, or local factors.
How to update during service (quick rules)
- If actual usage for an item exceeds forecast by 20% within 30 minutes, trigger a top-up batch and notify FOH manager.
- If trending down by 20% for 30+ minutes, pause non-critical prep to avoid overproduction.
- Log every in-service adjustment with time, item, reason, and initials for later reconciliation.
Quick actions for rush events
- Prioritize sprintable tasks: portioning, par-level plating, reheat-ready components.
- Hold non-essential garnish and finishing until throughput steadies.
- Enact the pre-determined "rush kit" for busiest seats (pre-portioned fries, portioned proteins).
Example: scaling a recipe for forecast
Recipe yields 10 portions from 2 kg raw chicken (yield 80%). Forecast = 60 portions. Required finished portions = 60. Raw needed = 60 ÷ 0.8 = 75 portions equivalent → scale recipe to 15× base batch (2 kg × 15 = 30 kg raw).
Definitions & common mistakes
- Par: the on-hand amount you want available at service start.
- Yield %: expected usable portion after trimmings/cooking.
- Common mistakes: using average sales without accounting for menu mix shifts; batching too large for hold times; unclear ownership of prep tasks.
Shift Handover
At handover, the outgoing lead should record: actuals vs planned for top items, carryover items (with timestamps), any quality or equipment issues, and recommended adjustments for the next shift.
Discussion
Comments and conversation will live here.