The Guest Guidebook as a Compliance Document: House Rules, Emergency Contacts and Local Fees

A guidebook that only lists the wifi password is decoration. The same document, written slightly differently, is the evidence you were told to provide.

Last updated: September 28, 2026

A guidebook that lists the wifi password and the bin day is decoration. The same document, written slightly differently, is often the record that shows a guest was told the house rules, where the exits are, who to call when something goes wrong, and what local charges apply. Nothing about the format changes. The content does.

Key Takeaways

• Three sections do the work. The rules, the safety and access information, and the money collected locally.
• Plain sentences survive. 'No smoking indoors' is a record; 'please respect our home' is a mood.
• Fees need an authority. Name the fee and who requires it, not an amount you guessed at.
• Contacts decay every season. A number that worked last summer isn't a number that works now.
• Send it before arrival. A document first read at the door has arrived too late.

The three sections a regulator looks for in a guest document

Ask what an inspector or a local authority wants from a guest document and the answer is usually smaller than hosts expect. They want to see that the guest was told, in writing, about three kinds of thing.

The first is the rules the guest is expected to follow. Whether smoking is allowed, indoors or anywhere on the property. Whether pets are allowed. The maximum occupancy, stated as a number. Whether events are permitted. And what the building's own rules say about shared areas, which often exist independently of anything you'd choose yourself.

The second is safety and access. Where the exits are and how to open them. Where the smoke alarms and the extinguisher are. What to do if an alarm sounds at night. Where the first aid kit lives. Who to call in an emergency, including the local emergency number for the country the property sits in.

The third is money and local obligations: any tourist tax or local fee the guest pays, who collects it, when, and in which currency, plus anything local law asks the guest to do at check-in, such as presenting identification.

Apply a reading test to your own document. A guest who's tired, arrives at midnight and skims it for ninety seconds should still be able to answer three questions: what are the rules, how do I get out, and what will I be asked to pay. If they can't, the document isn't doing the job, however nice it looks.

One more habit belongs in this section: say what the guest isn't expected to do. A document that only lists prohibitions reads as hostile, and a hostile document gets skimmed harder. Naming the permitted version alongside the restriction — where smoking is allowed, which shared areas guests may use — makes the restrictive lines likelier to be read at all.

Writing local fees so a guest is not surprised at check-in

The fee is rarely the problem. The surprise is.

Separate what's already inside the rate from what's collected locally. Then say which fee it is, who requires it, and how it's set. Fee levels are decided by the local authority, and they change. So point the guest at the requirement rather than freezing a number into your document. If you do quote a figure, date it and add a line telling the guest to check the current one. A document that names the wrong amount is worse than one that names none.

State the currency, not just the symbol, because a guest paying in another currency will convert in their head and get it wrong. Say when the fee is collected: with the deposit, at check-in, or afterwards. And say who collects it, because 'the platform collects it' and 'I collect it in cash at the door' read as two different things on arrival.

Where the guest's language isn't one you share, this section is where the cost of a bad translation shows up. LOCALSBNB supports six interface languages — English, Simplified Chinese, Traditional Chinese, Japanese, Thai and Malay. It falls back to English when a translation is missing, and it keeps each property's time zone and currency aligned to where the property sits rather than where the reader is. That matters more than it sounds: a check-in time converted into the wrong time zone is a support message waiting to happen.

Emergency contacts that are still correct next season

Contacts decay faster than any other part of a guidebook. The cleaner changes number. The handyman retires. The building manager moves to another block. The host relocates and never updates the page that still lists a number in a city they left.

Write roles, not just names, so the document survives a change of person. Put a review date on the page. Then test the numbers, which almost nobody does: dial them once a season rather than trusting that last year's list is still live. Include the local emergency number, the building manager or neighbour who holds a key, and one person reachable outside business hours.

State the property's time zone in the document too. 'Call before 21:00' means nothing without knowing whose 21:00 it is, and it matters most when the host and the property sit in different zones.

Contacts aren't the only thing that goes quiet. A channel that dropped off, or a listing that's no longer live, reads exactly like one that's fine — right up to the moment somebody checks. LOCALSBNB shows each direct channel's source status against one calendar, which is the same seasonal check you'd run on your phone list, applied to the listings behind the property. That's at localsbnb.com.

Making the guidebook you already send do this work

You almost certainly send something already — a PDF, a long message, or a printed sheet on the kitchen counter. The upgrade isn't a new document. It's a reorganization of the one you have.

Split it in two. Keep the friendly half: the restaurant list, the coffee place, the walk to the beach. Separate the half that has to be accurate: rules, safety, fees and contacts. Then put the accurate half at the front, so it gets read rather than discovered as an appendix on day three.

Version it. A date and a version number at the top of that section tells you, a year later, which guests received which wording. Send it before arrival rather than at the door, and keep a copy of what went out and when.

Write it in the guest's language where you can, and treat the rules as the part worth translating first. A rule the guest can't read isn't a rule the guest was told.

FAQ

Isn't a guidebook just a nice extra for guests?

It's both, and the two jobs don't conflict. A good guidebook is read because it's useful; a compliance document is kept because it's dated and specific. The same file can do both if the accurate section sits at the front and the friendly section follows it.

Do I need to state exact local fee amounts?

State the fee, who requires it and when it's collected. The amount itself is set by the local authority and changes, so the safer wording points the guest at the requirement. If you do quote a figure, date it and tell the guest to confirm the current one.

What if a guest ignores the rules anyway?

That's a different problem from whether they were told. Keep the record — the dated document, and the version that was sent — and handle the breach under whatever the booking terms and local rules allow. The document's job is to show the information reached the guest.

None of this makes a guidebook legally bulletproof, and none of it is legal advice. What it does is turn a document you already send into a record saying the guest was told: the rules, the exits, the contacts and the local charges. That's a small change in wording and a much larger change in what the file is worth. The upkeep is the hard part, and it gets easier when the listings behind the property are visible in the same account — localsbnb.com.

---

This article is general guidance for hosts, not legal advice. What a guest must be told, and when, differs by country, region and building, and changes over time; check your local authority's current requirements and the platform terms in force where you list.