Every translation project starts the same way: a client sends over their files and says, "Please translate this into Swahili." And then the questions begin.

Who's the audience? Tanzanian professionals or a pan-East African consumer market? What's the tone — formal government communications or casual social media? Is there existing terminology we need to match? What format do you need the final files in? When do you need it?

These aren't annoying questions. They're the difference between a translation that hits the mark on the first draft and one that requires three rounds of revisions.

A translation brief answers all of these questions upfront. It takes about 20 minutes to write, and it will save you days of back-and-forth, reduce your costs, and produce dramatically better results.

Here's how to write one that actually works.

What Is a Translation Brief?

A translation brief is a short document that gives your translator everything they need to understand the project before they start working. Think of it as a creative brief, but for language work.

It covers the practical details — source language, word count, deadlines — and the strategic context that shapes how the translation should read. Who will read this? What action should they take afterward? What does your brand sound like?

Without a brief, your translator is guessing. And guessing costs money.

Why a Good Brief Saves You Time and Money

I've translated hundreds of projects over the past decade. The correlation between brief quality and project success is almost perfect. Here's what happens with and without one.

Without a brief:

The translator makes assumptions about tone and audience
You receive the first draft and it doesn't match your expectations
You send feedback, the translator revises
Second draft is closer, but terminology doesn't match your existing Swahili content
Another revision round
Three weeks later, you have a final version — and you've paid for the revision time

With a brief:

The translator understands your audience, tone, and terminology from day one
First draft is 90% aligned with your expectations
Minor adjustments in one revision round
Done in half the time, at lower total cost

A 20-minute investment in writing a brief typically eliminates at least one full revision cycle. For a large project, that can save thousands of dollars.

The 10 Essential Elements of a Translation Brief

Every translation brief should cover these ten areas. You don't need to write pages for each one — a sentence or two is usually enough.

1. Source and Target Languages

This seems obvious, but specify exactly. "English to Swahili" is a start, but which variety of Swahili? Standard Swahili (Kiswahili sanifu, based on the Tanzanian standard) is appropriate for most professional and business contexts. If you need a specific regional variety — Kenyan Swahili for a Nairobi-focused campaign, for example — say so explicitly.

Also specify the source language variant. British English and American English can lead to different translation choices.

2. Target Audience

Who will read this translation? Be specific.

"Tanzanian consumers aged 25-40 who use mobile banking" is useful.
"Swahili speakers" is not useful.

The audience determines everything: vocabulary level, formality, cultural references, even sentence length. A legal document for Tanzanian corporate attorneys reads very differently from a health education pamphlet for rural communities.

3. Purpose and Context

What is this content for? What action should the reader take after reading it?

A product description aims to drive purchases. A safety manual aims to prevent injuries. A marketing email aims to generate clicks. Each purpose demands a different translation approach — even for the same source text.

Also explain where the translation will appear. A billboard has different constraints than a website, which has different constraints than a printed manual.

4. Tone and Style

Describe the voice you want in the target language. Useful descriptors include:

Formal vs. conversational: Government communications require formal Swahili. Social media posts work better in a conversational register.
Technical vs. accessible: Are you writing for specialists who know the jargon, or a general audience who needs concepts explained?
Authoritative vs. friendly: A bank's terms of service should sound authoritative. A health app's onboarding flow should sound friendly and encouraging.

If you have a brand voice guide, share it. Even if it's in English, it helps the translator understand your brand personality.

5. Glossary and Terminology

If you have existing Swahili content, share the terminology that's already been established. Consistency matters enormously in professional translation.

Provide any of the following:

Previously translated documents in the same domain
A terminology list or glossary (even a short one)
Brand names, product names, or terms that should NOT be translated
Industry-specific terms and your preferred Swahili equivalents

If you don't have any of this, say so. A good translator will build a glossary as part of the project and share it with you for future use. At SwahiliBridge, we maintain client-specific glossaries across every project.

6. Reference Materials

Give your translator everything that helps them understand the context.

Style guides: Brand guidelines, writing standards, formatting rules
Previous translations: Past work in Swahili, even if done by someone else
Visual context: If translating UI strings, share screenshots. If translating a brochure, share the layout.
Competitor examples: "Here's how [competitor] communicates in Swahili. We want to be [similar/different] in these ways."

More context always leads to better translation. Don't hold back.

7. Word Count and Scope

Provide the total word count of the source material. If the project includes multiple files, break it down by file.

