A client sends an INDD file, asks for a translation, and wants a firm price before the working files have been checked. The title page looks simple, but the links are missing, the PDF shows a different revision, and nobody has said whether the quote includes a typeset deliverable. A price based on that email alone is a guess.
An InDesign translation quote is an estimate of the work required to translate content and return the requested files in an agreed condition. The quote depends on the editable source, the assets needed to inspect the layout, the languages, the text included, and the expected desktop publishing work. Clarifying those items before pricing makes the estimate easier to explain and reduces surprises after work begins.
This guide is for translation providers, project managers, and agencies who need to scope an InDesign job before committing to a price or schedule. The goal isn’t to make every client fill in a long form. The goal is to ask a small set of specific questions that reveal whether the project is ready to quote.
Start by separating translation from layout work¶
A client may use “translate the InDesign file” to mean several different things. One client may want translated text returned for an in-house designer to place. Another may expect a translated, adjusted layout and a print-ready PDF. Those are different scopes, even when they begin with the same file.
Translation work covers the linguistic content: identifying the text to translate, translating it into the requested language, and returning it in the agreed format. Desktop publishing, often shortened to DTP, covers work on the page layout, such as placing translated text, adjusting text frames, and checking the resulting pages. A project can include either task or both.
Ask the client to choose what they expect from the quote:
- Translation only, with the translated content returned in the agreed exchange format.
- Translation plus importing or placing the translated content in an InDesign file.
- Translation, layout adjustment, and a visual check of the completed pages.
- A final package that includes an editable source file, a PDF, or both.
The list isn’t a substitute for inspecting the materials. It gives the client useful language for describing the outcome, and it makes scope differences visible before anyone starts work.
A translated file doesn’t automatically mean that the layout has been checked. A text workflow can extract and return content without resolving a full page’s visual problems. If your price includes layout adjustment or visual review, name that work in the estimate. If it doesn’t, say who will do it and what file you will deliver.
Ask what “finished” means in practical terms. Should all translated text be in the InDesign project? Should the client receive a translated IDML, an updated INDD, a PDF for review, a print-ready PDF, or a combination? The answer affects the work and the handoff. Adobe’s package guidance is a useful reference for discussing project files intended for output.
Make the estimate specific enough to compare¶
A useful estimate names what it includes, what it assumes, and what falls outside its scope. For example, the estimate might cover translation of editable text, return in IDML, and one visual review of the supplied PDF, while excluding text that is part of a placed image. The wording should match the actual service offered, not a generic promise to “handle the InDesign file.”
Separate linguistic review from layout review. A translator checking whether a sentence is accurate isn’t necessarily checking whether every page has acceptable spacing. A DTP operator checking a page layout isn’t necessarily reviewing translation choices. If both kinds of review are required, identify them separately.
State what happens if the files don’t match the brief. If the client later supplies a new revision, extra languages, additional sections, or image-editing work, the estimate may need to change. A clear scope gives you a fair way to discuss those changes instead of trying to absorb them silently.
Kevin Lossner, a translation technology practitioner, explains the format issue in his account of InDesign translation workflows:
“Unfortunately, most translation environments cannot handle the current native InDesign format (INDD). Instead, the IDML is used in most translation scenarios.”
That observation doesn’t mean every provider should demand the same format. It means you should ask which workflow the provider will use and what exchange file that workflow needs. Don’t promise a particular handoff until you’ve checked the source and the tools involved.
Request the right source files and visual references¶
The first file question is whether the client has an editable InDesign project. A PDF can show the page as a reader sees it, but it isn’t the same as an editable InDesign source. If the client has only a PDF, treat that as a different workflow and ask what editable material, if any, is available.
Ask for the native INDD file and, when your translation workflow needs an exchange format, an IDML export. INDD is InDesign’s native document format. IDML is an interchange format used in many translation scenarios, but compatibility can depend on the software and features used in the project. Adobe’s documentation on saving IDML notes that converting documents for compatibility may not preserve every newer feature. Confirm that the provider can open and handle the supplied material rather than assuming the extension settles the question.
A practical request might say: “Please send the INDD source and an IDML export if available. Let us know which InDesign version created the file, and tell us whether the document uses features that must remain unchanged.” The client doesn’t need to know the technical details of every feature. The request makes the compatibility check explicit.
Ask for a current PDF of the source layout as well. The PDF gives the translator, reviewer, or DTP operator a visual reference for page composition and the position of text. It can also help identify headings, captions, notes, and content that may not be obvious from a plain text extraction.
A PDF reference needs a status. Ask whether it shows the approved source content or only the intended design. If the PDF and editable file contain different text, the team needs to know which one controls. A PDF from an older revision can lead reviewers to flag valid changes as errors or miss content that appears only in the current source.
Lossner points out why visual context is useful in the same translation workflow article:
“And even if an IDML file is received, translators usually benefit from a look at the original layout in a preview or a PDF, that is often forgotten”
A PDF doesn’t replace the editable file, and an IDML doesn’t replace the PDF reference. Each answers a different question: the editable file supports the project workflow, while the PDF helps people understand the original page design.
Ask for a package, not just a document¶
InDesign documents can refer to assets stored separately. A placed graphic may remain linked to its original file outside the InDesign project. Adobe describes that behavior in its tutorial on sharing InDesign projects. If a client sends only an INDD file, the layout may refer to graphics that the recipient hasn’t received.
Ask whether the client can provide a packaged project or send the linked graphics and fonts separately. Adobe’s package workflow gathers a copy of the document and, where applicable, necessary fonts and linked graphics. The Adobe tutorial on sharing projects explains how those parts fit together.
A package still needs checking. Confirm that it includes all the files for the sections being quoted, rather than only one document from a larger book or campaign. Ask whether linked graphics live in another folder and whether the project contains multiple documents or book sections. A client may use “the file” to describe a folder of related components, so ask for the whole handoff in concrete terms.
Fonts need their own question. Ask whether the required fonts are included, activated through Adobe Fonts, or unavailable and in need of an agreed substitute. Adobe’s sharing tutorial notes that fonts may need to accompany a project, while Adobe Fonts can prompt collaborators to sync them. Font access can affect what a recipient sees when opening or rendering a document, so don’t leave the assumption unstated.
If the client can’t share a font, agree on what happens next. A substitute might change text fit or appearance, so a decision about replacement can affect visual review and layout work. Don’t tell the client that a substitute is harmless before the document has been checked.
| Ask for | What it helps establish |
|---|---|
| INDD source | Whether the native project is available for inspection or later layout work |
| IDML export, if your workflow needs it | Whether the content can enter the planned translation workflow |
| Current source PDF | What the intended source layout looks like |
| Linked graphics | Whether the recipient can see the complete project |
| Fonts or a font plan | Whether the layout can be viewed with the intended typography |
| Full project or book sections | Whether the quoted material covers all relevant files |
The table is a request checklist, not a claim that every job needs every file. A translation-only project may not need the same handoff as a job that includes rebuilding or adjusting the layout. Ask for the materials that match the work you are quoting.
Define exactly what content is in scope¶
A document’s text count isn’t the same as the full amount of text a client may expect to translate. Text can appear in the main story, a caption, a chart, a figure, a placed graphic, or a hidden layer. The file name doesn’t tell you which items the client considers part of the assignment.
Ask the client to identify everything that must be translated. That can include:
- Main body text, headings, captions, and footnotes.
- Tables, charts, labels, callouts, and text in figures.
- Text inside placed images or other graphics.
- Hidden layers, optional sections, and content marked for later use.
- Repeated elements such as running headers, footers, or navigation labels.
A placed image needs particular attention. Text embedded in a graphic isn’t necessarily editable as InDesign story text. Extracting it, translating it, and recreating or editing the image may be separate work. The ProZ discussion on questions to ask about INDD files raises embedded graphic text as a scope issue. Ask the client to mark these items or confirm that they are out of scope.
Check whether the file has hidden layers or alternate content the client hasn’t mentioned. A designer might keep superseded text or optional language elements in the project. Don’t assume every piece of visible or stored text belongs in the translation. Ask which sections are approved, which are for reference, and which should remain untouched.
Confirm the target language or languages before quoting. A request for “translation” isn’t complete until the client names the destination language and confirms whether the same content is needed in more than one language. The translation workflow article describes target language as part of the project brief. Treat each requested language as a scope decision, not an assumption based on a previous job.
Ask for any existing translations, terminology, style instructions, or reference documents. A translation memory or approved terminology list can help the team maintain consistency, but the client needs to say which source takes priority if references conflict. Ask whether names, product terms, legal phrases, or recurring labels must follow an established spelling.
The client may expect you to translate text in figures but not modify the graphics. Another client may want every translated label rebuilt and placed in the artwork. Both requests can be reasonable; they simply describe different work. Write down the difference before you estimate.
Clarify the source of truth¶
Projects sometimes arrive with an editable file, a PDF, a Word document, and a spreadsheet of approved text. Ask which source is authoritative. If a client says the PDF is the approved version but the InDesign file is the editable source, confirm how you’ll handle differences between them.
A practical question is: “If the PDF and InDesign source don’t match, which version should we follow, and who can approve a change?” The question gives the project a decision route before conflicting text appears during production.
Ask who can answer questions and approve the translated content. A project manager may coordinate the files while a subject-matter reviewer approves terminology. Knowing who has authority helps prevent comments from different reviewers turning into unplanned revision cycles.
Confirm the deliverables, layout work, and review¶
Once the source and content are clear, confirm what the client expects to receive. A translated IDML or INDD file, a review PDF, and a final PDF are not interchangeable deliverables. Ask which files are required and whether the client expects an editable project as well as a PDF.
Some useful questions are:
- Does the client need a translated IDML, an updated INDD, a PDF, or more than one format?
- Should the provider place the translated text into the layout?
- Does the quote include adjustments to text frames or other page elements?
- Should someone inspect the translated pages visually?
- Is the PDF for review or intended as the final output?
- Who approves the layout and linguistic content?
A visual review can look for text that no longer fits, awkward spacing, or differences from the intended source layout. The review should have a defined purpose. A quick check that the file opens is not the same as a page-by-page review of the output.
Ask whether the provider must change the design or only preserve it as far as possible. A translated passage can take more or less space than its source, which can affect text frames and page composition. Don’t promise that every layout will remain identical after translation without inspecting the material and agreeing what adjustments are in scope.
Specify how the client wants feedback handled. Should comments go into a PDF, a tracked review document, or a single consolidated list? Who resolves conflicting comments? A clear review route helps distinguish a correction from a request to revise approved content.
Set revision boundaries¶
A quote should say what triggers a change in scope. Examples include a new source revision, added target languages, missing graphics supplied after work begins, or a request to translate text in images that wasn’t included in the original brief.
Don’t treat all client feedback as the same kind of work. A correction to a translation, a change to approved source content, and a new request to redesign a page may require different handling. State how the client should report each type and who decides whether it changes the estimate.
The wording can stay simple: “The quote covers the files listed and the deliverables named here. If the source, languages, or requested output changes, we’ll confirm the effect on scope before proceeding.” That statement sets a useful boundary without turning the conversation into contract language.
Name what the quote doesn’t include¶
An estimate is clearer when it identifies exclusions. Depending on the project, exclusions could include editing text embedded in graphics, providing unavailable fonts, reconstructing missing layouts, translating hidden content, or producing a print-ready PDF. Don’t list exclusions that don’t apply just to make the quote look thorough. Use the list to make the actual boundaries visible.
The client should also know what happens if the supplied file can’t be opened or if the package is incomplete. You might need a corrected IDML export, an updated package, or a decision about a substitute font. A quote can be conditional on receiving files that open and contain the expected assets. If you need to inspect the files before giving a firm price, say so plainly.
Build the deadline around a complete handoff¶
A requested delivery date is only one part of the schedule. Ask when the complete, approved source package will be available, when the client needs a review version, and when final files are due. If the materials arrive in stages, confirm which files are ready and which are still pending.
A working schedule can name the key events without inventing a duration:
- Client supplies the editable source, reference PDF, assets, and brief.
- Provider checks the files and confirms that the planned workflow can use them.
- Client answers questions about scope, source revisions, and terminology.
- Translation and any agreed layout work take place.
- Client reviews the agreed draft or PDF.
- Provider applies approved corrections and returns the named deliverables.
The schedule needs a start condition. If the quote assumes that the complete package is ready, say when work starts and what happens if files or approvals arrive later. An incomplete handoff can block conversion or visual review, so a deadline that ignores file readiness isn’t a dependable commitment.
Ask whether the client has milestones. A launch date, print deadline, or internal review meeting may affect when the client needs intermediate files. Don’t promise a sequence you can’t support; instead, ask which dates are fixed and which can move if the source package changes.
Confirm whether the source content is approved. If the client expects text to change after translation starts, identify how those updates will be supplied and whether the estimate assumes a stable source. A late content revision can mean revisiting translation and layout decisions.
Use the proposed handoff to test the schedule. For example, if the client needs both a translated editable file and a final PDF, ask who will approve the PDF and whether that review is part of the quoted work. A deliverable that depends on client approval needs room in the plan for that approval step.
Catch the common quoting mistakes before they become rework¶
The costly errors often come from a reasonable assumption that nobody checked. A client says “InDesign file,” and the provider assumes the package includes links. The provider receives an IDML and assumes it can be opened with the intended workflow. The PDF looks complete, but it shows a different revision. Each assumption can change what the quote actually covers.
Quoting from INDD alone¶
An INDD file may not be directly usable in the provider’s CAT environment. A CAT tool is software for computer-assisted translation; it helps a translator process and manage source content. Ask whether the planned workflow needs IDML and request an export if it does. Confirm that the chosen InDesign and CAT-tool combination can handle the material before accepting a file-based commitment.
Treating IDML as a complete project package¶
IDML can support an exchange workflow, but the file may not include every asset needed to inspect or reproduce the layout. Request the relevant linked graphics, fonts or a plan for supplying them, and a PDF reference. Adobe’s explanation that placed graphics can remain linked to files outside the document is a reminder that an editable file and a complete project handoff aren’t always the same thing.
Assuming a PDF is the source file¶
A PDF can help with visual reference, but it doesn’t replace an editable INDD or IDML workflow. If the client has only a PDF, ask what editable source exists and whether the requested work can be done from the materials available. Don’t quote a native-file workflow based on a visual reference alone.
If only a PDF is available, the separate guide on translating a PDF without the InDesign source file can help explain the difference between a reference document and an editable source. The scope and deliverables still need to match what the client actually has.
Forgetting text inside images¶
A quote based on editable story text can omit labels baked into graphics. Ask the client to identify those items and decide whether they need translation, extraction, image editing, or no action. The ProZ discussion about questions for clients with INDD files is a source for this scope distinction.
Promising a finished PDF without defining review¶
A translated source file doesn’t automatically include a checked final PDF. Name who exports the PDF, who checks it, and whether layout review is included. If the client needs a final print-ready file, include that deliverable explicitly rather than relying on “finished files” as a vague phrase.
A related formatting QA checklist for translated files can help define what a review should look for. The key is to agree on the check before pricing it.
Starting before the source revision is settled¶
A client may send an editable file and a PDF with differences. Ask which one controls and who can approve changes. If the client expects you to reconcile the versions, include that work in the scope rather than assuming it will take care of itself.
The ProZ discussion provides a concrete reminder that project components and scope questions can be easy to miss: a client may send an INDD and PDF reference while the package still needs links and fonts. Use the forum thread as a prompt to check the handoff, not as a reason to assume every project has the same missing files.
A second client example makes the file distinction visible: an Adobe community discussion describes a handoff with INDD and IDML alongside separate font and source-image folders. The discussion of keeping IDML reinforces that project components may be delivered separately. Ask what the client has and what your workflow requires; don’t infer a complete package from a file extension.
FAQ¶
What files should a client send for an InDesign translation quote?¶
Ask for the editable InDesign source, an IDML export if your workflow needs one, and a current PDF reference. Request the linked graphics and fonts or a packaged project, plus any instructions or terminology that define the assignment.
Should I ask for INDD or IDML files for translation?¶
Ask which file format the provider’s workflow can handle. INDD is the native InDesign format, but many translation environments use IDML as an exchange format; check the planned InDesign and CAT-tool workflow before quoting.
Why do translators need a PDF as well as an InDesign file?¶
A PDF provides a visual reference for the source layout, so a translator or reviewer can see text in context. The editable InDesign file supports the translation or layout workflow; the PDF doesn’t replace it.
What details should be confirmed before quoting InDesign DTP and translation?¶
Confirm the target languages, the content in scope, whether the quote covers translation, DTP, visual review, or a combination, and the deliverables the client expects. Also clarify source-file readiness, milestones, approval responsibilities, and the deadline.
How do fonts and linked images affect an InDesign translation quote?¶
Missing fonts can affect how a document appears when opened, while missing linked graphics can leave parts of the layout unavailable. Ask how the client will provide these assets and whether any text embedded in graphics needs separate work.
Can I quote an InDesign translation job from a PDF alone?¶
A PDF can serve as a visual reference, but it isn’t the same as an editable InDesign source. Ask whether an INDD or IDML file exists and confirm what work can be done with the files the client can supply.
Should the quote include a print-ready PDF?¶
Include a print-ready PDF only if the client requests it and your scope covers producing and checking that output. State whether the client will receive an editable translated file as well, because one deliverable doesn’t imply the other.