A PDF comes back with accurate translated wording, but the client still can’t send it: the tables have shifted, the captions are missing, and nobody agreed who would rebuild the layout. The problem isn’t necessarily the translation. The project brief may have asked for translated text when the client expected a finished document.
“Client-ready” sounds clear until someone has to decide what “ready” means. Ready for an internal editor? Ready to publish online? Ready to submit to an authority in a particular format? Each version can involve different linguistic checks and production work.
A translation agency’s deliverable is the set of files and services named in the agreed scope, not one universal package attached to the word “translation.” A clear brief turns expectations into specific items: the target file, the review level, the treatment of visual elements, and the final acceptance check.
What counts as a client-ready translated document?¶
A client-ready translated document is a file prepared to meet an agreed purpose, audience, format, and quality-check scope. The phrase describes a project outcome, not a standard file type or fixed list of included services.
For one team, client-ready means an editable Word file that an in-house subject expert can review. For another, it means a designed brochure that can go straight to a printer. A third team may need a draft translation in a bilingual table for internal editing. Those are different deliverables, even if each project begins with the same source document.
The American Translators Association’s project-preparation checklist recommends identifying deliverables such as a hard copy, file format, other media, and any certification or notarization requirement. The point is practical: a request for “translation” doesn’t tell an agency whether you need a Word file, a print-ready layout, or a certified document.
The service standard doesn’t fill in those project-specific details. The EVS listing of ISO 17100:2015+A1:2017 describes requirements for core processes, resources, and other aspects needed to deliver a translation service that meets applicable specifications. The listing says those specifications can come from the client, the provider, industry codes, best-practice guides, or legislation.
“This International Standard provides requirements for the core processes, resources, and other aspects necessary for the delivery of a quality translation service that meets applicable specifications.”
That wording puts the project specification at the centre. A standard can describe a service process without deciding that every agency must return the same file type or include publishing work in every quote. Your brief and the provider’s agreed scope establish those details.
A useful way to define “ready” is to describe what the recipient should be able to do with the file. If an editor needs to change wording, specify an editable file. If a marketing team intends to publish a page, describe the target layout and who will check the final proof. If an authority requires certification, state that before the quote is prepared.
The distinctions matter because translated text and a client-ready artifact solve different problems. Translation transfers meaning into another language. File preparation makes that content usable in a chosen environment. Quality checks test particular aspects of the wording or layout. One service can include several of these tasks, but the name of the service alone doesn’t confirm that it does.
The difference between certified, sworn, and notarized translation is another example of why the final purpose belongs in the brief. A document intended for an authority can need a specific form of certification in addition to translation. A document intended for internal discussion may need neither.
How agencies turn source material into a final file¶
A translation project can involve several separate workstreams: preparing source material, translating it, checking the target text, placing it in a file, and checking the finished layout. The project scope determines which of those workstreams the agency handles.
The source file affects what production work is practical. Editable files give the team access to text and structure. A PDF may need reconstruction before the translated wording can be placed back into a similar layout. A scan is an image, so the text first needs to be read; stamps, handwritten notes, or poor image quality can make that reading less reliable.
The ATA’s technical-project advice recommends providing editable source files, preferably before final layout, because text length changes across languages. The same guidance suggests sharing glossaries, product context, and previous translations where available. Those materials help the team work with the content, but they don’t replace a decision about the final format.
A simple handoff can follow this sequence:
- Define the use. Tell the agency who will read the translation and what the reader needs to do with it.
- Identify the source and target files. Name the actual source format and the format you expect to receive.
- Agree the language work. State whether the project needs translation alone, bilingual revision, monolingual review, or another defined check.
- Agree the production work. Describe how the agency should handle tables, images, charts, footnotes, page breaks, and layout.
- Set the final acceptance check. Say whether anyone needs to check the translated file after it has been laid out.
The sequence isn’t a universal production recipe. A short editable memo may need no separate layout stage. A brochure built from a PDF can require substantial work before the translated text fits the design. The ATA’s guidance on quoting a large translation project recommends identifying the target document and its finished format, especially when that format differs from the source. A bilingual Word table made from a PDF is one example of a different target artifact.
Images and tables need their own instructions. A translated label may be delivered as text for a designer to place, as an image with the translated label inserted, or as part of a rebuilt file. Those options are not interchangeable. The ATA’s quoting guidance advises clarifying how images, graphics, and tables will be handled because a translation by itself doesn’t determine how non-running-text elements will appear.
“Some clients expect publication-ready output while others only need a draft for internal editing.”
The ATA’s quoting guidance makes the difference explicit. A draft can be the right deliverable when an internal team will edit it. A publication-ready file calls for a different scope, and the quote should show that distinction rather than leave it to inference.
The production schedule also depends on the workstreams. The ATA’s scheduling guidance identifies revision, desktop publishing, screenshot capture, and testing as possible specialist work beyond translation. Those activities can use different productivity measures, so treating the whole job as one block of “translation time” can obscure what has to happen before delivery.
A practical example: a company sends a PDF manual and asks for a translated manual. The translator can translate the text, but that request doesn’t say whether the agency should rebuild diagrams, adjust the page layout, or review the final typeset pages. A quote that names only the target language leaves those expectations unresolved. A quote that names the finished file and visual tasks gives both sides a clearer handoff.
For a team working with machine translation, the same distinction applies. Machine translation post-editing describes human work on machine-produced text; it doesn’t by itself promise a formatted or publication-ready document. ISO 18587:2017 is the standard the ISO page describes as setting requirements for full human post-editing of machine-translation output and post-editors’ competences. Its scope concerns MT-processed content, not desktop publishing.
Revision, review, proofreading, and DTP are different tasks¶
Revision is bilingual checking: a reviewer compares the translation with the source to assess accuracy and completeness. Review is monolingual checking: a reviewer focuses on how the target text reads, including clarity, tone, and suitability for its audience.
Those terms can sound interchangeable in a quote, but the tasks answer different questions. A bilingual reviser asks whether the target text reflects the source. A monolingual reviewer asks whether the target text works for its readers. A project may need one, both, or neither as a separate paid step, depending on purpose and risk.
The European Commission’s Directorate-General for Translation explains the distinction on its translation-quality page. The same page says purpose and intended audience shape the process, and that quality management can take account of the potential impact and likelihood of errors, including factors such as time pressure, available resources, and translator expertise.
“The use of raw output from machine translation plus post-editing is outside the scope of this International Standard.”
The statement appears in the EVS listing of ISO 17100:2015+A1:2017. A claim that a service follows that standard shouldn’t be read as evidence that a particular job is machine-translation post-editing. Ask the provider to name the actual workflow and review stage.
Proofreading needs a similarly precise description. Some teams use the word for checking text after revision; others mean a final read of designed pages. If an agency will check a typeset proof, ask whether the check covers language errors caused by the layout process, such as misplaced text or characters that disappeared during production.
Desktop publishing, often shortened to DTP, is the formatting and adjustment of a document’s layout for print or online publication. The ATA’s description of translation and interpreting specializations distinguishes DTP from linguistic translation and proofreading.
That difference becomes clear when the text expands. Translated wording may take more or less space than its source, so a paragraph can overflow a box, a heading can wrap, or a table can become hard to read. A linguistic check can’t guarantee the layout works, and a layout check can’t confirm that the translation preserves the source’s meaning.
| Service | Main question it answers | Typical evidence in a handoff |
|---|---|---|
| Translation | Does the target text convey the source meaning? | Target-language text or translated file |
| Bilingual revision | Does the translation accurately and completely reflect the source? | Checked target text, with corrections or comments as agreed |
| Monolingual review | Is the target text clear and suitable for its intended readers? | Edited target text, with language or tone changes |
| Proofreading | Does the final text or proof contain errors that need correction? | Marked or approved proof, if included in scope |
| DTP | Does the document’s layout work for its intended format? | Formatted file prepared for print or online use |
The table describes purposes, not automatic inclusions. A vendor may bundle several tasks, but the quote should still name them. Ask whether “proofreading” means a read of the Word file or a check of the typeset proof. Ask whether “formatting” means basic headings and tables or full page-layout work.
Quality control also depends on what is being checked. A language reviewer can compare content, but that person may not be responsible for checking whether a chart label fits or a page number matches the final layout. The ATA’s technical-project guidance recommends proofreading both the final text and the final layout. Its example of a missing Spanish ñ illustrates how typesetting can introduce an error that a text-only check won’t catch.
A client can make the review request more useful by identifying the failure that matters. For a contract, completeness and accurate terminology may carry particular weight. For a public-facing brochure, audience fit and layout can matter as much as the first translation draft. The European Commission describes quality management as risk-based: consider the possible impact of an error and the likelihood of one, rather than assuming every file needs the same review path.
When a client-ready document is worth requesting¶
A finished, laid-out file matters when someone needs to use the document without doing another production pass. Examples include material prepared for publication, a form that needs to retain its structure, or a manual that users will follow in its final layout.
A translated text file can be the better choice when the client’s team owns design and publishing. A marketing editor may want the translated copy in a table or content-management system fields. An in-house specialist may need to add company-specific wording before publication. Paying for an agency to reproduce a design that the client will replace can add work without improving the handoff.
The right choice depends on where responsibility sits after translation. If a designer will take the target text and build the final asset, specify that the agency should return editable copy in the designer’s preferred format. If the agency is expected to return the finished asset, name the source design, the final output format, and the visual elements that must remain.
An editable file is especially useful when a reviewer needs to make changes. The ATA recommends providing editable sources before layout where possible, partly because translated text length varies by language. Starting with editable material can give the production team more room to adjust text and layout than working from a fixed page image.
Not every project needs the original layout reproduced exactly. An internal reference document might work better as a bilingual table, even if the source is a PDF. A client-ready file can be fit for purpose without copying every visual detail, provided the recipient agrees to that format. The cultural differences between Ukrainian and German document conventions can also affect whether a source layout should be copied or adapted for the target audience.
An agency can also separate the work into stages. The first delivery might be a translated and revised text file. A designer can then build the target layout, followed by a proof check if the agreement includes one. Staging gives the client a chance to approve wording before design work, but the quote needs to say who owns each handoff.
Consider an internal training guide with tables and screenshots. The client may want the translated text in an editable document, while its design team will replace screenshots and rebuild the final guide. In that case, the agency needs to know which text belongs in the screenshots and which can be translated as editable copy. A request for a “finished translation” alone doesn’t answer that.
For an official document, the recipient’s requirements can affect more than layout. The client may need a particular certification or notarization in addition to translation. Those requirements are separate from DTP, and they should be confirmed with the receiving organization rather than inferred from a polished-looking file.
Where projects go wrong, and how to prevent it¶
The most common handoff problem is a gap between what the client imagines and what the quote names. A client may interpret “translation” as a finished document, while the agency interprets it as translated content in an editable file. Neither side can rely on an unstated assumption to settle the difference.
The fix is to describe the final artifact in concrete terms. “Client-ready” is less useful than “editable Word file with tables retained, images supplied separately, and no page-layout recreation.” “Publication-ready” becomes clearer when the quote names the file type, intended use, treatment of graphics, and whether a reviewer will check the final proof.
The ATA’s large-project quoting guidance recommends settling whether third-party review is included. Some clients want a publication-ready result; others only need a draft for internal editing. The guidance also treats proof review as an explicit scope question because typesetting can introduce language-specific errors.
A second failure point is assuming that basic formatting and DTP mean the same thing. Preserving headings and lists in an editable document may be a different task from rebuilding a designed page with images and adjusting it for publication. The source materials can help show where the boundary lies: ask the agency to describe what it will preserve, what it will recreate, and what it will return as separate material.
A third problem is checking only the text or only the layout. A translation can read correctly in a bilingual table but become difficult to read after placement. Conversely, a page can look polished while a number, name, or phrase has been carried over incorrectly. The ATA recommends checks of both the final text and final layout in its technical-project guidance.
Scan-based work needs extra care. A scan is an image, not an editable text document, so the team must read the text before translating or rebuilding the page. Printed text, stamps, signatures, and handwritten notes may not be equally clear. If the scan is poor or the source contains handwriting, ask how uncertain text will be flagged and who will compare it with the original.
A fourth risk is treating a process label as proof of a particular deliverable. ISO 17100 describes translation-service processes and applicable specifications; the EVS listing doesn’t define one universal file format, DTP package, or final-proof check. The client still needs to agree on the actual target artifact and acceptance criteria.
The standard also has a specific boundary around machine translation. The EVS listing says raw machine-translation output plus post-editing is outside ISO 17100:2015’s scope. ISO 18587:2017, by contrast, is described on the ISO page as applying to full human post-editing of machine-translation output. Ask which service is being quoted instead of assuming that a standard name tells you the production method.
A short scope checklist can prevent avoidable back-and-forth:
- Purpose: internal review, submission, online publication, print, or another defined use.
- Target artifact: editable text, bilingual table, formatted Word file, PDF, or another named output.
- Visual content: how images, tables, graphics, captions, links, and page breaks should be handled.
- Language checks: translation, bilingual revision, monolingual review, proofreading, or a stated combination.
- Final proof: whether the provider checks the text after typesetting.
- Special requirements: certification, notarization, audience, tone, terminology, and any relevant deadline.
The ATA recommends sharing source and target languages, deliverables, audience, tone, start date, and turnaround time for each team in its project-preparation checklist. For a quote, send the source file and a description of the intended finished file when possible. If the final format differs from the source, say so directly.
The useful question isn’t simply, “Does the agency deliver a client-ready document?” Ask what the recipient can do with the file on arrival, which checks have already happened, and which tasks remain with your team. A precise answer makes it easier to compare quotes and prevents translated text from being mistaken for a finished publishing job.
FAQ¶
What does a translation agency deliver besides translated text?¶
Depending on the agreed scope, an agency may also provide an editable file, bilingual revision, monolingual review, formatting, desktop publishing, or a proof check. The quote should identify which items are included and what format the client will receive.
Does translation include formatting and desktop publishing?¶
Basic formatting may be included, but DTP is a separate production task when it involves adjusting or rebuilding a document’s layout for print or online publication. Specify the required file and visual work in the brief.
What should a client-ready translated document include?¶
A client-ready document should match the agreed purpose, audience, target format, layout, review level, and handling of visual elements. The phrase alone doesn’t establish a universal package.
How do agencies distinguish revision, review, proofreading, and DTP?¶
Bilingual revision compares source and translation for accuracy and completeness. Monolingual review focuses on clarity and suitability for readers, proofreading checks a specified text or proof, and DTP adjusts the layout for publication.
What should be specified in a translation project quote?¶
Name the target file and format, audience and tone, treatment of images and tables, language checks, certification needs, and whether the provider will check the final typeset proof. A quote should also make clear which production tasks remain with the client.