A man reaches the front of the queue, holds out his phone with the QR code already open, and says nothing. You scan it, the screen goes green, and you say "lovely, you are in hall two, straight through and on your left". He nods, smiles, and walks the wrong way.
He did not misunderstand the check-in. He understood the scan perfectly, because a scan needs no language. He missed the sentence afterwards, which is the part nobody plans for.
This is more common than the guest list suggests
Nothing on a registration form tells you how confident someone is in English, and very few people volunteer it. So the size of this is easy to underestimate.
The scale in the population is documented. In the 2021 census, 8.9% of usual residents of England and Wales aged three and over, 5.1 million people, did not have English or Welsh as a main language. Within that group the census recorded 17.1% (880,000) who could not speak English well, and a further 3.1% (161,000) who could not speak it at all (Language, England and Wales: Census 2021, ONS).
Then add the people who do not live here. VisitBritain forecasts 45.5 million inbound visits in 2026, growth of 4% on 2025 (VisitBritain 2026 inbound tourism forecast). Conferences, trade shows and industry events take a share of that, and those guests arrive at the same desk as everyone else.
You do not need to know which of your guests these are. You need a door that does not depend on knowing.
The scan is already language-neutral. Everything around it is not
Worth being precise about where the problem actually sits, because it is not where people assume.
| Moment | Needs shared language | What usually carries it |
|---|---|---|
| Finding the right entrance | Yes | Signage and the pre-arrival email |
| Presenting a pass | No | The code itself |
| The scan and the confirmation | No | The screen going green |
| Being told where to go next | Yes | A spoken sentence at the desk |
| Something going wrong | Yes | A longer spoken sentence, under pressure |
Two of those five are already fine. A signed QR pass works the same for everyone holding one, which is one of the quieter arguments for a signed pass rather than a screenshot. The failure points are the approach, the instruction afterwards, and the exception.
Fix those three and the door works. Nothing else needs translating.
Send the arrival details as a picture, not a paragraph
Most of the work happens before anyone reaches you.
The confirmation email is where a guest decides which door to walk to, and it is usually written as prose. Three sentences about the venue entrance on the north side, the registration desk in the main atrium, and the doors opening at half past eight. That is the hardest possible format for someone reading in a second language on a phone at a station.
Rewrite the arrival section as a small block of facts. The venue name and full address, in the local spelling, exactly as it appears on the building. The nearest station. A photograph of the entrance they should use. The time, in figures. The QR code, large. A guest who reads none of the surrounding text can still match a photograph to a building and hold up a code, and that is enough.
We have written separately about the emails that get people to the door, and this is the version of that advice that survives translation: fewer words, more figures, one picture of the door.
Signage in symbols, then words
Inside the venue, the same rule. A guest looking for registration is scanning for a shape, not reading a sentence.
Put the word "Registration" on the sign because it is close enough in a lot of languages to be recognisable, but do not rely on it. Rely on an arrow, a queue barrier that visibly leads somewhere, and the desk being visible from the entrance. If you have split the door into lanes, number them rather than naming them, so "lane 2" works without any English at all. That is a small change to the way you sign the route in and it costs nothing at print time.
The badge itself matters here too. A name and an organisation are legible to anyone. A cryptic session code is not. Keep what goes on the badge to things that can be read without context.
The instruction after the scan is the weak point
This is the sentence that gets lost, and it is lost every time because it is spoken once, quickly, by someone who has said it four hundred times that morning.
Stop saying it. Print it.
Whatever the guest needs to do next belongs on the badge or on a slip that comes out with it. Hall number. Table number. Start time. If the badge is printed at the desk, it can carry the room. If it is pre-printed, put a numbered sticker on it as you hand it over. Point at the number, then point at the sign with the same number on it. That exchange works between two people with no shared language at all, and it takes less time than the sentence did.
For crew, this is one line in the briefing rather than a policy. Hand the badge over pointing at the room number, every time, for everybody. Doing it only for guests who look like they need it is both slower and worse, because the judgement is usually wrong. Add it to the five-minute door brief and it becomes the habit by the second hour.
Kiosks are quietly good at this
A self check-in kiosk has one real advantage that rarely gets mentioned. It does not rush anybody.
A guest at a kiosk can read the screen twice, use their phone to translate it, and try again, with no queue of faces behind them and no member of staff waiting. The same person at a staffed desk will very often nod, say yes, and walk away rather than ask a second time. Nobody enjoys being the person holding up a queue.
That makes kiosks worth placing deliberately rather than only as overflow, which is a different argument for them than the usual one about throughput. It also raises the bar on the wording. Short prompts, one instruction per screen, a button that says what it does rather than "continue". All of which is good practice anyway, and we set it out in writing kiosk prompts people actually read and designing a kiosk flow people finish.
Leave a phone charging cable near the kiosks. Someone translating a screen is doing it on a phone that has been navigating since six in the morning.
Have a plan for the exception, because that is where it breaks
Everything above handles the normal case. The hard case is the guest whose pass will not scan, who is not on the list, or who has arrived at the wrong event entirely, and who cannot easily explain any of that.
Three things make this survivable.
- Search by more than the name. Names get transliterated inconsistently, so the spelling on your list and the spelling on their passport may genuinely differ. Searching by email, booking reference or organisation finds people that a name search will not. Ask for the confirmation email and search what is in it.
- Take them out of the queue. Move the conversation to the side, where there is no audience and no time pressure. Half of what looks like a language problem is embarrassment, and it resolves the moment the queue is not watching.
- Let the phone do the talking. A member of crew holding out their own phone with a translation app open is not a failure of professionalism, it is the fastest tool available and everybody in the exchange knows it. Say so in the briefing so nobody feels they need permission.
Keep the record of what happened in the system rather than in somebody's memory, as with any other exception at the desk. If the resolution was "found by email, badge reprinted", that note is what stops the same guest explaining themselves again after lunch.
What this actually costs
A photograph of the entrance in the confirmation email. Numbers instead of names on the lane signs. A room number pointed at rather than said. One line in the crew brief. A kiosk placed where somebody can stand at it without being hurried.
None of that is a translation budget, and none of it is only for guests who do not speak English. Every one of those changes makes the door faster for the guest who has run from the station, the guest who is on a call, and the guest who simply was not listening. Which is most of them, most of the time.
The scan was never the barrier. It was the sentence afterwards, and the sentence was avoidable.
