How do you approve 20 language versions of one video?
Approve the master once and lock it. Then let one native reviewer per market approve their language version, checking only what localization changed: voice, on-screen text, captions and local legal lines. Track every version in one register with its status, reviewer and date, and when the master changes after approval, send only the changed parts of each version back for a new check.
Why do language versions go wrong?
Because the approvals scatter across inboxes while the files multiply.
A brand team makes one 30-second film and needs it in 20 markets. That is 20 voiceovers or subtitle sets, 20 sets of supers, and often several aspect ratios per language. The approvals travel by email: a market lead replies “looks good” to a link, another sends a PDF of notes, a third approves an older version because the newer one went to a colleague. Two weeks later, nobody can say with confidence which version was approved in which market.
The work itself is rarely the problem. The problem is that the approval of a language version is treated like a new creative review, with all its back-and-forth, instead of a narrow check against a master that is already decided.
What should be locked before localization starts?
The picture, the script, the textless master, and the list of legal lines per market.
Localization multiplies whatever is unfinished. If the master is still moving, every change has to be made 20 times. Before the first translation goes out, lock these:
- The master picture. Picture lock on one numbered version, approved by the global owner.
- The final script and supers. The source text that all translations start from.
- A textless master. The film without on-screen text, so each market gets its own text layer instead of a re-edit.
- Separate audio. Shootsta’s localization guide advises keeping narration off the picture, so a new voice can be dropped in without touching the edit.
- Legal lines per market. Vozo’s guide suggests collecting the required regional disclaimers before localization starts, not after the first version comes back.
- A do-not-translate list. Product names, brand terms and claims that must stay exactly as they are.
If something on this list is not ready, the localization schedule is not ready either. Our deliverables list guide covers how to agree the textless master and caption files at the quote, when they are cheap.
Who approves a language version, and what do they check?
A native reviewer in that market, with a narrow remit: does this version say the same thing, correctly, for this market?
| Check | Who | What they look at | Not their job |
|---|---|---|---|
| Translation and on-screen text | Native reviewer in the market | Meaning, spelling, tone, line breaks, text fitting the frame | The edit or the music |
| Voiceover or dub | Market lead, with the native reviewer | Performance, pronunciation of product names, sync with picture | Rewriting the script |
| Captions | Native reviewer | Spelling, timing, reading speed, line length | Choosing a caption style |
| Local legal lines | Legal or compliance in the market | Required lines present, readable and on screen long enough | Tone or creative choices |
| Technical check | Producer or post house | Correct master, audio levels, file specs per channel | Language |
The column on the right matters as much as the others. A market reviewer who starts commenting on the edit is reopening a decision that was made for every market at once. If a scene genuinely does not work locally, that is a question for the global team, not a note for the editor. Our guide on who approves what in a brand video covers the same principle for the master itself.
How do you track 20 approvals without losing count?
One register, one row per deliverable per market, and one person who keeps it current.
A spreadsheet is enough for this, as long as everyone uses the same one and nobody approves outside it. A minimal register looks like this:
| Market | Deliverable | Master version | Language version | Reviewer | Status | Date |
|---|---|---|---|---|---|---|
| DE | 30s 16:9, voiceover | v7 | DE-v2 | Market lead DE | Approved | 3 Nov |
| FR | 30s 16:9, voiceover | v7 | FR-v1 | Market lead FR | Notes sent | 2 Nov |
| ES | 15s 9:16, subtitles | v7 | ES-v1 | Native reviewer ES | Waiting | |
| IT | 30s 16:9, voiceover | v6 | IT-v2 | Market lead IT | Recheck: master changed |
Three columns do most of the work. Master version shows which master a language version was built on, so an approval on v6 is never mistaken for an approval on v7. Language version counts that market’s own versions. Status has a fixed short list: Waiting, Notes sent, Approved, Recheck.
To keep the rounds short, give markets a fixed window. Contentoo’s approval guide recommends 24 or 48 hours for content reviewers; for a short video with a narrow remit, two business days per market is a workable default. Send markets in waves of five or six, so the voiceover studio and the editor are not waiting on all 20 at once, and so a problem found in the first wave can be fixed before it is copied into the rest.
What happens when the master changes after markets approved?
The approvals stop covering the new version, and only the changed parts go back for a check.
It happens more often than anyone plans for: a product shot is replaced, a claim is reworded, a packshot gets a new price. When the master moves, do three things:
- Raise the master version and write a short change note: which shots changed, at which timecodes, and why.
- Set every affected language version to Recheck in the register. Versions that do not use the changed shots can keep their approval, but write down that you checked.
- Ask reviewers to check the change only, with the timecodes from the change note, instead of watching the whole film again.
The rule underneath is simple: an approval belongs to a specific version. It never quietly carries over to the next one. Review tools can enforce that for you. In Kadrenta, made by the same team behind The Production Brief, rounds chain as v1, v2, v3 under one review item, and its help pages state that an approval on v2 never covers v3. Compare lets a reviewer wipe between two rounds to see exactly what changed, and remarks can be left on a set of items when the question is which of several variants works best.
How do you keep markets from slowing the whole launch?
Agree in advance what happens when a market does not respond, and keep the global team as the referee.
Set the market’s window at kickoff, and agree what a missed window means: the version goes out on the global team’s approval, or the market’s launch date moves. Either can be right; what matters is that the market knows before the deadline, not after. For how rounds and windows fit together, see what counts as a revision round, and for how market notes should be written so the editor can act on them in one pass, see video feedback an editor can act on.
Frequently asked questions
Should the global team approve every language version?
No. The global team approves the master and the rules for localization. Each language version is approved by someone in that market who reads and hears the language, checking only what changed.
Subtitles or voiceover: which is quicker to approve?
Subtitles are usually quicker, because a reviewer can check spelling and timing in one pass. A voiceover adds a performance to judge and a mix to check, so plan an extra round for it.
What is a textless master and why does it matter here?
It is the finished film without on-screen text. Every language version is built on it, so new text can be added without reopening the edit or the graphics.
Can a market change the creative?
Only through the global team. A market reviewer can flag that a scene does not work locally, but the decision to change the master belongs to the master's owner, because it affects every other market.