Finding damage after a guest checks out is stressful, and what actually determines the outcome is how well you document it and how closely you follow the platform's own process.
Discovering damage after a guest has checked out puts you in a position where the evidence you gather in the next hour matters more than anything you say afterward. This walks through documenting the damage properly and working through the resolution process, without guessing at coverage details that depend on your specific situation and current terms.
Before cleaning anything or allowing the next guest in, photograph the damage from multiple angles, including a wide shot that shows where it is in the room and a close-up that shows the extent of it. If you have a turnover checklist or move-in photos from before this guest's stay, pull them now — a before-and-after comparison is far more persuasive than either photo alone.
If the damage affects whether the space is usable by the next guest, you may need to act on that logistics problem in parallel, but keep the documentation step first wherever possible. Once something is cleaned, repaired or replaced, you've lost the ability to document it as it was found.
A resolution process generally works from what can be shown, not from how the damage is described. Photos with context — timestamps, multiple angles, something in frame that establishes scale or location — hold up better than a single close-up that could be read differently without the surrounding detail. An itemized estimate of repair or replacement cost, even a rough one from a local vendor, gives the process something concrete to work with rather than an amount you've simply stated.
Keep your communication with the guest about the damage factual and dated — what was found, when, and what you're doing about it — rather than accusatory. That record becomes part of the same resolution process and reads differently depending on tone.
Airbnb's resolution process is the correct channel for a damage claim, and its current terms — timing windows, what's eligible, how a claim is submitted — are worth checking directly on the platform before you proceed, since these details are updated periodically and shouldn't be assumed from memory or a past experience. Submit your documentation through that process promptly rather than waiting, since most resolution processes operate within a defined window after checkout.
If the guest disputes the damage or its cause, the process typically allows both sides to respond, which is another reason the initial documentation matters — it's often the only account that was created before the dispute existed.
This is largely a documentation and process question outside the booking system itself, but activity history helps in the background — a record of who changed what and when, kept for a meaningful stretch of time, can be useful if a damage dispute also raises a question about booking details, dates or who was staying under which reservation. It's a small piece of the picture, viewable in the public demo at try.primehostpartners.com if you want to see how it's kept.