
In brief: Kitchen and front-of-house teams have very different scheduling constraints, skill requirements, and peak hours. Coordinating the two is one of the most demanding aspects of restaurant management. This guide covers how to schedule kitchen and FOH teams effectively, manage the interface between them, and use planning tools to keep both sides aligned.
A restaurant runs on the synchronisation of two teams that work in very different environments. The kitchen operates on production logic: mise en place, cooking sequences, plating precision, brigade hierarchy. Front-of-house operates on service logic: guest flow, table turns, upselling, complaint handling. When the two are out of sync, the service suffers — and the customer notices.
Scheduling must reflect this dual reality. A kitchen heavy enough to handle a Friday evening service but a thin FOH team means backed-up food and frustrated guests. The inverse — a full FOH team with an understaffed kitchen — means slow tickets and mounting stress behind the pass.
Kitchen scheduling starts with the brigade. The number of cooks needed per service depends on the menu complexity, the number of covers, and the kitchen's physical layout. A 40-cover tasting menu restaurant needs a different brigade ratio than a 120-cover brasserie.
Typical kitchen shift structure for a restaurant with lunch and dinner service:
Most kitchen workers in traditional restaurants work split shifts. The rules under Joint Committee 302 (Belgian hospitality collective agreement) apply: genuine break, maximum 14-hour span, maximum 5-hour split. The schedule must track these constraints for every cook on a split.
The kitchen schedule must ensure that every critical station has adequate coverage. You cannot schedule a service where no qualified person is available on the grill or the pastry station. Build your schedule with skills mapped to stations, not just names to shifts.
Standard FOH staffing ratios vary by service type and price point. A rough guide:
Add a floor manager or head waiter for services above a certain size, plus a host or reception function for venues with reservations.
Not all FOH staff need to arrive at the same time. Staggering arrivals — some staff come in 30-45 minutes before service to handle setup, others arrive at service time — reduces idle time and optimises the labour cost per service.
FOH demand is not linear. The peak arrival window in a restaurant is often a 30-45 minute window at the start of a service. Scheduling too many staff across the full service adds cost without adding value after the initial rush. Consider scheduling some staff for shorter, peak-focused shifts.
If kitchen and FOH breaks are not coordinated, you end up with a skeleton crew in the kitchen just as FOH is returning from break, or vice versa. Build the schedule so that breaks are staggered across both teams, maintaining minimum coverage at all times.
Beyond the schedule, the kitchen and FOH teams need to share operational intelligence: expected covers, any special bookings, menu changes, event details. This is pre-service briefing territory, but it should connect to the scheduling layer so that the right people are on duty when the information matters.
Shyfter handles multi-role, multi-team scheduling natively. You can create separate scheduling views for kitchen and FOH, apply different shift templates by team, and see the consolidated labour cost of both teams in a single view. Time tracking records each worker's actual hours separately, feeding into individual payroll calculations that correctly apply the relevant premiums per role and schedule.
Have a pre-vetted pool of casual kitchen workers in your Shyfter account. When a cook calls in sick, use Shyft Market to push the open kitchen shift to available replacements immediately. Keep contact details for your regular casual cooks updated in the system so notifications reach them instantly.
Build your staffing model based on the menu and cover targets for each service, not on general rules of thumb. Then review actual cover data weekly and adjust the template ratios based on what actually happens. Shyfter lets you run labour cost and coverage reports that reveal imbalances before they become operational problems.