Every property fails a guest eventually. The service recovery log records what happens in the minutes after: what failed, how it reached you, who resolved it and how long it took, whether anyone had to be asked for permission, and the cause. Above the log sits the recovery plan, the sequence the operators in the book follow when an experience breaks, so that the team has it in front of them before they need it.
Where it comes from
Chapter 10 of the book is about recovery, and it was the discipline the hoteliers and chefs discussed least in public and most precisely in private. Alexander Pichel, then general manager of Hotel Indonesia Kempinski Jakarta, gave me the sequence in three steps: listen carefully and without prejudice, apologize honestly, then offer a solution. The order matters. A fix delivered before the guest has been heard is a second failure.
“Take the time to genuinely hear a complaint, and empathize with that frustration. Listening is half the battle.” Alexander Pichel, then general manager of Hotel Indonesia Kempinski Jakarta
Anneke Brown, then general manager of COMO The Treasury in Perth, added the step most properties get wrong: when a luxury experience goes wrong, correct it and compensate without question. Waiting for the guest to ask for compensation turns a recovery into a negotiation. And Gerrit Graef, then general manager of The Ritz-Carlton, Riyadh, supplied the attitude the whole chapter rests on: negative feedback is the breakfast of champions. The log’s last column, the cause, is where that attitude becomes a practice.
What is on the page
At the top, the recovery plan in five lines: listen without explaining; apologize honestly; correct the failure now; compensate before being asked; fix the cause so it cannot recur. Each line has a short note on what it looks like at your property, which you fill in once and keep.
Beneath it, the log. Five columns: what failed; how it reached you (voiced, observed, review); who resolved it and how long it took; whether anyone above the resolver had to be involved; the root cause, in one sentence, even if provisional. Room for about fifteen entries, and a tally at the foot of the page for failures resolved by the person who first heard them against failures that waited for permission.
How to use it for five shifts
Record every instance, including the small ones a guest shrugs off, and write down honestly whether your first move was to listen or to explain. Add one question to your own routine that invites the complaint, such as asking a guest halfway through the stay or the meal whether anything has fallen short, and log what it surfaces. On the last day, read the log through once and share the causes with the people who can fix them, in person rather than by message.
What to look for
Two gaps. The gap between how fast a failure could have been fixed and how fast it was, which almost always comes down to who was allowed to fix it. And the causes that appear more than once, which are the ones worth a conversation with the people who own them. Speed in recovery depends on authority; if the tally shows most failures waiting for permission, the next tool to use is the authority statement.