Screening Guests Without Breaking Discrimination Rules

Every host screens. The difference between a defensible check and a complaint is usually what you wrote down and what you asked for.

Last updated: October 4, 2026

Every host screens. You read a profile, weigh a message, and decide. That's normal, and done well it protects both you and your guests. What turns a routine check into a complaint usually isn't the decision itself. It's what you asked for and what you wrote down.

Key Takeaways

• Screening is for fit, not for filtering people out. You're matching a booking to your rules, not judging who someone is.
• Ask everyone the same questions. A question you'd put to every guest is far easier to defend.
• Drop the ones that probe the person. Anything that looks at who someone is, rather than what they need, creates risk.
• Write the rule before the booking. A rule you can state in advance is one you can apply the same way every time.
• Keep the record clean. Note the decision and the rule it missed, and keep guest details to a minimum.

What screening is actually for

Screening isn't a personality test. It's a short, repeatable check that a booking fits your listing and your rules. That's the whole job.

What you're checking is capacity and fit. How many guests, which dates, what the trip is for, and whether the guest has read your rules. Those are facts about the booking, and facts are easy to apply the same way twice.

When screening stays on the booking, it stays defensible. When it drifts onto the person, it gets risky, and the risk grows quietly. A host who screens on instinct, without a written rule, can't easily explain later why one booking was fine and another wasn't.

There's also a practical reason to keep it simple. Guests can tell when a check feels routine and when it feels personal, and the second kind is the one that gets reported.

A written rule also protects you from yourself. On a busy week, instinct says yes to one booking and no to another that looks the same. The rule is what stops that drift.

Screening cuts both ways, too. When a booking genuinely doesn't fit, a clear rule lets you decline without making it personal, which is easier on you and fairer to the guest.

Screening isn't only about who you let in. It's also about what you can explain later. Two hosts can make the same call and end up in different places, depending on whether one can point to a rule and the other can only describe a feeling. That's the real reason to write it down. Not to protect guests from you, but to protect a fair decision from being misread as an unfair one. A rule you can quote does that quietly.

Questions you can ask every guest

Some questions work for any booking, which is exactly what makes them safe. You can put them to anyone and get a useful answer.

• How many guests will be staying?
• Will anyone be visiting during the stay, or only the guests on the booking?
• What brings you to the area, and when do you expect to arrive?
• Have you read the house rules, and is anything unclear?
• Will you need something specific, like a cot or an early check-in?

Run your eye down that list and one thing stands out. Every question is about the stay. None is about who the person is. Keep the list short, too. Five questions is plenty, and a long form starts to read like an interview. Keep them in the same order as well, so the check feels routine and any comparison stays honest.

That's your test. Before you send a question, ask whether you'd send it to every guest. If the answer is yes, it fits. If you'd only ask it of some, it doesn't.

Questions that create the problem

The questions that cause trouble aren't usually rude. They're the ones that probe who someone is, rather than what the booking needs.

That covers anything about a guest's background, beliefs, family, health or where they come from, framed as a reason to decide. It also covers the softer version: asking one guest for details you never ask another.

The wording isn't the only issue. The pattern is. A host who asks some guests for extra documents, and not others, has built a record that looks like a rule even when there isn't one. If that record ever gets read by someone else, the pattern is what they'll see.

So the fix isn't a cleverer way to ask. It's consistency. Same questions, same standard, same short note, whatever the guest.

If you catch yourself writing "just to be safe" before a question that only some guests get, that's the signal. Safety applies to every booking, or it isn't the reason.

A guest who is asked more than another will notice, even when you don't say why. That notice is what turns a routine check into a complaint, and it's why the questions you keep matter as much as the ones you drop.

Writing a rule you can apply consistently

A rule you can't state in one sentence is a rule you can't apply the same way twice. Write it down before the next booking, not after the next complaint.

Sit down and put your screening rule in four lines: the few questions you ask every guest, what your listing can't host, and what you do when a booking doesn't fit. Keep it short enough to remember and specific enough to use.

When a booking doesn't fit, say so plainly and point to the rule, not the person. "This listing can't host more than four guests" is a sentence about a limit. Anything about the guest is a sentence you don't want to write.

Then make the tool match the rule. LOCALSBNB shows you the guest and the dates before any action, and runs check-in, check-out, extensions and room changes only after you confirm, on overseas stores. Your records stay under your control: credentials sit on your device, and guest names, phone numbers and ID numbers are masked automatically. You can see how that fits your workflow at localsbnb.com.

A written rule also makes the quiet cases easier. When you're tired and a booking feels off, the rule answers for you, and it answers the same way it did last week. If a booking is declined, keep the note short and tie the reason to the rule. A long explanation invites argument; a clear one closes the question.

Store the rule where you'll see it while you work, not in a folder you open twice a year. The version you actually use is the one that sits next to your inbox.

Consistency is easier to keep than to recover. Once you've asked one guest for more than another, you can't un-ask, and the record stands. Start as you mean to continue, from the first booking of the season. If you change your rule, change it for everyone at once and note the date. A rule that shifts per guest isn't a rule, and it won't help you if you're asked to explain it. Write the new version above the old one.

Two things to do this week: write your four-line rule, and check it against the last ten bookings you accepted.

FAQ

Can I refuse a booking I'm not comfortable with?

You can decline a booking that doesn't fit your listing or your rules, and you should say which rule it misses. What you can't do is turn someone away because of who they are. Check your local requirements and your platform's current terms for how to word a refusal.

What screening questions are safe to ask?

Questions about the stay tend to be safe, such as how many guests, when they'll arrive and what they need. Ask the same ones of every guest. Anything that probes who someone is, rather than what the booking needs, is where risk starts.

Do I need a written screening policy?

It isn't required everywhere, so check your local requirements first. Even where it isn't, a short written rule helps you apply the same standard to every booking and explain a decision if you're asked.

Screening works best when it's boring. The same questions, the same rule and the same short note for every booking. That consistency is what separates a defensible check from a complaint, and it costs you a single page. When you're ready to keep your booking decisions and guest details in one place you control, you can open your workspace at localsbnb.com.

---

This guide offers general advice for hosts. It isn't legal advice. Rules change over time and differ by place, so check the current requirements of your local authority and the current terms of each platform you use.