A QA check is an automated or semi-automated review that verifies translation consistency, terminology use, numbers, inline tags, placeholders, punctuation, and spelling against project-specific settings. It is typically run within a CAT tool or standalone QA application after translation and editing, before delivery, to catch technical and basic linguistic errors such as mismatched tags, missing placeholders, or changed numerical variables.
Angel Translation editorial reference · Confirm the rendering against your source and approved project terminology.
Check source meaning → confirm the preferred term → record approved variants and references.
QA checks run in the final stages of translation projects, using predefined profiles in CAT tools or QA software. Linguists, project managers, and localization engineers review the results, resolving issues such as untranslated segments, forbidden characters, tag mismatches, and terminology noncompliance before final delivery; the output often feeds into language quality assessment.
A common mistake is relying on QA checks to catch all translation errors. Automated checks miss context errors, false friends, register shifts, and awkward wording, and they can generate many false positives if the profile is too strict; ignoring project-specific settings may also let serious technical defects pass, such as broken variables.
Creative and consumer content needs accurate meaning as well as tone and context. Subtitles, interfaces and voice scripts also require checks for timing, character limits and pronunciation.
Provide approved terms and previous translations with the source files. Agree how variants, ambiguous wording and revisions will be reviewed. Terminology maintenance and any termbase handback are confirmed in the project scope. See the 8-step AI + expert workflow.
Employee-training video transcription and dubbing.
Read the published project →Brand documentation.
Read the published project →Published scope shows related industry experience; it does not confirm that this specific term was used or reviewed in the project.
Include the source and target languages, file types, intended use, deadline and any approved termbase. Agree handling before sending sensitive files. Acknowledged in 4 hours, quoted in 24.
Prepare an inquiry email →Content Globalization solutions →File handling →A glossary entry is not an official standard or evidence of regulatory acceptance. Confirm current requirements for your project separately.