local booking

A booking is local when the guest's home location, the city most platforms show on the profile, is the same city as the listing or close enough to drive home from. There is no fixed radius; the practical test is simple: could this guest comfortably sleep in their own bed tonight? If yes, the booking is local, and the stated purpose of the stay matters more than it would for any traveller.

The signal is behavioural, not personal. It says nothing about who the guest is, only that the usual reason for booking, needing somewhere to sleep away from home, does not apply, so a different reason must.

An unauthorised party needs a venue, not accommodation. The organiser books close to home, where their friends already are, usually for a single night that includes a Friday or Saturday, often at the last minute, and often for a group at or over the listing maximum. Each of those facts is innocent alone. Stacked together on a local booking, they describe a venue search, not a trip.

This is why screening services and experienced hosts treat the local signal as the anchor: it is the one fact that changes how every other fact should be read. A same-day one-night weekend booking from a traveller is a spontaneous trip. The same booking from someone two streets away deserves a conversation first.

Most local bookings are fine, and treating every one as a threat costs you real revenue and real goodwill. Common legitimate reasons include a renovation or repair making the guest's own home unusable, hosting visiting family who did not fit at home, a staycation or anniversary night, relocation gaps between homes, and quiet space to work or study.

The difference between these and a party booking is that a legitimate reason is easy to state. A guest with a real reason answers a friendly question naturally, usually in the first reply. Evasion, vagueness, or silence is the actual red flag, not the location itself.

Do not decline on the signal alone. Send a warm, professional message before approving: ask what brings them to the area and confirm who is coming. Restate the house rules, including the guest maximum and the no-party rule, so expectations are on record in the platform thread. Where the platform allows it, ask the guest to complete ID verification before check-in.

Then read the reply, not the profile. A clear answer plus a confirmed guest count usually resolves the risk entirely. A non-answer on a booking that also stacks other signals, single weekend night, full-capacity group, brand-new account, is a booking you can legitimately decline within platform rules, based on the booking facts.

In a structured screening process, the local signal carries the highest single weight, but it is never the whole score. The free Guest Risk Pre-Screener combines it with eight other behavioural facts, timing, account age, reviews, group size, into a transparent 0 to 100 score, and turns each triggered pattern into the concrete check to run before approving.

For the full playbook around the decision, including the anti-discrimination lines you must not cross, read the Guest Screening Guide.