Sample result
Service Error Recovery Procedure Builder for Restaurants
The owner asked this:“I run a dining room plus delivery. On Friday a new server argued with a table over a wrong dish, and yesterday an incomplete order ended up on Instagram. Everyone answers as best they can. I want a short procedure anyone can apply, not a manual.”
① The four moves, adapted to both channels
| Move | In the dining room | On delivery |
|---|---|---|
| 1 · Listen all the way | No interrupting, no defending, right beside the table | Read the whole message before replying |
| 2 · Apologize without excuses | «You're right, this should not have happened» — the kitchen does not travel to the guest | In writing within 10 minutes, with your own name |
| 3 · Resolve on the spot | Remake the dish now; the boss stops by before dessert | Replacement on the way or on the next order, guest's choice |
| 4 · Report and log | The boss hears it from you, not from the review | Photo of the order ticket and a log entry before closing the shift |
The floor rule: move 3 asks no permission below the ceiling. Remaking a wrong dish costs less than arguing about it, and the argument gets paid for in the review that everyone comparing restaurants reads.
② This house's mistakes, with the line and the cost stated
| Mistake | Done NOW | The line | Compensation | Does it escalate? |
|---|---|---|---|---|
| Wrong or cold dish | Pulled and remade first in the pass queue | «I'll change it right now; the new one goes out first» | A: the dish, with its waste absorbed | No |
| Long wait in the room | Give the real time and offer a house drink | «It'll be 15 min longer than I told you; this lemonade is on the house» | A: a drink | If repeated: shift leader |
| Incomplete delivery order ticket | Replacement on the way or a discount on the next order | «An item was missing and that's our error: shall we send it now or take it off your next order?» | B: item and delivery | Only if the guest asks |
| Wrong charge | Corrected in front of the guest, no justifying | «You're right, here it is corrected; thank you for telling me» | None | If a refund: shift leader |
SUPUESTO: no «normal» industry complaint percentage is hard-coded here, because it shifts by format and by country. The first rung's autonomy ceiling is set as a multiple of the average ticket you declare, and it says so. If your real ticket were half the assumption, the ceiling drops and the incomplete delivery order climbs a rung.
The full example has 1 more part(s): you see them inside the library, with your account.