Note: Swahili text is typically 15-25% longer than the equivalent English text. If you have strict character or space limits (for UI elements, advertisements, or subtitles), flag them here. Your translator needs to know upfront so they can adapt the translation to fit.

8. File Formats

Specify what you're sending and what you need back.

Common scenarios:

Word document in, Word document out (most straightforward)
InDesign file in, translated InDesign file out (requires DTP skills)
JSON/XLIFF localization files (for software localization)
SRT/VTT subtitle files (for video and audio projects)
Plain text for CMS import

If you need the translator to work within a specific tool — a TMS like Phrase, memoQ, or Smartling — mention it. Not every translator uses every tool.

9. Deadline and Timeline

Be realistic and specific. "ASAP" is not a deadline. "By Friday, April 17 at 5 PM EAT" is a deadline.

A professional Swahili translator typically handles 1,500-2,000 words per day for careful, publication-quality work. Use that as a benchmark when setting expectations.

If you have a hard launch date, share it — along with any internal review steps that need to happen after translation. Working backward from the real deadline helps your translator plan appropriately.

10. Review and Approval Process

Explain what happens after the first draft is delivered.

Who will review the translation on your side?
Do you have an in-house Swahili speaker who will provide feedback?
How many revision rounds are included?
What's the process for submitting feedback?

Setting these expectations upfront prevents scope creep and miscommunication during the review phase.

Common Mistakes That Derail Translation Projects

Even with a brief, certain mistakes can undermine your project. Here are the ones I see most often.

Sending unfinished source content. If your English copy is still being revised, wait until it's final before requesting translation. Translating a moving target wastes everyone's time and budget.

Assuming the translator knows your industry. Even a specialist needs context. Don't assume that because someone translates legal documents regularly, they understand your specific legal framework. Provide background.

Skipping the glossary step. If you've been creating Swahili content for years without a glossary, you probably have inconsistencies you don't even know about. A new project is a good time to establish one.

Setting unrealistic deadlines. Rushing translation doesn't make it faster — it makes it worse. If you need something urgent, say so, but understand that rush fees exist for a reason and quality may require trade-offs.

Not providing visual context. Text in isolation is ambiguous. The English word "Save" could mean a button label, a financial instruction, or a conservation message. Screenshots and layout files eliminate these ambiguities.

Your Translation Brief Template

Copy and adapt this template for your next Swahili translation project. You can also submit it directly through the SwahiliBridge client portal.

PROJECT: [Your project name]

1. Languages: [Source language] to [Target language/variety]

2. Target audience: [Who will read this? Demographics, profession, location]

3. Purpose: [What is this content for? What action should the reader take?]

4. Tone and style: [Formal/conversational, technical/accessible, authoritative/friendly]

5. Glossary/terminology:

Existing glossary attached: [Yes/No]
Terms that must NOT be translated: [List brand names, product names, etc.]
Key terms with preferred translations: [List any you have]

6. Reference materials attached:

7. Scope:

Total word count: [number]
Number of files: [number]
File breakdown: [file name — word count — description]

8. File formats:

Source format: [format]
Required delivery format: [format]
Translation tool requirements: [if any]

9. Timeline:

Delivery deadline: [specific date and time with timezone]
Hard launch date: [if applicable]
Internal review time needed: [number of days]

10. Review process:

Reviewer: [name and role]
Revision rounds included: [number]
Feedback format: [tracked changes, comments, email]

Additional notes: [Anything else the translator should know]

How to Submit Your Brief to SwahiliBridge

You can share your translation brief with us in several ways.

Client portal: Upload your brief and source files through your SwahiliBridge portal account. This is the fastest way to get a quote and kick off the project.
Email: Send your brief as an attachment to the email listed on our contact page.
Consultation call: If your project is complex or you'd like help developing the brief, schedule a call and we'll build it together.

We review every brief within one business day and respond with a detailed quote, timeline, and any clarifying questions. The better your brief, the faster we can get started.

The Brief Is Where Good Translation Begins

I've worked on projects with budgets of $50 and projects with budgets of $50,000. The constant in every successful engagement is clear communication at the start. A translation brief isn't bureaucratic overhead — it's the foundation of a productive working relationship.

Take 20 minutes to write a proper brief before your next Swahili translation project. Your translator will thank you. Your budget will thank you. And your Swahili-speaking audience will receive content that actually works.

Mathayo Kapela is the founder of SwahiliBridge and a native Tanzanian Swahili linguist with over 10 years of professional experience in translation, localization, and transcreation for enterprise clients.

How to Write a Translation Brief for Your Swahili Project (Free Template)