A digital guest directory for a small hotel

A hotel guest directory is a different object from a holiday-rental welcome book, and the difference is not size. A rental guest is alone with the building and the guide has to answer everything. A hotel guest has a person downstairs, so the directory’s job is narrower and stranger: it has to answer what the desk should not have to, without pretending to be the desk.

Get that boundary wrong in either direction and the directory fails quietly. Too thin and the phone rings all evening. Too thorough and it reads as a wall between the guest and a human being, which for a small property is the opposite of the thing you are selling.

This is about building the digital version. The argument for replacing the printed one at all — the maintenance arithmetic across a room count — is in the in-room binder problem; if you have not decided yet, start there.

The boundary: in the room, or at the desk

The useful test is not importance. It is whether the answer changes.

Put it in the directory when the answer is stable and the question is frequent. Breakfast hours. How the air conditioning works. Whether there is an iron. The Wi-Fi. Where the lift is. Check-out time. What the towel card means. These do not change between Tuesday and Thursday, and answering them in person for the fortieth time this week is not hospitality, it is transcription.

Leave it with the desk when the answer depends on today, or on this guest. Whether the restaurant can fit four at eight. Whether the late check-out is possible on a full Saturday. Whether that taxi will actually come in this weather. A directory that answers these has to either be vague, which is useless, or wrong, which is worse.

And be explicit about the seam. The most valuable line in a small hotel’s directory is often the one that says what the desk is for and how to reach it — because a guest who cannot tell which of their questions is a desk question will either ask none of them or all of them.

What belongs in it

Ordered by how a guest actually meets the property, not by department.

Wi-Fi. First, always, and written to be typed. Network name exactly as it appears in the list; password exactly as entered, with a note if it is case-sensitive. If you run separate networks for guests and for conference space, say which is which in the room it is in. Sharing Wi-Fi with guests covers the handover in more detail than it deserves and rather less than it needs.

Breakfast. Hours, where, and whether it is included — the three questions in that order, because the third one is the awkward one and guests would rather not ask it out loud. Add the weekend variation if there is one; it is the single most common front-desk correction.

Check-in and check-out. The times, what happens to luggage on either side of them, and whether late check-out is a thing that exists at all. Do not promise a late check-out in the directory. Say whether to ask.

The room itself. Heating and cooling, in one paragraph, written for somebody who has never seen this thermostat. How to get more towels. What the safe code defaults to. Which switch is the one by the bed that nobody can find.

Facilities. Restaurant, bar, sauna, gym, pool, parking, laundry — each with hours and any rule that matters. A closed facility should say it is closed, with a date, rather than disappearing; a guest who read about the sauna on the booking site will go looking for it either way.

Safety and contact. The emergency number for the country, the fire exit nearest this room, and how to reach the desk at three in the morning. This is the section most likely to be missing from a directory built from the marketing side, and the only one whose absence is genuinely serious.

Local recommendations. Fewer than you want to include. Six places you would send a friend, with why and how far, beats forty with opening hours you cannot maintain. Recommendations age fastest of anything in here.

The things only this hotel has. The honesty box. The dog that lives in the lobby. The stairs to the roof that are worth it at sunset. This is what stops a directory reading like it was generated, and it is the part a chain cannot copy.

Multilingual guests, which is the whole reason to bother

For a small hotel this is often the strongest single argument for going digital, and it is not really about convenience.

A printed directory exists in one language, or in two if somebody once paid for a translation and it has been drifting since. Everything else is handled by the desk — which means a guest with no shared language with the person on duty has, in practice, no directory at all. They have a laminated card they cannot read and a conversation they cannot have.

A digital directory is offered in the languages you switch on, and the guest chooses on their own phone without asking anyone. QRiousStay carries 129 translation languages in the catalogue; how many a given property may expose at once depends on its plan, and the property’s own source language is always present and never counts against that.

Two things worth getting right in the source text, because they are where translated directories go wrong: write one instruction per sentence, and do not bury an obligation inside English politeness. “You might want to leave the key at reception” is an instruction in English and a suggestion in most translations. Building a guest guide in your guests’ languages is the longer treatment, and it applies to a directory unchanged.

Where the code goes

Placement decides whether any of this is read, and hotels have a specific problem rentals do not: the guest is in the room for a few days, but they form their habits in the first ten minutes.

In the room, at eye height, where a guest already stops. The desk, if there is one. Beside the kettle. On the back of the door is popular and mostly wrong — guests look at the back of the door when leaving, not when arriving.

Not on the television. The TV welcome screen is the most-skipped surface in a hotel room.

A second code at reception does more work than it looks like it should. It turns a repeated verbal answer into a gesture, and it lets an arriving guest scan while somebody is still finding their booking.

One code per room, or one per property? One per property is simpler, and correct for most small hotels — the directory is the same document in every room. Per-room codes only earn their complexity if the content genuinely differs by room, or if you want to know which rooms are scanning, and the second reason is weaker than it sounds. In QRiousStay each accommodation carries its own guide, its own permanent code and its own scan data, so “per room” and “per property” is a decision about how you model the building, not a limitation.

The physical craft — size, contrast, paper, what survives a damp bathroom and a year of cleaning — is in printing and placing your QR sign. Hotel signage fails more often than rental signage for one boring reason: it is reprinted less and cleaned more.

Keeping it current, which is the actual job

The reason printed directories go stale is not laziness. It is that the cost of fixing one typo is a reprint across every room, so nobody fixes one typo, so the corrections queue up until they justify a reprint, by which time the directory has been wrong for a season.

Digital removes that arithmetic, and replaces it with a different failure: an editable thing that nobody has been made responsible for editing. The fix is unromantic.

Give it an owner. One person, named, who can change it without asking.

Give it a trigger, not a schedule. “Review the directory quarterly” does not survive a busy season. “Whenever breakfast hours change, the directory changes in the same ten minutes” does, because it is attached to the event rather than to a calendar.

Check the seasonal facts before the season, not during. Pool opening, bar hours, which of your six recommendations closed over winter.

Watch the questions, not the analytics. The things guests still ask at the desk are the directory’s actual bug list. Scan counts tell you whether the sign is working — whether anyone is scanning at all, whether a move helped — and deliberately not what anyone read. What scan data shows sets out that boundary properly, because over-reading it is the most common way a good measurement becomes a bad decision.

What this is not

A guest directory is not a property management system, and a small hotel evaluating one should be clear about that before the demo rather than after.

It does not hold bookings, availability, rates or the channel connections that keep them in sync. It does not check anyone in, take payment, assign rooms, or talk to your PMS. It is the document a guest reads once they are already in the building, and the value it creates is in the questions that stop arriving and the information that is finally correct in every room at once.

That is a smaller claim than the category usually makes, and it is worth insisting on, because a hotel that buys a directory expecting operations will be disappointed by something that was working correctly. A guest guide is not a PMS is the full version of where the line sits.

A reasonable first week

Build the room-facing half first: Wi-Fi, breakfast, check-out, heating, the desk’s number, the fire exit. Six sections, none longer than four sentences. Print one sign, put it in one room, and leave the binder where it is.

Then stay in that room for an hour and use it as a guest would — on a phone, not knowing the building. The gaps show up immediately and none of them require a reprint to fix.

Add the rest across a fortnight, and take the binder out of the other rooms only once somebody has scanned the code in that room and not come downstairs to ask what it was for. How to set up a digital guest guide has the step-by-step version of this arc, written for a single property but true of a floor of them.