ISO 17100:2015 & ISO 9001:2015 certified  ·  Offices in Dublin, Milan & Budapest info@bttranslations.com
Home/Resources/Buyer's Guide
Buyer's Guide

Translation quality: how to evaluate what you receive

A practical framework for judging a translation you cannot read - written for the procurement, legal, and regulatory teams who commission translation but do not speak the target language.

7 min read ISO 17100 process Updated 2026
The problem

Why translation quality is uniquely hard to judge

Translation quality is uniquely difficult to evaluate if you do not speak the target language. And the people who commission translation - procurement managers, project coordinators, legal teams, regulatory affairs specialists - frequently do not speak the target language. They receive a translated document, look at it, and have no reliable way of knowing whether it is excellent, adequate, or dangerously wrong.

This creates a structural vulnerability. Errors persist in published documentation, legal agreements, and regulatory submissions because no one in the commissioning organization was equipped to find them.

"A translator who produces poor work is rarely caught by the person who paid for it."

This guide gives you practical tools for evaluating translation quality even when you cannot read the target language - and explains what to look for when you can.

"It looks fine" is not a quality assessment

A translation can look completely professional - correct fonts, correct paragraph structure, no obviously missing sections - and still be substantially wrong. Terminology may be inconsistent. Key technical terms may be translated incorrectly. A contractual clause may have been mistranslated in a way that changes its legal effect. A safety warning may have been softened or omitted. None of these failures are visible to someone who cannot read the target language.

Conversely, a bilingual reviewer who is not a translation specialist will often flag stylistic preferences - "I would have phrased it differently" - as errors. Translation allows multiple valid formulations of the same meaning. Effective evaluation requires a framework applied consistently, not an impression.

The framework

The four dimensions of translation quality

Professional quality is assessed across four dimensions. Understanding what each covers lets you evaluate output systematically rather than impressionistically.

01
Accuracy

Does the translation convey the meaning of the source correctly? The most fundamental dimension - fluency cannot compensate for a mistranslated safety instruction or legal term.

Mistranslation Omission Addition Distortion
02
Consistency

Are the same concepts, terms, and structures translated the same way throughout - and across every document in an ongoing relationship? This is where long-term quality quietly degrades.

Terminology Structural Cross-document
03
Fluency & register

Does it read naturally, and in the register the document type demands? The dimension most often confused with preference - but systematic awkwardness signals a real problem.

Unnatural syntax Wrong formality Literal artifacts
04
Completeness

Has all source content been translated - nothing omitted, nothing added? One of the few dimensions you can check without reading the target language by comparing structure.

Omitted content Dropped formatting Untranslated segments
Practical tools

What you can check without speaking the target language

Five checks that reliably surface the most serious failures - none of which require you to read a word of the translation.

Structural completeness check

Place source and translation side by side. Do they have the same number of paragraphs, list items, table rows, headings, footnotes, and captions? Are there any untranslated passages? This takes minutes and catches the most serious omissions.

Terminology spot-check

Pick five to ten key terms - product names, technical terms, regulatory codes. Find each in the translation. Is it rendered consistently? Do certification numbers and standards references appear identically to the source? Does it match a previously approved translation? All of this is possible with a search function, not fluency.

Format & layout check

Does the translation fit its layout without overflow or truncation? Is text direction correct for right-to-left languages? Are numbers, dates, and units formatted to target conventions (1.234,56 vs 1,234.56; DD/MM/YYYY vs MM/DD/YYYY)? Are currency and measurement units right for the market?

Delivery specification check

Is the file in the format you requested? Are all files present and named correctly? Were special instructions - specific fonts, track changes removed, comments cleared - actually followed?

Certification check - for certified translations

Is the certification statement present, signed, and stamped where a stamp was required? Does it identify the translator or agency and the date?

In-country review

What bilingual reviewers should - and should not - do

An in-country employee or subject-matter expert is a valuable check. Use them for what they are good at, and protect against what they are not.

Good at
Spotting obvious mistranslations in their domain of expertise
Flagging terminology that does not align with local professional usage
Identifying register that is wrong for the local market or audience
Catching cultural references that do not transfer to the target context
Confirming product names and brand terms are handled correctly
Not good at - don't task them with
Comprehensive accuracy checking - they are not professional revisers
Distinguishing errors from preferences - they will flag both as "wrong"
Evaluating completeness systematically - they read for content, not structure
Assessing terminology consistency across long documents at scale

