A translation brief is a project document that states the purpose, target audience, tone, terminology preferences, and practical constraints for a translation or localization assignment, such as file formats, deadlines, and style requirements. It is the reference point that translators, editors, and reviewers use to align decisions when the source text allows more than one acceptable rendering or when client-specific choices must override general convention.
Angel Translation editorial reference · Confirm the rendering against your source and approved project terminology.
Check source meaning → confirm the preferred term → record approved variants and references.
Translation briefs are used at project kickoff for marketing campaigns, product launches, e-learning modules, or regulated content. The brief may be summarized in a style sheet or a client portal entry, and project managers distribute it to all linguists so that tone and terminology stay consistent across the entire language set.
The most common error is starting translation with only the source files and no brief, then guessing at register, audience, or terminology; this creates rework when the client expects a different tone. Another error is writing a brief so vague that it says only "translate into French" without explaining whether the text is for consumers, patients, developers, or regulators.
Creative and consumer content needs accurate meaning as well as tone and context. Subtitles, interfaces and voice scripts also require checks for timing, character limits and pronunciation.
Provide approved terms and previous translations with the source files. Agree how variants, ambiguous wording and revisions will be reviewed. Terminology maintenance and any termbase handback are confirmed in the project scope. See the 8-step AI + expert workflow.
Employee-training video transcription and dubbing.
Read the published project →Brand documentation.
Read the published project →Published scope shows related industry experience; it does not confirm that this specific term was used or reviewed in the project.
Include the source and target languages, file types, intended use, deadline and any approved termbase. Agree handling before sending sensitive files. Acknowledged in 4 hours, quoted in 24.
Prepare an inquiry email →Content Globalization solutions →File handling →A glossary entry is not an official standard or evidence of regulatory acceptance. Confirm current requirements for your project separately.