A late-arrival notice is not a new reservation, a confirmed table, or a reason to rewrite the room plan at the host stand. It is a service signal: a guest is telling the restaurant that the original arrival may no longer be accurate.
This guide starts only after that notice reaches the team. It does not set a universal grace period, decide when a held table returns to the waitlist, or rank a late reservation against a walk-in. Those capacity decisions belong in your walk-ins versus reservations seating policy. The narrower job here is to give the guest and the next host one current, verified status.
Open one recovery record before discussing options
The first response should not become a long negotiation at the door, on a personal phone, and in a staff chat at the same time. Put the late-arrival notice in the booking workflow that the host team already uses. Record only what changes the next operating decision:
| Record | Why it matters now | Do not turn it into |
|---|---|---|
| Original booking time | Shows which service band the booking entered | A reason to guess that the table is still held |
| Revised arrival estimate | Gives the floor a current fact to review | A guaranteed new seating time |
| Contact route | Lets the team answer through the route the guest used or chose | A personal-device contact list |
| Current booking status | Makes it clear whether review is pending, approved, changed, or closed | A private narrative about the guest |
| Decision owner and next review | Stops the next host from reopening the same question | An unnamed “we will see” promise |
The guest does not need to explain why they are late for the team to act. A revised estimate and a reachable service route are normally enough. Keep reasons, copied message histories, and personal details out of a shift handoff unless they change an approved seating decision.
Reply with a status, not a table promise
When a guest sends a late-arrival notice, a fast answer is useful only if it is true. The host can acknowledge receipt without telling the guest that the original table remains available.
Use a short sequence:
- Confirm that the team received the revised estimate.
- State that the booking is being checked against the current service.
- Give a specific next review point or named contact route.
- Send the approved outcome once the floor owner has decided it.
For example: “Thanks for letting us know. We recorded your updated arrival estimate and are checking the current seating plan. We will confirm the next option by 7:20 p.m.” The message is useful because it separates what the team knows from what it still must verify.
If the restaurant uses a digital path, make that path understandable without relying on a particular phone, app, or message thread. The W3C Web Content Accessibility Guidelines 2.2 are a practical reference for clear instructions and usable alternatives. A staffed route should reach the same current booking record, not create an invisible second process.
Re-triage the booking with the floor
The host gathers the notice. The named floor lead or manager checks what it changes. That person should review the booking against the room as it exists now: compatible tables, active sections, commitments already made, and the restaurant’s documented arrival rule.
This is not the same as running the seating rotation. Rotation chooses the next eligible party after the floor confirms a ready table. Late-arrival recovery asks whether the original booking can still follow its documented path or needs an approved new option.
Keep the possible outcomes small and explicit:
| Verified outcome | Guest-facing next step | Record update |
|---|---|---|
| Original path still applies | Confirm the next check or arrival instruction | Leave the booking active with the revised estimate |
| Another available option fits | Offer only the option the owner approved | Record the option and guest response |
| A change or cancellation is needed | Explain the available route under the restaurant’s rules | Mark the booking status and decision owner |
| An exception needs review | State who is reviewing it and when | Keep one open exception with a next review point |
Do not solve a capacity conflict by quietly moving a different party, changing a walk-in quote, or declaring a table free. The parent seating policy is where the team decides those effects consistently.
Keep late arrival, cancellation, and no-show separate
The same booking can move through several states, but the team should not treat them as synonyms. A late-arrival notice means the guest has provided new information. A cancellation is a deliberate change to the booking. A no-show is an outcome only after the restaurant’s own documented rule and contact process have run.
That separation prevents a late guest from disappearing in a generic “not here” bucket and helps the next host see what action is still due. It also keeps service messages current. Use the waitlist status update policy for the message cadence after an active guest promise changes; do not use a promotional campaign to fill the gap.
For a U.S. public-accommodation reference, review the ADA Title III Technical Assistance Manual with your own legal guidance where access or service exceptions are involved. This operational protocol does not replace the restaurant’s local legal obligations or counsel.
Test the recovery path before a busy service
Run one tabletop exercise with the host lead, floor lead, and manager. Give them a booking that reports a late arrival, then check whether they can answer these questions without improvising:
- Where does the notice enter the current booking record?
- Who confirms the live service effect?
- What can the host say before that review is complete?
- How is the result recorded for the next host?
If two people create two answers, simplify the protocol. The useful measure is not how many messages the team sends. It is whether the guest receives one accurate next step and the floor keeps one source of truth.
StoveOps Reservations is available on Business and shares a guest history with the waitlist. Guests can cancel, check in, or reschedule from their booking link within the restaurant’s rules. Assess the reservation workflow, the live waitlist workflow, and local pricing against the arrival and recovery process your team can actually operate.