LQA vendors and agencies have linguists review translated text, often on a sample, score errors against MQM or ISO 5060 and deliver a report each round. Loqalit checks the rendered product in every language on a schedule, so layout and context bugs are caught between rounds. Use Loqalit as the first pass, and spend reviewer time on the issues it flags and on judgment calls.
Last reviewed:October 2026
Numbers in brackets link to the source for each claim about the other product.
| Outsourced LQA | Loqalit | |
|---|---|---|
| What gets reviewed | Translated text or files, often a sample[3][5]. In-context testing on a build is often offered as a separate step[1][2]. | The rendered page: every page you add, in every language |
| When | In review rounds[2] | On a schedule you set |
| Scoring | MQM or ISO 5060 error typology with severity ratings[1][3][6] | MQM category and severity for every finding. Scores from 0 to 100, normalized per 1,000 words. |
| Disagreements | Rebuttal or arbitration rounds with translators[1][3] | Every fix is a proposal. A person accepts or rejects it. |
| What you get | A scorecard or report. In-context testing adds annotated screenshots[1][2][3]. | Findings with screenshots. Accepted fixes are posted to Crowdin or Phrase. |
| Rendered issues: truncation, layout, context | Found in in-context testing. Alconost notes that file reviews miss them[1]. | Measured in the browser on every scan |
| Brand voice, legal and medical nuance | Yes, including subject-matter expert review[4] | No. Flag it for a human reviewer. |
| Turnaround | Varies by vendor. Alconost states about 1–3 business days[1]. | Each scheduled scan |
Reviewers start from a located, screenshotted list instead of a sweep.
On your schedule, in every language you ship, before the LQA round starts.
Overflow, untranslated text and broken placeholders arrive with a screenshot and a suggested fix.
Your vendor’s hours go to tone, terminology decisions and the issues Loqalit flagged for a human.
Loqalit catches rendered issues continuously, so your LQA budget goes to judgment calls. Run a scan before each LQA cycle and hand your vendor the findings.
No. Your vendor’s linguists make judgment calls Loqalit doesn’t: tone, brand voice, legal wording, and formal vendor scoring. Loqalit covers the rendered product on every release, so those reviews start from a cleaner site.
Reviewer hours stop going to clicking through pages looking for text that doesn’t fit. Use the calculator on our homepage to put your own numbers on it.
Yes. Every finding gets an MQM category and a severity, and scores run from 0 to 100, normalized per 1,000 words, so locales and pages compare fairly.
Yes. Export findings as CSV, XLSX, PDF or JSON, each with a screenshot, a reason and an MQM severity, or invite them to a shared workspace.
Claims about other products come from their own public pages. Product names belong to their owners.
We scan your live site in up to 3 languages and email you a PDF with screenshots, MQM severities and suggested fixes.