Guide
Prepare a sermon translation glossary
Build a term sheet with the speaker and a competent language reviewer. Record the sentence, intended meaning, proposed wording and review decision, then rehearse it.
Use this guide and its free kit without an account. PewTranslate accounts are closed as of October 25, 2026; the kit supplies no approved translations or theological definitions.
Last reviewed
Unzip the download, then open templates/term-register.csv in your spreadsheet. Start with one term; keep your working copy private.
Start with one unfinished record
This fictional row from the kit shows what to record before a language reviewer approves any wording.
| Field | Unfinished example |
|---|---|
| Term and sentence | River Hall — The meeting is in River Hall. |
| Intended meaning | A fictional room name, not a river. |
| Review | PENDING. Target language is undecided; approved wording stays empty. |
| Next human action | Confirm the language and location with the local team, then ask a competent language reviewer for wording. |
1. Choose the passage and language pair
Use the current outline or a short passage the speaker expects to deliver. Confirm the source language, target language, and relevant language variety with the people who need support. Ask what material the reviewer can access and when the speaker will stop changing the outline.
Human interpreting and written translation require different work. The American Translators Association explains the distinction. Share the term sheet with an interpreter before the service if interpreting is planned; do not assume a written word choice settles how a live sentence should be conveyed.
2. Select terms because they matter in this sermon
- Names and places: record the spelling, pronunciation questions, and the actual person or place meant.
- Bible references: record the intended book, chapter, verse range, and chosen source/version where a quotation is planned. A reference and the quoted text are separate things to check.
- Context-dependent terms: ask what words such as communion, grace, church, or spirit mean in the particular sentence. Let the speaker explain; let the language reviewer assess the rendering.
- Conditions and instructions: mark negatives, times, locations, and words such as if or unless when changing them would change the message.
- Idioms and wordplay: ask the speaker for the intended point. A literal rendering may need explanation; do not invent that explanation on the speaker's behalf.
These categories are prompts for review, not a prescribed Christian vocabulary. Church traditions and the immediate context may differ. No term is approved by appearing on this list.
3. Make a record that exposes missing decisions
| Field | What to record |
|---|---|
| Term and sentence | The exact source word and the surrounding sentence from the current outline. |
| Intended sense and evidence | The speaker's explanation and the location of the outline, checked reference, or other source. |
| Proposed and approved wording | Keep these separate. A machine suggestion or an unreviewed draft stays proposed. |
| Review record | Language pair, variety, reviewer role, date, and the reason for the decision. |
| State | PENDING when review is incomplete; BLOCKED when a question prevents review; APPROVED only after actual review in context. |
For example, a fictional outline says, 'Meet in River Hall after the service.' The reviewer needs to know that River Hall is a room name. A second entry that merely says 'communion' without its intended use should remain blocked. These are English teaching examples, not approved translations.
4. Separate a team glossary from a software feature
A term sheet can help a human prepare even if the chosen app has no glossary import. DeepL documents preferred source/target word pairs, while Deepgram documents keyterm hints for speech recognition. They affect different stages. Check the current provider, language, model, plan, and app integration before assuming either feature is available.
Do not describe a CSV as installed merely because it was uploaded or emailed. If a tool supports an import, check its own required format and acceptance result, then rehearse the sentence. A successful import is not proof that meaning was preserved. This guide does not claim that PewTranslate exposes glossary import or vocabulary controls.
5. Rehearse the complete sentence and keep a correction path
- Use the planned microphone or interpreting arrangement and the current text. A quiet desk test does not establish what a listener receives in the room.
- If the system exposes a source transcript, compare it with the actual speech first. Check the selected names, numbers, negations, and references.
- Have the language reviewer assess the received target sentence against the speaker's intended message. Record the observed wording, not a memory of what the tool probably said.
- Agree who can correct an error, what recipients will be told, and what alternative is available if reliable support cannot continue.
- Mark the selected sample ready only after the required checks are observed. Keep unresolved questions visible, and reopen affected rows when the outline changes.
A rehearsal result applies to the material, people, language pair, and setup checked. It does not supply an accuracy percentage for a whole service or another language. For the speaker's broader preparation, see preaching with live translation.
Keep the working copy private and the reusable template simple
A public template needs headings and fictional examples, not congregation members' names, pastoral disclosures, or recordings. Keep the service team's working register in an agreed location and share the current version with the people using it. Only retain material the team has permission and a reason to keep.
A translated transcript also may not contain the speaker cues or relevant sounds needed for captions. W3C's captions guidance describes those distinctions and the need to review automatic captions. Ask recipients whether the planned support is usable; terminology review alone does not establish accessibility.
About the free review kit
The sermon term review kit includes blank registers, eighteen review prompts and twelve fictional cases. It is original AI-assisted material under the MIT license. Its README explains the optional administrative checker, which cannot approve meaning.
Frequently asked questions
Can I reuse a sermon glossary next week?
Reuse the record as a starting point. Recheck terms whose sentence, intended sense, language variety, source/version, or reviewer decision changed. Preserve the previous decision so the team can see why wording was revised.
Should an AI-generated translation be marked approved?
It can be recorded as a proposal. Approval requires an actual competent language review of the complete sentence and intended meaning. If that review is unavailable, keep the entry pending or blocked.
Keep reading
- Tips for Preaching with Live TranslationHow to preach so live translation works well: sentence endings, Bible references, names, idioms and humour, without changing your style.
- How to Set Up Live Translation in Your ChurchA practical checklist for sound volunteers: getting clean audio into the laptop, network for listeners, QR codes, a test run, and a Sunday-morning routine.
- How to Plan a Bilingual Church ServiceFormats for a service in two languages, with their trade-offs, and practical choices for songs, Scripture readings, prayer, announcements and the sermon.
- How to Check Sermon Translation ErrorsTrace a confusing sermon sentence through audio, source transcript, translated wording, and the receiving screen. Use observable checks and a correction record.