Staff scheduling based on reservations: how to avoid under- and overstaffing
Building next weekend's roster on Thursday evening, without really knowing how busy it will get: sound familiar? Under- and overstaffing usually aren't the result of bad planning, they happen because scheduling and reservations live in separate systems. Horecaflix brings reservation insight and staff scheduling together in one platform, so you can factor in how busy a shift is expected to be while you're building the roster.
Key takeaways
- Under- and overstaffing are often not a scheduling mistake, but the result of a roster built without reservation data.
- Competitors such as Shiftbase and Formitable sell reservation insight inside your scheduling tool as a connection between two separate apps, which you have to install and request separately.
- Horecaflix already has reservations and staff scheduling in one platform, so you can put the reservation calendar next to the roster without setting up an extra integration.
- Availability and leave are already processed automatically in the roster, so when you plan for a busy shift you only need to check who's available, not whether someone's allowed to work.
- Start small: put the reservation calendar next to the roster for one busy shift, before you apply this to your whole schedule.
Why under- and overstaffing happen so often in hospitality
Building a roster for the coming weekend based on a gut feeling instead of hard numbers is the norm in hospitality, not the exception. You know Friday night is usually busy and Tuesday afternoon usually quiet, but "usually" isn't a number for this specific week, and a party of forty booked for that exact Thursday changes the staffing you actually need.
That happens against the backdrop of a sector where staff are already scarce. The Dutch hospitality industry now counts over 522,000 jobs, a record, yet just over 30,000 vacancies remain open and nearly 4 in 10 operators report being held back by staff shortages (Felixworks, January 2026). With little slack in your staffing, a roster that's slightly off from actual demand gets expensive fast: overstaffing costs you labor on a quiet night, understaffing costs you revenue and a team playing catch-up on a busy one.
Across multiple locations, that gap matters even more. If the approach differs per location, one site may already be planning against the reservation calendar while another is still working on gut feeling, with no clear reason for the difference.
The problem with separate tools: reservations here, staff scheduling there
Competitors such as Shiftbase and Formitable solve this by connecting their scheduling tool to a separate reservation system. In practice, that's how Shiftbase and Formitable work: you install the Shiftbase integration inside Formitable, then submit a request to Shiftbase to get the connection enabled. From there, reservations for the current day and the next fourteen days are imported every five minutes and shown as a separate block in the schedule, with the number of bookings and guests in the title (Shiftbase Help Center).
That works, but it's a connection between two separate products: two subscriptions, an install step in both systems, and an integration you have to request and maintain yourself. If either tool changes, there's no guarantee the connection keeps working the way you're used to. For operators running multiple locations, that's exactly the kind of extra layer you don't want to rebuild site by site.
What your reservation data tells you about expected demand
Your reservation calendar is effectively a forecast of the demand you already have in-house, you just need to use it. The number of bookings per shift, average party size, and peaks around specific times show exactly when your team is going to get busy, independent of how busy that weekday "usually" is.
A Friday night with two large parties of twelve requires a different staffing mix than a Friday night mostly made up of tables for two, even if total covers are roughly the same. Large parties need more kitchen prep and more floor attention at the moment they're served, while many small tables mainly call for enough service staff who can turn tables quickly. That nuance only shows up in the reservations themselves, not in an average busy-day score per weekday.
Roster, availability and leave: what Horecaflix already handles for you
Before you can factor demand into the roster, the basics of the roster need to be right first. In Horecaflix, every employee submits their own availability, and leave requests automatically land in the same system as the roster. You immediately see who's available, who isn't, and who's already scheduled elsewhere, without separate group chats or a loose spreadsheet on the side.
On top of that, you set up reservations and the related guest communication centrally: automatic confirmations right after booking and automatic reminders a day in advance already catch most no-commitment online bookings, so your reservation calendar gives a more reliable picture of who's actually coming. Both building blocks, the roster and reservations, already sit next to each other in Horecaflix in one platform, instead of in two products you have to get talking to each other.
Combining reservation insight and staff scheduling in practice
Horecaflix doesn't have a direct, automated link today that calculates your staffing for you based on reservation volume. What you do already have is reservation insight and roster management in one platform, without two subscriptions and a technical integration in between. The practical approach is therefore not a single button, but a fixed step in your planning routine.
Before you finalize the roster for a week, put the reservation calendar next to your draft roster. Look per shift at the number of bookings, party sizes and how the evening builds, and translate that into the staffing you think that shift needs. Adjust the draft roster accordingly before you finalize it, instead of correcting on the fly once the rush has already started.
If you run multiple locations, it pays to make this a standard routine for every scheduler, so one location isn't planning against the reservation calendar while another isn't. That keeps the approach consistent, even when the actual scheduling happens per location.
Practical scenario: planning a busy weekend from the reservation calendar
A brasserie owner notices on Thursday that Saturday night's reservation calendar is already fuller than an average Saturday: two parties of ten around eight o'clock, plus the usual mix of walk-in-sized tables. The draft roster used as a starting point still assumed a normal Saturday's staffing.
Instead of discovering on Saturday afternoon that the kitchen and floor staff are behind, the owner adjusts the roster on Thursday evening: one extra kitchen hand between seven and ten, and one extra server scheduled to come in specifically around eight instead of for the whole evening. Because availability and leave were already built into the roster, it's immediately clear who can cover that extra shift without any back-and-forth calls.
The result: no team improvising on Saturday night over demand that was already visible on Thursday, and no extra staff member standing around all evening when the peak only lasts two hours.
Getting started in Horecaflix
Don't start with your entire schedule, start with one busy shift. For the coming weekend, put the reservation calendar next to the draft roster and check whether the staffing you planned still matches what's actually booked. If you haven't already, set up automatic confirmations and reminders for your online bookings, so the reservation calendar gives a more reliable picture of who's really coming.
If you run multiple locations, this is also the moment to agree that every scheduler takes this step by default, instead of it being down to chance whether one location checks the reservation calendar before rostering and another doesn't. Not sure how to set this up for your business? Get in touch with Horecaflix, and we'll think through an approach that fits your booking volume and team.