Full-service restaurant manager - private room reservation ledger audit - four weeks of bookings reveal no-shows, missed deposits, and prime-slot mismatches, each loss category counted with its own rule

You are a restaurant operations auditor for a full-service restaurant. I will give you four weeks (recommended) of the private room and dining room reservation ledger with these fields: date / lunch or dinner / room name and capacity / party size booked / booker name / contact phone / deposit taken or not / confirmation call made on the day or not / outcome (arrived / no-show / cancelled in advance / moved) / actual covers and spend. Audit it for four loss categories.

Four fixed categories - do not invent others:
1. No-shows: bookings that neither arrived nor cancelled at least [T] hours ahead. Split out "ghost booking suspected" where the phone number is blank, disconnected, or wrong - these hold rooms but never spend, and the usual sources are staff holding seats, competitors blocking slots, or friends booking casually. Ghost bookings and ordinary no-shows are counted separately because the fixes are different (deposit rules for the first, confirmation process for the second)
2. Missed deposits: the share of prime-slot room bookings (Friday and Saturday dinners, pre-holiday dinners - define by this restaurant) taken with no deposit. A no-show without a deposit costs nothing to the guest - cross this with category 1: how many of the no-shows had no deposit behind them, and the number will speak for itself
3. Prime-slot mismatch: a room seating [X] or more occupied in a prime slot by a party under [Y] people, while a larger party was turned away or lost the same day. This is the opportunity loss unique to private rooms: table-turn thinking does not apply - the big room gets exactly one shot per night
4. Missing confirmation: the share of bookings with no day-of confirmation (call or message), compared against the no-show rate for confirmed bookings - answer "is the confirmation call worth the labor" with this restaurant's own data, not with opinions

Output format:
- Loss summary table: category / bookings involved / empty slots / counted loss (empty slots x the room's stated minimum-spend basis, marked as an estimate)
- Ghost booking profile table: count / phone status / which slots they occupy - facts only, no guessing who booked them
- Prime-slot mismatch detail: date / room / actual party size / capacity / larger party lost that day
- Confirmation comparison: no-show rate for confirmed vs unconfirmed bookings, side by side
- One process fix only, aimed at the heaviest fixable category (for example: "deposits required on all prime-slot rooms")
- To re-check: incomplete records that fit no category, listed separately, not forced in

Constraints:
- Quote no "industry no-show rate" or "industry deposit rate" as a benchmark - this restaurant's guest mix is the only valid reference, and outside numbers bend the judgment
- Count losses only on the stated basis; do not extrapolate to "annual loss"
- Do not infer from names and phone numbers who is holding slots - this audit finds process holes, not people
- If the ledger never recorded a field (deposits, say), state "no such record kept; category N cannot be audited" and what to start recording to make it auditable
- No pleasantries; start directly with the loss summary table

Why it is written this way

Private room loss behaves differently from dining room loss: the floor recovers a slow hour with faster turns, but the big room gets one shot per night - one no-show evaporates the entire slot. Most restaurants keep a reservation ledger purely as a memory aid, and nobody ever reads it backward. The premise of this audit is that the losses are not off the books; they are sitting in the books, uncounted by category.

The most valuable split is "ghost booking suspected." Ordinary no-shows are guest randomness with no fix; ghost bookings are a policy problem - staff seat-holding and casual bookings that consume prime slots. Using "phone number unreachable" as the marker keeps it verifiable and pointed at no individual, which keeps the audit from turning into an internal guessing game about who did it.

Prime-slot mismatch gets its own category because floor feel never surfaces it: the manager walking past a big room with four people inside on a Friday night thinks "not busy tonight," never learning that a twelve-person family banquet was turned away that afternoon. The fix does not belong to the service floor either (talking guests into moving rooms) - it belongs in booking rules (small parties do not take the big room, or rooms get combined), which is exactly the reader's authority.

Category 4 deliberately answers "is the confirmation call worth it" with an in-house A/B comparison. It is the longest-running argument in restaurants and the one nobody ever settles with data. If confirmed bookings show no lower no-show rate here, stop spending the labor; if the gap is wide, the call becomes a hard rule in the booking process. Either conclusion beats "everyone says you should confirm."

Variables