Skip to content
An independent guide to international theatreMany cultures. A shared stage.
The InternationalistsTHEATRE ACROSS BORDERS

A GUIDE TO THEATRE ACROSS BORDERS

Translation & Multilingual Theatre

How to Write a Translation Brief for a Play Production

THE SHORT ANSWER

A translation brief for a play production is a written commissioning and collaboration document that sets out the source text, production context, desired language and cultural approach, deliverables, revision process, and credit or rights expectations. It should separate fixed requirements from negotiable artistic choices, be agreed with the playwright or rights holder and translator, and be revised as the production develops. The brief does not replace a translation agreement or grant rights.

At a glance Quick facts
Document type
Written commissioning and collaboration document for a play translation
Core purpose
Records source text, production context, language policy, deliverables, revision process and credit or rights expectations
First practical step
Establish the rights route and a written agreement before translation begins
Key distinction
Translation versus adaptation, including who may authorise cuts, relocations or additions
Typical users
Translator, director, dramaturg, producer, playwright or rights holder, and actors
Not a substitute for
A translation agreement, rights permission or contract

A translation brief for a play production is a written commissioning and collaboration document. It tells a translator what the production needs to know about the source text, audience, staging, language policy, deliverables, revision process and rights or credit expectations. It also gives the director, dramaturg, playwright and producer a shared record of decisions that would otherwise remain implicit.

There is no single mandatory format. The useful question is not whether the document follows an official template, but whether it lets the translator make defensible choices and lets the production check those choices without guesswork. A brief should be detailed enough to guide work and flexible enough to be revised when rehearsal reveals what the text can actually do on stage.

What a translation brief is, and what it is not

A brief is not a translation, a literal crib or a contract. It sits alongside the rights agreement and the translator’s contract. The PGC Translation Guidelines 2015 recommends that playwrights and translators use a letter of agreement before translation begins, covering matters such as royalty splits, billing and territorial rights (PGC Translation Guidelines 2015). Those are legal and commercial questions. The brief records artistic and operational intentions; it should not be used as a substitute for signed terms.

Theatre translation is a specialised activity because the text is made for performance, not only for the page. Geraldine Brodie notes that readers of translated theatrical texts include practitioners, actors, audience members, teachers and students, and that the translator must serve a performed text and its users (Brodie, ‘Translating for the Theatre’). A brief therefore has to describe performance conditions: who will speak, where, to whom, and with what visual and acoustic resources.

It should also say whether the commission is a translation or an adaptation. The boundary is debated, but the practical distinction matters. In 1986, when the Royal Shakespeare Company was rehearsing José Triana’s Palabras comunes, the playwright objected that the dramaturg had adapted the play to England, deleted and added characters and scenes; the actors sided with the author and worked from a literal translation instead (Three Percent, ‘On Translating for the Stage’). A brief should state clearly if relocation, cuts, additions or other adaptation are permitted, and who may authorise them.

Before drafting: establish the frame

Rights, credit and decision-makers

Identify the rights holder and the person empowered to approve the translation. Translation rights are separate from production rights, and permission to stage a play does not automatically settle translation credit, royalties or approval. The PGC guidance exists because ad hoc arrangements can create disappointment and conflict before a signed agreement is in place (PGC Translation Guidelines 2015). If the rights route is unresolved, say so in the brief rather than implying that permission has been granted.

Amanda L. Andrei’s account of translating Romanian poetry and plays describes enlisting a native-speaker co-translator, workshopping with other translators, and eventually abandoning a project when a search for publication rights reached a dead end (HowlRound, ‘How to Get Started Translating a Play’). The lesson is not that every project will fail, but that rights status and collaboration structure belong in the record from the start.

Source text and version

Name the source text exactly: author, title, language, edition, publisher, year and, where useful, ISBN or manuscript reference. State whether the translator is working from a published edition, an author-supplied manuscript or a literal version prepared by someone else. If the play exists in several versions, say which one governs. This prevents a translator from polishing a scene that the production has already cut or from treating a variant as the authorised text.

Audience, venue and performance format

Describe the intended audience and the conditions of performance. A translation for a studio production, a large proscenium house, a touring double bill or a multilingual festival will make different demands on clarity, breath, rhythm and cultural reference. Note whether the production expects surtitles, captions, audio description, simultaneous interpretation or a published acting edition. If these are separate deliverables, say so; a surtitle script is not the same task as a performing translation.

The core components of a usable brief

1. Identifying information and credit

Include the production’s working title, company, venue, dates if known, source play, author, translator, director, dramaturg, producer and literary manager. Record the required credit line and billing order. Credit is not a detail to settle after the programme has gone to print. If the translator is also a co-translator, adapter or dramaturg, distinguish the roles and the agreed wording.

2. Artistic concept and performance grammar

