Every translation buyer eventually meets the same unpleasant surprise. The file arrives on time, the invoice matches the quote, and then someone in the Munich office or at the São Paulo distributor reads it and says that the sentences are fine but the document is wrong. Nothing is misspelled. The terminology is simply not what the company uses, the tone is too stiff for a product page, or a contract clause has drifted a few degrees away from its original meaning. That gap is where translation quality actually lives, and it is almost never closed by adding one more proofreader at the end.
After two decades of watching language projects succeed and fail, the pattern is consistent. Teams that treat quality as an inspection step get inconsistent results. Teams that treat it as a process get boring, predictable, reusable results, which in this industry is the highest compliment available.
Translation quality is decided before anyone translates a word
The single biggest predictor of a good translation is the quality of the brief that goes out with it. A vendor who receives a bare Word file and a deadline has to guess at everything that matters: who reads this, in which country, for what purpose, and which words are non-negotiable. A vendor who receives the same file with a two-paragraph brief, a short glossary and a link to the live page it will sit on can make dozens of small decisions correctly without asking a single question.
The source text matters just as much. Ambiguity in English does not disappear in transit, it multiplies. A sentence that could mean two things in the original will mean one thing in German and something slightly different in Spanish, and the mismatch surfaces months later in a support ticket. Cleaning up the source before it goes out is the cheapest quality work anyone will ever do, and almost nobody does it.
What translation quality assurance actually measures
Serious reviewers do not mark a file as good or bad. They classify what they find. Modern translation quality assurance frameworks sort issues into a handful of categories: accuracy (does it say what the source says), terminology (does it use the approved word), linguistic conventions such as grammar and punctuation, style (does it sound like the brand), and locale conventions covering dates, currencies, addresses and units. Every finding carries a severity, because a wrong decimal separator in a price list is not the same kind of problem as a clumsy comma.
The value of that structure is not the score at the bottom. It is that the same reviewer, reading a comparable file next quarter, produces a comparable result, and that patterns become visible. Ten terminology errors and zero accuracy errors means the glossary is incomplete, not that the translator was careless. Working from formal translation quality standards makes those conversations far less personal and far more useful.
Machines changed the shape of the errors, not the need for review
Neural machine translation writes fluent sentences. That is precisely the problem. Older engines produced obvious nonsense that any reader could spot in a second. Current engines produce confident, grammatical, well-formed text that is occasionally and invisibly wrong. A negation quietly disappears. A defined legal term arrives as a common synonym. A dosage unit converts itself into something plausible and incorrect.
This is why post-editing became its own discipline rather than a cheaper flavour of proofreading. Post-editors are trained to read against the source rather than for flow, because fluent output invites the eye to skim. Teams that skip the step and ship raw engine output are not saving money on translation, they are moving the cost to whoever handles the complaint. It also pays to understand how your provider configures its CAT tools, because that setup decides how much of a file a human being ever really looks at.
A translation quality management system people will actually use
Three assets do most of the work. A glossary locks down the words that must never vary: product names, legal terms, interface strings. A translation memory keeps previously approved sentences available so the same phrase is not reinvented every quarter, and so corrections stay corrected. A one-page style guide answers the tone questions that otherwise get relitigated in every review cycle, such as formal or informal address, sentence length, and how much of the English marketing register to carry across.
The fourth asset is a person. Someone inside the target market, ideally in sales or support, who reads the final text before it ships and is allowed to say no. Translation quality management usually fails not because the assets are missing but because nobody owns the last look. Spend an hour in the places where working translators compare notes, such as the long-running r/TranslationStudies community, and the same complaint appears again and again: unclear ownership on the client side turns careful work into a guessing game.
The questions worth asking before you sign
Ask a prospective provider who reviews the work, and what that reviewer is instructed to look for. Ask whether the reviewer is a second linguist or the same translator rereading their own file an hour later. Ask where terminology decisions are recorded and who can change them. Ask what happens when you reject a delivery, and whether that feedback reaches the translator or stops at the project manager. The answers will tell you more about the translation quality you can expect than any certification badge in the website footer.
None of this needs a large budget. It needs a decision, made once, that quality is something you build into the pipeline rather than something you hope to catch on the way out. The teams that make that shift stop having the Munich conversation altogether, and that is the entire point.