TRANSLATION PROJECT GUIDANCE

How to Write a Translation Brief

A translation brief gives linguists and reviewers the context needed to translate accurately. Use this guide to document project requirements before files enter production.

Translation brief
AudienceProduct users
Target localeses-MX · fr-CA
Reference materialApproved glossary ✓
Protected variablesRecorded ✓
Review ownershipAssigned ✓

Key Takeaways

  • A useful brief specifies the audience, purpose, target locales, and where the translation will be used—not just a language pair.
  • Document fixed terminology, protected content, reference materials, and the required output format before translation begins.
  • Name a final decision-maker for terminology questions, in-country feedback, and release approval.
  • Keep one approved version of the brief and record changes that affect scope, timing, or the meaning of the content.

Define the Audience, Purpose, and Publication Context

A translation brief is the document that tells translators what the source file alone cannot tell them. It identifies who will read the translated material, what those readers need to do, and where the finished content will appear. A paragraph written for an internal engineering team may use technical shorthand that is inappropriate for a customer help page. An employee policy may need a consistent formal register, while an app notification may have only a few words in which to communicate an action.

Start by recording the business purpose, document owner, and target users. Specify whether the material is informational, contractual, instructional, promotional, or safety-related. Identify the distribution channel: website, packaging, training system, support center, regulatory submission, product interface, or controlled document repository. These details influence tone, term selection, length constraints, layout, and review requirements.

Write target locales, not only languages. “French” may be insufficient where the audience is in Canada rather than France. “Portuguese” may require Brazilian or European language conventions. If a market spans several locales, record the intended variation and the reason for choosing it. Include any accessibility or readability requirements relevant to the audience.

ILLUSTRATIVE SCENARIO

Illustrative example: the same sentence for two audiences

Imagine the source sentence “Reset the controller before restarting.” In an internal maintenance procedure, the instruction may need an equipment identifier, a defined reset sequence, and a reference to the safe operating state. On a customer-facing help page, the same words may require a plain-language description of the control and a screenshot. A translator cannot reliably choose between those readings from the sentence alone.

A useful brief therefore includes an audience profile and a short explanation of what a reader must do after reading the text. If product screenshots are available, identify the relevant screen or document section. When a term has an approved technical meaning, include the glossary entry rather than expecting a reviewer to resolve it at the end.

Before sending the files, ask one practical question: could someone unfamiliar with this project distinguish a product identifier, an interface label, and an ordinary English word? If not, annotate those examples in the brief.

Identify the Files and the Deliverables

List the source files and their version identifiers, and identify which elements require translation. Source files may contain screenshots, footnotes, comments, hidden spreadsheet tabs, subtitles, embedded diagrams, or variables. These are easy to overlook when only the visible page is described in the request.

Brief field Example entry Why it matters
Project purpose Help-center article for product setup Establishes audience and tone
Source version Product Guide v3.2, approved 4 Nov Prevents translation of obsolete drafts
Target locales Spanish (Mexico), French (Canada) Defines regional conventions
Content included Main guide, callouts, UI strings, alt text Prevents omissions
Content excluded Internal reviewer comments, test IDs Avoids unnecessary changes
Final deliverables Editable DOCX and formatted PDF Defines formatting and handoff
Acceptance owner Product documentation lead Identifies who approves release

Clarify whether the final output must preserve layout, remain editable, include a certification statement, or support reuse in a content management system. If the project includes artwork or desktop publishing, attach the original editable assets and fonts where licensing permits. If only a PDF is available, state that explicitly so extraction or reconstruction can be scoped before production.

Record Terminology, Style, and Protected Content

Approved glossaries, earlier publications, brand style guidance, and translation memories are not optional decoration. They allow the linguist to distinguish a preferred product term from an otherwise reasonable synonym. Name the approved reference and its current version. If terminology is still being decided, identify who will resolve questions and how the decision will be documented.

Some source content must not change. Examples include product identifiers, part numbers, embedded placeholders, formulas, link targets, certain software keys, and legally defined names. Describe these in the brief rather than relying on the translator to recognize every exception. When a product name is localized in some markets but retained in others, specify the rule by locale.

