Running Photo Delivery at a Multilingual Event
TIME&SPACE · Organiser's Playbook
The scan itself needs almost no words. Everything around it does, and those are the parts that get machine translated at midnight and never read again.
Running Photo Delivery at a Multilingual Event
In short: The core action, scan a code and take a selfie, is close to language independent. The parts that surround it are not: the sign, the consent text, the email, and the message a guest sees when nothing is found. Get those four right in each language you actually serve, and stop there.
An international conference in Lisbon has attendees from thirty countries. A festival on the Algarve coast has a crowd that is half Portuguese and half everything else. In both cases the organiser eventually asks the same question: how many languages does the photo delivery need to be in.
The answer is smaller than it looks, because most of the flow is not made of words.
The scan is the easy part
A guest points a camera at a code, sees themselves on screen, takes a selfie, and their photographs appear. That sequence is understood by someone who reads none of the interface text at all. It looks like every camera they have used.
This is worth naming explicitly, because it changes where the effort goes. You do not need the whole experience translated. You need the four moments where a guest has to understand something they cannot infer.
The four things that genuinely need language
1. The sign. This is the one that decides whether anybody scans at all. Keep it to one instruction and let the pictogram carry the rest. A camera icon, a phone icon, four or five words. Two languages on a sign is fine. Five is a wall of text nobody reads, and at that point you are better off with an icon and no sentence. There is more on siting and sizing in where to place QR codes at your event.
2. The consent text. This one is not a courtesy translation. Face matching is biometric processing, and the consent a guest gives has to be given in a language they understand, or it is not informed consent. A translated legal notice is a legal notice in that language, with the same weight as the original. That means it gets the same review, not a quick pass through a translation tool the night before doors. The obligations themselves are covered in the GDPR consent guide for organisers.
3. The email that follows. Choose its language from what the guest actually gave you at registration, not from the country the event is in. A Dutch attendee at a Lisbon conference should not get Portuguese because the venue is Portuguese. If you have no signal at all, use the language of the ticket they bought. The post event email is the single highest-value message in the sequence, so it is worth the extra field on the registration form.
4. The empty result. When a scan returns nothing, the guest needs to know why, and this is the string that gets translated worst because nobody proofreads a message they hope never appears. It is also the moment a guest decides the whole thing is broken. Say plainly that the photographs may not be uploaded yet and that they should try again later. Guests not finding their photographs is usually timing rather than failure, and the message has to carry that in every language you ship it in.
Pick your languages from the ticket data
Most organisers guess at this and over build. The registration list already tells you the answer. If ninety percent of attendees come from two countries, you need two languages and a clean English fallback, not seven.
The cost of an extra language is not the translation. It is that every future change has to be made in that language too, and the ones that quietly go stale are always the low traffic ones.
Have one native speaker read it
Machine translation is good enough for a first draft and not good enough to ship. The failure mode is rarely a wrong word. It is register: a consent notice that reads as brusque, or an invitation that reads as an automated warning. One native speaker, twenty minutes, before the event rather than after it.
The short version
Translate the sign, the consent, the email, and the empty state. Choose the languages from your own registration data. Have a human read each one once. The scan in the middle takes care of itself, which is the part most people expect to be hard.
If you are setting this up for the first time, how to set up photo delivery at your event covers the rest of the sequence.
Founder, TIME&SPACE