Giving guests the Wi-Fi without the paper slip

Wi-Fi is the first thing a guest looks for and the most reliably mishandled piece of information in accommodation. Not because it is difficult — because it is so obviously simple that nobody examines how it is being delivered until the messages start.

The failure is nearly always transcription. A password is a string of characters that must be reproduced exactly, on a phone keyboard, by somebody tired, often from handwriting, sometimes in a second alphabet. Every step in that chain is a place to lose a character, and losing one character produces the same result as having no password at all.

Write it so it can be typed

Most of the damage is done before anyone gets to the technology.

Give the network name exactly as it appears in the phone’s list. Not “our Wi-Fi”, not the name of the house. If the router broadcasts TP-Link_4F2A and your card says Granvik Guest, the guest is looking for something that is not there. If you have renamed it, the renamed one is the truth.

Say whether the password is case-sensitive. It almost always is, and a guest cannot tell by looking at it. One line — “all lowercase, no spaces” — removes an entire category of failure.

Avoid characters that look like other characters. If you get to choose the password, choose one without l and 1, O and 0, or rn next to each other. If you do not get to choose, spell out the ambiguous ones: “that is a lowercase L, not a one”.

Do not use a font that fights you. A handwritten card and a decorative display face both turn a solvable problem into a guessing game. If it is printed, print it in something plain and monospaced.

Never write it only once. A slip of paper on the kitchen table is a slip of paper that will eventually be behind the fridge.

That last point is where most hosts start looking for something better, and it is the right instinct — but it is worth noticing that the four points above fix most of the problem with no technology at all.

Two different QR codes, which is the thing people conflate

This is the part that causes genuine confusion, because both are “the Wi-Fi QR code” in conversation and they are not the same object.

A Wi-Fi join code encodes the network credentials themselves. A phone that scans it offers to join the network directly — no typing, no transcription. It is the best answer to the narrow question “how do I get this person onto the network”, and it is the one that feels like magic when it works.

A guest guide code points at your guide, which contains the Wi-Fi section along with everything else. Scanning it opens a page; the guest reads the password and types it, or copies it.

The join code is faster for exactly one task. The guide code is more useful for every other task, and it has a property the join code does not: what it points at can be changed without reprinting it. A join code has the password baked into the ink, which is fine until the password changes, at which point every printed copy is wrong and silently so — the phone simply fails to connect and the guest has no idea why. This is the same class of failure described in QR codes that survive the season: a code that contains the answer rather than pointing at it cannot be corrected.

In practice most properties want both, and they are not in competition: the guide code goes where guests arrive, and the join code — if you use one — goes next to the written credentials, as a shortcut rather than a replacement. QRiousStay prints one code for the guide and can add a Wi-Fi code alongside it when you want one, on the same sign.

Two cautions on join codes. Support is good but not universal, particularly on older Android builds and on laptops, so the written password must still be present — a join code is an accelerator, never the only route. And a printed join code is a printed password: anyone who can photograph the sign has the credentials, which matters more in a shared hallway than in a private cabin.

Where to put it

The rule is the same as for any information a guest needs: put it where the question is asked, not where information lives.

Where they sit down. The kitchen table, the desk, the sofa arm. The Wi-Fi question is asked in the first ten minutes, sitting down, bag not yet unpacked.

Where they arrive. Inside the door, at eye height. This is also where the guide code belongs, and the two can be the same sign.

Not only in the welcome message. A message sent before arrival is three screens up a thread by the time it matters, and the guest is now on a different phone task entirely.

In the guide as well as on the wall, always. Paper gets moved, covered, spilt on and taken home by accident. The wall copy and the guide copy cost nothing to keep in step when the guide is the thing you edit.

For the physical craft of the printed part — how large the code has to be for the distance it is read from, which colour combinations quietly stop scanning, what paper survives a steamy bathroom — printing and placing your QR sign is the detailed version.

A Wi-Fi password sign that never goes out of date

Most Wi-Fi signs are printed once. That is the whole problem with them: the sign is a photograph of a password taken on the day it was printed, and nothing on the wall tells a guest how old the photograph is.

