Why Vocabulary Setup Has Outsized Impact

Most caption errors are not random. They usually come from predictable sources: names, acronyms, product terms, theological language, legal wording, and organization-specific phrases. InterScribe includes two mechanisms to improve this: Event Context and Custom Vocabulary.

When teams use both, quality improves before the event starts rather than after complaints arrive.

Understand the Two Accuracy Controls

Event Context

Event context tells the engine which language environment you are in (for example: faith-based service, technical webinar, professional training). This affects how captions and translations are interpreted.

Custom Vocabulary

Vocabulary lets you define terms that should be boosted, replaced, or filtered. This is where you handle speaker names, local place names, ministry terms, medical jargon, or abbreviations.

When to Use This Guide

Use this guide when:

• You see recurring mistranscriptions of key terms.
• New speakers or topics are being introduced.
• You run recurring programs with repeat terminology.
• Accuracy matters for legal, educational, medical, or faith contexts.

Step-by-Step: Build and Apply Vocabulary

1. Gather high-risk terms before the event

Ask speakers for names, acronyms, and critical phrases at least one day before go-live. Build a simple list with canonical spelling.

2. Set Event Context in session settings

During session creation/editing, open transcription settings and choose the context that best matches your content type.

3. Open vocabulary management

In Customization → Vocabularies, create a vocabulary list for this event family.

4. Add terms by category

Add entries for:

• People and organizations.
• Product or ministry names.
• Acronyms and abbreviations.
• Technical vocabulary.

5. Use replacement rules where needed

For known mishears, define replacement terms so the output normalizes to the expected wording.

6. Use block rules for problematic words

If your governance requires filtering certain terms, set block rules accordingly.

7. Attach vocabulary to the actual session

Vocabulary does nothing unless attached to the session. Confirm assignment before the event starts.

8. Run a live dry test with real speech

Speak through names and terms at normal pace. Validate caption output in at least two attendee languages.

9. Correct in real time when necessary

If a reviewer sees a critical mistake, use live correction so updates propagate to translated outputs.

10. Version your vocabulary after each event

Capture misses and improve the shared list. Reuse across recurring sessions instead of starting from zero.

Concrete Accuracy Workflow for Teams

A reliable flow looks like this:

1. Pre-event: context + vocabulary load.
2. Live: reviewer monitoring with correction authority.
3. Post-event: error review and vocabulary revision.

This turns quality from a one-time setting into a managed process.

Accuracy Checklist Before Go-Live

• Context selected in session settings.
• Vocabulary attached to the correct session.
• Top 20 terms tested in rehearsal.
• Reviewer assigned for high-value sessions.
• Restart plan ready if mid-session vocabulary updates are required.

Common Mistakes

Mistake	Consequence	Better approach
Adding vocabulary but not attaching it to session	No effect during live event	Confirm assignment in session setup
Using one generic list for all events	Irrelevant substitutions and noise	Maintain domain-specific lists by event type
Skipping rehearsal pronunciation test	Surprises during live delivery	Run 5-minute term pass before doors open
Waiting for post-event fixes only	Live audience sees avoidable errors	Combine pre-event setup with live correction

Example Term Strategy

For a church conference, you may add speaker names, ministry names, recurring phrases, and scripture book references. For corporate training, include internal product names, acronyms, policy terms, and region-specific office names. The logic is the same: give the engine your domain language before the first sentence is spoken.

Operational Ownership

• Content owner: prepares terminology list.
• Event operator: applies context and attaches vocabulary.
• Live reviewer: corrects mission-critical mistakes.
• Program manager: updates persistent vocabulary library.

When these responsibilities are explicit, accuracy improves session over session rather than resetting each week.

Final Checklist Before You Publish This Process Internally

• The workflow names the exact InterScribe menu path for every critical action.
• Your team has a pre-event test session and a post-event review rhythm.
• Staff can explain fallback behavior in one sentence.
• Attendee-facing instructions are short, visible, and multilingual.
• Ownership is clear for setup, go-live monitoring, and post-event follow-up.

When these five points are true, the process is no longer theoretical. It is operational, trainable, and repeatable.