Quiet at six, drowning at eight
Two chefs and a counter person start at five on a Thursday. From five to seven it is quiet enough that they are prepping for tomorrow. At eight the apps light up, a football match finishes, the phone rings, and you have one person on the counter trying to handle three tablets, the phone and the riders. A driver is called in at short notice and arrives at half nine, when it has calmed down.
The rota was written by copying last Thursday, which was written by copying the one before. It was probably right once. The trade has shifted since then, especially as more orders come through the apps late in the evening.
Why the rota lags behind the orders
Nobody has a clear picture of when orders arrive. The till knows counter sales by hour. Each app knows its own orders by hour, in its own portal. The phone line knows nothing. So you rely on feel, and feel is anchored to how it used to be.
Things like weather, school holidays, a big match on television and app promotions change the shape of a night, not just its size. A match that finishes at ten moves the rush. A wet Tuesday brings more delivery. Without the data, these adjustments are made in the moment, by ringing people in or sending them home.
The cost of a rota built on habit
| Mismatch | Effect |
|---|---|
| Overstaffed early evening | Wages spent on quiet hours |
| Short at the peak | Slow orders, missed acceptances, lower ratings |
| Drivers arriving late | Food waiting, cold deliveries |
| Last-minute call-ins | Staff frustrated by unpredictable shifts |
| Rota by memory | Nobody else can write it when the manager is away |
Wages are usually the biggest cost you can actually control week to week, so a rota that is out of step with orders is expensive in both directions. Paying for quiet hours is the visible part. The less visible part is the peak you were short for: orders auto-rejected on a tablet nobody had time to tap, prep times missed, and ratings that take weeks to recover.
Staff feel it too. Being sent home early on a quiet night and called in last minute on a busy one is one of the most common reasons good takeaway staff drift away.
A rota guide built from real orders
- We collect order times from every channel: till, phone orders, each delivery app and your website, into one list.
- The tool shows the average number of orders in each half-hour for each day of the week, over recent weeks, with the busiest and quietest shown so you see the range.
- You set simple ratios based on how your kitchen works, such as orders per cook per half-hour, and how many drivers you need for a certain number of your own deliveries.
- The tool turns expected orders into a suggested number of cooks, counter staff and drivers for each hour of each shift.
- You can mark special days, such as a big match or a bank holiday, and see what similar past days looked like.
- The suggestion is exported to your rota tool or a spreadsheet, where you turn it into actual shifts with people's availability.
This is a planning aid, not a rota system and not employment advice. Your staff contracts, availability and the rules you follow stay with you.
Writing next week's rota
You open the guide and see that Thursday orders now build from half seven and peak between eight and half nine, with a longer peak on match nights. You move one chef's start later, put a second person on the counter from half seven and bring the extra driver in at eight. The following Thursday the early evening is calmer and the rush is covered.
- Staffing matched to when orders really arrive
- Match nights and holidays planned in advance
- Fewer last-minute call-ins
- A rota someone else can write from clear numbers
Does your rota fit your orders?
- Your rota is copied from the previous week.
- Early evening is quiet while the peak is short-staffed.
- You regularly ring staff to come in or go home early.
- You do not know your busiest half-hour on each app.
- Only one person can write the rota.