Sign in

Summer Terrace Bookings: Plan for Sunshine and Sudden Rain

· Jasmine Apps

An illustrative hospitality scene for summer terrace plans, with Jasmine Apps branding.

Summer terrace bookings can create capacity that disappears when the rain arrives. Table Jasmine can organise tables, areas, reservations and guest conversations. The venue still needs a workable weather decision and an honest promise about what happens when an outdoor table cannot be used.

Separate physical space from dependable capacity

Review the actual terrace seats, table arrangement and staff service route. Identify which bookings rely on being outside and what indoor alternatives genuinely exist. Do not count the same indoor table as both a confirmed reservation and a contingency for the terrace. An illustrative evening with several outdoor parties and a private indoor event is a useful stress test: the fallback must work with that real room plan, not an empty restaurant imagined in the office.

Check the result: The promise remains realistic if weather changes.

Illustrative dependable capacity checklist: Check indoor fallback and outdoor seating. Expected result: The promise remains realistic if weather changes.

Make the booking promise explicit

Explain the intended seating and enquiry route in the approved guest-facing information. Decide who confirms a change if outdoor service becomes unavailable. Use the configured widget rules and party limits deliberately, and keep any date or area closure under the manager's control. The product does not establish an automatic weather feed or weather-triggered cancellation process. Confirm any additional integration before promising that the system will contact every guest without staff action.

Check the result: Guests understand the agreed arrangement.

Illustrative booking wording checklist: Explain whether outside seating is guaranteed. Expected result: Guests understand the agreed arrangement.

Prepare the reassignment process

Table Jasmine's documented reservation workflow changes Table Assignment in Quick Edit and saves the record. Use that supported route for a genuinely agreed move, after checking the destination's occupancy and size. Keep floor-plan properties and actual table readiness consistent. Communicate the change to the host and service team; a saved reassignment alone does not tell the colleague preparing the terrace. Avoid deleting outdoor table records merely to hide a temporary closure, because assignments and history need preserving.

Check the result: A move does not create another seating conflict.

Illustrative reassignment route checklist: Check tables and existing reservations. Expected result: A move does not create another seating conflict.

Give weather decisions a named owner

Agree when the duty manager reviews conditions, who contacts affected parties through the supported reservation conversation and how the kitchen is briefed. Keep the information factual and service-focused. For unsafe conditions, follow the venue's established site procedures and qualified advice where relevant; this article is a booking plan, not a safety assessment. Review the guest's agreed alternative and update the accurate booking status if they change their plan.

Check the result: All staff give the same updated information.

Illustrative weather owner checklist: Name who decides and briefs the team. Expected result: All staff give the same updated information.

Put the plan into practice

Test a sunny service, a partial terrace closure and a complete move indoors. Write down the capacity available in each case and the guest contact owner. Compare the exercise with a genuinely busy booking date, then adjust the promise before opening online availability.

Questions venue teams ask

Can we promise an indoor seat for every terrace booking? Only if the operational plan genuinely reserves that capacity. Be clear about the agreed alternative.

Will Table Jasmine react to weather automatically? No such workflow is established by the current product page. Use the supported records and an explicit manager decision.

Explore Table Jasmine.

Example from the actual app

The live widget has a seating option labelled Guests can choose which area to sit in. Its description says an area step is added and the booking is seated in that area when a table is free. Review that option together with the actual terrace promise. Do not describe an area preference as a weather-proof guarantee unless the venue has agreed that arrangement.

A working checklist for your venue

CheckWhat to doResult to verify
Dependable capacityCheck indoor fallback and outdoor seating.The promise remains realistic if weather changes.
Booking wordingExplain whether outside seating is guaranteed.Guests understand the agreed arrangement.
Reassignment routeCheck tables and existing reservations.A move does not create another seating conflict.
Weather ownerName who decides and briefs the team.All staff give the same updated information.

Use the checklist with a colleague who did not configure the workflow. Ask them to complete the ordinary task without coaching, then compare the result with the expected outcome. Record the point where they hesitate or need information from another shift. That observation gives you a specific improvement to make before extending the setup.

Discuss your own setup

Bring your service hours, table capacities and one ordinary booking alongside a larger-party example. Contact Us to discuss how Table Jasmine would fit that booking and service journey.

Illustrations explain the workflow and are not product screenshots. Any numerical example is labelled illustrative and is not a customer result. Product wording and documented setup checks reviewed on 13 October 2026; confirm the features available in your current installation.

More Table Jasmine guides