Linguistic QA
Linguistic Quality Assurance is the process of reviewing a localized product to catch errors that automated tools and even good translators can miss – in context. This means reviewing the actual build, the live app or the in-engine implementation, not just the source files.
Text that looks fine in a spreadsheet can break the experience in the product. A menu item might be truncated. A character name might be inconsistent with earlier references. A joke that was correct in translation might land completely wrong when players see it after a particular cutscene. A UI element might overflow its container in German or Japanese. None of these issues are visible outside the final environment.
Our LQA team reviews localized content where it actually lives. We check for linguistic errors, cultural inappropriateness, formatting issues, truncation, encoding problems and consistency – and we deliver structured, prioritized bug reports your team can act on immediately.
ZH-Hans · ZH-Hant · ES · FR · IT · DE · KO · RU · TR · UK · EL · and more
Standalone LQA · Bundled with translation · As part of full pipeline · Post-correction verification included
In-engine (game builds) · Web browser · iOS & Android apps · Desktop software · Console platforms · Staging environments
What we deliver
Services included
01
In-context linguistic review
Review of all localized strings in their final display environment – not just in a spreadsheet. We play through the game, navigate the app or browse the platform as a real user would.
02
Structured bug reporting
Prioritized, actionable bug reports with severity levels (critical / major / minor), screenshots, string references and suggested corrections – ready for your dev or loc team to action immediately.
03
Consistency checking
Cross-referencing of terminology, character names, UI labels and tone across all localized content – ensuring the same term is always the same term, everywhere in the product.
04
Cultural & market review
Flagging of content that may be culturally inappropriate, offensive, legally sensitive or simply misaligned with local market expectations – before it reaches players or users.
05
Formatting & truncation checks
Identification of display issues: text overflow, truncation, broken line breaks, incorrect date and number formats, and encoding errors across all target languages and platforms.
06
Post-correction verification
Follow-up review after developer fixes to confirm all reported issues have been resolved correctly – and that no new issues were introduced during the correction process.
How we work
Our process
01
Scope & environment setup
We agree on scope, languages, platforms and priority areas. You provide access to the build, app or staging environment and we confirm technical requirements before starting.
02
Reference material review
We review any available glossaries, style guides and translation memories before starting the LQA pass – so we know what “correct” looks like for your product specifically.
03
In-context review pass
Our linguists go through the product in its final environment, navigating every screen, interaction and content area methodically, logging every issue with full context and evidence.
04
Bug report delivery
We deliver a structured bug report in your preferred format – spreadsheet, your bug tracker, or a dedicated LQA tool – with severity ratings, screenshots and correction suggestions for every issue.
05
Developer fix cycle
Your team implements the fixes. We remain available to answer questions, clarify issues and provide additional context during this phase to avoid misunderstandings.
06
Verification pass
We review the corrected build to confirm all reported issues are resolved correctly. A final sign-off report is delivered, giving you confidence before release.