Translation tools shaped by real worship-service failures serve churches better because each feature answers a moment that actually went wrong in a room full of people, not a scenario someone imagined at a desk. That's the heart of church translation built from experience. You watch where the message breaks down on a Sunday, you write it down, and you let those notes decide what gets built next. A lab can check whether a sentence translates correctly. Only a live service shows you the family who slipped out halfway through, the visiting preacher's name turned into nonsense, or the older member who never touched the QR code. Jesus Speaks grew out of exactly that kind of log. A missionary church planter kept facing congregations from many nations with no affordable interpreter and no budget for booths. What came out of those services now translates one speaker into 87+ languages at once, with listeners joining from any browser.
What is a "field log," and why does it belong in church tech?
A field log is simply a running record of what went wrong, and what almost went wrong, during real ministry. Missionaries keep them without calling them that: a note in a journal after a service, a voice memo on the drive home, a list of words the interpreter stumbled over.
The value isn't the notebook itself. It's the discipline of treating every rough Sunday as information instead of embarrassment. When the same problem shows up three weeks running, it stops being bad luck and becomes a design requirement.
Paul wrote that he had "become all things to all people, that by all means I might save some" (1 Corinthians 9:22). That kind of adaptation only happens when you pay close attention to the people in front of you. A field log is attention, written down.
How do tools designed in isolation fall short on a Sunday?
They fall short because they're built around assumptions a worship service quietly breaks. A tool designed for business meetings or travel usually expects:
- One clear speaker, close to the microphone, in a quiet room
- Listeners who will happily download and set up an app
- A strong, stable internet connection
- That a shortened summary is good enough when things fall behind
- Ordinary vocabulary, with few unusual names
Now picture a church plant meeting in a rented hall. The preacher moves around. There's singing, a prayer, a Scripture reading, a child crying near the back. The connection is a phone's data plan. Half the room is newcomers who don't know anyone yet, and the sermon is full of biblical names and the name of a town the engine has never seen.
None of that is exotic in ministry. It's an ordinary week. A tool that wasn't tested against ordinary weeks will fail at exactly the moments that matter most.
Which real-service failures shaped Jesus Speaks?
The features in Jesus Speaks trace back to specific kinds of breakdowns the missionary who built it kept running into. Here are four, briefly, since several are explored in more depth elsewhere on this blog.
The room with many nations and no budget
Interpreters were costly and hard to find, and booths with racks of receivers belonged to budgets a church plant never sees. So the starting point became one phone and no hardware. Listeners scan a QR code or open a link in any browser, pick their language, and read live captions while hearing a natural spoken voice.
The sentence that went missing
When translation lags, many systems skip ahead. On the field, a skipped sentence can be the one that carried the gospel. So when playback falls behind, it speeds up rather than dropping words.
The name that came out wrong
Generic engines mangle proper names, places and ministry terms. Uploading sermon notes, glossaries and name lists gives the system the context to get them right.
The member who couldn't follow on a phone
Not everyone will use a phone. That's why the audio can also go out through the soundboard or to wireless listening receivers a church may already own, and why there's a side-by-side captions view for the hard of hearing.
Why does real-world translation testing look different in a worship service?
Real world translation testing in church has to include the parts of a service that a lab never simulates. A clean sentence read into a microphone tells you very little about Sunday.
If you're evaluating any tool, test it under the conditions you actually have:
- Your real room. The same mic, the same distance, the same echo off the same walls.
- Your real connection. If you'll run on cell data on Sunday, test on cell data, not the office Wi-Fi.
- Your real preacher. Accent, pace, the stories they tell, the asides they toss in.
- Your real vocabulary. Read a passage full of names, like a genealogy or a list of Paul's greetings in Romans 16.
- Your real listeners. Ask one person from each language group to follow along and tell you plainly what they missed.
That last test matters more than any accuracy score. The person in the third row is the measure, not the demo.
How can your church keep its own sermon translation field notes?
You can start keeping sermon translation field notes this Sunday with nothing more than a shared document and one person who's willing to write things down. Keep each entry short and specific.
What to record after each service
- Which languages were used, and roughly how many people listened in each
- Any word, name or place that came out wrong, written exactly as it should be
- Moments where listeners looked lost or stopped following
- Technical hiccups: audio dropouts, connection trouble, volume problems
- Anyone who wanted to listen but couldn't get connected
- One thing that went well, so you don't lose it
What to do with the notes
Once a month, read the log back. Recurring name errors go straight into your glossary or name list. Recurring connection issues might mean moving the phone or adjusting where the audio is sent. And recurring stories of people who couldn't connect point you toward a different way of delivering the audio for them.
Those are the practical translation lessons ministry teams tend to forget by Tuesday. The log keeps them.
Is the language need in our churches big enough to justify this much care?
For many congregations, yes, and the numbers in some countries make it hard to ignore. In the United States, about 74.1 million people age 5 and older, or 23%, spoke a language other than English at home in 2024, and only 60.9% of them said they spoke English "very well" (U.S. Census Bureau ACS 2024, via USAFacts).
Congregations are already adjusting. The share of U.S. congregations with Spanish or bilingual services rose from 6.3% in 2006-07 to 10.0% in 2018-19 (National Congregations Study, Duke University). And roughly one-third of U.S. worship attendees now go to a congregation where they aren't part of the racial or ethnic majority (Pew Research Center, Feb. 26, 2025).
If you serve outside the U.S., your national statistics office will have its own picture, and your field log will tell you more than any census about your own room.
Either way, the vision is bigger than a statistic: a multitude "from every nation, tribe, people and language" standing before the throne (Revelation 7:9).
How do you try a field-built tool without risking a Sunday?
You try it where a stumble costs little: a midweek prayer meeting, a small group, or a rehearsal with a few bilingual friends listening on their phones. That gives you real conditions without the weight of the main service.
A few things make that easier with Jesus Speaks:
- A small, clear cost. Credits are prepaid, 1 credit = €1, and drawn down per language per minute actually heard. A 1-hour service in 3 languages on the standard voice comes to about 10.8 credits. Listeners are always free and unlimited.
- Room to grow. You can start from a single phone, then move to the soundboard or receivers later. The features page lays out all four ways to run it.
- Help for tight budgets. Scholarships and subsidies are available for ministries that need them.
On Pentecost, each person heard the apostles "speaking in his own language" (Acts 2:6). The goal of a field log is to move your church a little closer to that every week.
Jesus Speaks is available only to Christian ministries who share its statement of faith. Approved ministries can start with €5 of credit and run a first test at a midweek gathering, logging what they hear. Five credits covers a little under half of that 1-hour, 3-language example.