A localization ledger connects each source asset to its target-language version, product references, terminology decisions, language review, and final approval. Review meaning, product availability, visuals, and destination together; a fluent translation can still describe the wrong offer.
Build the localization record.
Keep a source version that everyone can identify.
Record the source asset ID and script version before translating. If the source changes later, mark the dependent language versions for review. Otherwise one market can publish an older offer while another publishes the corrected one.
Keep a separate row for each delivered language version. Share a common concept ID so the relationship is visible, but give each final export its own version and approval record. Do not overwrite the source asset when saving a translation.
Review meaning with a small comparison table.
| Source intention | Possible drift | Review question |
|---|---|---|
| Start a free trial under stated conditions | “Use it free” removes the conditions | Does the target wording describe the same offer and limits? |
| Choose a supported product option | The translation implies unlimited customization | Do the available choices match the actual product? |
| Get a recommendation from the app | The wording promises a guaranteed solution | Does the claim stay within the supported capability? |
These examples illustrate review decisions. They are not claims about Aitoma’s pricing or features. A reviewer should compare the intended promise and conditions, not just whether individual words have dictionary equivalents.
Check the parts outside the spoken script.
- Product screenshots: current version, correct language, and realistic actions.
- Captions: line breaks, reading time, accents, and agreement with the voice.
- On-screen labels: room for longer translations and clear visual hierarchy.
- Offer details: actual availability and applicable conditions in the target market.
- Destination: the page the viewer will reach, in the intended language when available.
A translated voiceover on top of untranslated controls may confuse the demonstration. If a product interface is only available in the source language, explain that limitation rather than replacing it with an invented localized screen.
Name the deliverable before approving it.
A translated script, a subtitle file, and a dubbed video are different deliverables. Record which one you ordered and which one the reviewer accepted. Approval of the wording does not establish that the finished video has correct timing, readable text, or an appropriate destination.
| Deliverable | What to check | What still needs a separate check |
|---|---|---|
| Reading translation | Meaning, terminology, and clear identification of the source. | It is not synchronized to playback and does not replace a caption or subtitle file. |
| Timed translated subtitles | Translated wording, cue timing, line breaks, and rendering in the intended player. | The spoken language stays unchanged unless a new voice track is produced. |
| Dubbed video | New speech, pronunciation, pacing, mix, and agreement with the visible scenes. | On-screen labels, captions, screenshots, and the landing page may still need localization. |
Terminology varies by region. W3C uses “captions” for synchronized speech and meaningful non-speech audio in the spoken language, and “subtitles” for translation into another language. A transcript is readable text; a descriptive transcript also conveys needed visual information. These distinctions help define the deliverable, but this worksheet is not an accessibility certification. Sources: W3C captions and subtitles and W3C transcripts, reviewed October 20, 2026.
For a concrete boundary, the NAIARA introduction example provides Spanish dialogue and an English reading translation beside the Spanish video. The English text helps readers follow the speech; it is not an English dub or a client-approved English export.
One source correction. Which versions need another review?
Fictional software example. A product reviewer changes the source line from “Export all your tasks” to “Export the tasks in your current view.” The Spanish script has been corrected, but the older voice, subtitles, and video still say “all.” The translated wording can pass its review while the final video remains blocked.
| Component | Current state in this example | Next action |
|---|---|---|
| Source EN-script-v03 | Current wording limits the export to the current view. | Retain this version as the source for the correction. |
| Spanish ES-script-v02 | Wording accepted: “Exporta las tareas de la vista actual.” | Use the accepted line for the replacement recording and subtitles. |
| ES-voice-v01 and ES-subtitles-v01 | Still based on the superseded broader promise. | Replace the speech, correct the text, and retime against the new recording. |
| ES-video-v01 | Blocked: its component files are still outdated. | Re-export, inspect adjacent scenes and text, check the destination, and record a fresh final decision. |
Download the worked localization record. Its five rows distinguish the source, translated script, voice, subtitle file, and final video. All names, versions, and review decisions in this record are invented for teaching; they do not describe a NAIARA correction or an Aitoma customer result.
Keep the previous approval as history, tied to its exact file. Add the new decision after the changed export is reviewed; do not carry an “approved” label forward merely because the concept ID stayed the same. For a voice change, use the voiceover review guide to recheck captions and the surrounding edit. For changes affecting several published assets, use the outdated creative guide to find the dependent versions.
Accept the localized export, not just the translation.
Review the complete video or carousel after all text and audio are placed. Longer wording can alter pacing, cover the product, or push the final action outside the readable area. Those are production issues that a script-only review will miss.
NAIARA’s examples on this site are Spanish originals for its Spanish market. They are useful evidence of that delivery, not proof that an English adaptation has already been produced or approved. Use the same distinction in your own records.