Live translation fails far more often from an empty chair than from a technical fault. If one person knows how to start it, the system works beautifully until that person is ill, travelling, or serving somewhere else — and the Sunday it fails will be a Sunday somebody was relying on it.
The fix is not better training. It is making the role small enough that anybody can hold it.
The job is genuinely small
Strip away the setup, which happens once, and a volunteer does three things: start the broadcast before the talk, pause it if the service moves to something that should not be translated, and stop it at the end.
That is the whole job. Everything else — the languages, the archive settings, the codes — was decided once by whoever owns the account and does not change week to week. If your volunteer needs to make decisions on a Sunday morning, something has been left configured wrongly.
The before-service checklist
- Open the operator page and sign in early, not while the welcome is happening. Ten minutes before, at the same time as the sound check.
- Confirm the speaking language and the languages the congregation will be offered.
- Say one test sentence into the microphone the speaker will actually use, and check the words appear correctly on screen.
- Check the sign or slide with the attendee code is where people can see it.
- Check the storage setting for today. Ordinary service, or something that should not be archived?
Five items, two minutes. Print it and stick it to the machine.
The one thing to watch
Teach a single habit, and teach it as the whole job: if the speaker is talking and the text is not moving, something is wrong.
That one observation catches nearly every real failure — a dropped connection, a muted channel, a radio microphone that ran out of battery, a broadcast that was never actually started. Everything else can wait until after the service.
The corollary matters too: text that is moving but reads as nonsense is an audio problem, not a software one, and the answer is the microphone rather than any button on the screen.
What to do when it goes wrong
Give your volunteer permission to do very little, because a panicking operator makes things worse.
- Text stopped. Check the microphone is on and the channel is not muted. Then restart the broadcast — it takes seconds and attendees rejoin automatically.
- Text is nonsense. Leave it. It is the audio, and it cannot be fixed mid-sermon. Note it and tell whoever owns the setup afterwards.
- Somebody says it is not working on their phone. Ask whether they are on the church Wi-Fi, and suggest mobile data. That solves most of them.
- Anything else. Write it down and carry on. Nothing else is worth interrupting a service for.
Being explicit about what not to do is as valuable as the checklist. Volunteers who are afraid of breaking something will not volunteer twice.
Write down what only you know
Every setup has two or three local details living in one person's head: which channel on the desk carries the pulpit microphone, where the sign is kept, which laptop is the right one, the password to the operator account, what to do about the second microphone that has never worked properly.
Put them on a laminated card next to the machine. That card is the difference between a system with one operator and a system with four, and writing it takes twenty minutes once.
Train by doing, not by explaining
Nobody learns this from a demonstration. The pattern that works:
- They watch you run one service, holding the checklist.
- They run one while you stand behind them and say nothing unless asked.
- They run one alone while you are in the building but not at the desk.
- They are on the rota.
Three weeks, and the third one is the important one — the confidence comes from having done it without help, not from having been shown carefully.
Practise on a midweek meeting rather than a Sunday if you can. Lower stakes, smaller room, and a mistake costs nothing.
Who to ask
The instinct is to look for someone technical. It is the wrong instinct: this job needs reliability and attention, not skill. The best operators tend to be people who are already at the building early — the sound team, the welcome team, a parent whose children are in the first group.
Two groups worth considering that churches often overlook. Teenagers are excellent at it and take the responsibility seriously when it is real. And someone who uses the translation themselves has an obvious stake in it working, and will notice problems nobody else does.
Rotate deliberately
Train the second volunteer before you need them, not when the first one announces they are moving away. Three or four people on a rota turns a fragile arrangement into a dependable one, and it means nobody has to be at every service to protect it.
Rotate often enough that everyone stays current. Somebody who last did it in March will have forgotten the checklist by September, which is precisely why the checklist is on the machine.
Keep the tools simple
InMyTongue's operator view is a single screen with a start button, a pause button and the live text — deliberately little to learn, and the live text means a problem is visible immediately. New accounts include free credit, so a volunteer can practise on a midweek meeting first. See the operator view.