When a Reinstatement Doesn't Stick: Keeping Your Own Case File

A reinstatement that isn't recorded is a reinstatement you'll argue for twice. The file you keep is what makes the second conversation short.

Last updated: October 19, 2026

Your listing comes back on a Tuesday. Six weeks later it's down again, and the only proof of the first decision is a message thread you can't find. That's not bad luck. It's a missing case file. A reinstatement is a decision made on specific evidence at a specific time, and the file is what lets you show both.

Key Takeaways

• A reinstatement reverses a decision, not a condition. If the condition behind the original action returns, the same action can return with it.
• Four documents carry the weight. The notice, what you submitted, the decision in writing, and proof of the fix.
• A sent message isn't a received one. Only a reply, a decision or a status change confirms that someone read it.
• Write the timeline once, then append. An edited timeline reads as constructed, which is the opposite of what you need.
• Store it per channel, per property, per year. One merged folder is how a good record becomes unfindable.

Why a reinstatement can lapse

A reinstatement isn't a permanent status you earn. It's a decision someone made about a specific situation, usually after reading a specific set of documents.

That distinction explains most of the ways it lapses.

The condition behind it changes. A licence expires. An insurance certificate lapses. A safety item gets removed during a renovation and put back a week later. The decision was sound when it was made, and that basis is now gone.

The account changes shape. A new co-host joins. A payment method is replaced. A second property is added under the same account. Any of these can put the account back in front of a reviewer, who will look at the current state rather than at last spring's decision.

The evidence goes stale. Photos of a smoke alarm taken in 2024 don't prove an alarm is fitted in 2026. A policy document that hasn't been updated doesn't prove the policy is followed.

Nobody can find the record. This is the most common one, and the least discussed. The second reviewer doesn't have your message thread. They have a system that may or may not show a note. If you can't produce the decision, the conversation restarts from zero — and a restart costs more than the original.

There's a fifth pattern worth naming: the reinstatement came with conditions. Fix the alarm, add the licence number, brief the cleaner. You did three of the four, or did all four but told nobody. Conditions without a dated record look unmet.

The four documents that carry weight

Most hosts keep everything and can prove nothing. The fix is to keep four things properly.

One: the notice. The original action, as it was sent. Keep the exact date, the listing or account it names, and the reason in the platform's own words. Don't paraphrase it into your own summary, even if the summary is fairer. You'll need their wording later, and their wording is the thing being argued about.

Two: what you submitted. Every document, photo and statement you sent, with the file names you sent them under and the date. If you uploaded six photos, keep the six. If you filled a form, keep a copy of what you typed. The question later won't be whether you fixed something. It'll be whether you told them you did, and when.

Three: the decision, in writing. The reinstatement message, the date, the reviewer's wording, and any conditions attached to it. Screenshot it and save the screenshot as a file with the date in the name. A decision that exists only in a notification is a decision that disappears with the next app update.

Four: proof of the fix. The thing that changed on the ground, dated. A photo of the new alarm with the install receipt. The licence number as it now appears on the listing. The cleaner's updated brief, signed and dated. This is the document that answers the only question a second reviewer has: is the problem still there?

Everything else is commentary. A long letter explaining how unfair it felt is worth less than a dated receipt for a $30 device.

Writing a timeline that reads

A case file needs one page that a stranger can read in two minutes. That page is a timeline.

Four columns: date, what happened, who did it, and where the evidence sits. One line per event. No adjectives, no argument, no summary of how you felt.

Here's the shape of a line:

• 14 September 2026: the listing is removed from search. The notice cites safety documentation. Saved as 2026-09-14-notice.pdf.
• 15 September 2026: the hallway smoke alarm is replaced. You did it, and you kept the receipt and a photo. Filed as 2026-09-15-receipt.pdf and photo-01.jpg.
• 16 September 2026: three photos and the receipt go to the support thread. Saved as 2026-09-16-submission.pdf.

Three habits make it readable.

Date everything, including the boring things. "Sent documents" without a date is a rumour. "2026-09-16, submitted three photos and a receipt through the support thread" is a fact.

Separate what you sent from what they confirmed. A sent message proves effort. A reply proves receipt. Two different lines, two different dates. When the second reviewer asks whether the platform acknowledged your submission, only the second line answers.

Quote, don't characterise. Put the platform's wording in quotation marks, with the date and where it appeared. Then, on a separate line, write what you did about it. Mixing the two produces a paragraph that reads as argument, and argument is what a reviewer is trained to skim.

Then leave it alone. Append new lines at the bottom and never rewrite the old ones. A timeline edited after the fact looks constructed, and a constructed record is worse than a thin one.

Storing it where you can find it

A good record in the wrong place is a record you don't have.

Use one folder per property per year. Inside it, a single document for the timeline and a subfolder for evidence, named by date and type: 2026-09-14-notice.pdf, 2026-09-15-receipt.pdf, 2026-09-16-photos. The naming matters more than the folder structure, because search is how you'll actually find things at eleven at night.

Keep each channel's thread separate. The four channels LOCALSBNB connects — Airbnb, Booking.com, Agoda and Trip.com — each run their own process, and a merged file makes it easy to send the wrong thread to the wrong reviewer. Our inbox connects Airbnb only, so threads from the other three stay in those channels. Save them from there, in their own folder, with their own dates.

Keep one offline copy. Platforms change interfaces, notifications expire, and access can be interrupted at exactly the moment you need the record. A PDF in a folder you control is the version that survives all three.

Give a copy to the person who'd answer the phone if you were travelling. A case file only one person can find is a single point of failure, and the second conversation usually happens at a bad time.

Check it twice a year. Two questions. Does the file still prove the fix — is the certificate current, is the photo still an accurate picture of the room? And would a stranger understand the first page without you in the room? When you want the booking and message record in the same place as the property details you're citing, localsbnb.com is where they sit.

FAQ

Is a reinstatement permanent?

No. It reverses a decision at a point in time. If the condition behind the original action returns, or the evidence behind the decision stops being true, the same action can come back. The file is what shortens the second review.

What if I never received a written decision?

Write down what you were told, when, by whom, and through which channel. Mark the line as your own record, not theirs. Then ask for the decision in writing the next time you're in contact. A verbal decision isn't worthless, but it's weaker, and saying so in the file is honest.

How long should I keep the file?

At least as long as the listing is active, plus a year. Keep it longer if a licence, an insurance policy or a safety certificate is involved, because those documents have their own renewal cycles and their own retention habits.

The file takes an hour to build and five minutes a quarter to maintain. Do it while the details are still in your inbox, not after the second removal. You can keep the property record and the channel threads together at localsbnb.com, and the case file wherever you'll open it under pressure.

---

This is general guidance for hosts, not legal, tax or insurance advice. Platform policies, review processes and local requirements differ by market and change over time, so check the current terms of each channel you use and the rules where you operate.