How to plan a multilingual worship service, from the welcome to the benediction

Walk through your order of service one element at a time, decide how each language group will receive it, then build a run of show, assign roles and follow up in every language.

By SermonLingo TeamUpdated 10 min read

What goes into planning a multilingual worship service?

Planning a multilingual worship service means going through the order of service one element at a time and choosing how each language group will receive it: live captions for the sermon, two-language slides for songs, readings and set prayers prepared ahead, and short announcements. Then you write a run of show, give each task an owner, and follow up with every language group.

Work in that order. Start with the people who will be in the room, design each part of the service around them, and only then choose tools. Teams that start with the software tend to caption the songs (which live AI translation does badly) and forget to explain how communion works (the moment a guest most needs to understand).

If this is your church's first attempt, pair this guide with the four-week launch playbook, which turns the plan into dated tasks.

Who are you planning for?

Before you touch the order of service, write down who you expect. For each language, note roughly how many people come, how much of the main language they follow, and whether they read their own language comfortably. A Korean grandmother who understands little English, her bilingual grandson and a visiting Brazilian couple need different things from the same hour.

Ask rather than guess. A conversation with one trusted leader from each language community will tell you more than a survey, and three questions cover most of it:

  1. Which parts of the service do people currently miss?
  2. Would people rather read captions, listen through earphones, or both?
  3. Which Bible translation and which worship songs does the community already know?

The answers shape your choices. People who prefer listening will want a language with a live AI voice: SermonLingo shows captions in 54 languages and adds a natural AI voice in 13 of them (English, Spanish, Portuguese, French, German, Italian, Korean, Mandarin Chinese, Japanese, Hindi, Vietnamese, Indonesian and Russian). If an important group reads its own language slowly, plan for a human helper alongside the captions.

How should each part of the service be translated?

Most services share the same building blocks, and each block has a method that suits it. Use this table as a starting point and adjust it to your tradition.

Match the method to the moment
Service elementBest methodPrepare ahead
Welcome and call to worshipLive captions on phones, plus a two-language welcome slideA short scripted welcome that names the languages on offer
Congregational songsLyrics on slides in two languages, with live translation pausedPublished song translations, checked by a native speaker
Scripture readingsThe passage on screen from a version each group knows, with captions running for the spoken readingReferences and the version name for each language
Creeds and set prayersPrinted or projected text in each language, said togetherWording from your tradition's own published sources
Spontaneous prayerLive captionsA microphone for whoever prays
SermonLive captions, plus the AI voice for languages that have oneOutline, names and scripture references sent to reviewers
Communion or the Lord's SupperA spoken explanation plus a slide in each language on how to take partWho may take part and how, written in each language
Announcements and offeringPre-written slides in each language, with captions for the spoken partShort sentences, with dates and times in numerals
Response time and prayer ministryBilingual prayer team members from each language groupWho will pray with whom, and where they will stand

Two principles sit behind the table. Anything poetic or sacred that people say or sing together (lyrics, creeds, the words of institution at communion) should come from a translation a person has made, because live AI translation handles rhyme, meter and fixed liturgical wording poorly. Anything personal, such as praying with someone after the sermon, belongs to a person who speaks their language.

For readings, project the version each community already knows. Many Spanish-speaking congregations read the Reina-Valera 1960, and many Korean Protestant churches use the New Korean Revised Version (개역개정), but ask your own people before you build slides. For songs, look for official translations first (many widely sung worship songs have published versions in other languages), and check that your song license covers what you project.

A sample run of show you can adapt

A run of show is your order of service with extra columns: what happens, how each language group follows it, and what the translation operator does. Here is an example for an English-speaking service of about 75 minutes with Spanish and Korean listeners.

Example: English service with Spanish and Korean listeners
TimeElementHow guests followOperator
10:15Doors open and walk-inWelcome slide with the join QR code; greeters help with phonesRoom open, speaker language English, listener languages Spanish and Korean
10:30Welcome and call to worship (3 min)Captions and AI voice on phonesGo live
10:33Worship set (18 min)English and Spanish lyric slides; Korean lyric sheetPause
10:51Scripture reading (3 min)English and Spanish on screen, Korean on the sheet, captions on phonesResume
10:54Pastoral prayer (3 min)Captions and AI voiceStay live
10:57Sermon (35 min)Captions and AI voiceStay live and watch listener counts per language
11:32Response song (5 min)Lyric slides and sheetPause
11:37Communion explanation, announcements and offering (8 min)Captions, plus slides in each languageResume for speaking; pause for offering music
11:45Benediction (1 min)Captions, with the blessing on screen in each languageStay live, then end the session

Notice the printed sheet. Slides hold two languages comfortably, but a third usually needs paper or phones. Decide in advance which language joins the main one on screen (normally the largest group) and make the sheet for everyone else.

Now add up the speaking time: welcome 3 minutes, reading 3, prayer 3, sermon 35, roughly 5 minutes of talking in the communion and announcement block, and the benediction 1. That comes to 50 minutes. SermonLingo counts translation hours only while someone is speaking, so the songs and offering music use nothing.

