InterScribe · Practical event resources
Church language rehearsal pack
Prepare a service role card, trace the audio path, review theological terms and practise a clear guest welcome before Sunday.
Worksheet revision: October 12, 2026 · Free to use without an account
1. Agree the role before assigning it
Bilingual ability alone does not establish interpreting competence. Agree each volunteer’s task, willingness, preparation, relief and limits with a person able to assess the relevant language work. A welcoming role must not quietly expand into a confidential pastoral or specialist conversation.
| Role | Owns this decision | Name / relief / escalation |
|---|---|---|
| Service coordinator | Final service order, changes and permission to pause | |
| Audio operator | All intended microphones reach the selected source | |
| Interpreter / language reviewer | Meaning, terminology questions and agreed handover | |
| Welcome volunteer | Joining instructions, listening check and help route |
- 1 · Spoken sourceLectern, handheld and remote speaker microphones
- 2 · Selected feedDesk or device sends the intended speech to the session
- 3 · Language deliveryCaption or interpreter route receives the correct source
- 4 · Guest deviceA second person checks the chosen listening or reading route
2. Rehearse meaning as well as sound
Ask the speaker for names, the sermon outline, the passage and the named Bible translation. A theological term’s intended meaning belongs in its passage and tradition. Keep the pastoral explanation and qualified language review separate from software vocabulary controls; configuration is not doctrinal authority or model training.
| Term / passage / version | Intended meaning and proposed wording | Reviewer / status / unresolved question |
|---|---|---|
For sound rehearsal, speak a distinctive phrase into each planned microphone. Have the language worker confirm the floor they hear and a separate person confirm the guest output. Rehearse an audience question and a handover, not only the opening welcome.
3. Use a guest script that matches access
“Which language or way of following the service would help you? We have [arranged support] for [segments]. I can show you the joining route and check it with you. If it stops working, [person / help point] can help.”
Fill those brackets with confirmed arrangements. Offer a typed route beside a QR code. For an InterScribe web session requiring an access code, the direct link or QR does not prompt for it: use the join page or portal with both event code and access code. In the app the access code is called a Pin Code. A partnership pass requirement additionally needs sign-in and a valid pass. Do not publish a restricted access code on a public poster.
4. Decide how to pause and follow up
If the source is missing, a term is uncertain or the assignment exceeds someone’s competence, use the agreed clarification route. Do not ask a volunteer to guess to preserve the schedule. A suitable response is: “We want to communicate this carefully. Let us arrange the right support before continuing.”
- Confirm the coordinator can receive a problem report during the service.
- Agree the fallback with the people who need support; do not assume another format meets the same need.
- Afterward, record one concrete gap, its owner and when the correction will be rehearsed.