How can a company translate documents professionally under ISO 17100:2015 without confusing a fluent translation with a controlled translation service? This practical guide explains translation-service specifications, translator competence, independent revision, client briefs, quality evidence and release decisions. It is written for people commissioning multilingual documents in business, public services, product communication or technical publishing, not for a single national school system.
Readers looking for ISO 17100 translation requirements, ISO 17100 certified translation services, how to choose a translation agency, translation revision versus proofreading, or translation quality assurance need a practical answer: what does the client actually specify, who carries out the work, and what proof shows that the agreed process happened? The hardest failures are often not grammar mistakes but unidentified versions, missing annexes, unfixed client queries and a review step described more confidently than it was performed.
ISO 17100:2015 is a published international standard covering processes, resources and other aspects of delivering translation services against applicable specifications. It has a published 2017 amendment; a future edition was under development when this guide was prepared. Its public scope expressly excludes interpreting services and raw machine-translation output with post-editing. This article is an independent educational explanation of practical service decisions, not a reproduction of the copyrighted standard or a claim of ISO certification.
Primary standard reference: ISO 17100:2015 — ISO catalogue. The following source-text snippets are invented teaching examples, not quotations from the ISO standard. They illustrate the kind of communicative decision a client or language professional must verify.
The practical problem this guide solves
A professional translation is not just a sentence converted from one language into another. It is a controlled service that joins a defined source, a declared target audience, competent people, documented decisions and an accepted output. The useful starting question is therefore not only ‘Is the French or Arabic correct?’ but ‘Which file, which audience, which review, and which version is being approved?’ These are small questions with large practical consequences.
A phrase has at least three lives: the author intended something, a language professional renders that intention, and a reader or listener uses the result. A service succeeds only if those lives are connected with enough evidence for the consequences involved. What looks like a vocabulary question may actually be about who has authority, whether an action is complete, or what conditions still apply. For this reason, the examples below begin with a realistic source situation rather than a dictionary definition.
Do not treat the examples as translations into a named language: the suggested language below is an English explanatory back-rendering that identifies meaning to preserve. The appropriate final wording must be written or interpreted by someone competent in the actual target language and setting. If the source is wrong or incomplete, language work cannot make the underlying policy or instruction true. The source owner must resolve factual and legal uncertainties.
A practical workflow from source to verified communication
Step 1: Specify exactly what must be delivered
Separate source document IDs, revisions, language pairs, locales, included annexes, editable files and final media. In this kind of work, the practical question is not whether someone can read the sentence aloud fluently. It is whether a second person could inspect the evidence, follow the choice and explain why this wording is safe for this audience. A clear service specification makes it possible to detect omissions before production rather than after release. Put the decision into the assignment record, not only into a private chat message, and identify the person allowed to approve it.
Try a simple acceptance test: show the relevant source and proposed target to two competent people who understand their respective roles. Ask each to identify the speaker or actor, the condition that activates the statement, any quantity or deadline, and what the reader is entitled to do next. If their answers conflict, find out whether the difference comes from terminology, source ambiguity, missing context or an unauthorized change of meaning. Fix the actual cause rather than voting for the more elegant sentence.
Step 2: Check competence against the subject
Look for translation experience, subject competence and an appropriate reviewer for the real task. In this kind of work, the practical question is not whether someone can read the sentence aloud fluently. It is whether a second person could inspect the evidence, follow the choice and explain why this wording is safe for this audience. A credential is evidence of some skill, not proof that every domain has been mastered. Put the decision into the assignment record, not only into a private chat message, and identify the person allowed to approve it.
Try a simple acceptance test: show the relevant source and proposed target to two competent people who understand their respective roles. Ask each to identify the speaker or actor, the condition that activates the statement, any quantity or deadline, and what the reader is entitled to do next. If their answers conflict, find out whether the difference comes from terminology, source ambiguity, missing context or an unauthorized change of meaning. Fix the actual cause rather than voting for the more elegant sentence.
Step 3: Make the revision role explicit
Ask who translates, who checks and whether a second qualified linguist compares source and target. In this kind of work, the practical question is not whether someone can read the sentence aloud fluently. It is whether a second person could inspect the evidence, follow the choice and explain why this wording is safe for this audience. Translation, bilingual revision, monolingual review and final proof are distinct activities. Put the decision into the assignment record, not only into a private chat message, and identify the person allowed to approve it.
Try a simple acceptance test: show the relevant source and proposed target to two competent people who understand their respective roles. Ask each to identify the speaker or actor, the condition that activates the statement, any quantity or deadline, and what the reader is entitled to do next. If their answers conflict, find out whether the difference comes from terminology, source ambiguity, missing context or an unauthorized change of meaning. Fix the actual cause rather than voting for the more elegant sentence.
Step 4: Maintain a question register
Capture ambiguous source language, alternatives, evidence, owner decisions and dates. In this kind of work, the practical question is not whether someone can read the sentence aloud fluently. It is whether a second person could inspect the evidence, follow the choice and explain why this wording is safe for this audience. A translator should not turn an unresolved legal or technical question into an unsupported certainty. Put the decision into the assignment record, not only into a private chat message, and identify the person allowed to approve it.
Try a simple acceptance test: show the relevant source and proposed target to two competent people who understand their respective roles. Ask each to identify the speaker or actor, the condition that activates the statement, any quantity or deadline, and what the reader is entitled to do next. If their answers conflict, find out whether the difference comes from terminology, source ambiguity, missing context or an unauthorized change of meaning. Fix the actual cause rather than voting for the more elegant sentence.
Step 5: Control file versions
Track source identifiers, updated screenshots, glossary revisions and changed paragraphs. In this kind of work, the practical question is not whether someone can read the sentence aloud fluently. It is whether a second person could inspect the evidence, follow the choice and explain why this wording is safe for this audience. A polished older edition may be unsuitable for a newer source without a fresh comparison. Put the decision into the assignment record, not only into a private chat message, and identify the person allowed to approve it.
Try a simple acceptance test: show the relevant source and proposed target to two competent people who understand their respective roles. Ask each to identify the speaker or actor, the condition that activates the statement, any quantity or deadline, and what the reader is entitled to do next. If their answers conflict, find out whether the difference comes from terminology, source ambiguity, missing context or an unauthorized change of meaning. Fix the actual cause rather than voting for the more elegant sentence.
Step 6: Audit nonlinguistic elements
Check numbers, diagrams, hyperlinks, variables, identifiers and final page layout. In this kind of work, the practical question is not whether someone can read the sentence aloud fluently. It is whether a second person could inspect the evidence, follow the choice and explain why this wording is safe for this audience. Readers act on more than sentences, and an invisible warning is not a usable warning. Put the decision into the assignment record, not only into a private chat message, and identify the person allowed to approve it.
Try a simple acceptance test: show the relevant source and proposed target to two competent people who understand their respective roles. Ask each to identify the speaker or actor, the condition that activates the statement, any quantity or deadline, and what the reader is entitled to do next. If their answers conflict, find out whether the difference comes from terminology, source ambiguity, missing context or an unauthorized change of meaning. Fix the actual cause rather than voting for the more elegant sentence.
Step 7: Test the actual audience and medium
Check the final page, interface, leaflet or printed label with intended readers. In this kind of work, the practical question is not whether someone can read the sentence aloud fluently. It is whether a second person could inspect the evidence, follow the choice and explain why this wording is safe for this audience. A target sentence can be linguistically sound yet unusable in the delivery channel. Put the decision into the assignment record, not only into a private chat message, and identify the person allowed to approve it.
Try a simple acceptance test: show the relevant source and proposed target to two competent people who understand their respective roles. Ask each to identify the speaker or actor, the condition that activates the statement, any quantity or deadline, and what the reader is entitled to do next. If their answers conflict, find out whether the difference comes from terminology, source ambiguity, missing context or an unauthorized change of meaning. Fix the actual cause rather than voting for the more elegant sentence.
Step 8: Record acceptance and maintenance
List delivered versions, residual issues, decision owners and the route for future corrections. In this kind of work, the practical question is not whether someone can read the sentence aloud fluently. It is whether a second person could inspect the evidence, follow the choice and explain why this wording is safe for this audience. Traceable acceptance lets a translation be maintained safely instead of becoming an orphaned file. Put the decision into the assignment record, not only into a private chat message, and identify the person allowed to approve it.
Try a simple acceptance test: show the relevant source and proposed target to two competent people who understand their respective roles. Ask each to identify the speaker or actor, the condition that activates the statement, any quantity or deadline, and what the reader is entitled to do next. If their answers conflict, find out whether the difference comes from terminology, source ambiguity, missing context or an unauthorized change of meaning. Fix the actual cause rather than voting for the more elegant sentence.
Worked casebook: ISO 17100:2015 Translation Service Briefs, Independent Revision and Quality Evidence
Each of the following cases isolates a different reason apparently good language can fail. The situations are illustrative. The proposed wording describes meaning that requires competent rendition, not an official standard clause, legal instruction or automatically acceptable target text.
Case 1: Translation project scope
Consider a manufacturer sends a single PDF containing product instructions and a separate warranty page. The working English source message is: “Translate the attached manual for all customers.” Its purpose cannot be judged from syntax alone; the intended audience, responsible speaker, time and supporting record determine what a faithful version needs to carry. The first task is to write down the decision a real person could make after reading or hearing this line. If the translated statement changes that decision, the apparent fluency is beside the point.
A tempting but unsafe version would amount to: “Translation completed for the entire product range.” The danger is not merely that a different word was chosen. A vague attachment reference can hide a missing annex or a superseded safety paragraph. Identify the exact additional promise, removed limit, changed actor or unsupported assumption in the tempting version. Then return to the source evidence: who issued the original instruction, how current is it, and is there a document or subject expert able to answer a real ambiguity? A linguist should not manufacture an authorization that does not exist.
A safer working instruction is: “Name the exact document version, language pair, territory, file set and whether the warranty page is included.” This is guidance on the semantic outcome, not a ready-made certified target-language sentence. Before delivery, have an appropriately competent language professional express it in the actual target language with the necessary register and local conventions. Check it both forwards against the source and backwards against the real user task. Where the source lacks enough information, retain an open query rather than disguising it as editorial polish.
For a practical quality check, ask someone who did not draft the text to explain what this version says a person can do, cannot do, must do or may only consider doing. Ask what evidence supports that conclusion, and whether the proposed form can still be understood in its final context: spoken exchange, customer email, screen, form, label or published document. Record the answer under this case heading. The point is not bureaucratic paperwork; it is to prevent a silent semantic change from becoming the basis of a real decision.
Now imagine the underlying source changes next month. A responsible maintainer would need to find this phrase, the term or condition it depends on, the target versions affected, and the reason for the earlier choice. Keep identifiers and review notes that permit that search. If a user reports an error, respond to its consequence first: incorrect eligibility, a wrong number, mistaken scope, missing consent or a lost warning may need immediate correction rather than a routine style update. That maintenance test makes the original quality claim meaningful.
Case 2: Locale specification
A tempting but unsafe version would amount to: “One Spanish version is legally suitable throughout the world.” The danger is not merely that a different word was chosen. A language name does not determine a single regional convention or legal vocabulary. Identify the exact additional promise, removed limit, changed actor or unsupported assumption in the tempting version. Then return to the source evidence: who issued the original instruction, how current is it, and is there a document or subject expert able to answer a real ambiguity? A linguist should not manufacture an authorization that does not exist.
A safer working instruction is: “Ask the client to identify the intended markets, regulatory constraints, terminology and review contacts.” This is guidance on the semantic outcome, not a ready-made certified target-language sentence. Before delivery, have an appropriately competent language professional express it in the actual target language with the necessary register and local conventions. Check it both forwards against the source and backwards against the real user task. Where the source lacks enough information, retain an open query rather than disguising it as editorial polish.
For a practical quality check, ask someone who did not draft the text to explain what this version says a person can do, cannot do, must do or may only consider doing. Ask what evidence supports that conclusion, and whether the proposed form can still be understood in its final context: spoken exchange, customer email, screen, form, label or published document. Record the answer under this case heading. The point is not bureaucratic paperwork; it is to prevent a silent semantic change from becoming the basis of a real decision.
Now imagine the underlying source changes next month. A responsible maintainer would need to find this phrase, the term or condition it depends on, the target versions affected, and the reason for the earlier choice. Keep identifiers and review notes that permit that search. If a user reports an error, respond to its consequence first: incorrect eligibility, a wrong number, mistaken scope, missing consent or a lost warning may need immediate correction rather than a routine style update. That maintenance test makes the original quality claim meaningful.
Consider an online shop sells to Spanish-speaking customers in more than one country. The working English source message is: “Spanish is fine for every market.” Its purpose cannot be judged from syntax alone; the intended audience, responsible speaker, time and supporting record determine what a faithful version needs to carry. The first task is to write down the decision a real person could make after reading or hearing this line. If the translated statement changes that decision, the apparent fluency is beside the point.
Case 3: Source-file readiness
A safer working instruction is: “Record extraction, image text, diagrams, dimensions, source legibility and unresolved words before pricing.” This is guidance on the semantic outcome, not a ready-made certified target-language sentence. Before delivery, have an appropriately competent language professional express it in the actual target language with the necessary register and local conventions. Check it both forwards against the source and backwards against the real user task. Where the source lacks enough information, retain an open query rather than disguising it as editorial polish.
For a practical quality check, ask someone who did not draft the text to explain what this version says a person can do, cannot do, must do or may only consider doing. Ask what evidence supports that conclusion, and whether the proposed form can still be understood in its final context: spoken exchange, customer email, screen, form, label or published document. Record the answer under this case heading. The point is not bureaucratic paperwork; it is to prevent a silent semantic change from becoming the basis of a real decision.
Now imagine the underlying source changes next month. A responsible maintainer would need to find this phrase, the term or condition it depends on, the target versions affected, and the reason for the earlier choice. Keep identifiers and review notes that permit that search. If a user reports an error, respond to its consequence first: incorrect eligibility, a wrong number, mistaken scope, missing consent or a lost warning may need immediate correction rather than a routine style update. That maintenance test makes the original quality claim meaningful.
Consider a medical-equipment supplier provides an image-only document without editable drawings. The working English source message is: “We can translate whatever appears on the screen.” Its purpose cannot be judged from syntax alone; the intended audience, responsible speaker, time and supporting record determine what a faithful version needs to carry. The first task is to write down the decision a real person could make after reading or hearing this line. If the translated statement changes that decision, the apparent fluency is beside the point.
A tempting but unsafe version would amount to: “All diagrams and embedded labels have already been processed.” The danger is not merely that a different word was chosen. Text may be embedded in artwork or unreadable at normal zoom. Identify the exact additional promise, removed limit, changed actor or unsupported assumption in the tempting version. Then return to the source evidence: who issued the original instruction, how current is it, and is there a document or subject expert able to answer a real ambiguity? A linguist should not manufacture an authorization that does not exist.
Case 4: Reference materials
For a practical quality check, ask someone who did not draft the text to explain what this version says a person can do, cannot do, must do or may only consider doing. Ask what evidence supports that conclusion, and whether the proposed form can still be understood in its final context: spoken exchange, customer email, screen, form, label or published document. Record the answer under this case heading. The point is not bureaucratic paperwork; it is to prevent a silent semantic change from becoming the basis of a real decision.
Now imagine the underlying source changes next month. A responsible maintainer would need to find this phrase, the term or condition it depends on, the target versions affected, and the reason for the earlier choice. Keep identifiers and review notes that permit that search. If a user reports an error, respond to its consequence first: incorrect eligibility, a wrong number, mistaken scope, missing consent or a lost warning may need immediate correction rather than a routine style update. That maintenance test makes the original quality claim meaningful.
Consider a company provides last year’s brochure and a new specification sheet. The working English source message is: “Reuse the approved brochure sentences unchanged.” Its purpose cannot be judged from syntax alone; the intended audience, responsible speaker, time and supporting record determine what a faithful version needs to carry. The first task is to write down the decision a real person could make after reading or hearing this line. If the translated statement changes that decision, the apparent fluency is beside the point.
A tempting but unsafe version would amount to: “Prior publication is proof that every old term remains valid.” The danger is not merely that a different word was chosen. Previously approved marketing wording may contradict revised product features. Identify the exact additional promise, removed limit, changed actor or unsupported assumption in the tempting version. Then return to the source evidence: who issued the original instruction, how current is it, and is there a document or subject expert able to answer a real ambiguity? A linguist should not manufacture an authorization that does not exist.
A safer working instruction is: “Compare term choices with the new evidence and mark conflict rather than silently recycling.” This is guidance on the semantic outcome, not a ready-made certified target-language sentence. Before delivery, have an appropriately competent language professional express it in the actual target language with the necessary register and local conventions. Check it both forwards against the source and backwards against the real user task. Where the source lacks enough information, retain an open query rather than disguising it as editorial polish.
Case 5: Translator eligibility
Now imagine the underlying source changes next month. A responsible maintainer would need to find this phrase, the term or condition it depends on, the target versions affected, and the reason for the earlier choice. Keep identifiers and review notes that permit that search. If a user reports an error, respond to its consequence first: incorrect eligibility, a wrong number, mistaken scope, missing consent or a lost warning may need immediate correction rather than a routine style update. That maintenance test makes the original quality claim meaningful.
Consider a client requests an expert for a narrowly specialized engineering translation. The working English source message is: “A fluent bilingual speaker is qualified for every technical field.” Its purpose cannot be judged from syntax alone; the intended audience, responsible speaker, time and supporting record determine what a faithful version needs to carry. The first task is to write down the decision a real person could make after reading or hearing this line. If the translated statement changes that decision, the apparent fluency is beside the point.
A tempting but unsafe version would amount to: “A general language credential alone establishes subject expertise.” The danger is not merely that a different word was chosen. A person may be an excellent linguist and still misread a technical operating state. Identify the exact additional promise, removed limit, changed actor or unsupported assumption in the tempting version. Then return to the source evidence: who issued the original instruction, how current is it, and is there a document or subject expert able to answer a real ambiguity? A linguist should not manufacture an authorization that does not exist.
A safer working instruction is: “Check both translation competence and the actual domain knowledge needed for this assignment.” This is guidance on the semantic outcome, not a ready-made certified target-language sentence. Before delivery, have an appropriately competent language professional express it in the actual target language with the necessary register and local conventions. Check it both forwards against the source and backwards against the real user task. Where the source lacks enough information, retain an open query rather than disguising it as editorial polish.
For a practical quality check, ask someone who did not draft the text to explain what this version says a person can do, cannot do, must do or may only consider doing. Ask what evidence supports that conclusion, and whether the proposed form can still be understood in its final context: spoken exchange, customer email, screen, form, label or published document. Record the answer under this case heading. The point is not bureaucratic paperwork; it is to prevent a silent semantic change from becoming the basis of a real decision.
Case 6: Independence of revision
Consider a procurement team wants to count the translator’s self-check as external revision. The working English source message is: “The author checked the draft, so another reviewer is unnecessary.” Its purpose cannot be judged from syntax alone; the intended audience, responsible speaker, time and supporting record determine what a faithful version needs to carry. The first task is to write down the decision a real person could make after reading or hearing this line. If the translated statement changes that decision, the apparent fluency is beside the point.
A tempting but unsafe version would amount to: “Two independent sets of eyes have approved the content.” The danger is not merely that a different word was chosen. The same person rereading their own draft does not create independent challenge. Identify the exact additional promise, removed limit, changed actor or unsupported assumption in the tempting version. Then return to the source evidence: who issued the original instruction, how current is it, and is there a document or subject expert able to answer a real ambiguity? A linguist should not manufacture an authorization that does not exist.
A safer working instruction is: “Distinguish the translator’s review from a separate bilingual revision step and identify the reviser.” This is guidance on the semantic outcome, not a ready-made certified target-language sentence. Before delivery, have an appropriately competent language professional express it in the actual target language with the necessary register and local conventions. Check it both forwards against the source and backwards against the real user task. Where the source lacks enough information, retain an open query rather than disguising it as editorial polish.
For a practical quality check, ask someone who did not draft the text to explain what this version says a person can do, cannot do, must do or may only consider doing. Ask what evidence supports that conclusion, and whether the proposed form can still be understood in its final context: spoken exchange, customer email, screen, form, label or published document. Record the answer under this case heading. The point is not bureaucratic paperwork; it is to prevent a silent semantic change from becoming the basis of a real decision.
Now imagine the underlying source changes next month. A responsible maintainer would need to find this phrase, the term or condition it depends on, the target versions affected, and the reason for the earlier choice. Keep identifiers and review notes that permit that search. If a user reports an error, respond to its consequence first: incorrect eligibility, a wrong number, mistaken scope, missing consent or a lost warning may need immediate correction rather than a routine style update. That maintenance test makes the original quality claim meaningful.
Case 7: Unresolved source ambiguity
A tempting but unsafe version would amount to: “The legal trigger has been established by the translator.” The danger is not merely that a different word was chosen. A polished target sentence can invent a start date not present in the contract. Identify the exact additional promise, removed limit, changed actor or unsupported assumption in the tempting version. Then return to the source evidence: who issued the original instruction, how current is it, and is there a document or subject expert able to answer a real ambiguity? A linguist should not manufacture an authorization that does not exist.
A safer working instruction is: “Raise a question and preserve the ambiguity until an authorized client decision is recorded.” This is guidance on the semantic outcome, not a ready-made certified target-language sentence. Before delivery, have an appropriately competent language professional express it in the actual target language with the necessary register and local conventions. Check it both forwards against the source and backwards against the real user task. Where the source lacks enough information, retain an open query rather than disguising it as editorial polish.
For a practical quality check, ask someone who did not draft the text to explain what this version says a person can do, cannot do, must do or may only consider doing. Ask what evidence supports that conclusion, and whether the proposed form can still be understood in its final context: spoken exchange, customer email, screen, form, label or published document. Record the answer under this case heading. The point is not bureaucratic paperwork; it is to prevent a silent semantic change from becoming the basis of a real decision.
Now imagine the underlying source changes next month. A responsible maintainer would need to find this phrase, the term or condition it depends on, the target versions affected, and the reason for the earlier choice. Keep identifiers and review notes that permit that search. If a user reports an error, respond to its consequence first: incorrect eligibility, a wrong number, mistaken scope, missing consent or a lost warning may need immediate correction rather than a routine style update. That maintenance test makes the original quality claim meaningful.
Consider a contract states that a benefit is available after twelve months without saying from which date. The working English source message is: “Clarify it by choosing the most likely anniversary date.” Its purpose cannot be judged from syntax alone; the intended audience, responsible speaker, time and supporting record determine what a faithful version needs to carry. The first task is to write down the decision a real person could make after reading or hearing this line. If the translated statement changes that decision, the apparent fluency is beside the point.
Case 8: Controlled terminology
A safer working instruction is: “Maintain definitions and examples, and test consistency against the interface and data model.” This is guidance on the semantic outcome, not a ready-made certified target-language sentence. Before delivery, have an appropriately competent language professional express it in the actual target language with the necessary register and local conventions. Check it both forwards against the source and backwards against the real user task. Where the source lacks enough information, retain an open query rather than disguising it as editorial polish.
For a practical quality check, ask someone who did not draft the text to explain what this version says a person can do, cannot do, must do or may only consider doing. Ask what evidence supports that conclusion, and whether the proposed form can still be understood in its final context: spoken exchange, customer email, screen, form, label or published document. Record the answer under this case heading. The point is not bureaucratic paperwork; it is to prevent a silent semantic change from becoming the basis of a real decision.
Now imagine the underlying source changes next month. A responsible maintainer would need to find this phrase, the term or condition it depends on, the target versions affected, and the reason for the earlier choice. Keep identifiers and review notes that permit that search. If a user reports an error, respond to its consequence first: incorrect eligibility, a wrong number, mistaken scope, missing consent or a lost warning may need immediate correction rather than a routine style update. That maintenance test makes the original quality claim meaningful.
Consider a software supplier uses account, tenant and organization for different product objects. The working English source message is: “Translate every occurrence as user account.” Its purpose cannot be judged from syntax alone; the intended audience, responsible speaker, time and supporting record determine what a faithful version needs to carry. The first task is to write down the decision a real person could make after reading or hearing this line. If the translated statement changes that decision, the apparent fluency is beside the point.
A tempting but unsafe version would amount to: “These three different data objects are interchangeable.” The danger is not merely that a different word was chosen. Changing entity boundaries can misdirect support or configuration instructions. Identify the exact additional promise, removed limit, changed actor or unsupported assumption in the tempting version. Then return to the source evidence: who issued the original instruction, how current is it, and is there a document or subject expert able to answer a real ambiguity? A linguist should not manufacture an authorization that does not exist.
Case 9: Numbers and units
For a practical quality check, ask someone who did not draft the text to explain what this version says a person can do, cannot do, must do or may only consider doing. Ask what evidence supports that conclusion, and whether the proposed form can still be understood in its final context: spoken exchange, customer email, screen, form, label or published document. Record the answer under this case heading. The point is not bureaucratic paperwork; it is to prevent a silent semantic change from becoming the basis of a real decision.
Now imagine the underlying source changes next month. A responsible maintainer would need to find this phrase, the term or condition it depends on, the target versions affected, and the reason for the earlier choice. Keep identifiers and review notes that permit that search. If a user reports an error, respond to its consequence first: incorrect eligibility, a wrong number, mistaken scope, missing consent or a lost warning may need immediate correction rather than a routine style update. That maintenance test makes the original quality claim meaningful.
Consider an engineering report combines decimal commas, grouping spaces and inch measurements. The working English source message is: “Adjust the number style by eye.” Its purpose cannot be judged from syntax alone; the intended audience, responsible speaker, time and supporting record determine what a faithful version needs to carry. The first task is to write down the decision a real person could make after reading or hearing this line. If the translated statement changes that decision, the apparent fluency is beside the point.
A tempting but unsafe version would amount to: “The final numerical value was independently checked.” The danger is not merely that a different word was chosen. A familiar separator can conceal an order-of-magnitude error. Identify the exact additional promise, removed limit, changed actor or unsupported assumption in the tempting version. Then return to the source evidence: who issued the original instruction, how current is it, and is there a document or subject expert able to answer a real ambiguity? A linguist should not manufacture an authorization that does not exist.
A safer working instruction is: “Preserve numerical quantity and unit meaning while applying validated target-locale formatting.” This is guidance on the semantic outcome, not a ready-made certified target-language sentence. Before delivery, have an appropriately competent language professional express it in the actual target language with the necessary register and local conventions. Check it both forwards against the source and backwards against the real user task. Where the source lacks enough information, retain an open query rather than disguising it as editorial polish.
Case 10: Named entities
Now imagine the underlying source changes next month. A responsible maintainer would need to find this phrase, the term or condition it depends on, the target versions affected, and the reason for the earlier choice. Keep identifiers and review notes that permit that search. If a user reports an error, respond to its consequence first: incorrect eligibility, a wrong number, mistaken scope, missing consent or a lost warning may need immediate correction rather than a routine style update. That maintenance test makes the original quality claim meaningful.
Consider a company has a legal name, trading name and registered product name. The working English source message is: “Naturalize all three names for the target market.” Its purpose cannot be judged from syntax alone; the intended audience, responsible speaker, time and supporting record determine what a faithful version needs to carry. The first task is to write down the decision a real person could make after reading or hearing this line. If the translated statement changes that decision, the apparent fluency is beside the point.
A tempting but unsafe version would amount to: “Each name is now an officially registered translation.” The danger is not merely that a different word was chosen. Readers may search or rely on an exact legal party or product identifier. Identify the exact additional promise, removed limit, changed actor or unsupported assumption in the tempting version. Then return to the source evidence: who issued the original instruction, how current is it, and is there a document or subject expert able to answer a real ambiguity? A linguist should not manufacture an authorization that does not exist.
A safer working instruction is: “Keep protected names and distinguish any explanatory gloss from official nomenclature.” This is guidance on the semantic outcome, not a ready-made certified target-language sentence. Before delivery, have an appropriately competent language professional express it in the actual target language with the necessary register and local conventions. Check it both forwards against the source and backwards against the real user task. Where the source lacks enough information, retain an open query rather than disguising it as editorial polish.
For a practical quality check, ask someone who did not draft the text to explain what this version says a person can do, cannot do, must do or may only consider doing. Ask what evidence supports that conclusion, and whether the proposed form can still be understood in its final context: spoken exchange, customer email, screen, form, label or published document. Record the answer under this case heading. The point is not bureaucratic paperwork; it is to prevent a silent semantic change from becoming the basis of a real decision.
Case 11: Revision timing
Consider a client changes the source while a translator is already finishing. The working English source message is: “Just replace the changed paragraph at the end.” Its purpose cannot be judged from syntax alone; the intended audience, responsible speaker, time and supporting record determine what a faithful version needs to carry. The first task is to write down the decision a real person could make after reading or hearing this line. If the translated statement changes that decision, the apparent fluency is beside the point.
A tempting but unsafe version would amount to: “The surrounding cross-references are unaffected.” The danger is not merely that a different word was chosen. Small edits can change referents and invalidate earlier translation choices. Identify the exact additional promise, removed limit, changed actor or unsupported assumption in the tempting version. Then return to the source evidence: who issued the original instruction, how current is it, and is there a document or subject expert able to answer a real ambiguity? A linguist should not manufacture an authorization that does not exist.
A safer working instruction is: “Record the source version and recheck dependent sentences, figures, links and terminology.” This is guidance on the semantic outcome, not a ready-made certified target-language sentence. Before delivery, have an appropriately competent language professional express it in the actual target language with the necessary register and local conventions. Check it both forwards against the source and backwards against the real user task. Where the source lacks enough information, retain an open query rather than disguising it as editorial polish.
For a practical quality check, ask someone who did not draft the text to explain what this version says a person can do, cannot do, must do or may only consider doing. Ask what evidence supports that conclusion, and whether the proposed form can still be understood in its final context: spoken exchange, customer email, screen, form, label or published document. Record the answer under this case heading. The point is not bureaucratic paperwork; it is to prevent a silent semantic change from becoming the basis of a real decision.
Now imagine the underlying source changes next month. A responsible maintainer would need to find this phrase, the term or condition it depends on, the target versions affected, and the reason for the earlier choice. Keep identifiers and review notes that permit that search. If a user reports an error, respond to its consequence first: incorrect eligibility, a wrong number, mistaken scope, missing consent or a lost warning may need immediate correction rather than a routine style update. That maintenance test makes the original quality claim meaningful.
Case 12: Tracked queries
A tempting but unsafe version would amount to: “The term question has been approved by the responsible owner.” The danger is not merely that a different word was chosen. An undocumented choice can be overturned during the next release. Identify the exact additional promise, removed limit, changed actor or unsupported assumption in the tempting version. Then return to the source evidence: who issued the original instruction, how current is it, and is there a document or subject expert able to answer a real ambiguity? A linguist should not manufacture an authorization that does not exist.
A safer working instruction is: “Record alternatives, evidence, decision-maker, date and affected occurrences.” This is guidance on the semantic outcome, not a ready-made certified target-language sentence. Before delivery, have an appropriately competent language professional express it in the actual target language with the necessary register and local conventions. Check it both forwards against the source and backwards against the real user task. Where the source lacks enough information, retain an open query rather than disguising it as editorial polish.
For a practical quality check, ask someone who did not draft the text to explain what this version says a person can do, cannot do, must do or may only consider doing. Ask what evidence supports that conclusion, and whether the proposed form can still be understood in its final context: spoken exchange, customer email, screen, form, label or published document. Record the answer under this case heading. The point is not bureaucratic paperwork; it is to prevent a silent semantic change from becoming the basis of a real decision.
Now imagine the underlying source changes next month. A responsible maintainer would need to find this phrase, the term or condition it depends on, the target versions affected, and the reason for the earlier choice. Keep identifiers and review notes that permit that search. If a user reports an error, respond to its consequence first: incorrect eligibility, a wrong number, mistaken scope, missing consent or a lost warning may need immediate correction rather than a routine style update. That maintenance test makes the original quality claim meaningful.
Consider a reviewer asks whether a term should be translated literally or descriptively. The working English source message is: “Choose the prettiest phrase and close the comment.” Its purpose cannot be judged from syntax alone; the intended audience, responsible speaker, time and supporting record determine what a faithful version needs to carry. The first task is to write down the decision a real person could make after reading or hearing this line. If the translated statement changes that decision, the apparent fluency is beside the point.
Case 13: Reference to law
A safer working instruction is: “Separate statutory references from voluntary policy promises and request local legal review.” This is guidance on the semantic outcome, not a ready-made certified target-language sentence. Before delivery, have an appropriately competent language professional express it in the actual target language with the necessary register and local conventions. Check it both forwards against the source and backwards against the real user task. Where the source lacks enough information, retain an open query rather than disguising it as editorial polish.
For a practical quality check, ask someone who did not draft the text to explain what this version says a person can do, cannot do, must do or may only consider doing. Ask what evidence supports that conclusion, and whether the proposed form can still be understood in its final context: spoken exchange, customer email, screen, form, label or published document. Record the answer under this case heading. The point is not bureaucratic paperwork; it is to prevent a silent semantic change from becoming the basis of a real decision.
Now imagine the underlying source changes next month. A responsible maintainer would need to find this phrase, the term or condition it depends on, the target versions affected, and the reason for the earlier choice. Keep identifiers and review notes that permit that search. If a user reports an error, respond to its consequence first: incorrect eligibility, a wrong number, mistaken scope, missing consent or a lost warning may need immediate correction rather than a routine style update. That maintenance test makes the original quality claim meaningful.
Consider an HR policy mentions local statutory leave and a company discretionary benefit. The working English source message is: “Treat both as legally required entitlements.” Its purpose cannot be judged from syntax alone; the intended audience, responsible speaker, time and supporting record determine what a faithful version needs to carry. The first task is to write down the decision a real person could make after reading or hearing this line. If the translated statement changes that decision, the apparent fluency is beside the point.
A tempting but unsafe version would amount to: “The employer’s optional benefit is a statutory obligation.” The danger is not merely that a different word was chosen. The source may distinguish mandatory rights from a company’s additional offer. Identify the exact additional promise, removed limit, changed actor or unsupported assumption in the tempting version. Then return to the source evidence: who issued the original instruction, how current is it, and is there a document or subject expert able to answer a real ambiguity? A linguist should not manufacture an authorization that does not exist.
Case 14: Confidential files
For a practical quality check, ask someone who did not draft the text to explain what this version says a person can do, cannot do, must do or may only consider doing. Ask what evidence supports that conclusion, and whether the proposed form can still be understood in its final context: spoken exchange, customer email, screen, form, label or published document. Record the answer under this case heading. The point is not bureaucratic paperwork; it is to prevent a silent semantic change from becoming the basis of a real decision.
Now imagine the underlying source changes next month. A responsible maintainer would need to find this phrase, the term or condition it depends on, the target versions affected, and the reason for the earlier choice. Keep identifiers and review notes that permit that search. If a user reports an error, respond to its consequence first: incorrect eligibility, a wrong number, mistaken scope, missing consent or a lost warning may need immediate correction rather than a routine style update. That maintenance test makes the original quality claim meaningful.
Consider a firm sends payroll records through an unapproved public translation website. The working English source message is: “The tool is free, so input is harmless.” Its purpose cannot be judged from syntax alone; the intended audience, responsible speaker, time and supporting record determine what a faithful version needs to carry. The first task is to write down the decision a real person could make after reading or hearing this line. If the translated statement changes that decision, the apparent fluency is beside the point.
A tempting but unsafe version would amount to: “No personal data left the organization’s control.” The danger is not merely that a different word was chosen. Convenience cannot substitute for confidentiality and data-handling authorization. Identify the exact additional promise, removed limit, changed actor or unsupported assumption in the tempting version. Then return to the source evidence: who issued the original instruction, how current is it, and is there a document or subject expert able to answer a real ambiguity? A linguist should not manufacture an authorization that does not exist.
A safer working instruction is: “Agree secure tooling, access rights, retention, deletion and permissible subcontractors before uploading.” This is guidance on the semantic outcome, not a ready-made certified target-language sentence. Before delivery, have an appropriately competent language professional express it in the actual target language with the necessary register and local conventions. Check it both forwards against the source and backwards against the real user task. Where the source lacks enough information, retain an open query rather than disguising it as editorial polish.
Case 15: Layout and graphics
Now imagine the underlying source changes next month. A responsible maintainer would need to find this phrase, the term or condition it depends on, the target versions affected, and the reason for the earlier choice. Keep identifiers and review notes that permit that search. If a user reports an error, respond to its consequence first: incorrect eligibility, a wrong number, mistaken scope, missing consent or a lost warning may need immediate correction rather than a routine style update. That maintenance test makes the original quality claim meaningful.
Consider a translated label doubles in length and no longer fits its hazard box. The working English source message is: “Shrink the font until the sentence fits.” Its purpose cannot be judged from syntax alone; the intended audience, responsible speaker, time and supporting record determine what a faithful version needs to carry. The first task is to write down the decision a real person could make after reading or hearing this line. If the translated statement changes that decision, the apparent fluency is beside the point.
A tempting but unsafe version would amount to: “The small print remains readable and safe.” The danger is not merely that a different word was chosen. Semantic correctness is lost if a warning cannot be seen in its final placement. Identify the exact additional promise, removed limit, changed actor or unsupported assumption in the tempting version. Then return to the source evidence: who issued the original instruction, how current is it, and is there a document or subject expert able to answer a real ambiguity? A linguist should not manufacture an authorization that does not exist.
A safer working instruction is: “Run a layout proof with real target-language text, target media and reader accessibility checks.” This is guidance on the semantic outcome, not a ready-made certified target-language sentence. Before delivery, have an appropriately competent language professional express it in the actual target language with the necessary register and local conventions. Check it both forwards against the source and backwards against the real user task. Where the source lacks enough information, retain an open query rather than disguising it as editorial polish.
For a practical quality check, ask someone who did not draft the text to explain what this version says a person can do, cannot do, must do or may only consider doing. Ask what evidence supports that conclusion, and whether the proposed form can still be understood in its final context: spoken exchange, customer email, screen, form, label or published document. Record the answer under this case heading. The point is not bureaucratic paperwork; it is to prevent a silent semantic change from becoming the basis of a real decision.
Case 16: Regional terminology
Consider a financial app labels a payment as pending, settled or reversed. The working English source message is: “Use one general word for all payment states.” Its purpose cannot be judged from syntax alone; the intended audience, responsible speaker, time and supporting record determine what a faithful version needs to carry. The first task is to write down the decision a real person could make after reading or hearing this line. If the translated statement changes that decision, the apparent fluency is beside the point.
A tempting but unsafe version would amount to: “The payment lifecycle is unchanged.” The danger is not merely that a different word was chosen. Confusing states can cause users to assume a refund or transfer occurred. Identify the exact additional promise, removed limit, changed actor or unsupported assumption in the tempting version. Then return to the source evidence: who issued the original instruction, how current is it, and is there a document or subject expert able to answer a real ambiguity? A linguist should not manufacture an authorization that does not exist.
A safer working instruction is: “Define each transactional state and validate it with product owners and target-locale users.” This is guidance on the semantic outcome, not a ready-made certified target-language sentence. Before delivery, have an appropriately competent language professional express it in the actual target language with the necessary register and local conventions. Check it both forwards against the source and backwards against the real user task. Where the source lacks enough information, retain an open query rather than disguising it as editorial polish.
For a practical quality check, ask someone who did not draft the text to explain what this version says a person can do, cannot do, must do or may only consider doing. Ask what evidence supports that conclusion, and whether the proposed form can still be understood in its final context: spoken exchange, customer email, screen, form, label or published document. Record the answer under this case heading. The point is not bureaucratic paperwork; it is to prevent a silent semantic change from becoming the basis of a real decision.
Now imagine the underlying source changes next month. A responsible maintainer would need to find this phrase, the term or condition it depends on, the target versions affected, and the reason for the earlier choice. Keep identifiers and review notes that permit that search. If a user reports an error, respond to its consequence first: incorrect eligibility, a wrong number, mistaken scope, missing consent or a lost warning may need immediate correction rather than a routine style update. That maintenance test makes the original quality claim meaningful.
Case 17: Client sign-off
A tempting but unsafe version would amount to: “All acceptance conditions have been met.” The danger is not merely that a different word was chosen. A positive message without release scope is not traceable acceptance. Identify the exact additional promise, removed limit, changed actor or unsupported assumption in the tempting version. Then return to the source evidence: who issued the original instruction, how current is it, and is there a document or subject expert able to answer a real ambiguity? A linguist should not manufacture an authorization that does not exist.
A safer working instruction is: “Supply file IDs, language pair, unresolved issues, reviewer decisions and the exact sign-off role.” This is guidance on the semantic outcome, not a ready-made certified target-language sentence. Before delivery, have an appropriately competent language professional express it in the actual target language with the necessary register and local conventions. Check it both forwards against the source and backwards against the real user task. Where the source lacks enough information, retain an open query rather than disguising it as editorial polish.
For a practical quality check, ask someone who did not draft the text to explain what this version says a person can do, cannot do, must do or may only consider doing. Ask what evidence supports that conclusion, and whether the proposed form can still be understood in its final context: spoken exchange, customer email, screen, form, label or published document. Record the answer under this case heading. The point is not bureaucratic paperwork; it is to prevent a silent semantic change from becoming the basis of a real decision.
Now imagine the underlying source changes next month. A responsible maintainer would need to find this phrase, the term or condition it depends on, the target versions affected, and the reason for the earlier choice. Keep identifiers and review notes that permit that search. If a user reports an error, respond to its consequence first: incorrect eligibility, a wrong number, mistaken scope, missing consent or a lost warning may need immediate correction rather than a routine style update. That maintenance test makes the original quality claim meaningful.
Consider a release manager asks for a proof that a bilingual file is ready to publish. The working English source message is: “Send a friendly email saying it looks good.” Its purpose cannot be judged from syntax alone; the intended audience, responsible speaker, time and supporting record determine what a faithful version needs to carry. The first task is to write down the decision a real person could make after reading or hearing this line. If the translated statement changes that decision, the apparent fluency is beside the point.
Case 18: Handover package
A safer working instruction is: “Agree editable assets, terminology decisions, translation memory rights and change logs before completion.” This is guidance on the semantic outcome, not a ready-made certified target-language sentence. Before delivery, have an appropriately competent language professional express it in the actual target language with the necessary register and local conventions. Check it both forwards against the source and backwards against the real user task. Where the source lacks enough information, retain an open query rather than disguising it as editorial polish.
For a practical quality check, ask someone who did not draft the text to explain what this version says a person can do, cannot do, must do or may only consider doing. Ask what evidence supports that conclusion, and whether the proposed form can still be understood in its final context: spoken exchange, customer email, screen, form, label or published document. Record the answer under this case heading. The point is not bureaucratic paperwork; it is to prevent a silent semantic change from becoming the basis of a real decision.
Now imagine the underlying source changes next month. A responsible maintainer would need to find this phrase, the term or condition it depends on, the target versions affected, and the reason for the earlier choice. Keep identifiers and review notes that permit that search. If a user reports an error, respond to its consequence first: incorrect eligibility, a wrong number, mistaken scope, missing consent or a lost warning may need immediate correction rather than a routine style update. That maintenance test makes the original quality claim meaningful.
Consider a translation vendor delivers a PDF but omits source mapping and editable target files. The working English source message is: “A readable PDF is the complete deliverable.” Its purpose cannot be judged from syntax alone; the intended audience, responsible speaker, time and supporting record determine what a faithful version needs to carry. The first task is to write down the decision a real person could make after reading or hearing this line. If the translated statement changes that decision, the apparent fluency is beside the point.
A tempting but unsafe version would amount to: “The client can maintain and update this translation reliably.” The danger is not merely that a different word was chosen. Future correction becomes expensive or impossible without the proper handover. Identify the exact additional promise, removed limit, changed actor or unsupported assumption in the tempting version. Then return to the source evidence: who issued the original instruction, how current is it, and is there a document or subject expert able to answer a real ambiguity? A linguist should not manufacture an authorization that does not exist.
Case 19: Correction after release
For a practical quality check, ask someone who did not draft the text to explain what this version says a person can do, cannot do, must do or may only consider doing. Ask what evidence supports that conclusion, and whether the proposed form can still be understood in its final context: spoken exchange, customer email, screen, form, label or published document. Record the answer under this case heading. The point is not bureaucratic paperwork; it is to prevent a silent semantic change from becoming the basis of a real decision.
Now imagine the underlying source changes next month. A responsible maintainer would need to find this phrase, the term or condition it depends on, the target versions affected, and the reason for the earlier choice. Keep identifiers and review notes that permit that search. If a user reports an error, respond to its consequence first: incorrect eligibility, a wrong number, mistaken scope, missing consent or a lost warning may need immediate correction rather than a routine style update. That maintenance test makes the original quality claim meaningful.
Consider a user identifies an incorrect sentence in a published emergency instruction. The working English source message is: “Patch the sentence without recording the original.” Its purpose cannot be judged from syntax alone; the intended audience, responsible speaker, time and supporting record determine what a faithful version needs to carry. The first task is to write down the decision a real person could make after reading or hearing this line. If the translated statement changes that decision, the apparent fluency is beside the point.
A tempting but unsafe version would amount to: “No other language version requires checking.” The danger is not merely that a different word was chosen. A fix is incomplete if dangerous obsolete text remains discoverable. Identify the exact additional promise, removed limit, changed actor or unsupported assumption in the tempting version. Then return to the source evidence: who issued the original instruction, how current is it, and is there a document or subject expert able to answer a real ambiguity? A linguist should not manufacture an authorization that does not exist.
A safer working instruction is: “Classify severity, trace the source and affected locales, update versions and confirm withdrawal of old copies.” This is guidance on the semantic outcome, not a ready-made certified target-language sentence. Before delivery, have an appropriately competent language professional express it in the actual target language with the necessary register and local conventions. Check it both forwards against the source and backwards against the real user task. Where the source lacks enough information, retain an open query rather than disguising it as editorial polish.
Case 20: Certification claim
Now imagine the underlying source changes next month. A responsible maintainer would need to find this phrase, the term or condition it depends on, the target versions affected, and the reason for the earlier choice. Keep identifiers and review notes that permit that search. If a user reports an error, respond to its consequence first: incorrect eligibility, a wrong number, mistaken scope, missing consent or a lost warning may need immediate correction rather than a routine style update. That maintenance test makes the original quality claim meaningful.
Consider a supplier puts an ISO 17100 logo on a proposal without identifying scope. The working English source message is: “The logo proves every translator and job is certified.” Its purpose cannot be judged from syntax alone; the intended audience, responsible speaker, time and supporting record determine what a faithful version needs to carry. The first task is to write down the decision a real person could make after reading or hearing this line. If the translated statement changes that decision, the apparent fluency is beside the point.
A tempting but unsafe version would amount to: “This individual document has been independently endorsed by ISO.” The danger is not merely that a different word was chosen. A claimed management or service arrangement must not be converted into a blanket quality guarantee. Identify the exact additional promise, removed limit, changed actor or unsupported assumption in the tempting version. Then return to the source evidence: who issued the original instruction, how current is it, and is there a document or subject expert able to answer a real ambiguity? A linguist should not manufacture an authorization that does not exist.
A safer working instruction is: “Ask what entity, process, scope and assessment actually support the provider’s statement.” This is guidance on the semantic outcome, not a ready-made certified target-language sentence. Before delivery, have an appropriately competent language professional express it in the actual target language with the necessary register and local conventions. Check it both forwards against the source and backwards against the real user task. Where the source lacks enough information, retain an open query rather than disguising it as editorial polish.
For a practical quality check, ask someone who did not draft the text to explain what this version says a person can do, cannot do, must do or may only consider doing. Ask what evidence supports that conclusion, and whether the proposed form can still be understood in its final context: spoken exchange, customer email, screen, form, label or published document. Record the answer under this case heading. The point is not bureaucratic paperwork; it is to prevent a silent semantic change from becoming the basis of a real decision.
Case 21: Post-editing boundary
Consider a client wants to count raw machine translation with corrections as ISO 17100 delivery. The working English source message is: “Any translated text falls under the same service standard.” Its purpose cannot be judged from syntax alone; the intended audience, responsible speaker, time and supporting record determine what a faithful version needs to carry. The first task is to write down the decision a real person could make after reading or hearing this line. If the translated statement changes that decision, the apparent fluency is beside the point.
A tempting but unsafe version would amount to: “Post-editing automatically satisfies the original translation-service requirements.” The danger is not merely that a different word was chosen. The public ISO 17100 scope excludes raw machine output with post-editing. Identify the exact additional promise, removed limit, changed actor or unsupported assumption in the tempting version. Then return to the source evidence: who issued the original instruction, how current is it, and is there a document or subject expert able to answer a real ambiguity? A linguist should not manufacture an authorization that does not exist.
A safer working instruction is: “Treat machine-translation post-editing as a different service model and check ISO 18587 separately.” This is guidance on the semantic outcome, not a ready-made certified target-language sentence. Before delivery, have an appropriately competent language professional express it in the actual target language with the necessary register and local conventions. Check it both forwards against the source and backwards against the real user task. Where the source lacks enough information, retain an open query rather than disguising it as editorial polish.
For a practical quality check, ask someone who did not draft the text to explain what this version says a person can do, cannot do, must do or may only consider doing. Ask what evidence supports that conclusion, and whether the proposed form can still be understood in its final context: spoken exchange, customer email, screen, form, label or published document. Record the answer under this case heading. The point is not bureaucratic paperwork; it is to prevent a silent semantic change from becoming the basis of a real decision.
Now imagine the underlying source changes next month. A responsible maintainer would need to find this phrase, the term or condition it depends on, the target versions affected, and the reason for the earlier choice. Keep identifiers and review notes that permit that search. If a user reports an error, respond to its consequence first: incorrect eligibility, a wrong number, mistaken scope, missing consent or a lost warning may need immediate correction rather than a routine style update. That maintenance test makes the original quality claim meaningful.
Case 22: Quote and schedule
A tempting but unsafe version would amount to: “A fixed fee covers every rewrite, revision and layout change.” The danger is not merely that a different word was chosen. Price only makes sense against a defined service and output. Identify the exact additional promise, removed limit, changed actor or unsupported assumption in the tempting version. Then return to the source evidence: who issued the original instruction, how current is it, and is there a document or subject expert able to answer a real ambiguity? A linguist should not manufacture an authorization that does not exist.
A safer working instruction is: “State assumptions, excluded materials, change process, review milestones and acceptance criteria.” This is guidance on the semantic outcome, not a ready-made certified target-language sentence. Before delivery, have an appropriately competent language professional express it in the actual target language with the necessary register and local conventions. Check it both forwards against the source and backwards against the real user task. Where the source lacks enough information, retain an open query rather than disguising it as editorial polish.
For a practical quality check, ask someone who did not draft the text to explain what this version says a person can do, cannot do, must do or may only consider doing. Ask what evidence supports that conclusion, and whether the proposed form can still be understood in its final context: spoken exchange, customer email, screen, form, label or published document. Record the answer under this case heading. The point is not bureaucratic paperwork; it is to prevent a silent semantic change from becoming the basis of a real decision.
Now imagine the underlying source changes next month. A responsible maintainer would need to find this phrase, the term or condition it depends on, the target versions affected, and the reason for the earlier choice. Keep identifiers and review notes that permit that search. If a user reports an error, respond to its consequence first: incorrect eligibility, a wrong number, mistaken scope, missing consent or a lost warning may need immediate correction rather than a routine style update. That maintenance test makes the original quality claim meaningful.
Consider a client asks for a flat price without revealing file quality or regulatory risk. The working English source message is: “Quote by word count alone with no assumptions.” Its purpose cannot be judged from syntax alone; the intended audience, responsible speaker, time and supporting record determine what a faithful version needs to carry. The first task is to write down the decision a real person could make after reading or hearing this line. If the translated statement changes that decision, the apparent fluency is beside the point.
Questions readers and commissioners often ask
Does ISO 17100 certify an individual translated sentence?
No. Avoid treating a service-system claim as an automatic guarantee that each phrase or delivered file has independent ISO endorsement. Ask the provider to identify the scope, independent assessment where applicable, and job evidence.
For this question, ask to see the exact assignment specification and the responsible decision-maker rather than accepting a marketing phrase as proof. A useful quality question is concrete: what source statement and output would you examine, and what evidence would persuade you the reader understood the same condition? This approach respects the user’s ability to check the service instead of relying on terminology alone.
Can I use machine translation in an ISO 17100 project?
Do not assume that raw machine-translated output followed by post-editing falls within the published ISO 17100:2015 scope. For a service centered on full human post-editing, examine ISO 18587 and agree the workflow separately.
For this question, ask to see the exact assignment specification and the responsible decision-maker rather than accepting a marketing phrase as proof. A useful quality question is concrete: what source statement and output would you examine, and what evidence would persuade you the reader understood the same condition? This approach respects the user’s ability to check the service instead of relying on terminology alone.
Is revision the same as proofreading?
No. A bilingual revision compares source and target meaning. Proofreading commonly checks the final target artifact for surface and production defects; neither should be described as the other.
For this question, ask to see the exact assignment specification and the responsible decision-maker rather than accepting a marketing phrase as proof. A useful quality question is concrete: what source statement and output would you examine, and what evidence would persuade you the reader understood the same condition? This approach respects the user’s ability to check the service instead of relying on terminology alone.
What should I receive at the end?
Expect whatever the accepted service brief specifies: final target assets, relevant versions, agreed review records and an explanation of material unresolved limitations. If editability and future maintenance matter, contract for them explicitly.
For this question, ask to see the exact assignment specification and the responsible decision-maker rather than accepting a marketing phrase as proof. A useful quality question is concrete: what source statement and output would you examine, and what evidence would persuade you the reader understood the same condition? This approach respects the user’s ability to check the service instead of relying on terminology alone.
How this specialist chapter connects to eduKate’s existing learning resources
This is a focused field guide to one service decision, not a new master index or a competing translation hub. For the complete architecture of preserving meaning between languages, continue to Master Art of Translation: the complete system for moving meaning between languages. For understanding the development of words, concepts and distinctions, use the protected Vocabulary Learning Hub. For English wording, context and the relationship between language and meaning, read How English Works: translation and meaning across languages. These are existing canonical learning routes; this chapter belongs beneath them.
Final working rule
Good language service does not remove every uncertainty by making the prose sound confident. It preserves every distinction the reader needs: what is known, what remains possible, who is responsible, which condition applies, and what has been approved. Check those distinctions with the source and intended audience. If a claim is not supported, do not add it for the sake of elegance. The reader’s next decision is the most practical test of whether meaning travelled safely.
Primary standard reference: ISO 17100:2015 — ISO catalogue. The following source-text snippets are invented teaching examples, not quotations from the ISO standard. They illustrate the kind of communicative decision a client or language professional must verify.