Template

Rush-Day Prep & Staging Schedule

A reusable, fillable rush-day prep template that captures time-based station tasks, staging rules for peak windows, buffer rules, cross-training assignments, cutover checklist steps, contingency plans, and post-rush review notes — designed to be saved and reused across locations and dates.

Interactive Tool

Rush-Day Prep & Staging Schedule

Use this template to translate forecasted demand into concrete, time-based prep work and a clear cutover plan so peak windows run smoothly. Enter the rush date, the forecasted window and intensity, list stations in use, and spell out who does what and when. Use the examples below to format station plans consistently.

Example station plan format (single line or bullets): Grill — 14:00: Start charbroil batch (4 pans), 15:00: Pre-sear protein (10 portions), 17:00: Hold at 140°F in hot-holding pans. Repeat for each station.

Name or code for the kitchen, restaurant, or location this plan applies to.
Enter the date for this rush (YYYY-MM-DD).
Name of the person who created this plan.
Expected covers, sales, menu mix notes, or any forecasting details managers should know (e.g., large party, event, weather impact).
Start time for the peak window (HH:MM).
End time for the peak window (HH:MM).
Estimate how intense the rush will be so teams can prioritize (1 = light, 5 = extreme).
1.0 10.0
Select the stations that will be active during the rush. Use 'Other' to add location-specific stations.
Name any station not listed above.
For each station, list tasks with times and owner initials. Use the example format: 'Station — HH:MM: Task (owner) — HH:MM: Task (owner)'. Provide enough detail so the person on shift can follow without asking.
Describe where prepped items should be staged, how much to stage per time block, holding temperatures, and how long items can remain staged before service.
Define buffer quantities (e.g., always have 2 full pans ready at expo) and any rules for topping up or limiting production to avoid waste.
Note who can step into each role if a teammate is overwhelmed or called off. Include contact method or quick reminders for pairings. Example: 'Expo backup: Line cook A — can handle short tickets and communicate with FOH.'
Select the steps to run when switching from prep to service mode. These appear as checkable steps for the shift.
Map each selected cutover step to an owner (name or role) and expected completion time. Example: 'Verify temps — Kitchen manager — 17:45.'
List fallback steps if key ingredients run out, equipment fails, or a staff member cannot work. Be concrete: who calls who, which menu items to limit, where to pull components from.
Capture what to review after the rush: waste volumes, remakes, ticket times, staffing bottlenecks, guest issues, and suggested improvements for next time.
Choose yes to store this plan so it can be copied and adapted for future rush days or other locations.
Any other information that will help the shift run smoothly (vendor constraints, delivery times, special event notes).
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Sign In to Save Create an Account
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.