What should I include in a translation brief when I only have a rough draft?
Quick answer
A rough draft can still support a useful translation brief. Explain what the message is for, who will read it, what readers should do or understand, and where or how it will appear. Add relevant context and any known preferences or limits. Mark missing information as questions or placeholders rather than guessing, and label the draft as working material—not approved text.
The question, the details, the next step.
I have a rough draft, but it’s incomplete and I’m not sure what a translator needs from me. What should I put in the brief?
You don’t need to polish the draft first. Explain the assignment around it and make uncertainties visible. Include:
- Purpose: Why are you sending the message—for example, to invite, explain, remind, or request something?
- Audience: Who is expected to read it? Describe only what you know.
- Desired action or understanding: What should readers do, decide, or take away?
- Context and placement: Where will the message appear, and what background do readers need?
- Known constraints or preferences: Note confirmed requirements for length, format, tone, terminology, or other details. Mark unknowns as “not specified.”
- Open questions: List decisions or confirmations still needed.
Attach the draft as a working version. Mark unfinished sentences or placeholders instead of silently completing them, so confirmed intent stays distinct from assumptions.
Could you show me how that works with an incomplete draft? Say I have a note about an event, but I haven’t settled every detail.
Here’s a hypothetical example; bracketed details are placeholders, not facts to copy.
Translation brief — working version
- Purpose: Invite people to an upcoming community event.
- Audience: [Who is this for? Confirm whether it is for current participants, prospective participants, or both.]
- Desired action: Readers should [register / save the date / contact the organizer / other: confirm].
- Context and placement: It will appear in [email / printed notice / webpage / other: confirm]. Add any background readers need: [confirm].
- Draft status: Rough draft attached. Event name, date, location, and registration details are not confirmed. Bracketed text is not final.
- Known constraints or preferences: [Add confirmed requirements, or write “not specified yet.”]
- Open questions: See below.
Draft fragment: “Join us for [event name] on [date]. More details soon. [How to take part?]”
This brief explains the purpose without treating missing event details as settled. Update the placeholders when you have confirmed answers.
How should I handle questions I can’t answer yet? I don’t want the brief to become a long list of guesses.
Keep the list short and focus on questions that could change the assignment or the final message. Make each question answerable, and name who can confirm it if you know. For the hypothetical event note:
- What are the confirmed event name, date, and location? Status: awaiting confirmation from [person/team].
- What should readers do? Is there a confirmed deadline or method? Status: undecided.
- Where will the message appear, and is there a length or format limit? Status: awaiting confirmation from [person/team].
Don’t fill gaps with plausible-sounding details. Mark unknown preferences “not specified.” If you have a tentative preference, label it as tentative and say who can confirm or change it.
What’s a quick way to check my brief before I send it, especially if the draft may change?
Read the brief alongside the draft. Check that they agree about the assignment, that placeholders are clearly marked, and that open questions identify what remains undecided. You can use this compact template:
Purpose: [Why this message is needed] Audience: [Who should read it] Reader takeaway or action: [What they should understand or do] Context and placement: [Where it appears; relevant background] Confirmed constraints or preferences: [Details you know, or “not specified”] Draft status: [Rough / working / approved; note unfinished parts] Open questions: [Question — who can confirm — status]
If the draft changes, update the brief when its purpose, audience, action, context, or constraints change. Unresolved questions can remain open; make them visible so they aren’t mistaken for settled instructions.
A practical checklist
State the message’s purpose clearly.
Describe the intended audience without guessing.
Name the action or understanding readers should take away.
Add relevant context, placement, and confirmed constraints; mark unknowns.
Label the draft’s status and unfinished sections.
List open questions that need a decision or confirmation.
A few more useful answers
Should I finish the draft before I write the brief?
No. A rough draft is enough to describe the purpose, audience, intended action, and known context. Label unfinished or uncertain text so it is not mistaken for approved content.
What if I don’t know the audience or preferred tone yet?
Mark the information as not specified and add a direct question if it needs a decision. Don’t invent an audience description or present a tentative preference as confirmed.
Should I include every question I have about the draft?
Include questions that affect the assignment or a reader-facing detail. Keep minor editing uncertainties separate from decisions that need confirmation.