Summarise the production concept only as far as it affects the text. Relevant points may include period, design, casting, doubling, movement, music, accents or dialects, verse or chorus, direct address and the intended relationship with the audience. Mark which choices are fixed and which are provisional. A brief that says the production is set in 1920s Buenos Aires without saying whether the language should sound period-specific, neutral, stylised or contemporary leaves the translator guessing.

3. Language, register and cultural transfer

This is the heart of the brief. Specify register, formality, class markers, humour, taboo language, verse or prose, song lyrics, dialect and any multilingual passages. Explain the production’s policy on cultural references. Should source-language institutions, foods, titles and places remain and be made clear through performance, or be replaced with target-culture equivalents? Neither policy is universally correct. What matters is that the brief states a working principle and invites the translator to flag places where it strains.

Use a brief example. If a line refers to a source-language school qualification that the audience will not recognise, the brief might ask the translator to retain it and make the meaning clear through context, or to substitute a target-culture equivalent if the production wants a more domesticating idiom. The choice should be recorded, together with any dramaturgical note needed for rehearsal. The brief should not demand both authenticity and accessibility as slogans without explaining which matters more when they conflict.

4. Deliverables, format and deadlines

List the deliverables concretely. These may include a working translation, a literal or line-by-line version for the creative team, a rehearsal draft, a performing version, a surtitle script, a pronunciation guide, a glossary of names and institutions, notes on puns or wordplay, and a clean final text. State the preferred format: bilingual table, numbered lines, tracked changes, shared document or plain text. Give delivery dates and name the person who receives and circulates each version.

5. Collaboration, revision and approval

Describe how the translator will work with the production. Will there be a table read, a workshop, rehearsals, a dramaturgy session or a back-translation check? Who may request changes: the director, the playwright, the producer, the actors or a literary department? What counts as a minor edit and what requires renegotiation? The brief should distinguish the translator’s artistic authority from the production’s authority to cut or adapt.

Andrei’s account of workshopping and using a co-translator shows that collaboration is part of the translation method, not an afterthought (HowlRound). The RSC example shows the opposite risk: a production can make adaptation decisions that the author regards as illegitimate (Three Percent). A brief cannot prevent every dispute, but it can record who agreed to what and when.

6. Rights, payment, billing and territorial scope

Keep commercial terms out of the artistic paragraphs and put them in the agreement. The brief can cross-refer to the signed letter of agreement, which should cover royalty splits, billing, territorial rights and related matters (PGC Translation Guidelines 2015). Do not state that rights have been cleared unless the relevant permission has actually been obtained. Rights, contracts and tax or immigration questions depend on jurisdiction; the production should verify them through the appropriate rights holder, legal adviser or official route.

7. Access and multilingual circulation

If the production is multilingual, touring or intended for audiences who do not speak the target language, the brief should say which language versions are needed and for whom. A performing translation, a surtitle translation and a published translation may be different texts with different constraints. State whether the translator is expected to provide access materials or whether another specialist will do so. Avoid assuming that one English text will serve every audience in every venue.

A practical drafting sequence

  1. Collect documents first. Gather the source edition, any existing translations, rights correspondence, production schedule, design notes and audience plan.
  2. Hold a short framing meeting. Bring together the director, dramaturg, producer and translator, plus the playwright or rights holder where possible. Agree the decisions that cannot be left vague.
  3. Draft under headings. Use the components above, but cut any heading that has no bearing on the production. A short, precise brief is better than a long one that hides the key choices.
  4. Separate fixed from open questions. Mark requirements as fixed, provisional or negotiable. Give the translator room to propose solutions.
  5. Review and sign off the brief. Ask the translator to confirm that the brief is workable and the playwright or rights holder to confirm that the adaptation policy is acceptable.
  6. Version the document. Put a date and version number on each revision. When rehearsal changes the text, record who approved the change and whether it affects credit, royalties or future productions.

Illustrative skeleton

The following is a hypothetical skeleton, not a real production document.

  • Production: working title, company, venue and dates.
  • Source: author, title, language, edition and governing version.
  • Commission: translator, commissioner, fee, deadlines and agreement reference.
  • Audience and format: intended audience, venue type, touring, surtitles or access provision.
  • Concept: period, design, casting, movement, music and any fixed staging ideas.
  • Language policy: register, dialect, humour, cultural references, verse, songs and multilingual passages.
  • Deliverables: drafts, literal version, glossary, pronunciation guide and final performing text.
  • Process: workshops, readings, rehearsal attendance, approval route and revision limits.
  • Credit and rights: billing line, approval status and reference to the signed agreement.

Common problems and quality checks

  • The brief is treated as a contract. It is not. Use a separate agreement for rights, payment, credit and approvals.
  • Adaptation is requested but not named. If the production wants relocation, cuts or new scenes, say so and secure author approval. The Triana case is a cautionary example (Three Percent).
  • No source edition is specified. The translator cannot be responsible for a text the production has not identified.
  • Every line is over-directed. A brief that dictates breath, gesture and punctuation leaves no room for the translator’s linguistic judgement.
  • Performers are forgotten. Speakability, breath, pronunciation and audience audibility belong in the brief, especially where dialect or verse is involved.
  • No revision route is stated. Rehearsal changes need a record, particularly if they affect billing or future use.
  • Rights status is vague. Say what has been cleared, what is pending and who is responsible for the next step.
  • The multilingual audience is assumed away. If surtitles or multiple language versions are needed, commission and brief them explicitly.