The one briefing instruction that matters most: ask reviewers to separate errors (the translation says something different, something is missing, a term is wrong) from preferences (they would have phrased it differently, but it is not incorrect). Preferences feed the glossary and style guide. They are not translation failures.

Prioritization

The error severity framework

Not all errors are equal. Classifying severity prioritizes correction and keeps error counts honest.

CriticalLegal, safety, or regulatory consequences

A mistranslated pharmaceutical dosage. A missing safety warning in a machine manual. A contractual obligation translated as a permission. A regulatory requirement omitted from a compliance document.

→ Must be corrected before publication or submission, regardless of cost or timeline.
MajorSignificantly affects comprehension or usability

A technical term consistently mistranslated through a manual. A confusing or misleading procedural instruction. An omission that leaves a section incomplete. Register so wrong it impedes communication.

→ Requires correction before publication.
MinorAffects quality but not comprehension

Occasional terminology inconsistency that does not cause confusion. Mildly unnatural but correct phrasing. Punctuation or minor formatting variations following the translator's convention.

→ Note and feed into glossary/style-guide refinement; correction not always required.
PreferencesNot errors

A different but equally valid word choice. A sentence structure that differs from the reviewer's preference but is not incorrect. Valid regional vocabulary variation.

→ Conflating preferences with errors inflates counts, creates disputes, and trains reviewers to over-report.
Closing the loop

How to give feedback your provider can act on

Quality improves over time only if feedback identifies the specific location, the specific error, and the specific correction. Vague feedback produces vague results.

Providers can act on
"The term [X] was translated as [Y] throughout. The approved translation is [Z]. Please update the glossary."
"Section 3.2, para 2: 'do not exceed [value]' was translated as 'should not exceed'. The original is a prohibition, not a recommendation. Please correct."
"The register is more formal than required for a consumer-facing product. Our preference is [description]. Please update the style guide."
Providers cannot act on
"The translation doesn't feel right."
"This doesn't sound natural."
"Our local team doesn't like it."
"Please improve the quality."
Prevention over detection

Build quality into the relationship, not just the review

Catching errors after delivery is valuable. A relationship structured to prevent them before delivery is worth more.

A maintained terminology glossary

Every approved term documented, applied automatically, updated when decisions change. Terminology errors in delivery are a symptom of inadequate glossary management.

A style guide for your content

Register, tone, and formatting decisions documented once and applied across all projects. Style errors are a symptom of inadequate briefing.

Translation memory that is actually maintained

Approved translations from previous projects applied to current ones. Cross-project inconsistency is a symptom of TM that is not being maintained.

A briefing process that communicates context

What is this document? Who reads it? What is the most important quality requirement for this content type? A translator who receives context produces better output.

Revision as a process requirement, not a premium

Every translation reviewed by a second qualified linguist before delivery. Errors that revision catches are the process working; errors that reach you are process failures to investigate.

Take it with you

The quality evaluation checklist

Without the language
Structural completeness - paragraphs, list items, headings, table rows
Terminology spot-check - key terms consistent, proper nouns correct
Format & layout - no overflow, correct number formats and direction
Delivery spec - correct format, all files, instructions followed
Certification - statement present, signed, stamped, dated
With a bilingual reviewer
Brief them on error vs. preference before they begin
Ask for specific location references for every flagged item
Ask them to classify each item: critical, major, minor, or preference
Ask for the correct version of any flagged error, not just the flag
After reviewing
Separate critical/major errors from minor errors and preferences
Communicate errors with location, description, and correction
Update your glossary with newly approved terms
Update your style guide and feed findings into the next briefing
ISO 17100:2015 certified process

Work with a quality-certified translation provider

Business Team Translations applies mandatory independent revision - a second qualified linguist checking every translation before delivery. We maintain client-specific translation memories and terminology databases, and we treat feedback as information that improves the next project. If you have received a translation you are uncertain about, contact us.

Request a Quote
Independent revision Terminology management Client translation memory