What Language and Localization Evaluators Actually Review
Check meaning, register and local conventions while distinguishing genuine errors from valid variation.
You'll learn
- Meaning preservation comes before a preference for one fluent phrasing.
- Locale and audience are separate from the language name.
- Negation, dates, units and terminology deserve explicit checks.
- Explain the effect of a language error rather than calling a sentence unnatural.
In this guide
A translated sentence can be smooth and wrong. A localized sentence can preserve the dictionary meaning while confusing its intended readers. Review therefore needs both a source comparison and a target-audience check.
What the evaluator inspects
| Dimension | Concrete question |
|---|---|
| Meaning | Did a condition, actor, negation or degree of certainty change? |
| Terminology | Does the text use the required glossary consistently? |
| Register | Does the tone fit the specified relationship and setting? |
| Locale conventions | Are dates, numbers, units and formats unambiguous for the brief? |
| Fluency | Is the target text grammatical and readable? |
| Task compliance | Did it preserve protected terms, formatting and length constraints? |
A fluent sentence can reverse the instruction
Evaluation example
- Ne fermez pas la fenêtre avant la fin du téléversement.
- Fermez la fenêtre avant la fin du téléversement.
A language label is not a complete locale brief
Ask what audience the text serves. A French-language task may specify a particular region, institutional style or product glossary. Follow that brief rather than treating your own regional usage as the only valid form. If no locale is specified, distinguish an actual error from a defensible variant.
Ambiguous dates are a useful practice case. The numeric string 04/05/2026 can be interpreted in different orders. A request to localize it needs a known source meaning; changing the separators alone does not resolve the date. Record the ambiguity or use the task’s clarification rule instead of guessing.
Common mistake
Calling every unfamiliar expression incorrect
A regional variant may be valid. Identify the named locale, glossary or style rule that makes it unsuitable here. If there is no such constraint, do not convert personal preference into an error label.
Writing and audio tasks add their own evidence
For original writing, inspect whether the response satisfies the audience, purpose and tone of the brief. For transcription, compare the text with the audio rather than polishing spoken wording into a different message. If the task permits normalization, apply its rules consistently and preserve meaning-bearing elements.
Language review check
- Compare actors, negations, conditions and certainty with the source.
- Apply the specified glossary and locale.
- Check numbers, dates and units.
- Separate meaning errors from style preferences.
- Identify the exact span and its consequence.
- Use the project’s convention for ambiguity or unclear audio.
Current language opportunities
Use the Languages listings on the roles board to inspect current language and locale requirements. A related listing or pay summary does not establish that every bilingual applicant qualifies; read the specific role and assessment requirements.
Open roles in this field
What it pays right now
Languages listings run a median of $34/hr across 89 rate observations, from $10 to $150.
See every field and platform on the rates page →