QA Checklist: Reviewing a Certified Translation Before It Ships
A production QA checklist for LSPs and immigration paralegals. The twelve recurring defects that get filings rejected, ordered by how often they occur and how cheap they are to catch.
Almost every certified translation rejection traces to one of twelve defects, and none of them are about language quality. They are completeness, certification format, and consistency failures — which means they are catchable by a checklist rather than by a second linguist.
This is that checklist, ordered by frequency. It is written for the person doing the final pass before a file ships, whether that is an LSP reviewer or a paralegal assembling a bundle.
1. Incomplete rendering
The most common defect by a wide margin. Every authority requires a full translation — pre-printed form text, seal text, registrar titles, footnotes, marginal notes, blank fields.
Check specifically:
- Reverse sides of every page
- Grading legends on transcripts (usually on the back, in small type)
- Every transaction row on bank statements
- Marginal annotations on Latin American and Spanish civil records
- Blank form fields, marked as blank rather than omitted
- Numbered clauses left empty on contracts such as a nikah nama
Cost to catch here: minutes. Cost after filing: a rejection cycle.
2. Certification defects
Absent, unsigned, undated, or missing a required element. Each destination has its own list:
| Destination | Certification must contain |
|---|---|
| USCIS | Completeness, accuracy, competence, name, signature, date, contact |
| UKVI | Accuracy confirmation, date, name, signature, contact, credentials |
| IRCC | Accuracy declaration, name, contact — plus provincial seal or sworn affidavit |
| Home Affairs | Name, NAATI number, signature, date (in Australia) |
The most-omitted element across all four is the date.
3. Wrong certification type for the destination
A USCIS-style certification sent to IRCC, which requires a provincially certified translator or a sworn affidavit. Or an Anglosphere certified translation destined for Germany, France, Spain, or Italy, which require a court-appointed sworn translator.
This one is not fixable at QA — it requires redoing the work with the correct credential. Catch it at intake, not review. See linguist-pool-vendor-management.
4. Certifier competence mismatch
The certifier does not actually read the source script. A Farsi reviewer signing Pashto, a Hindi reviewer signing Gurmukhi, a Mandarin reviewer signing a Cantonese-romanised Hong Kong document.
Check the vendor record against the actual document, not against the job ticket's language label.
5. Name inconsistency across the file
The same person spelled differently across documents in one bundle. Common causes:
- Spanish double surnames merged or the maternal one dropped
- Portuguese surname order confusion (paternal surname comes last)
- Vietnamese diacritics stripped
- Arabic and Urdu transliteration varying between documents
- Chinese surname order reversed
- Afghan patronymic chains truncated
The rule: each document reproduces its own source exactly; the romanised form matches the passport. Discrepancies are explained in a cover letter, never harmonised inside a translation. Altering a translation to make documents agree is falsification.
QA action: build a name table for the file and check every occurrence against it.
6. Structure lost
Tables flattened into prose. Transcript columns no longer aligned to headers. Right-to-left sources mirrored visually rather than remapped logically, so every value sits under the wrong heading.
This one is invisible unless you open the source alongside. Always compare structurally, not just linguistically.
7. Conversions the translator should not have made
Helpful translators break these constantly:
- Grades converted to GPA, or a division mapped to US honours
- Degree names rendered as Western equivalents — Licenciatura as "Bachelor's"
- Currency converted to dollars or pounds
- Credits converted to US semester hours
- Dates silently converted from Hijri or Solar Hijri
Evaluators and caseworkers do their own conversions. A pre-converted figure is unverifiable and, near a financial threshold, looks like an attempt to shape evidence.
8. Missing source document
The translation shipped without a legible copy of the foreign-language original. Officers compare the two; IRCC states this explicitly.
9. Expired source document
The translation is perfect; the underlying document is stale. Watch:
- Police certificates — commonly 3–12 months
- CENOMAR and single-status certificates — 3–6 months
- Pakistani Family Registration Certificates — 3–6 months
- Brazilian certidões — often 90 days, and they go stale because annotations attach to the registry entry, not your copy
- Spanish and Latin American civil records — request the literal, not the extracto
QA action: check issue dates against the expected filing date, not today's date.
10. Identifier transcription errors
Long identifiers are where careful work still fails:
- Chinese national ID — 18 digits
- Brazilian matrÃcula — 32 digits
- Mexican CURP — 18 characters
- Pakistani CNIC — 13 digits with hyphens as printed
Verify these character by character. An error makes the document unverifiable.
11. Unreviewed draft artefacts
The recognisable signature of output that was not actually read: collapsed tables, missing seals, characteristic false friends (vecino de as "neighbour", contrayentes as "contractors", filiação as "affiliation", bidoon as "without"), inconsistent name spellings within a single document.
If you see one of these, the file was not reviewed. The correct response is to send it back for genuine review, not to patch the instance — see ai-in-certified-translation-workflows.
12. Illegible or partial source
A phone photograph at an angle, a cropped page, a scan too low-resolution to read a registration number. The translation inherits the problem.
Catch at intake with a scanning specification: flat, 300 DPI, full page including margins, both sides.
The ship-ready pass
Before release, confirm:
- Every page translated, both sides, legends and marginal notes included
- Certification carries every element the destination requires, including the date
- Certification type matches the destination country
- Certifier reads the actual source script, credential current and correctly directed
- Certifier independent of the applicant
- Names consistent across the file and matched to the passport
- Legible copies of all originals included
- Tables and layout structurally verified against the source
- No grade, credential, currency, credit, or date conversions
- All source documents within validity at the expected filing date
- Long identifiers verified character by character
- A named human confirms they read the translation against the source
That last item is the control that catches most of the others.
Handling a rejection
Read what was actually flagged. Notices usually name the deficiency. Redoing everything is expensive and rarely necessary.
Classify it. Defects 1, 2, 7, and 10 are usually fixable by correcting a section and reissuing the certification. Defects 3, 4, 6, and 11 require redoing the affected documents. Defect 9 requires a new source document.
Fix the flagged item, then sweep the bundle for the same fault. If one transcript lost its grading legend, the others probably did too.
Log the cause. Rejection causes by type, by linguist, and by document type are the data that tell you which control to tighten.
Frequently asked questions
Should QA be a linguist or a trained checker? Most of this list is structural and does not require the source language — a trained checker catches items 1, 2, 3, 8, 9, 10, and 12. Items 4, 5, 7, and 11 need language competence.
How long should a QA pass take? Proportional to document count, not word count. Certified files are many short documents, and each needs its own certification check.
Can we skip QA when the linguist is trusted? The defects on this list are mostly not linguistic, so linguist quality does not predict them. Independence of the check is the point.
Rejections are procedural, not linguistic. Run the twelve, catch defect 3 at intake rather than review, and log causes so you know which control actually needs tightening.
Want fewer completeness defects reaching QA? Open ZenTrans and run a sample batch — the first 5 pages are free, and volume pricing runs to $0.70 per page.