What Should a Theatre Translation Approval Record Include?

A theatre translation approval record is the documented trail showing who agreed to which translated text, in which version, for which use, and on what credit and payment terms. It is not the same thing as the translation contract, although the two sit side by side: the contract establishes rights and obligations, while the approval record evidences that the people with authority actually signed off the words that reach the stage.

For anyone commissioning, directing, dramaturging or translating a play across languages, the practical answer is that the record must be specific enough for a producer joining the project two years later to reconstruct, without asking around, whose text was performed, who authorised the changes made in the rehearsal room, and how the translator is credited and paid.

Why theatre translation needs a documented trail

Play translation is unusually exposed to undocumented change. A translated script is rewritten in workshops, cut in rehearsal, reworked for surtitles, and sometimes reissued as a version or adaptation that carries a director’s name rather than the translator’s. Because the working text stays provisional for so long, approvals tend to be given verbally — in the room, by email, or through the quiet acceptance of a circulating draft — and then forgotten.

Two practitioner documents make the problem explicit. The PGC Translation Guidelines 2015, addressed to playwrights and translators, warn that starting work together without a signed agreement leaves an ad-hoc arrangement that can create disappointment, conflict and confusion; their remedy is a letter of agreement covering royalty splits, billing and territorial rights before translation begins. In Spain, a code of good practice issued by ACE Traductores and ADE notes that Spanish theatre frequently uses existing or specially commissioned translations as the basis for versiones, and that in many cases the translator is not named and the work goes unpaid. The code describes rewriting and merging a translation without its author’s approval as abusive exploitation of another’s work and an intellectual-property offence.

Geraldine Brodie’s study of gatekeepers and stakeholders in UK theatre translation approaches the question through contractual documentation. Scrutinising contracts, she argues, maps the progression of the translation process and identifies participants along the way — documents reveal not only who signed but also who was not party to the agreement. Her focus on indirect translation, where a text passes through an intermediate language, is a reminder that the person who produced the English an audience hears may be the last of several intermediaries. A record that names only the final translator conceals that chain.

What an approval record should include

The list below is a working template rather than a legal instrument. Which items are mandatory, and how they must be worded, depends on the jurisdiction and on the underlying rights in the play.

1. The work, the languages and the route

Identify the source play, its author and the edition or published text used, together with the source and target languages. State whether the translation is direct or indirect, and if indirect, name the intermediate translation and its translator. Record the working title in the target language and any alternative titles already used in publicity, so that later searches in an archive or a rights system find the same project.

2. The parties — and the missing parties

List everyone with an approval role: the original playwright or their estate, the translator, any literal or bridge translator, the dramaturg, the adapter or version writer, the director, and the producing organisation or its authorised signatory. Following Brodie’s emphasis on absences, it is equally useful to note who was consulted but holds no formal role, and who was never approached. That negative information is often what explains a dispute later.

3. The underlying permission

An approval record should state that permission to translate exists, on what basis, and who controls approval of the translated text — the playwright, the agent, or a licensor acting for the estate. Where the rightsholder must approve the translation before production, record the request date, the response and any conditions attached. Without this, a translator’s sign-off may be worthless because the underlying rights were never cleared.

4. Version control and the fixed approved text

Give every draft a date and a version number, and designate one file as the approved performance text. Rehearsal drafts, surtitle files and published acting editions should all be traceable back to it. In practice this means recording who holds the master document, in what format, and what happens when a director’s cut diverges from the approved text. The problem the Spanish code describes — a translation silently changed and merged — is a version-control failure as much as a credit failure.

5. Sign-off points and what counts as approval

Specify the moments at which approval is required — commission, delivery of the first draft, dramaturgical revision, start of rehearsal, press and publicity, final performance text, revival, tour or stream — and who must give it at each. Say explicitly whether email approval counts, whether silence is treated as consent, and how long a signatory has to respond. Vague approval is the most common source of later disagreement.

6. Credit and billing

Record the exact wording agreed for the translator’s credit, where it appears (script title page, programme, poster, website, press release, surtitle slides, published edition), its size or prominence where relevant, and how the credit distinguishes translation from version, adaptation or literal translation. This is the item most often lost between draft and opening night, and the one that the ACE Traductores and ADE code identifies as routinely missing in Spanish practice.

7. Money: fee, royalties and triggers

State the fee, the royalty percentage or split, and the events that trigger payment — signature, delivery, first performance, first paid performance, tour, publication. The PGC guidelines present an agreed royalty split and billing as matters to settle before translation starts, precisely so that a clean production contract can later be drawn up.

8. Rights granted and reuse

Record the territory, the duration, the media covered and whether the approved translation may be reused for a revival, a tour, a radio recording, a film, a stream or a published edition, and on what terms. A translation approved for one four-week run is not automatically available for a subsequent tour or a digital broadcast.

9. Consent to change, and deadlock

Set out how changes to the approved text are authorised and by whom, and what happens if the rightsholder repeatedly refuses a translation. Commercial translation agreements offer models: sample final-translation clauses collected by Law Insider provide for written notice of required corrections, a revision window, and referral to an intermediary after a set number of refusals. Such clauses are generic publishing and translation samples rather than theatre documents, but the structure — defined refusal, defined revision, defined escalation — transfers usefully to play translation.

10. Storage, duration and archive

Name the custodian of the record, where copies are held, how long they are retained and who may consult them. For projects that will be revived or taught, a copy lodged with the producing organisation’s archive or the playwright’s agent prevents the record from evaporating with a departed staff member’s inbox.

Approval points in a typical production

Common failures

• Ad-hoc starts. Work begins before any agreement exists, so no baseline text is ever fixed — the situation the PGC guidelines set out to prevent.
• The erasing version. A translation is reworked as a versión and the translator’s name and fee disappear, as documented in the Spanish code of good practice.
• Verbal approval. A nod in the rehearsal room is treated as consent but never written down, leaving the translator unable to show what was authorised.
• Approval by the wrong person. A director signs off a text that only the playwright or agent has authority to approve.
• Invisible intermediaries. Indirect translation hides the bridge translator and the pivot text, so credit and consent chain-break.
• Digital scatter. Approvals live across email threads, shared documents and messaging apps, with no decision about which channel is authoritative.

Jurisdiction and verification

Approval records sit inside national copyright and contract law, and the details differ. The Spanish code of good practice rests on the Ley de Propiedad Intelectual, which treats the translator as author of the translation with inalienable rights and frames the translator’s agreement as a cession of use rather than a sale, agreed with the director or producer. UK practice, as Brodie’s contractual analysis shows, is shaped by the agreements and commissioning conventions of British theatre. Moral rights, the treatment of adaptations and the enforceability of credit clauses vary further between countries.

None of this can be settled from a general template. Before relying on a record as proof of anything, check the applicable national law, the underlying licence for the play, and any collective agreement that covers translators or playwrights in that territory. Where a production crosses borders, record which jurisdiction’s terms govern the agreement.

A minimal checklist

1. Source play, author, edition used, source and target languages, direct or indirect route.
2. Named parties with approval authority, plus those consulted and those absent.
3. Underlying permission to translate, and who approves the translated text.
4. Dated, numbered versions with one designated approved text.
5. Sign-off points, accepted forms of approval and response deadlines.
6. Agreed credit wording and its placement.
7. Fee, royalty split and payment triggers.
8. Territory, duration, media and reuse terms.
9. Procedure for authorising changes and for resolving deadlock.
10. Custodian, storage location and retention period.