Documenting a Theatre Translation: What to Archive for Revivals and Publication

A theatre translation should be archived as both a text and a production process. The minimum record is not the final translated script alone: it includes the source text and edition, rights and permissions, successive translation drafts, rehearsal changes, the prompt book or production bible, surtitle and caption files, performance recordings where consent allows, credits, and enough metadata to reconnect these materials. For publication, the priority is a clean, rights-cleared playtext with translator notes. For revival, the priority is a production package that shows how the text was spoken, staged and titled in its first life.

The distinction matters because performance is transient. As Zammit notes in a 2025 study of archiving theatrical performance, a performance cannot be captured in its original form; archives can preserve material remains and functional documentation made to record it, including photographs and video (OAR@UM). A translated production adds another layer: the translation is not a neutral copy of a source play but a working version shaped by rehearsal, dramaturgy and performance choices. Research on performed but unpublished theatre in Spain shows how staging can be the only route by which a translated play reaches an audience, and how staging alterations need to be recorded if translation history is to be complete (LA Referencia).

Why a translation needs its own archive

General production archives tend to privilege the director’s prompt book, design, photographs and publicity. A translation archive must also explain the linguistic journey: which source edition was used, who authorised the translation, what was changed for performance, and which version is being published or licensed. Without that record, a later company may inherit a script that no longer matches the production, or a published text that cannot be traced to the version audiences actually heard.

Translation studies offers a useful corrective by treating translation as a documented process rather than a single product. Brodie’s account of a 2012 project at University College London, which retranslated four lesser-known one-act plays by August Strindberg, captured translators’ self-reflection in interviews recorded after performance. That record shows how collaboration between translators, and the dialogue created by the process, can be preserved alongside the performed text (UCL Discovery). For theatre companies, the practical lesson is to keep process evidence: briefs, drafts, correspondence, glossary decisions and post-performance interviews.

What to collect: a translation archive schema

A useful archive is selective but coherent. It should be organised around the life of the translation, from commission to revival, rather than around whichever files happen to survive on a shared drive.

Texts and translation record

• Source text: the exact edition used, including publisher, year and language; where relevant, the literal translation or existing published translation consulted.
• Rights and permissions: translation rights, adaptation rights, performance and recording permissions, territory, language, duration and any contractual credit requirements. Record what the agreement says and verify current terms with the rights holder; do not assume that a performance licence covers publication or streaming.
• Drafts: literal or first draft, working draft, rehearsal draft, preview version and final performance text. Label each by date, language and purpose.
• Translator’s paratexts: notes on ambiguity, cultural references, puns, dialect, register, pronunciation and cuts. These are essential for publication and for a future translator or dramaturg.
• Bilingual materials: side-by-side scripts, glossaries, pronunciation guides and source-language reference recordings where they exist.

Rehearsal and performance record

• Prompt book or production bible: blocking, cue calls, cuts, line changes, surtitle cues and the date of each change.
• Rehearsal notes: decisions about idiom, accent, rhythm, overlapping speech and audience address, with the person who authorised each change.
• Surtitle and caption files: the timed text, projection notes, speaker labels and any translations of songs, programmes or pre-show announcements.
• Performance documentation: audio or video recordings where performers and rights holders have consented, photographs, programmes, cast and creative credits, and audience access materials.

Rights, consent and access

Archiving is not only a curatorial act; it is also a rights and privacy decision. Separate public, internal and restricted files. Record consent for recordings, interviews and photographs, and note any embargo or expiry. For multilingual work, check whether surtitle files contain third-party text or images. When in doubt, keep the material but restrict access rather than destroying it.

Metadata and preservation

Digital theatre archives have been slow to adopt standards that make materials reusable, findable and interoperable, as a 2018 article comparing performance archives with language documentation observes (International Journal of Performance Arts and Digital Media). A small company need not build a full repository, but it should use consistent file names, dates, language tags, version numbers and a simple production identifier. Store a preservation copy separately from the working drive, and document who can open proprietary formats.

A practical workflow

1. Set scope and roles before rehearsal. Name who will maintain the archive: usually the producer or company manager, working with the translator, dramaturg and stage manager. Decide what will be collected, what will be restricted and where it will live.
2. Register the source and rights first. Create a one-page record of the source edition, rights holders, permissions and credit wording. This prevents later confusion between the translated text, the adaptation and the production.
3. Version-control the script. Use a clear naming convention, such as production-language-version-date. Keep a clean copy and an annotated copy of each significant draft.
4. Capture rehearsal changes as decisions, not noise. A short daily note can record cuts, new idioms, pronunciation choices and surtitle timing. Identify who approved each change and whether it affects publication.
5. Record performance proportionately. A single audio recording, a video of one performance, production photographs and the final prompt book are often more useful than exhaustive documentation. Obtain consent and state the permitted uses.
6. Describe and deposit. Add title, author, translator, language, production company, venue, date, version and access level. Link related items through the production identifier.
7. Prepare two outputs. At the end of the run, assemble a publication package and a revival package. Review both with the translator and producer before deposit.

Publication versus revival

Publication and revival draw on the same archive but ask different questions. A publisher needs a stable, authorised text and clear rights. A revival needs enough production evidence for a new team to understand how that text became a performance. Keeping the two outputs distinct prevents a rehearsal cut from being mistaken for the published play, or a clean reading text from being used as a revival script without the staging record.

Common problems and safeguards

• The ‘final’ script is rarely final. Keep dated versions and mark the performance text clearly.
• Rights are easily conflated. Translation, adaptation, performance, publication, recording and streaming may be separate permissions. Record each one and verify with the relevant rights holder.
• Files become orphaned. A recording without a date, venue, language and credit line is hard to use. Metadata is part of the archive, not an afterthought.
• Consent is overlooked. Performers, translators and interviewees may agree to one use but not another. Record the scope of consent.
• Over-collection creates risk. Not every rehearsal needs recording. Focus on decisions, versions and evidence that answer future questions.

For a small company, the first step is a simple archive register and a consistent folder structure. For a larger institution, the same principles scale into a catalogued collection with access controls. In both cases, the aim is the same: to leave a future director, translator, publisher or researcher with a reliable account of what was translated, what was performed and what may be reused. That is what turns a stack of scripts and recordings into a usable record of theatre across borders.