Why was my translation flagged for review?
A translation needs checking because an automatic check found a problem, because it was not confident enough to skip review, or because a person asked for a second look.
A flagged translation shows needs checking in the editor and counts towards the review figure on the project overview. The flag means a person should read it before you rely on it. It does not change the text.
Find out why
In the editor, select the string:
- In Table view, a flagged row has a Check button under its state (or QA when it has findings but no flag). It opens Quality findings for that string, with each problem, its category, its severity and, where there is one, a suggested fix you can take with Accept suggestion.
- In the context panel, Quality findings lists the same problems, and Provenance shows whether a person flagged it, and who. See Version history.
The reasons
An automatic check found a problem
The quality checks flag a translation when they find a serious problem, when its quality score is low, or when it runs over the key's maximum length. Typical problems are a placeholder that is missing or changed, the wrong plural forms for the language, and a glossary term that was not followed. Glossary terms are matched against source text and enforced during translation and during quality checks; a translation that departs from a glossary term is flagged.
Some problems are caught the moment a translation is saved, without a quality check:
- A translation saved by hand that is longer than the key's maximum length. The editor warns before you save: "Over the limit. Saving keeps your text and flags this row for review."
- A translation that already existed when someone lowered the key's maximum length, and is now too long.
It was not confident enough to skip review
This applies only to projects with Route AI translations by confidence turned on, under Settings, then Checks (Team and above). It is off by default.
Each AI translation carries a confidence signal. Translations that pass the automatic checks and come back confident can be marked as not needing review, so your reviewers only see the ones worth their time. Everything else is flagged for review. Automatic checks always win: a translation with a broken placeholder, the wrong plural forms, or a glossary conflict is always sent to review no matter how confident it was.
With the setting off, Glossa's translations arrive as draft and are not flagged for confidence. Use the Waiting for approval filter to find drafts nobody has read yet.
A person flagged it
- A reviewer selected Flag or Flag for a check. See Approve or flag a translation.
- A translator selected Ask for a check, which flags the string and notifies the project's reviewers.
Clear the flag
Fix the translation if it needs fixing, then have a reviewer approve it: approving clears the flag. Editing a translation does not clear its flag on its own, so a fixed string still reaches a reviewer.
Only Reviewers, Admins and the account's Owners can approve. If you are a translator, the flag stays until a reviewer reads the string.