Give the opening shift a clear request-review routine

The decision this workflow supports

Overnight requests can disappear into a busy opening routine if nobody owns the first review. A short opening check should identify what needs action today and who will respond, without assuming every message is equally urgent.

Put the review process in place

Have the opening manager inspect the designated request queue, check duplicates and assign an owner to each actionable item. Prioritize using the restaurant’s agreed rules rather than the assistant’s unsupported judgment. Mark what has been reviewed so the next shift does not repeat the triage.

Worked example for your team

In a fictional opening exercise, the queue contains an overnight table question for today, a catering inquiry for next month and a duplicate submission with a corrected contact. The opening manager assigns the first two and links the duplicate after reviewing its change. Ask the incoming staff to identify what they own without listening to recordings. If the same-day question is buried beneath future-event detail, improve the review order. The exercise should leave a clear next action for each real request while avoiding duplicate follow-up to the same organizer.

Sample wording to approve

“Staff handoff example: three requests await review; one concerns today’s service and two concern future events. Each has a named owner, and no guest has been told their arrangement is confirmed.” This wording is a draft for the restaurant owner to approve before use.

Fields for the staff handoff

Staff need request reference, received time, relevant service date, assigned reviewer, and next action. Mark uncertain details explicitly and keep the requested action separate from anything restaurant staff have already confirmed.

Acceptance tests before use

Every actionable request has an owner. A same-day question is visible during opening. The next shift can tell reviewed items from untouched ones. Record the observed result, assign any mismatch, and repeat the affected scenario after correction.

Related guides