Useful instruction: “Keep ${account_id}, {count}, and the product code AX-210 unchanged. Translate surrounding text and apply locale-appropriate number formatting only where the application supports it.” A rule like this is more actionable than “Preserve technical accuracy.”

Define the desired register in concrete terms: formal or conversational, second-person or third-person, preferred form of address, capitalization of product features, treatment of acronyms, and any plain-language requirements. Supply two approved examples if tone is difficult to describe.

Explain the Review and Approval Workflow

A brief should say what “reviewed” means for the particular project. The translator may check accuracy and consistency; an in-country marketing reviewer may assess local phrasing; a product engineer may verify technical behavior; a legal owner may approve an obligatory disclosure. These responsibilities should not collapse into a single vaguely defined “review” stage.

Document who comments, who consolidates competing feedback, and who makes final decisions. If two regional reviewers disagree, determine whether the issue is terminology, local preference, technical meaning, or a source-content ambiguity. Establish the escalation owner before comments arrive. Set a deadline for feedback and identify whether it will be supplied directly in the working files, through a review portal, or in an agreed comment log.

For recurring work, record how accepted changes enter the terminology glossary and translation memory. The brief can then be reused for future releases without restarting the same style and terminology discussions.

For projects managed with Stepes, the same brief can guide language-team instructions, terminology review, and delivery checks. The important starting point is a single approved source of instructions—not a collection of conflicting reviewer emails.

Translation Brief Template for a New Project

The following fields provide a practical starting point. They can be copied into a procurement request, project intake form, or translation brief document.

Section Information to supply
Project identity Project name, business owner, document version, planned publication date
Business context Audience, market, purpose, channel, user action, content sensitivity
Languages Source language, target locales, any locale fallback rules
Content inventory Files, formats, word counts if known, embedded media, exclusions
Quality requirements Subject matter, error impact, reviewer level, acceptance criteria
Language assets Translation memory, glossary, style guide, prior approved samples
Protected elements Tokens, variables, identifiers, URLs, trademarks, formulas
Production format Editable source, layout rules, subtitling or DTP needs, final output
Review workflow Linguistic reviewer, in-country owner, technical/legal approver, feedback path
Timeline Source freeze, translation delivery, review window, final handoff

A field should not be invented merely to complete a form. If a decision is genuinely pending, assign an owner and deadline; otherwise the uncertainty will reappear as rework later.

Handle Changes After Translation Begins

Translation programs often change because product terminology is updated, a legal clause is revised, screenshots are replaced, or a source author corrects an ambiguous sentence. Treat the source version as a controlled input. When the source changes, identify exactly which content has been added, removed, or altered and what this means for already translated versions.

Do not silently overwrite an approved reference. Record the change and ask whether it affects target languages already in review, the layout, the requested deadline, or budget assumptions. For large structured files, a change log tied to stable identifiers helps isolate updates and protect approved translations that remain unchanged.

A brief should also distinguish required changes from subjective preferences. For example, correcting the wrong dosage instruction is not equivalent to replacing a valid local expression with a preferred synonym. Clear change categories prevent reviewers from debating issues that have different business consequences.

Preflight Checklist Before Sending the Brief

Frequently Asked Questions

Is a translation brief necessary for a small project?

Yes, but it can be short. A single-page brief identifying audience, target locales, protected terms, file format, and approval owner can prevent more questions than its preparation requires. The level of detail should reflect the complexity and risk of the content.

How is a translation brief different from a project plan?

A project plan coordinates resources, milestones, budget, and ownership across the project. A translation brief concentrates on the instructions and context required to produce the correct target-language content. The two documents should agree, but they answer different questions.

Should each language have a separate brief?

Use a shared core brief for common requirements and add locale-specific notes where terminology, legal wording, design constraints, or reviewer responsibilities differ. Avoid creating ten independent copies that may drift apart as source instructions change.

Who should approve the brief?

The content owner should confirm the business purpose and source materials. Subject-matter, regulatory, legal, design, or product owners should approve the specific requirements within their responsibility. A localization project manager can consolidate the final approved version.

Prepare a Translation Brief for Your Project

Share your approved source, target locales, document types, terminology references, and required deliverables to define a translation scope.