Unified Global Onboarding: One Script → Multilingual Training Videos + Audio Dubs (StoryTool Workflow)

What you’ll build (the 4-asset “Global Onboarding Pack”)

For each module (5–8 minutes recommended):

1. MASTER_VIDEO_SUB.mp4 (video with subtitles)
2. MASTER_VIDEO_NOSUB.mp4 (clean master)
3. CAPTIONS_EN.srt (and other languages: CAPTIONS_ES.srt, CAPTIONS_DE.srt…)
4. DUB_AUDIO_[LANG].mp3/wav (audio-only tracks per language)

Step 1 — Pick 6–10 onboarding modules (don’t make one giant video)

A high-conversion module list:

1. Company + culture (what “good” looks like)
2. Tools & accounts (access + security basics)
3. Communication rules (async/sync, channels, response time)
4. Core SOP #1 (most frequent daily workflow)
5. Core SOP #2 (handoffs + escalation)
6. QA checklist (definition of done)
7. Compliance basics (do/don’t + reporting)
8. Role-specific playbook (optional)
9. Incident workflow (optional)
10. 30/60/90 day expectations (optional)

Rule: 1 module = 1 job-to-be-done.

Step 2 — Write the “Canonical Script” (copy/paste template)

Create: ONBOARDING_SCRIPT_v1_0.txt

Canonical Script Template (5–8 minutes)

Step 3 — Generate the master training video in StoryTool (Edu/Info)

StoryTool creation process:

1. Paste your text
2. Choose visual style and voice
3. Select an Agent and aspect ratio
4. Add intro, outro and background music (optional)
5. Generate title and description if needed
6. Click Generate

Recommended settings:

• Agent: Edu/Info Agent (for clear step-by-step visuals)
• Ratio: 16:9 for LMS/desktop onboarding
• Exports: Video with subtitles, SRT file, and No-sub video

Step 4 — Create the subtitle packs (SRT per language)

For each target language, produce: CAPTIONS_[LANG].srt

A minimum set for global companies might include: EN + ES + PT-BR + FR + DE + AR + HI + ID + VI (pick based on your workforce).

Keep a glossary: Product names, internal tools, team names, and policies should not be translated unless required by local convention.

Step 5 — Generate Audio Dub inside StoryTool (SRT → Dub)

This is the fastest way to standardize voice across regions without recording.

Audio Dub workflow (StoryTool)

1. Open Page Gen Audio
2. Import the SRT file in the target language (e.g., CAPTIONS_ES.srt)
3. Choose language + voice in the UI
4. Choose TTS model:
   • StoryVoice (TTS): select language + voice explicitly
   • OpenAI model: StoryTool will auto-detect the language
5. Click Generate
6. Download the completed Audio Dub in the target language

Output: DUB_AUDIO_[LANG] (ready for LMS / video platforms that support alternate audio)

Step 6 — Deliver in your training platform (3 hosting patterns)

Pattern A — One video + multiple audio tracks (best if you use YouTube)

If your organization hosts training videos on YouTube (private/unlisted or internal workflows):

• Upload the master video once
• Add multi-language audio tracks so viewers switch audio in the player

Pattern B — One video per language (best for strict compliance)

• Duplicate the video entry in your LMS for each language
• Pair each language video with its own captions (SRT) and audio dub (if needed)

Pattern C — One master video + downloadable audio dubs (fastest LMS setup)

• Keep one master video with subtitles
• Provide audio dub files as attachments for each language

Step 7 — Accessibility baseline (do it by default)

For prerecorded training video, captions are a practical minimum standard. Always keep:

• in-video subtitles for day-one consumption
• SRT files for accessibility and future edits

Step 8 — Versioning so updates never break global teams

Use a clear naming convention:

• HR_Onboarding_Module04_SOP1_v1_0_EN_VIDEO_SUB.mp4
• HR_Onboarding_Module04_SOP1_v1_0_EN_VIDEO_NOSUB.mp4
• HR_Onboarding_Module04_SOP1_v1_0_ES_CAPTIONS.srt
• HR_Onboarding_Module04_SOP1_v1_0_ES_DUB_AUDIO.mp3

Versioning Rules:

• v1.0: first publish
• v1.1: small corrections
• v2.0: major process change

Change Note Template:

• Changed on: [Date]
• Version: [e.g., v1.1]
• What changed: [Summary]
• Effective date: [Date]
• Owner: [Team/Person]

Edit text → regenerate → replace → log.

Step 9 — QA checklist (copy/paste)

Before publishing any language pack:

• Terminology matches the company glossary
• Numbers, dates, and tool names are correct
• Captions are readable (no long walls of text)
• Dub timing sounds natural (no rushed segments)
• The “Definition of done” is unambiguous
• The owner/team contact is correct

Step 10 — Metrics that prove onboarding works

Track these metrics per module:

• Completion rate
• Quiz pass rate (3–5 questions)
• Time-to-competency for new hires
• Error rate / support tickets related to the SOP
• Repeat plays (signals it’s being used as a job aid)

Trial → Paid (fast pilot)

The StoryTool trial is free for up to 3,000 characters / account / month.

Pilot plan:

1. Convert one high-impact SOP module into video + SRT.
2. Create one target-language SRT + audio dub via Gen Audio.
3. Roll it out to one region/team for 7–14 days.
4. Upgrade only when completion rates and fewer mistakes prove ROI.