Free template · No signup
A translation brief tells an AI system or a person what the content means, who it is for and what must stay true. Use this free template before sending an article, design, document or app string for translation.
Use this when a translator would otherwise have to guess the meaning of a short label, the promise behind a campaign or the person who should approve the result.
The sample is a fictional battery setup guide for Spanish-speaking customers in Mexico. Notice how the brief explains “charge” and names the finished screen to review. Replace the example with your own content; it is not an approved translation.
Edit the worked example. These fields are processed in your browser and are not sent to a Vitra server. Page analytics, if enabled, are separate.
Your handoff, ready to edit
Battery setup guide — help a new owner charge the device before first use.
First-time customers in Mexico; Spanish (es-MX).
The instruction appears beside a charging-port diagram. Charge means put power into the battery, not bill a payment.
Keep the fictional product name Luma One unchanged. Link the approved es-MX glossary. Use the agreed term for charging port.
Direct instructions in a friendly tone. Two lines beside the diagram; flag overflow instead of shrinking below the design's minimum font size.
Local language reviewer checks meaning; product owner checks the charging instruction; designer checks the final screen. Release only after all three sign off.
0 of 4 checks selected. This is not a quality score or release approval.
Free. No signup required. Markdown includes selected checks; CSV contains the editable fields. Changes are not saved after leaving or reloading this page.
For an app button, one screenshot and an explanation of the action may be more useful than a long brand document. For an insurance notice, the reviewer also needs the approved policy meaning and the jurisdiction. Add the context the job needs, not every document the company owns.
Tell the translator which sentences can be adapted and which claims must remain unchanged. A local idiom may improve a campaign, but it must not change an eligibility rule, a price or a product promise. If the source itself is unclear, resolve that before producing more language versions.
A brief for yesterday's offer may be wrong for today's asset. Name the source version, link the approved references and send changes back to the reviewer. Copying the brief into a workflow is useful only if the instructions remain attached to the content they describe.
When the job repeats
Connect the brief to Vitra TM, Vitra TB, glossary and style guidance, then route the result to human review.
Include the content's purpose, audience, locale, product context, approved terms, layout or format limits, and the review owner. Add source references that help resolve a real ambiguity.
Yes. Download Markdown for a readable handoff or CSV for a planning sheet. The files are general-purpose templates, not guaranteed import formats for a particular TMS.