When a Neighbour Files a Complaint: Documenting Your Response

The complaint is somebody else's account of events. What decides the outcome is whether you have a record of your own, written on the day.

Last updated: September 30, 2026

A complaint arrives as a neighbour's version of events, told from their side of a wall. It usually isn't the same thing as the problem that produced it, and treating the two as one is where hosts lose ground. What decides the outcome months later is whether you wrote your own record while the details were fresh, and whether your reply settled the cause rather than adding to it.

Key Takeaways

• The complaint and the problem aren't the same thing. One is an account; the other is what actually happened in the building.
• Write your own record on the day. A note made a week later reads like a defence, not a record.
• Answer the problem, not the accusation. Fixing the cause ends the matter; arguing about the description extends it.
• Your reply can be filed too. Tone and timing can turn one complaint into two.
• Keep the whole trail with the property. Dates, what you changed and who you told belong in one file.

Why the complaint and the problem are two different things

A complaint is a report, and every report is filtered. It comes through someone's experience of the night, their mood when they wrote it, and what they assume about rentals in general. That doesn't make it false. It makes it a version.

The problem underneath may be real, partial or a mismatch of expectations. A door that bangs at midnight is real. A late arrival is real, though its effect depends on where the bedroom sits. A bin left out is real. But the same night can produce two sharply different accounts from two neighbours, and neither of them is a finding of fact.

Separating the two matters because they need different responses. The problem needs a fix: a soft-close on the door, clearer arrival instructions, a reminder about bins. The account needs an answer: an acknowledgement, a short factual reply, and a record of what you did. Hosts who confuse the two end up arguing about the description while the cause keeps repeating.

It also helps to remember that a complaint isn't automatically unfair. Sometimes a neighbour is describing something you genuinely didn't know about, and their report is the first you've heard of it. Reading it as an attack closes the door on the cheapest possible fix.

And these complaints increasingly feed into something larger than one building. Cape Town has a draft short-let bylaw that would require platform listings to be registered. It cites fair competition as part of its reasoning, and public comment runs to 5 October 2026 (reported; still a draft out for consultation rather than a rule in force). Whatever your own city does, the pattern is that individual complaints now shape rules that apply to every host.

Writing your own record on the day, not the week after

The most useful document in any dispute is the one written closest to the event. Memory is generous with itself. A note you write a week later will quietly tidy up the gaps, and it will read like something assembled for an argument rather than something observed.

Write the same day. Note the date and time you were told, who raised it and through what channel, and the account as they gave it. Then keep that separate from what you know yourself: what you saw, what you heard, who was on site, and when they left. The two belong side by side, not blended together.

Leave out conclusions. "The guest was loud" is a judgement. "The front door was heard closing twice on the night in question, and the guests left the next morning" is something you could repeat a year later without changing a word. Facts you can restate are worth more than opinions you have to defend.

Then record what you did about it, and when. A note that ends with a fix shows a host handling a problem. A note that ends with an explanation shows a host preparing to argue. The first is far easier to stand behind.

Keep the note with the property, not in your head or in a message thread you'll scroll past. The unit is what the complaint concerns, and it's where the record is most useful later.

Responding in a way that does not create a second complaint

A good reply resolves the cause and closes the exchange. A poor one fixes the cause and opens a new argument, which is how one complaint becomes a pattern.

Reply promptly and briefly. Acknowledge that they raised it, say what you're doing about it, and give them a way to reach you if it happens again. That's the whole structure. Long replies invite line-by-line debate, and by the time you're disputing their account you're no longer talking about the door.

Don't argue with their experience. You can disagree with a conclusion without telling someone they didn't hear what they heard. "Sorry you were disturbed, here's what I've changed" lands differently from "that shouldn't have been audible", and only one of those ends the conversation.

Don't promise what you can't deliver. A commitment you can't keep becomes the subject of the next complaint, and it's in writing. Offer what you can actually do, then do it.

Keep the exchange in one channel. A conversation spread across a doorstep, a phone call and two message threads is hard to reconstruct and easy to misquote. One channel, in writing, is worth more than three verbal ones.

This is also where records software helps more than a shared password does. localsbnb.com keeps guest names, phone numbers and ID numbers masked by default and grants access by area. A neighbour dispute then doesn't pull a guest's personal details into a conversation that has no need of them.

Closing the loop, and keeping the paper trail

The last stage is the one most hosts skip: telling the person what changed, and then keeping everything together. A complaint that quietly fades is a complaint that can return.

Follow up once, after the fix has had time to work. One short message confirming what you changed is enough, and it does two things. It shows the neighbour you took it seriously, and it puts a dated line in the record showing the matter was closed and when.

Then build the file. The complaint as it arrived, your own note from the day, your reply, the evidence of the fix, and any correspondence with the building or the local authority all belong in one place. When a dispute resurfaces months later, a single file answers the questions that scattered messages can't.

Put a review date on it. If the same issue recurs, the file tells you whether the last fix worked or whether the cause is something you haven't found yet. That's the difference between a recurring problem and a problem you're still solving.

Keep the file to what's relevant. A record of an incident doesn't need personal details about guests beyond what the issue requires, and where rules apply, the local authority and the building's own documents set what you may keep and for how long. None of this is a substitute for checking those; it's the habit that makes checking them easier.

FAQ

What should I do first when a neighbour complains?

Separate the problem from the account. Write down what you were told, on the same day, alongside what you observed yourself. Then fix the cause and reply briefly, rather than arguing about the description.

Should I reply to the neighbour in writing?

Yes. Keep it short, acknowledge the concern, state what you're changing, and give one way to raise it again. One written channel is far easier to stand behind than a doorstep conversation nobody can reconstruct.

How long should I keep the record?

That depends on where you are and on your building's own requirements, so check those rather than assuming a period. What matters is keeping the complaint, your note, your reply and the fix together with the property, with a review date on the set.

A complaint is someone else's account, and the only counterweight is your own. Write the note the day you hear about it, answer the problem rather than the description, and keep the file with the property. localsbnb.com keeps each unit's listing, availability and rates in one calendar, so the property your record describes is the same place your bookings live.

---

This article is general guidance for hosts and isn't legal advice. Rules on short-term letting, noise and building occupation differ by country, city and building, and they change over time; check the current requirements of your local authority and your building's own documents.