Translation Review Template for Product Planning

For a batch under 500 strings, review everything. For larger batches (500-2,000 strings), review all critical paths (signup, billing, core workflows) plus a 30% random sample of remaining strings. For very large batches (2,000+), review critical paths plus 15-20% random sample. Always review 100% of legal and compliance-related text regardless of batch size.

A native speaker of the target language with product domain knowledge. The reviewer should not be the same person who translated the content (they will be blind to their own errors). Ideally, the reviewer is a product user or has been briefed on the product's features and terminology. In-market colleagues, contractors, or specialized linguistic QA vendors all work.

The PM has the final call on meaning and intent. The native speaker has the final call on fluency and cultural fit. When they disagree on terminology, defer to the glossary. If the glossary does not cover the term, make a decision, document it in the glossary, and apply it consistently going forward. Do not allow unresolved disagreements to delay release.

A weighted score of 4.0 or higher is good. Between 3.5 and 4.0 is acceptable for launch with a plan to improve. Below 3.5 means the translation needs significant rework before release. For critical content (legal, billing, onboarding), aim for 4.5+. Track scores over time. A vendor consistently scoring below 4.0 should be replaced. ---