Ukrainian speakers in your church: what to offer this year

Start with the service itself, because that is where the gap is widest. A Ukrainian-speaking family sitting in a German-language service hears the music, the welcome and the prayers, and loses the sermon — the twenty-five minutes the whole morning is built around. Live translation on their own phone closes that, and it needs nothing from them but a QR code on the way in: they scan, they pick Ukrainian, they listen through their own earphones, under a second behind the preacher, in a natural voice that keeps his tone and rhythm rather than a flat read-out. Captions run alongside for anyone who would rather read, which in practice is more people than you expect — older members, anyone in a noisy row, and anyone who left their earphones at home.

That is the first third of the answer. The rest of it is what happens after the sermon ends, and three years in that is where most churches are actually losing people.

Do we need headphones, an app or a second room?

No app, no second room, no receivers to hand out and collect. The code goes on a card at the door or on the slide before the sermon; the listener uses the phone already in their pocket. The one thing worth buying is a box of cheap wired earphones for the welcome desk, because the person who needs translation most is usually the person visiting for the first time, and first-time visitors do not arrive carrying earphones. We wrote up what to print on that card separately; the short version is that the languages should appear in their own script, so Українська is readable at a glance by someone who cannot yet read your German sign.

Your sound desk work is one cable: a clean feed of what goes through the main microphones, not the room mic. That is the whole setup, and it is the same whether you serve one extra language or five.

What happens after the service?

This is the part worth planning harder than the translation. A second code — on the screen as people stand up, or on the same card — opens a short screen on the phone: a prayer request, a box that says this was my first time here, a testimony, a question to put to the sermon, and the message to read. Someone who has just understood a sermon for the first time in three years will often write something, and they will write it in Ukrainian.

Every one of those lands in one follow-up list with a status against each name, so the Monday conversation is not "did anyone catch who that family was". And the reply can go back in the language they wrote in. That matters more than the translation did: a prayer request answered in Ukrainian is the point at which a visitor stops being a visitor. We have written about what has to happen before Tuesday if you want the timing.

What about the sermon during the week?

Within the hour after the service you can have a clean transcript, a summary, the full message written out, a small-group guide and drafts for the newsletter and socials — in Ukrainian as well as German, from the same recording, without anyone sitting down to translate anything by hand. For a family who is still building their German, a written Ukrainian version of Sunday's message is worth as much as the live audio was, because they can read it twice.

Two more things come out of the same recording. Someone can put a question to the sermon during the week and get an answer grounded in what was actually preached, with the passage cited, in their own language. And a teaching series can become a printed study guide or a small book in the languages you choose, which is how a church with Ukrainian-speaking members ends up with something to hand them that is not a translation of a German leaflet.

Who decides how the names and terms are translated?

Someone on your team, not the machine. Place names, your church's own vocabulary, the way you render a particular theological term, the names of your own people — those are exactly where every system slips, and a Ukrainian-speaking listener notices immediately when a village name comes out as a common noun. A glossary your team approves, carried into every translation and every draft afterwards, is the difference between a service that reads as careful and one that reads as automatic. Build it slowly: start with twenty words you say every month, add one each week when something lands wrong.

What we have actually seen

Our own church in Vienna runs four languages. Farsi and Armenian are the two we run live every Sunday, so the detail here is honest about where it comes from: it is Farsi-speaking listeners, not Ukrainian ones, that taught us most of this — what changed for them is a separate post. But the shape of the problem is the same, and so is the shape of the fix. A congregation whose newcomers arrived under pressure, who are rebuilding a life in a second language all week, do not want a special service in a side room. They want the same service as everyone else, understood.

What to try this Sunday

Pick the family you already know and ask them one question: which part of the morning do you lose? If the answer is the sermon, start there and leave the rest alone for a month. Print one card with the code and the word Українська on it, hand it to them yourself rather than putting it on a table, and ask them afterwards what was wrong with it. Then ask whether they would rather read it or hear it — they will have a clear preference, and it is not always the one you expect.

If you want to see what the whole Sunday looks like end to end, the pricing page lists what is included at each level; it is the only place we publish numbers, so it is the place to check them.