Table reservations by room: prepare the capacity map
Room-level planning here means restaurant rooms or zones, not hotel bedroom reservations.
Published and updated: · NOVUZA
Illustrative screens with sample data.
Who this is for
For the manager and team responsible for the workflow described below; guest-facing and internal access must remain separate.
Daily workflow
Illustrative scenario — not a customer case study
Illustrative example: an indoor dining room and a terrace share a service team. The manager needs a capacity map and a bad-weather rule. Demonstrate the supported room, zone and time-slot setup before assuming automatic allocation or guest-record linking.
Preparation checklist
- 01
Draw a simple plan, give every table a unique label and note seats and accessible routes.
- 02
Separate physical seats from the number your service team can handle in each time window.
- 03
Write rules for terrace closure, large parties and manual confirmation; name the decision-maker.
- 04
Bring the plan to a demo and test supported rooms or zones, capacity changes and staff permissions.
- 05
Verify any reservation-to-guest link explicitly; keep public menu visits separate from identified records.
- 06
Write a sample booking card for a party that does not fit one table: desired time, seats, acceptable zone and who decides whether tables may be combined. Bring this card to the demo instead of assuming automatic table joining.
- 07
Rehearse bad weather: list the terrace requests affected, indoor seats actually serviceable and the staff member who contacts guests. Ask to see the supported change process; do not infer automatic reassignment or notifications.
- 08
Test the boundary between public and private views: a guest needs the booking choice, while staff may need permitted reservation details. Confirm exactly which fields are visible, who can amend a request and what happens if the same service is reviewed twice.
Questions before you decide
Does this page guarantee the complete workflow is enabled for my venue?
No. Use the described scenario as a demo checklist. Confirm the supported steps, permissions and exact scope before operational use.
Where can I verify the price and billing unit?
Use the published pricing page for listed modules and packages. HR is per organization; other listed modules are per establishment. Unlisted scope and integrations require a quotation, not an assumed package inclusion.
Availability and scope
Listed in the public offering. Confirm actual availability, permissions and your exact workflow in a demo before ordering.
Limits to check
This is a restaurant capacity-preparation guide, not a hotel-room booking specification. Zones, allocation, changes and record links remain demonstration questions; a diagram alone does not prove software support.
Start simply.
Table reservations by room: prepare the capacity map