Running an accessible drop-in event when your community speaks many languages

You set up a stall in the community centre expecting a steady trickle of residents, then a few people arrive who clearly want to take part but hesitate because of language.

Why language matters at face to face events

Drop-in events feel simple on paper. Put up a poster, book a room, and speak to whoever comes through the door. In practice the people you most want to hear from are often the ones least likely to stop by if they cannot understand the information on the table or the person behind it.

Language is not only about translation. It affects trust, the time people can spend with you, and whether they feel confident their answers will be understood and used. The good news is that small, low-effort changes make a big difference. Below are tactics you can use with a small team and a modest budget.

Quick ways to let visitors self-select their language

If someone has to ask for an interpreter, they will probably walk away. Make language selection immediate and visible.

• Entrance signage in multiple scripts: A simple sign saying Welcome and Information in other languages available in the community's common languages reduces friction.
• Colour-coded language cards: Put a stack of small cards on the desk, each in a different language and colour. People pick the card that matches their language and hand it to the person at the stall. It is fast and discreet.
• Flag or laminated list: A clear list of languages and a tick box people can point to works well when space is tight.
• Language QR codes: Stick a QR code on the table that links to the event summary in different languages. This lets people read on their own phone in private.
• Tablets with language menu: If you have tablets for surveys, let people choose their language on the welcome screen. The device becomes a private, self-service point.

Any of these methods works on its own. Use two if you can so people have options based on comfort and tech confidence.

Recruiting and briefing bilingual volunteers

You do not need professional interpreters for every interaction. Trained bilingual volunteers usually cover the practical needs of a drop-in, especially for short conversations and survey guidance. The key is to recruit the right people and give them a short, useful briefing.

Where to find volunteers

• Local community centres and faith groups
• School parent networks
• Staff networks within your organisation
• Local colleges and language courses

What the volunteer role should be

• Greet visitors in the chosen language and explain what the event is about
• Ask if they want to complete a short survey now or take a one-sheet summary
• Assist with tablet or paper forms without leading answers
• Note any wording that causes confusion and flag it for you
• Keep conversations confidential and signpost to support services where relevant

Five-minute volunteer briefing (print this and give to every volunteer)

1. Purpose: Explain the consultation in two simple sentences and the deadline for responses.
2. Privacy: Tell people how their responses will be stored and whether they are anonymous.
3. Suggested greetings and short scripts in English and the target language. Example: Hello, my name is [X]. I can help in [language]. Would you like to answer some questions now or take a paper summary?
4. How to use the tablet or paper form, including where the language selector is and how to mark the language on paper forms.
5. Escalation: Who to call for a complex query or safeguarding concern.

Pay or reward bilingual volunteers when you can. Even a modest voucher or travel reimbursement recognises their time and encourages reliability.

Produce one-sheet translated summaries that actually get read

People often want a quick summary before deciding to take part. A one-sheet in the person’s language reduces the time they need to commit and gives them a record to read again.

What to include on the one-sheet

• Plain language description of the proposal or issue
• Three short bullet points of what you are asking for feedback on
• How responses will be used and the deadline
• How to take part: QR code, tablet location, or contact details
• Contact for further support or complaints

Design tips

• Keep it short: one side of A4, clear section headings, large font
• Use plain language so translations are less likely to become awkward
• Ask a bilingual volunteer or community representative to check the translated version for tone
• Provide a visible way for people to note they received the sheet, such as ticking a list. That helps your monitoring and shows who you reached.

Tablet-guided surveys that work on the spot

Tablet surveys are ideal for drop-ins because they combine privacy, language choice, and instant capture.

Design principles for on-the-spot surveys

• Keep the survey very short: aim for five questions that can be completed in under five minutes
• Start with a language selector and a question asking Which language are you answering in? so you tag data correctly
• Use simple, clear options rather than long text boxes; include one optional free-text question for anything people want to add
• Make the first question something obvious the respondent can answer quickly to build confidence
• If possible, allow offline completion and batch upload later so you do not rely on venue WiFi

Practical setup

• Pre-load tablets with the survey and a clear welcome screen
• Lock the device to the survey app so people do not accidentally open other apps
• Have paper backups in the main languages with a language tick box
• If you use a third party platform, ensure you can export the original-language responses and the language tag

Capturing language-tagged feedback you can analyse later

Collecting the response is only half the job. You need to know what language the response is in and keep the original wording.

Simple ways to tag language

• A mandatory question at the start: Which language are you using to answer these questions?
• A language tick box on paper forms that volunteers complete for respondents who dictate answers
• If a volunteer is assisting, include a short note field: Assisted by [initials], language: [code]

Storing and analysing responses

• Save the original text and the language tag so you can review nuances later
• Run automatic translation back into your working language for quick analysis, but keep the original for quality checks
• Keep a short log of any translation issues volunteers reported during the event
• When you see repeated confusion about wording, flag that question for revision and note suggested alternative phrasing from the community

A short event checklist you can actually use

Before the event

• Prepare one-sheet summaries and print enough copies in the main languages
• Load tablets and test offline mode
• Recruit and brief bilingual volunteers with the five-minute script
• Make simple directional signage in multiple languages

During the event

• Put language self-selection options where they are seen first
• Have a staffed welcome point and a clear volunteer rota
• Offer the choice: quick help, survey now, or take a summary away
• Ask volunteers to log any wording issues and any follow-up needs

After the event

• Upload tablet data and tag responses by language
• Check original-language answers for anything that needs human translation
• Collate volunteer notes and suggested wording changes
• Send a short thank you to community partners and volunteers and share next steps

Common mistakes that trip people up

• No visible way to choose a language. If people must ask, many will not.
• Overlong forms. Even fluent respondents rush through long surveys at drop-ins.
• Leaving translation to volunteers without briefing. They can help but must know the task boundaries.
• Throwing away original language responses. You lose nuance and cannot correct machine translation mistakes.

Final practical takeaways

Running an inclusive drop-in is mostly about a few small, visible choices: show languages at the door, let people self-select, give volunteers a clear and short brief, offer a one-sheet they can take away, and capture what language each response is in. These steps are low cost and save time in the long run because you will hear from more people and you will not be spending days chasing missing translations.

If you leave with only two actions, do this: print a one-sheet in the top three community languages, and make sure every tablet or paper form starts by asking which language the person is answering in. That simple pair will change who feels welcome to take part and make your analysis far more useful.

People already have a voice. Your job is to make it easy for them to use it.