Translation Brief Template: What to Include Before Sending Content to a Translator
Translation ServicesTranslation TemplatesLocalization WorkflowProject ManagementContent Preparation

Translation Brief Template: What to Include Before Sending Content to a Translator

LLingua Bridge Editorial Team
2026-11-21
7 min read

Use this translation brief template to give translators clear instructions on language, audience, tone, terminology, files, deadlines, review, and privacy.

A strong translation brief gives a translator the information needed to make accurate decisions before work begins. Use this practical template to define languages, audience, tone, terminology, files, deadlines, review arrangements, confidentiality, and localization needs—then revisit it whenever the content or project conditions change.

Overview

A translation brief is a short project document that explains what is being translated, who will read it, where it will appear, and what the finished work must achieve. It is useful for a single document, a website section, product content, subtitles, internal communication, or an ongoing multilingual content program.

The brief does not need to be long. It needs to remove guesswork. A translator may otherwise have to infer whether a phrase should sound formal or conversational, whether a date should follow a regional convention, or whether a legal term must match language used in an existing document. Clear instructions reduce avoidable revisions and help everyone evaluate the translation against the same goal.

Before sending content, prepare the following core information:

  • Source language: State the language and, when relevant, the regional variety, such as British or American English.
  • Target language and region: Identify the language, country, audience, and preferred spelling or vocabulary conventions.
  • Purpose: Explain whether the content is for publication, legal use, software, marketing, education, customer support, or internal communication.
  • Audience: Describe readers by role, knowledge level, age group, location, or industry where those details affect wording.
  • Desired tone: Specify whether the translation should be formal, friendly, concise, technical, persuasive, neutral, or conversational.
  • Deadline and delivery format: Include the final deadline, milestones, file type, naming convention, and delivery location.

For official records, also state whether you need a certified translation, a signed statement, a particular layout, or supporting documents. Requirements can vary by receiving organization, so identify the intended recipient before work starts. For more background, see Certified Document Translation Services Explained.

What to track

Reusable translation brief template

Copy the checklist below into a project document and complete the fields that apply. Mark unknown items as “to be confirmed” rather than leaving them ambiguous.

  1. Project name and owner: Record the project title, requesting department, main contact, and backup contact.
  2. Source material: List the files, URLs, versions, word counts, page counts, or media durations. Identify any text that must not be translated.
  3. Languages: Name the source language, target language or languages, and regional preferences.
  4. Purpose and audience: Explain where the translation will be used and what readers should understand or do after reading it.
  5. Tone and style: Describe the desired voice. Add an approved example if one exists.
  6. Terminology: Supply a glossary of product names, technical terms, personal names, acronyms, preferred translations, and words that should remain in the original language.
  7. Formatting: State whether the translator should preserve headings, tables, links, tags, variables, line breaks, page design, character limits, or right-to-left layout.
  8. Reference materials: Attach previous translations, style guides, brand guidance, product documentation, screenshots, or parallel texts.
  9. Review process: Name the reviewer, define the number of review rounds, and explain how comments will be collected and approved.
  10. Delivery: Specify the required file format, folder, naming rules, tracked-change preferences, and whether a translation memory or glossary update is expected.
  11. Timing: Include the start date, draft milestone, review window, final deadline, and any launch or publication dependency.
  12. Privacy and access: Identify confidential, personal, financial, health, legal, or unreleased information. Explain approved storage and transfer methods.

Which details matter most?

Content typeHighest-priority brief detailsUseful additional guidance
Official documentsTarget authority, certification needs, names, dates, formatting, and deadlineProvide a clear scan and explain whether stamps, signatures, or handwritten notes must be translated.
WebsitesTarget regions, page purpose, SEO terms, links, metadata, and publishing systemNote character limits, image text, forms, accessibility labels, and language-specific navigation.
Product contentProduct terminology, user skill level, interface limits, variables, and safety wordingInclude screenshots and identify text that appears in software or packaging.
SubtitlesVideo duration, speaker identification, reading limits, time codes, and delivery formatFlag humor, cultural references, music lyrics, on-screen text, and accessibility requirements.
Business communicationAudience, relationship, purpose, tone, and sender identityExplain whether the message should sound direct, diplomatic, formal, or conversational.

