Localization Prep Board for Beginners | Glossary, Style Rules, Review Criteria First, Then Launch

Project & Development

Localization Prep Board for Beginners | Glossary, Style Rules, Review Criteria First, Then Launch

First-time localization coordinators and agency project managers use this template to set glossary, style, and review rules before translating, then move every language through review to launch. Across four pages, page 1 lists what to translate, the languages, and launch dates; page 2 sets glossary and style rules and logs terms; page 3 picks which materials need the heaviest native review by reach and risk; page 4 tracks each language to launch. The task board has five columns - preparing, translating, reviewing, fixing, published - with four parent tasks (listing materials, setting terms, narrowing review criteria, advancing each language), three subtasks each. The three localization basics: finalize the source first, settle glossary terms before translating, and reserve native review for high-impact materials. Share the board with outside translators by URL; the interface runs in 12 languages, but your content stays in the language you wrote it in.

0 Likes 0 Copies Author: WeProcess
localization translation glossary multilingual beginner-friendly
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Preview mode Localization Prep Board for Beginners | Glossary, Style Rules, Review Criteria First, Then Launch

Whiteboard preview

① How to Fill This Board ② Start Here (What, Languages, Launch... ③ Materials to Translate (break down ... ④ Glossary Rules (from ③'s materials) ⑤ Style Rules ⑥ How to Settle Disputes ⑦ Glossary (terms pulled from ③'s mat... ⑧ Review Criteria (check the terms &a... ⑨ Pick Materials for Heavier Review (... Low readership, high impact High readership, high impact Low readership, low impact High readership, low impact ⑩ Progress by Language & Stage (l... ⑪ The Flow for One Language ⑫ Rules for Sharing the Board with Ou... Localization Prep... How to use (4 pag... What to translate... Glossary & st... Watch out & c... Review tips &... 1/4 Gather what to tr... Ctrl+F / ⌘F : 2/4... → 2/4 2/4 Set terms and style ↙ 3/4 1. Gather what to translateWrite what to translate, languages, and launch dates, and confirm the source is locked 2. Set terms and styleAlign how to translate product names and UI wording, plus number and tone rules 3. Set review criteriaDecide what to check and how far, and pick materials for heavier review 4. Work by languageMove translation, native review, fixing, and layout check through for each language 5. LaunchLaunch each language once every step is done. e.g. Launch English first, Thai the next week What to translatee.g. 30 pages of the product manualand the settings screen text Which languagese.g. From Japanese to English, Chinese (Simplified), and Thai Launch datee.g. November 30 (owner: ____) Volume Format Source locked date Body text e.g. 30 pages, ~20,000 words e.g. Word file e.g. Oct 20 UI text e.g. ~300 buttons & messages e.g. Spreadsheet list e.g. Oct 25 Text in images e.g. Text in 12 diagrams e.g. Images & source design files e.g. TBD: don't translate until set Video subtitles e.g. Two 3-minute videos e.g. Subtitle files e.g. Nov 1 Keep the glossary in one place; every translator uses the same version e.g. Don't translate product names by meaning - keep the transliteration (table ⑦) e.g. Match UI button names to exactly what's on screen e.g. Notify the owner before adding a new term Align how numbers, units, dates, and tone are written, per language e.g. Use half-width digits; put the unit after the number (10 cm) e.g. Write dates in the order each language commonly uses e.g. Pick one tone per language, formal or casual, and stick to it Don't decide a tricky term on the spot - log it for the owner to decide e.g. Write "needs discussion" in the notes column of table ⑦ e.g. Only the glossary owner decides (owner: ____) e.g. Tell every language's translators by the next day once decided Source Translation Notes Product name e.g. Japanese product name e.g. Kantan Kakei Note e.g. Keep the transliteration, don't translate Feature name e.g. Japanese feature name e.g. Auto Sort e.g. Match what's shown on screen Button name e.g. Japanese button label e.g. Save e.g. Keep buttons to one short word Common word e.g. Japanese menu word e.g. Settings e.g. Match wording between body text and buttons Don't translate e.g. Company name, model number e.g. (keep as is) e.g. Needs discussion: translate the abbreviation or not 3/4 Narrow review cri... → 4/4 4/4 Advance by language Who checks What counts as OK Common mistakes Meaning e.g. A native speaker of that language e.g. Same meaning as the source, reads naturally e.g. A negative sentence turned positive Terms e.g. The translator themselves e.g. Matches the ⑦ glossary e.g. Same feature name translated two different ways Style e.g. The translator themselves e.g. Follows the ⑤ style rules e.g. Full-width and half-width digits mixed Layout e.g. The source owner & that language's reviewer e.g. No overflow or odd line breaks e.g. Button text too long and gets cut off 縦軸: Impact if wro... e.g. Safety notices, pricing text. Few readers but a mistake is risky: have two native reviewers check it e.g. UI text, operating steps. Top priority: two native reviewers, then a second read after fixes e.g. Changelogs. The translator's own review is enough e.g. Supplementary notes. Native-review a sample, not everything Translation Native Review Fixing Layout Check Language 1 e.g. E... e.g. Done e.g. Done e.g. In progress (5 left) e.g. Not started Language 2 e.g. C... e.g. Done e.g. In progress e.g. Not started e.g. Not started Language 3 e.g. Thai e.g. In progress (up to page 15) e.g. Not started e.g. Not started e.g. Not started Language 4 e.g. Fill in once added e.g. — e.g. — e.g. — 1. TranslateTranslate using the ⑦ glossary and ⑤ style rules. e.g. Log unsure words in the ⑦ notes column 2. Native ReviewA native speaker of that language reads it against the ⑧ criteria. Two people review the ⑨-picked materials 3. FixFix what the review flagged; update the ⑦ table too if a term changed 4. Layout CheckCheck for text overflow or bad line breaks in the actual screen or page 5. LaunchLaunch each language once all four stages are done, and mark ⑩'s layout check as: done, published How to sharee.g. Send translators the board URL;they view the glossary and progress here Don't write on the boarde.g. Unpublished product info or the source text itself(share the source a separate, fixed way) About the display languagee.g. The interface switches across 12 languages,but board content stays in the language it was written in → 2/4 Set terms and style ↙ 3/4 Narrow review cri... → 4/4 Advance by language
100%

Drag to move, scroll to zoom

Task board contents

Preparing 16 items

Gather source items
Set terms & style
Set review criteria
Advance by language
List item & language
List all materials
Check source date
Set glossary rules
Set style rules
Add glossary terms
Write check criteria
Sort materials in 4
Pick priority items
Make a status table
Run flow to launch
Set sharing rules

Translating 0 items

Reviewing 0 items

Fixing 0 items

Published 0 items

← Back to templates