A Wi-Fi QR code fixes the typing and not the ageing. It still encodes one password, so replacing the router still means replacing every card in the house. It is a real improvement for guests and no improvement at all for you.

The version that stops going out of date works differently: the sign carries a code that points at your guide, and the guide holds the password. The paper never changes, because the paper does not contain the answer — it contains the address of the answer. Change the password once and every sign in the building is correct again, including the one in the room somebody is standing in.

That is worth spelling out, because it is the part that sounds like a technicality and is not. With a printed password, correcting a change means finding and replacing every copy, and the cost falls on you at exactly the moment you are busiest. With a code that points at a guide, the correction is one edit and the distribution is already done.

There is a practical consequence for how the sign is worded. If the code leads to a guide, the sign should not also print the password underneath it — two copies of a changing fact is one copy too many, and the printed one will be the one a guest reads and the one that goes stale. Let the sign say what it is for and let the guide say what the password is.

The sign also stops being a Wi-Fi sign. The same code answers the check-out time, the bin day and how the hob works, which means one piece of paper by the door instead of four scattered around the property.

When the password changes

This is the scenario that decides which of the approaches above you actually wanted, and it happens more often than people plan for: a router replaced, an ISP swap, a security tidy-up, a password that got shared somewhere it should not have been.

With the password written in the guide, the change is one edit and it is live at the next scan. Nothing on the wall changes, because the sign points at the accommodation rather than at a snapshot of it.

With the password printed on cards in every room, the change is a reprint across every room, which is why in practice the password does not change — the cost of changing it is high enough that hosts quietly decide it does not need to. That is a security decision being made by a printer.

With a printed join code, the change is worse than a reprint: the old code does not announce that it is stale. It fails silently, on the guest’s phone, with no explanation, and the guest concludes the Wi-Fi is broken rather than the sign.

If you change nothing else after reading this, put the authoritative copy of the password somewhere you can edit in under a minute, and treat every printed copy as a convenience that follows it.

Separate networks, when they are worth it

If your router supports a guest network, using it is usually sensible — not because of any dramatic threat, but for two ordinary reasons. It keeps guest devices off the same network as your own printer, storage, cameras and thermostats, which is mostly about accidents rather than attacks. And it lets you change the guest password without changing yours.

Some genuinely useful specifics:

• Name it so it is obviously the right one. Granvik-Guest beats TP-Link_4F2A_5G for a guest choosing from a list of nine networks.
• If you broadcast 2.4 GHz and 5 GHz separately, say which to prefer and why — 5 GHz for speed near the router, 2.4 GHz for the far bedroom. Otherwise half your guests are on the wrong one and concluding the internet is slow.
• In a building with several units, make it unmistakable which network is this apartment’s. Guests will otherwise try the strongest signal, which may be the neighbour’s.

What to avoid claiming, to yourself or in your guide: a guest network is not isolation, a shared password is not authentication, and none of this makes the connection private for the guest. Say what is true — “this is the guest network” — and do not dress it up as protection it does not provide.

Where Wi-Fi sits in the rest of the guide

Wi-Fi is the section most likely to be read and the least likely to be read twice, which makes it a good front door and a bad place to put anything else. Keep it to the network, the password, and the one line about case sensitivity. Resist the temptation to add the streaming logins, the printer, the smart TV instructions — those are their own sections, and a guest hunting for a password should not have to read past them.

It is also the clearest test of whether a guide is working at all. If the Wi-Fi question stops arriving by message and everything else continues, the guide is being found and read, and the remaining questions are content gaps rather than discovery gaps. If the Wi-Fi question keeps arriving, guests are not getting to the guide, and no amount of writing will fix that — the sign is in the wrong place.

How to stop answering the same guest questions is the method for telling those two failures apart, and what to include in a guest guide covers the fifteen subjects that belong alongside this one.

The tea and coffee by the kettle are a different object with a different job: what to put in a holiday let welcome pack covers the consumables, and why a password should never be in the basket with them.