Four layers of quality checks before delivery.

QA tools, AI-assisted checks, expert review, and in-game LQA check the text from translation files through to the playable build. We fix and recheck issues, targeting an objective error rate of no more than 0.3%.

Discuss your translation project
A quality lead and language reviewers checking an issue board, marked proofs and revision history.
Quality target≤ 3‰

An objective error rate of no more than 0.3%

Error categories, counting methods, review samples and acceptance criteria are defined in the project brief and used for checks, reporting and acceptance.

How the four stages work together.

Select a stage to see what it checks and produces. Each stage catches different issues, and fixes return to the appropriate stage for verification.

Find an issue → Correct it → Recheck the relevant stage
What this stage checks

Find errors with automated rules

Check approved terminology, missing translations, number mismatches, missing variables or tags, punctuation and formatting.

Stage output

Rule-based QA reports and issue lists

What this stage checks

Flag possible problems with meaning and context

Use supplied glossaries, style guides and context to flag potential mistranslations, meaning shifts, inconsistencies and unusual tone for human assessment.

Stage output

Potential issues with the source, translation, and reason for review

What this stage checks

Check meaning and clarity for players

Specialist reviewers resolve source queries and assess mechanics, natural expression, character voice and cultural context. They confirm issues and determine revisions.

Stage output

Confirmed issues, revision decisions and localization files

What this stage checks

Verify the text inside the game

Check display, truncation, overlap, action feedback, dialogue triggers and rule explanations in the game. Record issues with build references and screenshots.

Stage output

Bug reports, reproduction steps, and retest results

Humans confirm tool and AI findings. Related text is checked after revision. In-game issues are retested in updated files or builds and closed once resolved.

Checked fixes. Documented delivery.

Deliver localization files, QA records and acceptance notes so revision decisions and issue status remain traceable.

Player feedback & ongoing maintenance

We track quality feedback from Reddit, Discord and in-game channels, then review it internally and refine the localized experience.

  • Reddit communities
  • Discord communities
  • In-game quality feedback
  1. Track feedback

    Collect feedback on translation, terminology, wording, text display and cultural content, recording the language, version and relevant issue details.

  2. Review internally

    Check the source, translation and game context. Distinguish language and display issues from preferences, then prioritize the findings.

  3. Refine the content

    Revise confirmed issues, coordinate UI or implementation fixes, and update terminology, style guides and language assets.

  4. Verify the update

    Recheck changes in the relevant build, follow subsequent feedback and carry review findings into the next content update.

Support continues after delivery.

Our quality commitments include checks, corrections, and follow-up on feedback after delivery.

  • 24/7 support
  • No time limit on fixes for our errors

We offer 24/7 support and fix quality issues caused by our work with no time limit. This covers errors in language, meaning, formatting, consistency, and cultural wording. New source content, changed requirements, and additional test coverage are quoted separately.

Explore in-game LQA

Deliverables

Files, records and acceptance criteria are agreed for each project.

  • Rule-based QA, AI-assisted QA and human review records
  • Revised localization files and reasons for changes
  • In-game LQA tickets, retest records and acceptance notes

Tell us about your localization project.

We translate terminology, UI, gameplay rules, and dialogue, with expert review and in-game checks to make sure the language works for players.

Discuss your translation projectExplore in-game LQA