To configure a holiday or special-menu service without changing regular availability, use a date-specific schedule if your reservation system supports one. Set its hours, seating limits and guest-facing terms for that date only. Then check the dates immediately before and after it, along with any bookings already on the books.
If the system cannot isolate the change to one date, do not overwrite your regular schedule and hope to remember every setting. Ask the provider about a temporary workaround, such as closing online booking for that service and taking requests manually. Assign someone to manage those requests and update the booking record.
Restaurant holiday reservation rules cover more than holding back a few tables. You also need to decide when guests can arrive, how long they can stay, what menu they are accepting and what happens to reservations made before the change.
Compare the regular shift with the special date
Start with the service you normally run on that day of the week. Record the usual opening and closing times, bookable arrival times, party-size limits and any turn-time rules. Take a screenshot or write down the settings and the date they were recorded. That gives the person checking the schedule a reference that does not depend on memory.
Next, write the special-service plan separately. A holiday dinner might start earlier than a normal shift, use a fixed menu and accept arrivals only at two set times. The key decision is whether those rules replace the regular schedule for that date or supplement it. If both sets of availability appear at once, guests may be able to book times the kitchen did not plan to serve.
The following worksheet is a hypothetical example, not a description of a particular product's features. Assume a restaurant normally takes dinner reservations from 5:00 p.m. through 9:00 p.m. On one holiday, it wants two arrivals, at 5:00 p.m. and 7:30 p.m., instead. The restaurant has eight physical tables available for this service. Each seats up to four guests; tables will not be combined.
| Decision | Ordinary dinner | Holiday setting and result |
|---|---|---|
| Bookable arrivals | 5:00–9:00 p.m. | 5:00 p.m. and 7:30 p.m. only |
| Dining time | Use the regular rule | Two hours per party, with 30 minutes between seatings |
| Physical tables | Use the regular floor plan | Eight tables, each seating up to four; no combinations |
| Maximum bookable parties | Use the regular capacity rules | Eight parties per seating; 16 table seatings across the service |
| Menu and terms | Regular menu and terms | Holiday menu and booking terms shown before confirmation |
The table describes eight physical tables, not 16. Each table can accommodate one party at each of the two arrivals, giving a maximum of 16 parties across the service. If every party has four guests, the theoretical maximum is 64 guests. Smaller parties reduce the guest total without freeing a table for another party in the same seating. The restaurant may choose a lower limit for staffing or kitchen capacity.
Under these assumptions, the first seating ends at 7:00 p.m., leaving 30 minutes before the second begins. The second seating ends at 9:30 p.m. The operator should confirm that the kitchen, front-of-house team and closing plan can support those times before publishing them.
Ask your provider whether a date-specific rule replaces regular availability or adds to it, and whether it expires automatically. Also ask how the rule appears in each booking channel. A schedule that looks right in the back office is not enough if an old arrival time remains bookable elsewhere.
Map menu, booking terms and seating capacity
Put the guest's decisions in the order they encounter them. Before confirmation, they should be able to see the date, arrival time, party size, special menu and any conditions that matter to the booking. Tell guests where they can review the menu and how to raise dietary questions. Do not assume a reservation note reaches the kitchen without a clear staff handoff.
If you plan to collect a deposit or apply a cancellation term, ask whether the booking workflow supports it and how the amount and conditions are presented. A deposit is a payment toward or associated with a booking; it is not the same as a processing fee or the restaurant's completed sales. Confirm how staff will handle changes and refunds. Have a qualified adviser review contract or legal questions where needed.
Set capacity in the unit your team actually manages. In the example, the limit is eight parties per seating because there are eight physical tables and no table combinations. A guest-count limit alone could allow a mix of parties that does not fit the room. Conversely, a party limit alone could allow larger groups than the tables can seat. Check both the table and party-size rules.
Also decide what happens when a guest requests five seats, wants to arrive between the two windows or asks to bring a high chair. The answer may be to decline the online request, handle it by phone or set aside a suitable table. Whatever you choose, give the host team one instruction so an exception does not quietly exceed the plan.
Existing bookings deserve a separate review. List reservations already accepted for the special date, including their time, party size, status and relevant requests. Determine whether each fits the new service. Do not silently move a guest to a different time or assume they agreed to a different menu. Assign staff to contact affected guests and record the outcome in the booking record.
A holdback for a private group can be part of the plan, but it does not establish the holiday schedule. If you hold back two of the example's eight tables for the entire service, only six remain for general booking at each seating. The general-booking maximum then becomes 12 parties across both seatings, provided the holdback is applied to both. Confirm whether the private group needs one seating or both before setting it.
For more on handling reservation questions, see Fleksa's reservations FAQ. For a separate way to think about missed bookings, read the guide to measuring reservation no-show costs.
Check the dates around the exception
Before opening the special service for booking, make a small test plan. The goal is to check the holiday rule and the regular schedule around it, not merely confirm that one attractive time appears.
- Day before: Check that the normal arrival times and party limits appear. Try an arrival that should be available under the regular schedule.
- Special date: Check both intended arrival times, the party-size limit, menu information and booking terms. Try an unwanted arrival time and confirm it cannot be selected.
- Day after: Check that the normal schedule appears again. Try a regular arrival that would not be permitted under the holiday rule.
- Capacity: Check that the last available table can be taken and that another party cannot be accepted for that seating. Check the other seating separately.
- Existing bookings: Reconcile the reservations already accepted against the new table and seating plan.
Use a simulation, preview or provider-approved test environment for these checks. Practice records should not trigger a real payment, guest message or courier dispatch. If there is no safe way to simulate capacity or confirmation, ask the provider to demonstrate it without creating a real transaction or sending a message.
A live service pilot is different: it involves actual guests and operational consequences. If you choose one, give the team a limited, clearly managed scope and a way to intervene. Do not treat a practice booking as proof that every live channel and staff handoff will work.
Check every route you intend to leave open, including your website, phone process and Google bookings where available. Ask how changes reach each channel, how quickly they appear and how staff can identify the source of a booking. If a channel cannot show the special terms or obey the capacity plan, decide whether to pause it for that date and direct guests to a controlled booking route.
When something fails, correct the rule and repeat the affected checks. For example, if a regular 8:00 p.m. slot still appears on the holiday, remove the conflicting availability and check both adjacent dates again. Do not declare the setup ready simply because the intended 5:00 p.m. slot appears.
Assign the service and restoration checks
Name one owner for the special-date setup and a backup who can act if that person is unavailable. The owner does not have to perform every task, but should know who is responsible for the menu, the floor plan, guest contact and the final schedule check.
Keep a short service record where the host and manager can find it. Include the special date, approved arrival times, physical tables in use, maximum party size, menu link or printed reference, booking terms and the procedure for exceptions. Record when the online rules were changed and who approved them. Avoid putting sensitive guest details in a broadly shared worksheet.
Before service, compare the booking list with the floor plan. Check party sizes and requests, identify any unresolved changes and make sure the kitchen knows the expected arrivals. If an exception was accepted by phone, make sure it appears in the same operational record the host will use. A second list is useful only if someone reconciles it.
After service, the owner should confirm that the exception has ended and that the next regular service displays the intended hours and limits. If the system requires manual restoration, record the exact settings to restore and set a deadline before the next booking window matters. Even when an exception is meant to expire automatically, verify the result.
Finally, review any outstanding guest issues and bookings that were changed during setup. Note which workarounds consumed staff time and which settings were difficult to verify. That record makes the next holiday easier to configure without assuming the same rules will fit a different menu or staffing plan.
Ready to compare options? Use this worksheet to list your required date override, seating limits, guest-facing terms and channel checks. Then compare them with Fleksa's restaurant reservation system and ask for a demonstration of the relevant workflow, including how regular availability stays separate.
Frequently asked questions
Should I change my regular opening hours for one holiday?
Prefer a date-specific exception when the system supports it. If it does not, agree on a controlled workaround and assign someone to restore and verify the regular schedule.
How many reservations should I allow for a special menu?
Start with the physical tables available at each seating, then account for party sizes, dining time, staffing and kitchen capacity. A table used twice can support two parties across service, but only one at a time.
What should I do with reservations made before the holiday rules changed?
Compare each booking with the new plan. Contact guests whose time, menu or terms would change, record their response and reconcile the final list with the floor plan.
