A clear translation brief is the cheapest way to improve the quality of any translation project, and yet most companies send their files with little more than a deadline and a target language. The translator then has to guess who the text is for, how formal it should sound and which terms the company prefers. Some guesses will be right. Others will lead to rounds of revisions that cost time, money and patience on both sides.

After years of watching projects succeed and stumble, I am convinced that the difference often comes down to the first email. Here is what a useful brief contains and how to put one together in less than half an hour.

What a translation brief actually is

A translation brief is a short document that tells the translator everything they need to know about the purpose and context of a text. It is not a contract and it does not need to be long. One or two pages are usually enough. Think of it as the conversation you would have with a translator if you sat down together for coffee before they started work.

Translation scholars have long argued that the purpose of a text shapes how it should be translated, an idea known as skopos theory and described in the Wikipedia article on translation. In practice, that means the same sentence may be rendered differently in a legal notice, a social media post and a technical manual. Without a brief, the translator cannot know which one you need.

The essentials every brief should cover

Start with the audience. Who will read the translation, in which country, and how much do they already know about your product or subject? A brochure for engineers in Munich needs a different register from a newsletter for retail customers in Vienna, even though both are in German.

Next, describe the purpose. Is the text meant to inform, persuade, instruct or meet a legal obligation? Marketing copy may need adaptation and creative freedom, while a safety instruction must be precise and literal. Say clearly how much freedom the translator has.

Then cover the practical details: target language and locale, deadline, file format, word count, where the text will be published and whether there are space limits. A translation for a mobile app button with a 20 character limit is a very different task from a white paper.

Terminology, tone and reference material

Consistency is where many business translations fall down. Your company probably has preferred names for products, departments and processes, and some words it never wants to see. Share them. A simple glossary in a spreadsheet, with approved translations where you have them, makes an enormous difference. This explanation of glossary and termbase creation shows how even a modest list grows into a valuable asset over time.

Larger organisations benefit from treating this as an ongoing process rather than a one-off list. Good terminology management keeps the same words in the same places across every document, website and campaign, which is exactly what readers notice when it is missing.

Tone matters just as much. Include a style guide if you have one, or at least a few lines describing your voice. Do you address customers formally or informally? Do you prefer short sentences? Are there examples of previous translations you liked, or disliked? Reference material, such as earlier versions, competitor websites or images that accompany the text, helps the translator see the bigger picture.

Who answers questions, and how fast

Even the best brief will not anticipate everything. Name one person who can answer the translator's questions and make sure they are available during the project. Nothing slows a translation project down more than queries that sit unanswered in an inbox for a week, while the deadline stays exactly where it was.

It also helps to agree on how questions will be handled. Some teams prefer a shared query sheet, others a short call. Translators and project managers discuss their favourite methods openly in communities such as r/TranslationStudies, and the consensus is clear: fast, decisive answers lead to better translations.

A simple template you can reuse

You do not need special software to start. Create a one-page template with the following headings and fill it in for each project: project name and contact person, source and target languages with locales, audience description, purpose of the text, tone and formality, key terms and words to avoid, reference material, format and layout constraints, deadline and delivery method, and review process. Save it alongside your files so that every new project begins with the same set of answers.

Once the template exists, update it whenever a project teaches you something. If a reviewer keeps correcting the same term, add it to the glossary. If a translation came back too formal, adjust the tone description. Over a few months, your brief becomes a living record of how your company wants to sound in every language.

Better input, better translation

Translators are skilled professionals, but they are not mind readers. A thoughtful translation brief turns a guessing game into a collaboration. It reduces revisions, keeps your terminology consistent and gives every reader, wherever they are, the impression that your company speaks their language naturally. Spend twenty minutes on the brief, and you will save hours on everything that follows.