From booking to cleared table

A reservation commits more than a table. It creates work for the host, servers, drinks station, kitchen and clearing team, often at slightly different times. Good coordination makes those handoffs visible. It also recognises limits: an empty seat does not necessarily mean the restaurant has the capacity to serve another guest well at that moment.

Know what the booking record promises

Keep one current record of party size, arrival expectations and relevant service arrangements. Separate confirmed commitments from requests awaiting approval. If a guest asks for a particular table or timing, staff should not imply it is guaranteed unless the operation has accepted that commitment.

Record only information needed for the service and restrict access appropriately. A guest’s full conversation does not belong in a general staff chat. Where a dietary or accessibility request needs coordination, use the restaurant’s approved process and share the minimum necessary information with the people responsible. Handle sensitive information under the applicable privacy requirements.

Assess capacity across the whole route

Review expected arrivals against available stations and current staffing. A cluster of bookings can overload order-taking and the pass even when the floor has enough tables. Include walk-ins, collection orders and other channels that draw on the same equipment or people. The relevant limit may be kitchen output, host attention or trained server coverage rather than seating.

Use actual service observations to refine the plan. Track where work waits and what prevents the next step. A long ticket time might reflect a sudden order burst, missing prep, equipment trouble or incomplete information. Avoid assuming that every queue is a reason to ask people to move faster.

Give booking changes an owner

When a party changes size or timing, assign one person to update the authoritative record and identify who else needs to know. The floor lead may need to change the table plan, while the pass lead may need to reassess expected order timing. Confirm consequential updates directly rather than assuming a system notification has been noticed.

Be clear about decision rights. A host may be authorised to amend a contact detail but need a manager’s approval for an additional large party. Staff should know where those boundaries sit before a guest is waiting for an answer. If a request cannot be accepted, provide an honest alternative rather than creating a promise the next station cannot fulfil.

Keep the kitchen pass connected to the floor

The pass needs a concise picture of changes that affect production and release. The floor needs an accurate account of delays and unavailable items. Agree who communicates each change and how it becomes visible in the relevant ordering or availability system. Verbal updates are important, but they should not leave old information active elsewhere.

Allergen concerns require the restaurant’s specific safety procedure and competent staff. Never infer that a booking note alone guarantees safe preparation. If information is uncertain, stop the relevant action and escalate through the approved route. This guide is not an allergen-management procedure or a substitute for local food-safety advice.

Use software as a record, not an assumption

OpenTable, Resy, SevenRooms and Tock are examples of reservation platforms. Toast, Square and Lightspeed are examples of point-of-sale providers. Mentioning them does not imply endorsement, a commercial relationship or that any particular integration is available. Confirm current capabilities directly with the provider.

Before connecting systems, test what happens when a booking changes, a table is moved or connectivity fails. Check permissions, duplicate records, update delays, export options and guest-data retention. An integration may transfer information without making its operational meaning clear. The team still needs a named owner and a fallback process.

Finish with a verified reset

A cleared table is not ready until the required reset checks are complete. Likewise, a closed shift is not complete simply because everyone has left. The closing lead should verify authorised shutdown tasks, outstanding equipment issues and anything that affects reopening. Keep detailed safety records in their proper place and reference them from the handover when necessary.

Review the service without reducing it to one average measure. Look at late arrivals, bottlenecks, guest recovery and staff workload together. Use the findings to adjust the next coverage plan or introduce a specific training task. A useful improvement connects an observed problem to an action someone can actually own.