Note: This article describes how this feature works in Lokalise Expert. The same feature is also available in Lokalise Vantage but the overall workflow differs. To learn more, see: Lokalise Vantage: Onboarding, Lokalise Vantage projects, Lokalise Vantage: Editor.
This feature is available from the Growth plan and above.
The AI-powered translation scoring feature helps you evaluate translation quality by identifying potential issues and assigning a score from 0 to 100 based on Multidimensional Quality Metrics (MQM).
High score (≥ 80): Few or no issues detected. The translation may require little or no human review.
Low score (< 80): More significant or multiple issues detected. Human review is recommended.
A high score doesn't guarantee a perfect translation. It simply means that AI scoring detected fewer or less severe issues.
You can request scores for individual translations in the editor or enable scoring for eligible Pro AI translation tasks. AI scoring is optional and disabled by default for tasks created in the Lokalise interface.
This helps you focus human review where it's needed most, rather than reviewing every translation or skipping reviews entirely.
What translation scoring offers?
With translation scoring, you can:
Identify potential translation issues directly in the editor
Prioritize human review based on translation scores
View detected issues and their severity to help reviewers decide what needs attention
Automatically route lower-scoring translations for review through Workflows
Translation scoring is integrated into the Lokalise editor, automatic translation tasks, and Workflows, helping teams incorporate quality checks into their existing localization processes.
Can we really trust an AI score to determine translation quality?
The goal of Translation Scoring isn’t to replace human reviewers: it's to help them focus on the content that truly needs attention. Instead of reviewing every string manually (slow and expensive), teams can:
Automatically route translations below your configured quality threshold for human review
Use higher scores to help prioritize review, while considering the importance and risk of the content
Spend review time more strategically, without sacrificing quality
In practice, teams can use translation scores to prioritize human review. Lower-scoring translations may need closer inspection, while higher-scoring ones may require less attention, depending on the content and its importance.
This can help reduce unnecessary review work, but a high score doesn't guarantee that a translation is error-free.
Why do you use MQM to evaluate translation quality?
MQM (Multidimensional Quality Metrics) is a widely used framework for evaluating translation quality. It organizes translation issues into categories such as accuracy, fluency, terminology, and style, and distinguishes between different levels of severity.
Lokalise uses an MQM-based approach to identify potential issues in translations, explain their severity, and calculate quality scores.
This gives reviewers more actionable information than a score alone: they can see what problems were detected and decide whether corrections are needed.
How to view scores for translations
To see translation scores, open your Lokalise project editor and look for a target translation value. You’ll notice a small lens icon next to it:
This icon only appears for target translations, not source (base) values.
Click the lens to trigger scoring. AI will check the translation quality and show a score. Click the score to get more details. If the translation has issues, points will be deducted, and you’ll see a list of detected problems:
Scoring does not consume any extra AI words from your team’s quota.
Access AI scoring programmatically
You can retrieve AI scoring information programmatically using the Lokalise MCP server or REST API.
With the Lokalise MCP server, ask your AI agent to retrieve keys or translations and include their AI scoring information.
With the REST API, AI scoring information is available when listing keys, retrieving a key, listing translations, or retrieving a translation. Set
include_ai_scoring=1to include this information in the response. For key endpoints, also include translations in the response. When available, the results are returned in theai_scoringobject for each translation.
Scoring and AI tasks: Generating scores in bulk
You can generate scores for many translations at once. To do this, select one or more keys in the editor, then choose Create a task from the bulk actions menu.
In the task settings, select Automatic translation as the task type. To assess the quality of translations generated by AI, enable Trigger AI quality scoring with task. This option is disabled by default.
When enabled, Lokalise evaluates eligible AI-generated translations and assigns quality scores from 0 to 100. Scoring does not consume additional AI words from your quota.
AI scoring is available for Pro AI translation tasks when the task's source language matches the project's base language. Translations retrieved from 100% translation memory matches are not scored.
Scoring won’t apply to 100% matches from the translation memory. If a translation comes straight from your translation memory, it won’t be scored. Lokalise only scores translations generated by AI within tasks.
Using scoring in workflows
You can also set up scoring as part of your workflows. To do this, go to the Workflows page and create a new workflow that includes the Review task with AI scoring step. This step comes after the AI translation step, which may be preceded by the TM step.
When setting up the AI scoring step, you’ll see the following options:
You can set a quality score threshold. By default, it’s set to 80. If a translation score falls below this value, the translation is automatically added to a review task created during this step. Any translations that could not be scored for any reason will also be added to the task.
Keep in mind that scoring ignores translation memory entries with 100% matches. Lokalise only scores AI-generated translations within tasks.
Optionally, select Exclude reviewed translations. When enabled, translations already marked as Reviewed won’t appear in the reviewer’s queue.
You can also customize the review task: give it a name and description, set a due date, and assign team members to handle the translations flagged for review. For more details on review tasks, check the Tasks documentation.
How scoring works
Translation scoring is powered by the MQM (Multidimensional Quality Metrics) framework — the industry standard for evaluating translation quality. MQM breaks down issues into categories such as grammar, spelling, fluency, terminology, and meaning errors. Each issue type is assigned a penalty weight based on severity:
Critical (−75 points): Serious issues that make a translation unsuitable for use or could cause legal, safety, financial, or reputational harm.
Major (−25 points): Significant issues that change the meaning or make the translation difficult to understand.
Minor (−5 points): Noticeable issues that don't change the meaning or prevent understanding, such as minor grammar or phrasing problems.
The final score is calculated as:
100 – (total penalties)
Examples:
One major (-25) + one minor (-5) → Score: 70
Two criticals (-75 each) → Score: 0 (scores cannot go below 0)
Score thresholds:
100: No issues detected by AI Scoring. The translation may still benefit from review, depending on the content.
80–99: Few or relatively minor issues detected. Additional review may be appropriate.
Below 80: More significant or multiple issues detected. Human review is strongly recommended.
In workflows, you can configure a score threshold to automatically route lower-scoring translations for human review. Higher-scoring translations can continue through the workflow without being added to that review task, depending on your configuration.
Remember that AI Scoring provides an additional quality signal, not a guarantee that a translation is ready to publish.
Translation scoring vs. AI LQA
Both translation scoring and AI LQA help evaluate translation quality using the MQM framework, but they are separate features that work differently and serve different purposes.
Translation scoring
Evaluates translations and assigns quality scores from 0 to 100 based on detected issues and their severity
Available on demand in the editor or as an optional feature for eligible Pro AI translation tasks
Integrates with workflows, allowing translations with lower scores to be routed for human review
Helps prioritize review during everyday translation work
AI LQA
Evaluates existing translations through dedicated AI LQA tasks
Generates downloadable Excel reports with detected issues, comments, and suggested corrections
Useful for large-scale quality assessments and translation audits
Does not affect workflow automation or determine which translations require human review
Although both features assess translation quality, they use different underlying processes. Translation scoring is designed for evaluating individual translations and supporting automated review decisions, while AI LQA focuses on producing detailed reports for broader quality assessments.
Frequently asked questions
💡 Looking for more?
Find all answers in AI: Frequently asked questions!