Checklist before the brief is sent

  • Does it name the source edition and governing version?
  • Does it state whether adaptation is permitted and who approves it?
  • Does it describe the audience, venue and performance format?
  • Does it distinguish fixed requirements from negotiable choices?
  • Does it list deliverables, formats and deadlines?
  • Does it explain the revision and approval process?
  • Does it cross-refer to the rights agreement and required credit line?
  • Has the translator confirmed that the brief is workable?
  • Has the playwright or rights holder confirmed any adaptation policy?
  • Is there a dated version number and a named owner for future revisions?

A good translation brief is not a monument. It is a working instrument that makes assumptions visible, allows the translator to make informed choices and gives the production a fair way to review them. When it is written alongside the rights agreement and revised with the rehearsal process, it reduces the chance that the most consequential decisions about language will be made by accident.

FAQ

Is a translation brief legally binding?

It can record agreed intentions, but rights, payment, credit, approval and territorial scope need a separate signed agreement. The PGC guidelines recommend a letter of agreement before translation begins. A brief is not legal advice or a substitute for that agreement.

Should the brief tell the translator exactly how to render every line?

No. It should set constraints and principles, mark which choices are fixed or provisional, and leave room for the translator to propose solutions. Over-specifying breath, gesture and punctuation can prevent the translator from making sound linguistic judgements.

Who should approve an adaptation?

The playwright or rights holder, as appropriate, should approve changes that go beyond translation, such as relocation, cuts, added characters or new scenes. The brief should identify the approval route and record any limits.

When should the brief be written?

Before translation begins, alongside the rights route and written agreement, and then revised through workshops and rehearsals. Rehearsal changes should be recorded with a dated version and the person who approved them.

Does one brief cover surtitles and a published translation?

Usually not. A performing translation, a surtitle script and a published translation may have different constraints and audiences, so they should be commissioned and briefed as separate deliverables where needed.

READ FURTHER

Sources & references

  1. Amanda L. Andrei, 'How to Get Started Translating a Play', HowlRound Theatre Commons, 3 October 2024. https://howlround.com/how-get-started-translating-play
  2. Three Percent (University of Rochester), 'On Translating for the Stage', 13 May 2011. https://www.rochester.edu/College/translation/threepercent/2011/05/13/on-translating-for-the-stage/
  3. Geraldine Brodie, 'Translating for the Theatre', UCL Discovery PDF, n.d. https://discovery.ucl.ac.uk/id/eprint/10145363/3/Brodie_TranslatingfortheTheatre_chapter_AAM.pdf
  4. PGC Translation Guidelines 2015, 'Translation Guidelines for playwrights and translators'. http://www.the-fence.net/Resources/NYC/PGCTranslationGuidelines2015.pdf

THE LANGUAGE OF PRACTICE

Related terms

Translation brief
A written document setting out the source text, production context, language policy, deliverables and revision process for a translation commission.
Literal translation
A close, often line-by-line working version used to clarify meaning; in the Triana case, actors used one after rejecting an adaptation.
Adaptation
A version that changes setting, characters, scenes or other dramatic material, requiring clarity about authorisation and credit.
Dramaturg
A production role concerned with textual research, structure, context and the development of the script in rehearsal.
Surtitles
Projected translation or captions used in performance, often requiring a separate script and delivery process from a performing translation.
Letter of agreement
A preliminary written agreement recommended by the PGC guidelines to cover matters such as royalty splits, billing and territorial rights.

A SHARED BODY OF KNOWLEDGE

Something to add or correct? Help us keep the conversation informed.

Corrections & updates

Leave a Reply

Your email address will not be published. Required fields are marked *

THE CONVERSATION CONTINUES

Keep a window open to the world.

Fresh perspectives and practical reading, straight to your feed reader.

Subscribe via RSS

FOLLOW YOUR CURIOSITY

Find your next idea.

Search the journal, practical guides, and pages.

THE PRACTICAL TOOLKIT / 01

Your first conversations.

Use these prompts to begin planning with your collaborators. Your progress is saved in this browser.

A starting point for discussion. Adapt it to your project and check local requirements with the relevant organisations.

THE PRACTICAL TOOLKIT / 02

A time to come together.

Choose a date and time in UTC to see when your collaborators would meet. Times account for daylight saving on your chosen date.

Shaded times fall outside 09:00–18:00 local time. Agree working hours and access needs with your team.

BEHIND THE IMAGES

Photography credits

Editorial stock photographs illustrate themes; they do not document the productions discussed on this site. Used under the Pexels licence.