Multi-campus church translation: one room or many, central or local operators
How to bring live translation to a church with several campuses: decide how many rooms you need, where the audio comes from, who runs it, and how to keep every campus set up the same way.

How do you translate a multi-campus church?
To translate a multi-campus church, first count how many live speakers you have at the same time. If one preacher is shown on video to every campus, one SermonLingo room can serve them all with a single audio feed. If campuses have their own live speakers, each needs its own room, and running several rooms at once is a Premium feature.
Everything else follows from that one count: how many rooms you need, where the audio comes from, who operates them and what the hours cost.
One room or several: how does each campus get the sermon?
Start from how the sermon reaches each campus, because that decides the number of rooms.
| How campuses get the sermon | Rooms | Audio source |
|---|---|---|
| One preacher, video to every campus | One room, joined by guests at every campus | The preaching campus's mixer feed into a computer, or an encoder sending RTMP (Advanced and Premium) |
| Live preaching at each campus at the same time | One room per campus, running together (Premium) | Each campus's own mixer feed or microphone |
| Different speaker languages at different campuses | One room per campus, each with its own speaker language | Each campus's own audio |
Listeners are unlimited, so adding a campus to a shared room adds no translation hours. What adds hours is speech multiplied by listener languages, room by room. If your campuses' services never overlap, ask in a guided walkthrough whether one room at a time covers you.
Where should the audio come from, and what about video delay?
For the video model, take the audio from the same place your video already takes it. That is usually the preaching campus's mixer, through a USB audio interface into a computer, or an encoder (OBS or vMix) sending RTMP, which is listed with the Advanced and Premium plans. The console shows step-by-step encoder settings.
Then test at a remote campus, because of delay. Captions usually arrive a second or two after the words are spoken at the source. Your video may reach a remote campus's screen later than that, depending on how it travels, so a guest watching the screen could see a caption just before the preacher says the words.
The stream's delay belongs to your video path, so measure it: have someone at the remote campus note whether the captions lead the screen. Test with real guests before deciding it is a problem, since many people read captions beside the screen rather than instead of it. If it bothers them, the lever is the video path to that campus, which your video team controls. Online viewers are a separate audience, covered in church livestream translation.
One more catch in the video model: each campus pastor's live welcome and announcements happen in the room, not in the shared feed. Write those as slides in each language, or ask a bilingual volunteer to repeat them from the platform. Church announcements translation has wording that works.
Who runs it: a central operator, local operators or both?
| Model | Strengths | Risks |
|---|---|---|
| Central operator: one trained person or team at the main campus runs every room | The same quality everywhere, fewer people to train, one person who knows the glossary | Nobody in the campus room to help a confused guest or fix a local microphone |
| Local operators: each campus trains its own volunteers | Problems fixed by someone in the room, and real local ownership | Uneven habits, more people to train, turnover at every campus |
| Hybrid: a central owner sets standards, and a trained lead at each campus handles Sunday tasks | Consistent standards with help on the spot | Roles must be written down, or each side assumes the other is handling it |
A central operator makes sense only when the audio reaches SermonLingo without a laptop microphone in the campus room, for example through an encoder feed. Before you decide who gets console access, ask in a guided walkthrough how several people can work on one account.
The console shows listener counts per language, not per campus, so a shared room cannot tell you where the Spanish listeners are sitting. If you need that, ask each campus's greeter for a quick tally.
How do you keep every campus set up the same way?
Consistency is where multi-campus translation is usually won or lost. A volunteer who moves from one campus to another should find the same setup. Standardize these six things:
- One runbook. A single page, laid out the same at every campus, with the ten-minute pre-service test, the pause points and who to call.
- One glossary. Campus names, pastors' names, ministry names and building names, owned by one person and reviewed monthly. Every plan includes a glossary for names and ministry vocabulary, so keep the master list there and share an export with each campus.
- One welcome slide and one sign design, with the campus name added wherever rooms differ, so a guest can tell which service they are joining. A line such as "Northside Campus: scan to follow today's message in your language" does the job.
- One kit list. Laptop, audio interface, cables, hotspot, printed QR sign and spare batteries.
- One test script. The same three sentences read aloud at every campus before service: a verse reference, a name and an announcement. Post the results in a shared channel.
- One escalation path. Campus lead, then the central owner, then SermonLingo support (email on Pay As You Go, priority support on Standard and above).
Premium also lists custom branding and an onboarding call. If you take Premium, use the call to walk through your campus list and audio paths together.
How should you roll it out across campuses?
- Pilot at one campus for four weeks. Choose the campus with the clearest language need and your strongest volunteer.
- Write the runbook from what actually went wrong, not from what you expected to go wrong.
- Add campuses one at a time, with the pilot campus's lead beside the new lead on the first Sunday.
- Review listener counts per language after a month, and put your effort where people are reading.
Training and the one-page runbook are covered in our guide to training church translation volunteers. When a second language group asks for its own room, a guided walkthrough is the place to confirm how rooms and access fit your campuses.
Questions
Do we need a separate room for every campus?
Not if every campus shows the same live preacher by video. One room has unlimited listeners, so guests at every campus can join it. Campuses with their own live speakers at the same time need separate rooms, and running several rooms at once is listed as a Premium feature.
Can campuses share one QR code?
Campuses that join the same room can share one QR code and link, which simplifies printing. Campuses with separate rooms need separate codes, and each printed sign should show the campus name so a guest knows which service they are joining.
Who should operate translation at each campus?
A hybrid usually works best: one central owner sets the glossary, runbook and standards, while each campus has a trained lead for setup, signs and guest questions. Where audio arrives through an encoder feed, ask in a guided walkthrough whether the console can be run from the main campus.
Does adding a campus increase translation hours?
Adding listeners costs nothing, because every plan has unlimited listeners. Hours depend on speech multiplied by listener languages in each room. A campus that joins an existing room adds none, while a campus with its own live speaker and its own room adds that room's speech times its languages.






