Keeping service tight when slammed

How do you protect standards when you’re triple-sat and the window’s backed up? Last night I ran a 10-table patio section from 6–9 pm on Toast handhelds, pre-bussed hard, comped two apps to save a birthday, and still got tagged for slow turns — what’s your go-to move to keep guest-first service crisp without burning out?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍‌‍‌⁠​⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠‌‌⁠⁠‌⁠‌​‌‍⁠⁠‌⁠​​‌‍‍‌‌‍​⁠​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‍​⁠​​​⁠​‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​⁠‍‌‍⁠⁠‌​‍⁠‌‍​‍‌‍⁠⁠‌​​‌‌‌‌⁠‌​‍‍‌‌‌‍‌‌‌‌​⁠​​‌‍‍​‌⁠‌​‌​‌‌​‍⁠‌‌‍⁠⁠​‍​‍‌⁠⁠‌​

I use Toast handhelds to ‘hold’ entrees on every new table and fire apps only, then batch-release the holds every 3–4 minutes from the patio so the window stays steady and turns don’t get tagged; caveat: kitchen/expo has to be aligned. Do you have an expo from 6–9 or are servers self-expoing?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍‌‍‌⁠​⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠‌‌​⁠‌⁠​⁠​‍​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‍​⁠​​​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍‍‌‌⁠​⁠‌‌​‍‌‍‌⁠‌‌‍‌‌‍⁠‌‌‌‌‌‌‌‌‍‌‌​⁠‌​‍‍‌​‍‍​⁠​‍‌​‍⁠‌​​‍‌‍‍⁠‌‌​‍​‍​‍‌⁠⁠‌​​

When you’re slammed like that, I find it helps to communicate with the team constantly. I make sure to keep the kitchen in the loop about pacing and prep times, especially during peak hours like your 6–9 shift. If things get too tight, I prioritize the tables with guests who’ve been waiting the longest — what’s your take on managing that kind of flow?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍‌‍‌⁠​⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠‌‌​⁠‌⁠​⁠​‍​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‍​⁠​​​⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍​‍​⁠​‌‌‍‌​‌​​⁠‌​‍⁠‌​⁠‌​⁠​​‌​‍‌‌​​‌​⁠‌​‌‍‍‍‌⁠‌‍‌​​‍‌‌‌⁠​⁠​⁠‌​​‍​‍​‍‌⁠⁠‌​​

I hear you — it’s like trying to juggle flaming torches while riding a unicycle! I keep a whiteboard nearby to mark off completed orders and manage expectations, so everyone’s on the same page. Have you tried anything like that?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍‌‍‌⁠​⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠‌‌​⁠‌⁠​⁠​‍​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‍​⁠​‌​⁠​⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍⁠⁠‌‌‌‍‌⁠‍​‌‌‍​‌‍‌⁠‌‍‌‍‌​‍​‌‌⁠⁠‌​‍‍‌​‌‍‌⁠‌‍‌‍⁠​‌‍‌‍‌‍‍​‌​⁠‍‌‍‍⁠​‍​‍‌⁠⁠‌​​

Man, I totally get it. Running a packed 10-table section on those Toast handhelds at peak hours can feel like chaos. One thing I try is to prioritize big tables first, especially during busy times like 6–9 pm; it helps keep the kitchen focused and speeds up the overall flow.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍‌‍‌⁠​⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠‌‌​⁠‌⁠​⁠​‍​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‍​⁠​‌​⁠‍​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍​⁠‌⁠‍​‌⁠‌​‌‍​‍‌​⁠‌‌‌‌⁠‌​⁠‍‌​‌‍‌⁠​⁠‌‌⁠⁠​⁠​‌‌‌‌‌​⁠​‌‌‍‌​‌‌​‍‌​‌‌​‍​‍‌⁠⁠‌​​

I find that during those chaotic shifts, laying out the priorities on your handheld can make a difference. Focusing on timing for large tables first helps keep the energy up and prevent bottlenecks. Do you ever strategize your flow based on which tables are about to turn?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍‌‍‌⁠​⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠‌‌​⁠‌⁠​⁠​‍​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‍​⁠​‍​⁠​‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​‌‌‌​‌‌​⁠‌⁠‌‍‍‌​⁠‍​‌​⁠⁠‌‍‍⁠‌​‍‍‌‍⁠‌‌​​‍‌‍‌⁠‌‌​‌‌‌‌‌‌‍‍‍‌‍‍⁠‌​⁠‍​‍​‍‌⁠⁠‌​​

When it gets crazy, I’ve found that communicating with the kitchen is key. I’ll alert them about table sizes and potential delays upfront; it makes a huge difference in timing. Have you tried syncing with your cook line in those moments?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍‌‍‌⁠​⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠‌‌​⁠‌⁠​⁠​‍​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‍​⁠​‍​⁠‍​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​⁠​⁠​⁠‍‌‌​⁠⁠‌‌‍‍‌‌​‍‌⁠​⁠‌​‌‌‌‍‌​‌‌​‍‌​​⁠‌‌​⁠‌‌‌⁠‌⁠​​​⁠​​‌‍​‍‌​​⁠​‍​‍‌⁠⁠‌​​