For web projects, combine the brief with a localization review. The website localization checklist can help you track regional content, interface elements, and accessibility considerations. For long source files, a text summarizer may help create an internal project overview, but it should not replace the complete source material or the translator’s review.

Cadence and checkpoints

Treat the brief as a living project record rather than a form completed once and forgotten. Use these checkpoints:

  • Before requesting a quote or start date: Confirm the files, word count, language pair, purpose, audience, deadline, and required output.
  • At project kickoff: Check that the latest source version, glossary, style guide, and reference files are available. Resolve questions about ambiguous terms before substantial work begins.
  • Before review: Confirm who will review the translation and whether the reviewer understands the target audience and subject matter. Consolidate comments where possible.
  • Before publication or delivery: Check links, variables, numbers, names, headings, layout, metadata, and file integrity. For documents, compare the final layout with the source.
  • Monthly or quarterly for recurring content: Review new terminology, product changes, brand language, regional preferences, and unresolved feedback. Update the glossary and brief.
  • Every six months for digital workflows: Recheck file-format support, content-management integrations, translation-tool settings, access permissions, and export or import procedures.
  • Annually: Review privacy guidance, accessibility requirements, localization conventions, approval contacts, and the usefulness of the template itself.

Keep a simple change log with the date, change, owner, affected languages, and action required. This makes it easier to distinguish a genuine language update from a one-off correction.

How to interpret changes

Not every change requires a new translation project. Use the type of change to decide what to do next.

  • Source wording changed: Identify whether the change affects meaning, legal accuracy, tone, terminology, or only formatting. Send the changed passages and surrounding context, not isolated sentences alone.
  • A new market was added: Reassess regional vocabulary, date and number formats, units, currency, examples, imagery, and whether the current target-language variety is appropriate.
  • A term is used inconsistently: Decide on the preferred term, record it in the glossary, and review earlier content for the same product or concept.
  • Reviewers disagree: Return to the purpose and audience in the brief. Ask which option better serves the intended reader instead of treating personal preference as the only criterion.
  • Layout breaks after translation: Check expansion or contraction, font support, line breaks, directionality, embedded text, and character limits. This is a production issue as well as a language issue.
  • Confidentiality conditions change: Pause file sharing until approved access, storage, and transfer arrangements are confirmed. Remove unnecessary personal or sensitive information from working files.

Use measurable project notes where possible: number of files completed, terms added to the glossary, review rounds, outstanding questions, and rejected or approved changes. These records help improve future briefs without turning language quality into a single score.

When to revisit

Revisit the translation brief whenever the audience, channel, source content, target region, terminology, reviewer, deadline, or confidentiality requirement changes. For an active multilingual program, schedule a short monthly or quarterly review even when no problem has been reported. Small updates are easier to manage than a large terminology or formatting correction at the end of a release.

Before your next translation request, take these five practical steps:

  1. Duplicate the latest brief and label it with the project name, language, and source version.
  2. Replace assumptions with explicit instructions about audience, purpose, tone, and regional preference.
  3. Attach the current glossary, style guide, reference materials, and screenshots or context.
  4. Confirm the reviewer, review dates, delivery format, privacy needs, and final approval route.
  5. After delivery, record terminology decisions and recurring issues so the next brief starts with better information.

A clear brief is especially valuable when several people contribute to a project. For related workplace language guidance, see these professional English email templates and Business English presentation phrases. The goal is not to predict every translation decision; it is to give the translator enough context to make appropriate decisions consistently.

Related Topics

#Translation Services#Translation Templates#Localization Workflow#Project Management#Content Preparation
L

Lingua Bridge Editorial Team

Language and Translation Editors

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.