Restaurant Peak Hours: A Readiness Checklist for the Friday-Night Rush

Most restaurants do not fail at peak hours because they are slow. They fail because something they could have checked at 4pm broke at 7:45pm — a sold-out hero dish nobody 86'd, a printer nobody refilled, a station nobody staffed. The rush does not create new problems; it amplifies the ones already sitting in the system.

This is a pre-shift readiness checklist for restaurant peak hours, built to be scored. Each station below has a small set of items, and each item describes exactly what "ready" looks like — not a vague aspiration. Give yourself one point per item you can honestly say is true today. Run it before Friday service, total your score per station, and fix the lowest-scoring station first. It is the practical companion to our guide on how to handle orders during peak hours, which covers the why; this is the what-to-check-before-the-doors-open.

How to Score This Checklist

There are six stations and 24 checkpoints total. Score one point each. A station scoring 3 or 4 out of 4 is rush-ready. A station at 2 will wobble. A station at 0 or 1 is where your Friday night breaks — fix that one before you touch anything else. Do not chase a perfect 24; chase removing the single weakest link, because peak failure is almost always a chain reaction starting from one weak station.

Run this 60-90 minutes before doors. Earlier than that and conditions change; later and you have no time to actually fix what you find.

Station 1: Menu Throttling & 86ing

The fastest way to wreck a rush is to keep selling something the kitchen can no longer make at speed. This station is about controlling what the menu offers, in real time, before and during peak.

• •Ready: every item you know runs low on Fridays has a live "sold out" toggle the line can hit in seconds, and it instantly hides the item on the online menu — not "tell the host to remember".
• •Ready: slow-to-cook or labour-heavy items can be temporarily scheduled off during the peak window and back on after, without deleting them.
• •Ready: a designated person owns 86ing during service — one phone or tablet, one source of truth, so two people don't un-86 each other.
• •Ready: combos and modifiers tied to a sold-out component disable too, so a customer can't order a burger "with the special sauce" that ran out at 6.

Station 2: Prep & Par Levels

Prep is the cheapest insurance you can buy. Every component pre-made before service is time you are not spending per-ticket during the rush, when each minute costs the most.

• •Ready: par levels for your top 10 sellers are written down and stocked to target before service — not "we think we have enough".
• •Ready: pars are set from data, not gut — you have looked at last month's same-weekday order mix, which your ordering reports make visible.
• •Ready: mise en place for the highest-volume tickets is staged at the station that needs it, so a cook never crosses the kitchen mid-rush.
• •Ready: there is a re-fire plan for the two or three items most likely to run out — who makes more, and how long it takes.

Station 3: Order Pacing & Pre-Orders

Peak is partly a load-shaping problem. If every order lands in the same 45 minutes you are guaranteed a backlog; if you can pull even a fraction of it earlier, the same kitchen handles more covers calmly.

• •Ready: scheduled / pre-orders are enabled, so the lunch crowd can place an order at 10am for 12:30 — work the kitchen does in a controlled window.
• •Ready: quoted prep times automatically lengthen as the queue grows, instead of promising 20 minutes when you are 12 tickets deep.
• •Ready: online orders queue first-in-first-out and the kitchen can see what is coming, not just what is in front of them.
• •Ready: a manager can throttle or pause incoming online orders for a few minutes if the line genuinely buries — a release valve, used rarely.

Station 4: KDS & Ticket Flow

During a rush, paper tickets get buried and read out of order. A kitchen display system keeps every active order on screen with the oldest highlighted, which is the whole game when twelve tickets land at once.

• •Ready: orders appear on the KDS in real time with a visible elapsed-time clock, so the line always knows which ticket is aging worst.
• •Ready: colour or time thresholds flag a ticket before it becomes a complaint, not after the customer calls.
• •Ready: items route to the right station (hot, cold, drinks) automatically, so nobody hand-sorts tickets mid-rush.
• •Ready: there is a fallback if a screen or the network drops — a backup printer or device — and the team has actually rehearsed switching to it.

Station 5: Staffing & Roles

The restaurants that handle peak best are rarely the ones with the most bodies — they are the ones where every body knows its single job and nobody is improvising roles at 7:45.

• •Ready: the schedule is built around your actual peak curve, not flat coverage — more hands in the hot 90 minutes, fewer on the shoulders.
• •Ready: one person is named as the expediter / exception-handler, so when something goes wrong there is a clear owner, not a huddle.
• •Ready: someone owns the online-order channel specifically — checking new tickets, marking ready, handling out-of-stock — separate from dine-in.
• •Ready: a 60-second pre-shift brief covered expected volume and any 86'd items, so the team starts the rush already aligned.

Station 6: Notification Load & Comms

At peak, the channel that breaks quietest is communication. Customers wonder where their order is, the kitchen misses a new ticket, and the phone rings for status updates you could have automated away. This station keeps the noise off the floor.

• •Ready: new online orders trigger an immediate, hard-to-miss alert (sound plus screen), so no ticket sits unseen for ten minutes during the surge.
• •Ready: customers get automatic status updates — confirmed, preparing, ready — so they are not calling the line to ask, and the floor stays heads-down.
• •Ready: real-time order tracking gives the customer a live page, which is the single biggest reduction in "where is my order?" calls during a rush.
• •Ready: alert volume is tuned — important events are loud, routine ones are quiet — so staff don't go alert-blind and start ignoring the screen.

When NOT to Over-Engineer This

If you do 15 covers on a Friday, you do not need KDS routing rules and a dedicated expediter — you need clean 86ing and good prep, and the rest is overhead. Match the checklist to your actual volume. A small kitchen can hit a real "ready" score with four of the six stations barely above the basics, because the chain reaction that wrecks a 200-cover service simply does not have room to build in a 40-cover one.

Equally, do not treat a perfect score as the goal every single shift. The point of scoring is to surface the one weakest station this week and fix it, then re-score next week. Peak readiness is a habit, not a one-time project — a quick post-shift note on what backed up feeds straight into next week's pars and roles.

Turn the Checklist Into a System

A checklist tells you what to verify; the tooling is what makes most of these items "always true" instead of a Friday scramble. Real-time 86ing and scheduled menu availability handle Station 1, scheduled and paced online orders handle Station 3, and a kitchen display turns Station 4 from a stack of paper into a single screen.

If you are deciding where to invest first, start with the stations that touch the customer fastest. See the KDS feature page for how ticket flow and station routing work, the Order Notifications feature page for the alerting and automatic status updates that keep the phone quiet, and the Real-Time Order Tracking feature page for the customer-facing live tracker. For the operational thinking behind all of it, read our companion guide on how to handle orders during peak hours.