For pharma & life sciences

The claim was approved in English. Each translation is a claim of its own.

Mechanism-of-action videos, HCP education, trial participant explainers and field-force training all carry wording that was argued over in review. Octavia localizes them with drug names and indications locked and the translated script approvable before any audio exists — so each language enters your MLR process as text, where changes cost least.

  • 60+ languages
  • One upload, every format
  • Review before anything ships
60+Studio-quality languages
1Upload, every output
~4sSubtitles for a 10-hour video
100%Reviewable before export
The problem

What gets in the way

The specific reasons this content usually stays in one language.

Approved wording does not survive by default

A claim that cleared review in the source language can overstate, hedge or lose its qualifier in translation — and the translation is what that market’s regulator reads.

Affiliates send finished videos back

Local reviewers receive a dubbed asset, find a problem in the script, and the whole video returns to the agency for another round.

Trial explainers meet participants, not HCPs

Participant information must be understood by people with no medical background, in their own language, and clear ethics review in each country.

Capabilities

What Octavia does about it

The parts of the platform that matter for this work, rather than the full feature list.

Approved terms, never paraphrased

Brand and generic names, indications, dosing terms and trademarked phrasing pinned in a glossary, so each renders exactly one approved way.

Review the script, not the dub

Transcript and translation are approvable before audio is generated, so affiliate reviewers mark up text instead of returning a finished video.

Mechanism of action, explained

Scientific narration voiced per language and paced naturally rather than compressed, so it still sits with the animation it describes.

Explainers for trial participants

Participant information and consent explainers in each site language, with captions and a transcript to accompany the ethics submission.

Advisory boards and symposia

Recorded expert panels transcribed and translated with each speaker kept distinct, for medical affairs teams in other regions.

Controls for pre-launch material

Encryption, configurable retention, role-based access with SSO and no training on your content — for data that is confidential until launch.

Workflow

How it runs

Four steps from the file you already have to every language you need.

Step 01

Lock the terminology

Load approved drug names, indications and safety phrasing — ideally from the glossaries your affiliates already maintain.

Step 02

Translate and hold

Generate the translated script, then stop: nothing is voiced until it is approved.

Step 03

Route to local review

Affiliate medical, legal and regulatory reviewers approve each language as text, against the approved source.

Step 04

Produce and file

Generate audio and captions from the approved script, and file the approved translation with your review record.

Deliverables

What you get back

One upload in, every format you need to publish out.

MOA videos per language HCP education versions Trial explainer videos Approved translated scripts Captions and transcripts Field-force training
FAQ

Questions worth asking

Including the ones where the honest answer is a limitation.

Does using Octavia satisfy regulatory review?

No — and nothing should be described that way. Octavia speeds up the part before review: a translated script with locked terminology, ready to approve before any audio is made. Each language version still goes through medical, legal and regulatory review in its market, and the approved text is what you file. Octavia does not approve claims, and its output is not pre-cleared for any regulator.

How do we stop a claim changing meaning in translation?

Three layers. Lock brand names, indications, dosing terms and fixed safety phrases in the glossary so they are never paraphrased. Review the translated script line by line against the approved source before generation, paying closest attention to qualifiers — “may”, “in some patients”, “compared with placebo”. And keep fair balance and safety information in the same proportion and prominence as the source.

Can a translated video stand in for informed consent?

No. A consent explainer supports the conversation with site staff and the approved informed consent form; it replaces neither. Each language version will usually need ethics committee or IRB review alongside the written materials, and site staff must still confirm understanding with each participant. Video earns its place through consistency — every participant hears the same explanation — not by removing a step.

Can an expert speaker’s voice be carried into other languages?

Only with that person’s written consent, covering which languages, which content and for how long — a standard speaker agreement will not have contemplated it. With consent in place, voice cloning keeps a KOL or medical director recognisable across markets. Without it, assign a professional synthetic voice per language and subtitle the original. Either way, the approved script is the only thing the voice should say.

Further reading

Go deeper

Practical guides from the Octavia editorial team.

Keep the approved claim in every language.

Start with field-force training or a recorded advisory board — real volume, lighter review, and a glossary you can prove before promotional work.