Your first multilingual service: a four-week playbook with dated checklists
A dated plan for launching translation at your church: choose languages, recruit and train, rehearse twice, announce in every language, run the first Sunday and fix what you learn the week after.

How do you launch a first multilingual service without chaos?
Give your first multilingual service four weeks of lead time. In week one, choose the languages and a coordinator. In week two, connect the audio and train volunteers. In week three, rehearse with the real preacher and announce the launch in every language. In the final week, rehearse again under service conditions. Afterwards, gather feedback and fix the three biggest problems before the next Sunday.
The timeline below counts back from launch Sunday. If your main service meets on Saturday evening or a weekday, shift everything by the same amount. Four weeks is not a rule, and a small church with a ready volunteer can compress it to two. What matters is the sequence: people and audio first, announcements only once a rehearsal has worked.
This playbook is about getting to the first Sunday. For designing the service itself (which parts get captions, how songs and readings are handled), see how to plan a multilingual worship service.
Four weeks out: decide and assign
This week is about decisions, not equipment. Hold one meeting with the pastor, a leader from each language community, someone from the sound team and the person who will coordinate translation. Leave with these settled:
- A coordinator. One person owns this checklist and makes the final calls.
- The launch service. Pick one service, not all of them: the one that people who need translation already attend.
- The languages. Choose one to three, based on people who actually come rather than languages you hope to reach someday. SermonLingo allows up to 8 listener languages per service, but every language you add needs its own greeter and reviewer.
- Voice or captions. Check which of your languages have a live AI voice (13 do) and which will be captions only, and plan help for anyone who struggles to read on a phone.
- The audio path. A feed from the mixer into a computer gives the cleanest result; a laptop or phone microphone near the pulpit can work in a small room; an encoder sending RTMP from OBS or vMix is available on the Advanced plan and above.
- An account. Create an account; it comes with 4 free translation hours and needs no card. If you'd like someone to show you around first, book a guided walkthrough.
Put the launch date in the church calendar now, but don't announce it until after the first rehearsal.
Three weeks out: recruit, connect and train
- Recruit the team. Two operators (a lead and a backup), one guest helper per language and one bilingual reviewer per language. Ask language leaders for names; a personal request works better than a bulletin notice.
- Connect the audio. Run a feed from the sound desk to the translation computer, select it as the audio input in the SermonLingo console, and play a recorded sermon through the desk to check levels. The church audio setup guide walks through cabling and levels.
- Train everyone together. One 45-minute session with the real equipment. The volunteer training guide has an agenda you can use as written.
- Start a names list. Pastors' names, the church's name, ministry names, local places and the books of the Bible you'll preach from soon. These go into the SermonLingo glossary on any plan; give the list to the preacher as well, so they can say tricky names clearly and spell them on slides.
- Prepare print. Draft the welcome slide, seat cards and signs with the QR code, but hold the print run until the link has been tested.
Two weeks out: rehearse once, then announce
Rehearse before you announce. If the first rehearsal exposes a problem with audio or volunteers, you still have time to fix it quietly.
- Rehearsal one (midweek, about 30 minutes in the room). The actual preacher speaks for 15 minutes at the pulpit microphone, ideally from a draft with real names and references. Reviewers follow on their own phones in each language and note anything that changed the meaning. Operators practice going live, pausing and resuming.
- Fix the top problems. They are usually audio level, a name the captions keep mangling or a preacher who speaks very fast.
- Announce the launch. From the pulpit, in the bulletin, on social media and, above all, through each language community's own channels, in their language, checked by a fluent speaker.
Announcement wording you can adapt:
Starting Sunday [date], our 10:30 service will offer live translation in Spanish and Portuguese. Bring your phone, scan the code on the screen or on your seat, and choose your language. There's nothing to download. If you'd rather listen than read, bring earphones. Invite someone who has been waiting for this.
Drop the earphones line if you are on Pay As You Go, which covers captions; the AI voice starts with the Standard plan.
The final week: rehearse under real conditions
- Monday: confirm every volunteer by name and send them the one-page runbook.
- Wednesday: print and place the QR cards and signs, then scan each design from the back row with an iPhone and an Android phone. Our guide to QR code placement and print size explains what to check.
- Thursday: the preacher sends the outline, names and references to reviewers and the slide team.
- Saturday, rehearsal two (about 45 minutes): run the real order of service at speed, including the welcome, one song (practice the pause), the reading, 20 minutes of sermon and the announcements. Test guests' phones on the church Wi-Fi and on mobile data. Rehearse one failure on purpose: unplug the mixer feed and switch the console to a laptop microphone.
- Saturday evening: send each language group a short reminder with the time and how to join.
Launch Sunday: a minute-by-minute plan
- 90 minutes before: the coordinator and operator arrive. Power up the translation computer, connect it to the network, open the service room and confirm the speaker language and listener languages.
- 60 minutes before: sound check with the real microphones. Watch the input level in the console while the preacher says a few sentences.
- 45 minutes before: join from a test phone in each language, and leave one phone running at the back of the room.
- 30 minutes before: a five-minute team huddle covering who helps whom, when to pause and who to tell if something breaks.
- 20 minutes before: the welcome slide with the QR code goes on screen, and guest helpers take their places at the doors and near the seats where language groups gather.
- During the service: go live for the welcome, pause for music, keep an eye on listener counts per language, and keep a paper log of anything odd with the time it happened.
- Straight after: guest helpers ask three questions in each language: Could you follow? What was hard? Will you come back?
Keep a fallback ready: printed sermon outlines in each language and a bilingual helper who can sit beside guests if translation stops. A sentence for the host, just in case: "Our translation has paused for a moment; we're fixing it, and the outline on your seat follows the sermon."
The week after: debrief and decide
- Debrief within three days, for 30 minutes, while memories are fresh. Ask the team what worked, what broke and what confused guests.
- Sort the reviewers' notes into errors that changed the meaning and wording that was merely awkward, and fix causes rather than symptoms.
- Read the listener counts for each language. A language with almost no listeners may need better invitations, or may not be needed yet.
- Choose three fixes and give each one an owner and a date.
- Decide the rhythm: weekly, every other week or monthly. Weekly translation is the easiest for guests to rely on.
- Thank volunteers by name, in public.
What will the first month cost?
SermonLingo counts translation hours per listener language, and only while someone is speaking, so the first month fits on the back of an envelope. Take a launch with two listener languages:
- Rehearsal one: 15 minutes of speaking × 2 languages = 30 minutes, or 0.5 hours.
- Rehearsal two: 30 minutes of speaking × 2 languages = 60 minutes, or 1 hour.
- Launch Sunday: 45 minutes of speaking × 2 languages = 90 minutes, or 1.5 hours.
That is 3 hours in total, inside the 4 free hours every new account receives, with one hour left toward the second Sunday. After that, each similar Sunday uses 1.5 hours: $7.50 on Pay As You Go, or $30 for four Sundays.
If you want the AI voice or a stage display on the projector, Standard costs $99 a month with 25 hours included. The pricing page compares all four plans.
Questions
How many languages should a first multilingual service include?
A first multilingual service should usually start with one or two languages that people in your church already speak and have asked for. SermonLingo can carry up to 8 listener languages in one service, but each added language needs a guest helper, a reviewer and invitations written in that language, so grow once the first ones run smoothly.
What should happen if translation fails during the first multilingual service?
If translation fails during a first multilingual service, the operator checks the audio input first and switches to a backup microphone if the mixer feed has dropped. Meanwhile the host says one calm sentence about the pause, guests use the printed sermon outline in their language, and bilingual helpers sit with anyone who is lost.
Why rehearse twice before launching a multilingual service?
Two rehearsals before a multilingual service launch test different things. The first, two weeks out, checks audio, names and the preacher's pace while there is still time to fix them. The second, the day before, runs the real order of service with volunteers in position, including pausing for songs and recovering from a deliberate failure.
When should a church announce its first multilingual service?
A church should announce its first multilingual service about two weeks ahead, right after a rehearsal has gone well, then remind people the week before and the evening before. Announce in each language through the community's own channels, with wording checked by a fluent speaker. Personal invitations from language leaders carry more weight than a bulletin line.






