Hybrid service translation checklist: in-room and online audiences together
A printable checklist for translating a service with people in the room and online at once: who does what, how audio is routed, which links go where, what to announce and what to do when something fails.

What should a hybrid service translation checklist cover?
A hybrid service translation checklist covers five things for a service with people in the room and online at the same time: named roles, a speech-only audio route into the translation, one listener link shared with both audiences, announcements for each audience, and a written fallback for every likely failure. Print it, tick it off each week, and keep it by the sound desk.
Hybrid churches have one advantage: a single SermonLingo service room serves both audiences. Guests in the pews and viewers at home open the same listener link, and listeners are unlimited, so online viewers don't need a separate translation room. What changes is coordination, because more people and more screens depend on the same audio.
Who does what? Assign the roles before Sunday
| Role | Before the service | During the service | Watches for |
|---|---|---|---|
| Translation operator | Opens the console, checks languages and audio input, starts the stage display | Goes live, pauses for music, resumes for speech | A flat input meter or listener counts falling to zero |
| Sound engineer | Builds and labels the translation send | Keeps the preacher's mic healthy and fresh batteries ready | Clipping, dead packs, band bleeding into the send |
| Stream producer | Adds the caption overlay to sermon scenes, updates the description | Switches cameras and slides with the overlay on | Overlay missing after a scene change |
| Online host | Drafts the pinned chat message | Posts the link at the start and before the sermon, answers viewers | Viewers saying captions stopped |
| Room helper | Places QR cards, stands near the entrance | Helps guests scan and choose a language, reports problems | Guests struggling to join |
In a small church, people double up. The stream producer can run the translation console in a pinch, but keep the room helper and the online host separate from the operator. During the sermon the operator's eyes belong on the console, not on a guest's phone. If you are training new people for these jobs, our guide to training church translation volunteers has drills for each role.
Checklist: the week before
- Confirm this service's listener languages (up to 8) and which one, if any, goes on the stream overlay.
- Check that your plan covers the outputs you need: phone captions on every plan; stage display, OBS overlay and AI voice from Standard; RTMP encoder input from Advanced.
- Get the sermon outline, scripture references and any guest names from the preacher. Add new names to the glossary and paste the outline into Sermon notes in room settings.
- Paste the listener link into the stream description template and the pinned chat message.
- Print fresh QR cards if the link has changed. Our guide to QR codes for church translation covers placement and print size.
- Book a 20-minute rehearsal with the operator, sound engineer and stream producer in the same room.
- Agree who makes the call when something fails: usually the operator for translation and the stream producer for the stream.
Checklist: audio routing for two audiences
A hybrid service runs three different mixes from one desk, and only one of them should feed translation:
- The room mix (front of house) is shaped for the building, with band, effects and level rides.
- The stream mix adds music and ambience mics so home viewers feel the room.
- The translation send carries speech only, as cleanly as possible.
In words, the signal flow looks like this: preacher's mic → mixer → main PA for the room; mixer → stream bus → encoder → platform; mixer → translation aux → USB audio interface → operator's computer → SermonLingo → listener page for both audiences, plus the overlay back into the encoder.
- The translation send has its own aux or matrix, labeled TRANSLATION on the desk.
- Only speech channels feed it: preacher, pulpit, readers, host and the handheld for testimonies. No band, no playback music, no ambience mics, no reverb returns.
- The console's input meter moves when the preacher speaks and stays quiet during the band's soundcheck.
- The operator's computer runs on mains power, is set not to sleep, and has its speakers muted so the listener page or AI voice never plays into the room.
- The stream mix and the translation send are each checked on headphones.
- The backup input is written down: if the interface fails, the operator switches to the encoder feed or, as a last resort, the laptop's own microphone near the front.
The details of aux sends, interfaces and levels are in our church audio setup guide for live translation.
Checklist: one link, two audiences
Both audiences use the same listener link. Put it wherever each audience is already looking.
In the room
- Stage display showing the welcome slide and its large QR code as people arrive.
- QR cards on seat backs or tables, and the short link printed in the bulletin.
- A room helper by the entrance who can show someone how to choose a language and enlarge the text.
Online
- The link in the first line of the stream description.
- A pinned chat message at the start, reposted just before the sermon.
- The caption overlay, if you use one, added to every scene used during the sermon.
- The link on the church website's live page.
Test both before the service: one volunteer joins from a pew on the church Wi-Fi and one joins from home or on mobile data. Both pick a language and confirm captions appear when the preacher tests the mic. For overlay settings and the gap between stream and captions, see church livestream translation.
What to announce, and when
| When | In the room | Online |
|---|---|---|
| 10 minutes before | Welcome slide with the QR code on every screen | Pinned chat message with the link |
| During the welcome | Host reads the short script below | Online host reposts the link |
| Just before the sermon | A one-line reminder or a slide | "Captions for the sermon start now" with the link |
| After the service | Room helper asks a few guests how it went | Online host invites feedback in chat |
A room script the host can read in about 20 seconds:
"If you'd like to follow today's message in another language, scan the QR code on the screen or on the card in front of you. Choose your language, and you can make the text bigger too. There's no app to download."
A chat message for the online host:
"Watching in another language? Open [listener link], choose your language and follow the sermon in live captions. They may run slightly ahead of the video."
Keep the spoken announcement to one language and let the welcome slide carry translated invitations. Guests who need translation are, by definition, not the ones best served by a long spoken explanation.
Failure plans: what to do when something breaks
| Problem | First check | Fallback | Who |
|---|---|---|---|
| Captions stop for everyone | Is the console's input meter moving? Check the mic pack, desk mutes and USB cable | Switch to the backup input, then resume | Operator and sound engineer |
| Overlay vanishes from the stream, phones are fine | Is the browser source in the current scene? | Cut to a scene that has it, then refresh the source | Stream producer |
| Guests in the room can't load the listener page | Is the church Wi-Fi overloaded? | Guests switch to mobile data; the helper shows them how | Room helper |
| The stream fails, the room is fine | Encoder and platform status | Share the listener link by email, website or social posts so remote viewers keep reading | Online host |
| Captions run during a song | Was the pause cue missed? | Pause now; agree a clearer cue with the worship leader | Operator |
| A name keeps coming out wrong | Is it on a slide? | Show it on screen; add it to the glossary afterwards | Operator, then glossary keeper |
| A guest asks for a missing language | Is it one of this room's languages? | Note the request and plan it for next week within the 8-language limit | Room helper |
Remember that SermonLingo needs an internet connection for the operator and for every listener. If the church connection is fragile, give the operator's computer a wired connection or its own hotspot rather than sharing guest Wi-Fi.
After the service: a five-minute wrap-up
- Pause or end the session once the benediction is over.
- Write down the listener counts per language you saw during the sermon.
- Collect issues from the room helper and the online host while they are fresh.
- On Advanced and Premium plans, export the transcript if you post sermon text for people who missed the stream, and have a bilingual reader check it before it goes public.
- Update this checklist with anything you learned, and date it.
Room helpers can practise beforehand on the demo service, which opens on any phone. When you are ready to run your own rehearsal, start with the free translation hours that come with a new account.
Questions
Can in-room guests and online viewers use the same translation link?
Yes. One SermonLingo service room serves everyone who opens its listener link, whether they sit in the pews or watch from home, and listeners are unlimited on every plan. Show the link as a QR code in the room and put the same link in the stream description and chat.
Does a hybrid service cost more to translate than an in-person service?
No. SermonLingo meters translation hours by spoken time and listener languages, not by audience size or location. A hybrid service with 50 minutes of speech in two languages uses about 1.67 translation hours (50 × 2 ÷ 60), whether 20 or 200 people follow along in the room or online.
What happens to the translation if our livestream goes down?
If the translation audio comes from the mixer rather than through the stream encoder, translated captions keep running while the operator's audio and internet connection work. Share the listener link by email, on the church website or on social channels so remote viewers can keep reading the sermon while the stream recovers.
How many volunteers does a hybrid translated service need?
A hybrid translated service usually needs four or five roles: translation operator, sound engineer, stream producer, online host and room helper. Small churches can combine some, but keep the operator free to watch the console during the sermon, and make sure someone in the room and someone online can answer guests' questions.