Fifty minutes in two listener languages is 100 minutes, or about 1.67 translation hours. On Pay As You Go ($5 per hour per language) that is about $8.33 a service, or roughly $33 for four Sundays.

The AI voice and a stage display for the projector come with the Standard plan ($99 a month with 25 hours included), which would cover this month with plenty to spare. The pricing page lists every plan.

Who does what on the day?

A multilingual service needs a few more hands than an ordinary Sunday, but not many. For a service like the one above, plan for these roles:

  • Service host: owns the run of show, welcomes each language group by name and cues the pauses.
  • Translation operator: runs the SermonLingo console, goes live, pauses for music and watches how many people are listening in each language.
  • Sound technician: sends a clean feed of the speaking microphones to the translation computer and keeps the band out of it. The church audio setup guide covers the wiring.
  • Slide operator: runs the two-language lyrics, readings and announcement slides, and knows exactly when the screen changes.
  • Language hosts: one bilingual member per language who greets, helps with phones, explains communion and the offering in person, and gathers feedback afterwards.
  • Reviewer: a bilingual listener who follows the captions and writes down anything that changed the meaning.

In a small church one person can host and run slides, and the operator can sit at the sound desk. The language hosts are the role not to cut. They are what turns a translated service into a welcoming one.

How do you tell each language group what to expect?

People relax when they know what will happen. Before the service, tell each language group three things in their own language: which service has translation, how they will follow it, and who will help them.

Ask a fluent member to write or check every message. A machine-translated invitation reads like an afterthought, and the first message is where trust starts. Send it through the channels each community already uses, whether that is a group chat, a social media page in their language or a word after a home group. Language hosts should also open the SermonLingo demo service on their own phones beforehand, so they can show others where to tap.

On the day, the host's welcome sets the tone. Here is wording you can adapt and have translated for the welcome slide:

Welcome, everyone. If you'd like to follow today's service in Spanish or Korean, scan the code on the screen with your phone camera and choose your language. You don't need an app. The translation is produced live by AI, so names and some phrases may come out imperfectly. Songs and Bible readings are on the screen and on the printed sheet, and our language hosts in yellow lanyards are glad to help.

Being honest about AI's limits up front pays off. When a name comes out wrong in the captions, people who were warned shrug and keep reading. For the announcements themselves, see how to write announcements that translate cleanly.

What should the preacher and readers prepare?

The person preaching has more influence on translation quality than any setting. A few habits help every listener, whether they read captions, listen to the AI voice or follow in the original language:

  • Finish sentences. Captions arrive phrase by phrase, usually a second or two behind the speaker, and half-finished thoughts translate badly.
  • Announce the book, chapter and verse before reading, and read from the version on the slides.
  • Explain idioms and local references instead of leaning on them. A sports idiom can come out word for word in Korean and mean nothing at all.
  • Write unusual names in your notes so reviewers and slide makers can prepare them.

Send the outline, names and references to the reviewers and slide team by midweek. The operator can add those names and ministry terms to the SermonLingo glossary, and paste the outline into Sermon notes, to help the captions handle them. Readers should practice their passage aloud once at the microphone, because a rushed reading is hard to caption and harder to follow.

How do you follow up after the service?

Follow-up is where a multilingual service starts becoming a multilingual church. Within a week, do four things:

  1. Ask each language group how it went. Language hosts can ask three questions in person: Could you follow the sermon? What was confusing? What should we change?
  2. Check the numbers you have. The operator console shows listener counts per language, which tells you whether each group actually used the translation.
  3. Review the error notes. Separate errors that changed the meaning from wording that was merely awkward, then fix the causes: a missing glossary term, a hard-to-hear microphone, a reading that went too fast. On Advanced and Premium plans, transcripts in every language make this easier, and the translation quality checklist has a full review routine.
  4. Connect people, not just captions. Invite newcomers to a meal, a small group or a newcomers' lunch where someone speaks their language.

Then update the run of show with what really happened, not what you planned. The next service starts from a better draft.

Questions

Should song lyrics be translated live in a multilingual worship service?

Song lyrics in a multilingual worship service are better prepared ahead than translated live. Live AI translation handles rhyme, rhythm and poetic language poorly, and a literal rendering is rarely singable. Project published translations of your songs in two languages, have a native speaker check them, and pause the live translation while the band plays.

How many languages can one multilingual worship service include?

A SermonLingo service can include up to 8 listener languages, with each guest choosing their own on their phone. The practical limit is usually preparation rather than software: every language needs someone to greet, help and review, and slides get crowded beyond two languages, so additional languages often rely on phones and printed sheets.

Who should be on the planning team for a multilingual worship service?

A multilingual worship service planning team works best with the pastor or worship leader who owns the order of service, one trusted leader from each language community, the person who will run translation, and someone from the sound team. The language leaders matter most, because they know which parts of the service their people currently miss.

Does a long worship set increase translation costs?

A long worship set doesn't add to SermonLingo translation costs, because translation hours are counted only while someone is speaking. Songs, instrumental music and silence aren't counted. A service with 50 minutes of speech in two listener languages uses about 1.67 translation hours whether the band plays for ten minutes or forty.

All articles