Delegation Starts Where the Checklist Ends

Picture a woman who has handed the opening checklist and service plan to the manager holding the room. The list is complete until the listed spirit is unavailable, a guest recovery reaches the edge of the house range, and a dining-room fixture stops working. Each task has an assignee. Each decision still comes back to her. She opens an exception audit because the return path reveals something a completed checklist cannot: the room has assignments, but its ordinary variations do not yet have decision routes.

Audit scope: collect interrupted decisions from the room

Start with questions that actually returned during a service review. Preserve the first message or record at the level of fact and decision. Then annotate what the manager knew, what was missing, which boundary applied, and why the question traveled. Group entries by exception type after the evidence is collected. This keeps the audit from becoming an imagined catalog of everything that could go wrong and shows whether the same missing boundary is sending several different tasks upward.

Exception 01: a menu item becomes unavailable

• OBSERVED: the item is marked unavailable, the affected menu entry is named, and the approved alternatives checked are recorded.
• MISSING: the checklist assigns the availability check but does not say who may select an approved substitute.
• BOUNDARY: the service manager may choose from the venue's already-approved alternatives and mark the original item unavailable.
• ROUTE: decide and record when the substitution remains inside that range; route before action when no approved alternative fits.
• CLOSEOUT: leave the unavailable item, alternative selected, decision holder, affected service state, and final menu marker in the service record.

Exception 02: guest recovery reaches a boundary

• OBSERVED: record what happened, the current guest context, the response already used, and the service state that remains open.
• MISSING: the guide names an initial response but leaves the edge of the manager's decision range unclear.
• BOUNDARY: the service manager may choose inside the existing house range and must identify the exact condition reached at its edge.
• ROUTE: decide and record inside the settled range; route before action when the next choice sits outside it.
• CLOSEOUT: preserve the response chosen, the boundary used, the role that decided, and whether any next action remains open.

Exception 03: a dining-room fixture stops working

• OBSERVED: name the fixture, its location, its current condition, and the part of the room affected.
• MISSING: the maintenance log captures the problem but does not identify who can use the approved service path.
• BOUNDARY: the manager holding the room may adjust the affected area and request ordinary service from the approved contact.
• ROUTE: decide and notify when both actions remain inside the set boundary; route before action when the provider path or requested work falls outside it.
• CLOSEOUT: record the room adjustment, provider path used, request state, notification destination, and next review point.

Exception 04: the service plan needs a live adjustment

• OBSERVED: identify the table, item, pacing, or service state that no longer matches the plan and the time condition for the decision.
• MISSING: the plan assigns execution but gives no range for changing item availability, table use, or pacing.
• BOUNDARY: name the exact adjustments the manager holding service may make and the facts required before making them.
• ROUTE: decide and record for a contained adjustment; decide and notify when visibility is needed before the next review; route before action at the named boundary.
• CLOSEOUT: preserve the initial state, action taken, decision holder, notification if required, and resulting open or complete state.

Read the annotations across the packet

The woman leading the operation reviews the packet by annotation, not by personality. A blank OBSERVED field means the handoff needs decision-ready facts. A blank BOUNDARY means the manager was assigned the work without the authority range. A route that says ask the general manager for anything unusual has no observable crossing condition. A missing CLOSEOUT means the decision can be made correctly and still disappear before the next review. Each gap has a different repair.

• Facts incomplete: define the minimum record that must travel with the question.
• Boundary absent: state the role, approved range, and exact condition that moves the choice.
• Route vague: replace importance or uncertainty with an observable crossing fact and named destination.
• Record absent: choose where the decision, evidence, and final state will remain visible.
• Same gap repeated: repair the shared decision route before adding another task to the checklist.

Delegation becomes inspectable when an exception has facts, a boundary, a route, and a home. The woman in charge should receive the decisions that cross her named boundary, with enough evidence to close them. The manager holding the room should be able to act on the rest and leave a record that can be reviewed later. That is the handoff the checklist cannot provide by itself, and the exception audit makes it visible.