To offer restaurant reservations for lunch and dinner without taking bookings during closure, set each service as a separate period when your booking system supports it. Give each period its own first and last seating, then check whether a reservation can extend into the break. If the system only offers one continuous schedule, ask whether you can block the closed interval and control bookings that start before it.
The important distinction is between a time a guest can select and the time their table remains occupied. A 1:30 p.m. arrival may look safe before a 2:00 p.m. closure, but it is not safe if the party needs the table for an hour and staff must clear the room by 2:00.
Map the whole service, not just opening hours
Start with the actual workday. Write down when staff prepare the room, when the first guests may arrive, the latest arrival you can serve, and when the room must be clear. Repeat the exercise for dinner. The time between services may be needed for cleaning, staff breaks, prep or a private event; it should not automatically become bookable time.
Decide what “closed” means in your operation. Does the kitchen stop taking orders at 2:00 p.m., or must guests leave by then? Can staff finish clearing tables after closure? Those answers affect your last seating. A system cannot make that decision for you.
Hypothetical worksheet: A restaurant has four physical tables available for online reservations, each seating up to four people. It does not combine tables for online bookings. Each guest party uses one table for a planned 60 minutes. All times below are local. The restaurant offers arrivals on the hour and half hour; it needs the dining room clear at each service end. These are operating assumptions, not software settings guaranteed by any vendor.
| Decision | Lunch | Dinner |
|---|---|---|
| Preparation | 11:00–11:30 a.m. | 4:30–5:00 p.m. |
| Service and room-clear deadline | 11:30 a.m.–2:00 p.m. | 5:00–9:00 p.m. |
| First and last arrival | 11:30 a.m. and 1:00 p.m. | 5:00 p.m. and 8:00 p.m. |
| Arrival times to expose | 11:30 a.m., noon, 12:30 p.m., 1:00 p.m. | 5:00–8:00 p.m. at half-hour intervals |
The last lunch party is expected to leave at 2:00 p.m. The last dinner party is expected to leave at 9:00 p.m. A 1:30 p.m. lunch arrival is excluded even though the restaurant is still open then. No arrival from 2:00 through 4:30 p.m. is offered. The four-table limit means at most four parties can occupy those tables at once, not four new parties at every arrival time. Overlapping reservations must share that same capacity.
This worksheet is a starting rule, not a promise that every meal lasts exactly an hour. If your parties commonly stay longer, build in more time or move the last seating earlier. If a table needs a reset between parties, include that time too. For example, a 60-minute meal plus a 15-minute reset before a hard 2:00 p.m. deadline calls for an arrival no later than 12:45 p.m.; with half-hour arrival slots, the last offered time would be 12:30 p.m.
Choose separate shifts or a continuous schedule
Separate lunch and dinner shifts are usually the clearer choice for a restaurant that closes between services. Staff can see two sets of boundaries, and a change to dinner hours is less likely to be confused with a change to lunch. Ask a vendor whether each shift can have its own arrival times, capacity and last seating, and how the guest sees the break.
A continuous schedule can work if the system lets you block the closed period and apply a last seating that accounts for the length of the booking. For the worksheet above, simply blocking arrivals from 2:00 to 5:00 p.m. is not enough: a 1:30 p.m. booking could still overlap the closure. You need a way to prevent that arrival or keep its expected end within lunch service.
Before choosing either approach, ask the vendor to show you the guest-facing times for a normal day. Then change one boundary and check the result. Does changing the closing time remove the right arrival slots? Can staff change lunch without reopening the afternoon? Can a booking already on the books remain visible when hours change?
Also separate service boundaries from the advance booking window. A rule that lets guests reserve up to 30 days ahead controls which dates are open for booking. It does not, by itself, close the gap between lunch and dinner on any of those dates. You need both decisions: how far ahead to sell and which arrival times to offer on each day.
If you accept bookings through more than one channel, ask where each channel gets its availability and how quickly changes appear. That includes your website, phone bookings entered by staff and Google bookings where available. A schedule is only useful if the people and channels taking reservations use the same boundaries and capacity.
Simulate the boundaries before live service
Use a sandbox, preview or another vendor-approved practice method that creates no real guest message, payment or courier dispatch. Ask the vendor how to run the checks without affecting the live booking book. If a safe practice environment is unavailable, review the settings and expected results with the vendor rather than placing a real guest reservation as a test.
For the hypothetical worksheet, check the following arrival requests and expected results:
- 11:00 a.m.: Not offered; the room is still in preparation.
- 11:30 a.m.: Offered if a suitable table is free.
- 1:00 p.m.: Offered if a suitable table is free; the planned end is 2:00 p.m.
- 1:30 p.m.: Not offered; a 60-minute booking would extend past lunch closure.
- 2:00 p.m. and 4:30 p.m.: Not offered; neither is a dinner arrival time.
- 5:00 p.m. and 8:00 p.m.: Offered if a suitable table is free.
- 8:30 p.m.: Not offered; the planned end would be after the 9:00 p.m. room-clear deadline.
Then check capacity, not just the clock. If all four physical tables are occupied by parties whose planned stays overlap a requested time, a fifth party should not be offered one of those tables. If one party leaves before another arrives, ask how the system handles the turnover and any reset time. A party of five should not be offered a single four-seat table under these assumptions. If you sometimes combine tables, make that a separate rule to discuss and test.
Check modifications as well as new requests. If a guest moves a noon booking to 1:30 p.m., does the same boundary apply? What happens if staff lengthen a reservation or change the party size? Ask whether an existing booking is flagged when an operator shortens a shift. Do not assume changing hours will automatically resolve every conflict.
Once the simulated checks match your rules, a live-service pilot is a separate decision. Brief the host on the intended schedule, watch the booking book during a real service, and give one person authority to correct a problem. Use normal guest bookings rather than fabricated transactions, and review any unexpected availability promptly. A pilot can reveal operational issues; it cannot guarantee uninterrupted service or that every edge case has been found.
Plan exceptions and staff overrides
Regular hours rarely cover every day. Build an exception routine for holidays, special events, reduced staffing and one-off closures. Decide who can make the change, how far ahead to make it and who checks the public booking view afterward. If dinner starts later for a private event, update the actual date rather than relying on a note for the host.
Before changing an upcoming shift, review bookings already accepted. Identify parties affected by the new hours and assign someone to contact them through your normal process. Keep the existing booking visible until the team has agreed on a resolution; merely hiding a time from new guests does not settle an existing reservation.
Staff overrides need a clear purpose. A manager might accept a known guest slightly after the usual last seating because the kitchen and host have agreed to stay. That should be an intentional exception, not a way to bypass a schedule that is routinely wrong. Ask who can override a boundary, whether the action is visible to the team and what happens to table capacity afterward.
Keep a short shift-change checklist:
- Confirm preparation, first arrival, last arrival and room-clear times with the kitchen and front of house.
- Check physical tables, maximum party sizes and any tables held back from online bookings.
- Apply the date-specific change and review existing reservations that may be affected.
- Check the guest-facing availability on each relevant booking channel.
- Tell the host who can approve an exception and how to record it.
Use your reservations documentation alongside the vendor's setup guidance, and make the host's written rules easy to find. If late cancellations or empty tables are part of the staffing decision, the guide to measuring reservation no-show costs can help frame that separate question.
Take your schedule to a vendor demonstration
Bring one ordinary split-shift day, one exception date and a list of physical tables. Ask the vendor to show the guest view, the staff booking view and how a change affects both. Include a booking that would run past lunch closure and a request when all suitable tables are occupied. If you use discovery channels as well as direct bookings, ask about channel attribution, permissions, exports and fees in a written quote.
Compare your requirements with Fleksa's restaurant reservation system and ask for a demonstration of the relevant split-shift workflow. Confirm which settings and booking channels are available for your setup before making the change.
Frequently asked questions
Can I use one schedule for lunch and dinner?
Possibly, if it can block the break and prevent bookings started before closure from running into it. Check both arrival slots and booking duration; a closed-time block alone may not be enough.
Should the last seating match the closing time?
Not when guests need time to eat before a hard closing deadline. Work backward from the time the room must be clear, allowing for the planned stay and any required reset.
Does a booking window stop reservations during the afternoon break?
No. A booking window generally controls how far ahead a guest can reserve. Set service periods or equivalent time restrictions separately, then check the guest-facing availability.
