How to Document and Archive Multilingual Theatre Productions

Documenting and archiving a multilingual theatre production means creating a durable, described record of the production’s language work, not simply filing a video. The record should include script and translation versions, language choices in rehearsal, performance capture, surtitle or caption files, credits, rights information and enough metadata for someone who was not there to understand what happened. Because performance is transient, no record is complete: archivists preserve aspects of an event and must decide which documents matter and how to organise them (Zammit, 2025). A documentation plan made before rehearsals begin is the most reliable way to avoid losing translation history, consent and rights evidence, or the language-specific materials that make a production intelligible later. The broader study of recording and researching theatre and performance treats documentation as a research practice as well as a preservation task (Dorney, in press).

Why multilingual productions need a documentation plan

Multilingual theatre is not one format. It may involve actors working in several spoken languages, deaf and hearing performers using different sign languages, a play text performed in translation, simultaneous interpreting, surtitles, or a devised piece that moves between languages. Documentation therefore has to record not only who appeared and when, but which language was used where, which text version was performed, and who made the translation or adaptation. A single-language recording can easily misrepresent a production if the viewer cannot tell whether a scene was performed in the source language, a translation, a mix, or a language invented for the stage.

The archival literature is clear about the limits. Zammit notes that a theatrical performance cannot be captured in its original form; only aspects can be preserved, whether material remains or functional documentation such as photographs and video. Her study identifies two persistent difficulties: deciding which performance documents should be preserved and how to organise and describe them (Zammit, 2025). Multilingual productions intensify both difficulties because there are more versions, more credits and more access conditions to record.

Language documentation offers a useful comparison. It is still an incipient field, but it has a more stable set of tools for recording, transcription, annotation and metadata than many theatre archives. The comparison is not exact, but it shows why multilingual performance needs structured description rather than a folder of unlabelled files (International Journal of Performance Arts and Digital Media, 2018). Digital theatre and performance archives remain few, and many have been slow to adopt standards for data reusability, findability and interoperability (International Journal of Performance Arts and Digital Media, 2018). A small company can still apply the underlying principle: collect with description in mind.

What to document

Documentation should serve both preservation and future research. It helps to separate three layers: the production text, the creative process, and the performance event. Each layer produces different evidence and needs different rights clearance.

Scripts, translations and version control

Keep every script version that carries meaning: the source-language text, literal or working translations, adaptation drafts, rehearsal changes, the final performance text, and surtitle or caption files. Record the translator, adaptor or dramaturg; the source and target languages; the date and status of each version; and whether it was commissioned, authorised, literal, adapted or devised. File names and catalogue entries should distinguish a rehearsal translation from a published translation and a performance text from a surtitle script. This is also the point at which to record whether the underlying play text and the translation are in copyright, and what permission has been granted.

Rehearsal and creative process

Not every rehearsal needs to be recorded. A focused documentation plan might preserve language coaching notes, pronunciation guides, dramaturgical correspondence, blocking notes that mark language switches, music and sound cues, sign-language interpretation plans, and short interviews with translators, performers or cultural consultants. Consent should be recorded at the time, not reconstructed later. Interviews are especially valuable for multilingual work because they can explain why a phrase was changed, which language a performer felt they were acting in, or how a joke or idiom was handled.

Performance capture

Record the performance in a way that makes the language audible and visible. A multi-camera video with a clean audio mix is useful, but separate audio feeds, surtitle screen capture, caption files and transcripts are often more important for multilingual research. Capture the programme, cast and creative credits, running order, venue and date. If the production used surtitles, live captions, audio description or interpreted performances, document those access routes as part of the event rather than as marketing extras. Audience reaction can be recorded only with a clear consent process; it is not essential to every archive.

Material and digital traces

Programmes, posters, publicity, reviews, photographs, contracts and correspondence can all help explain a production, but they carry different rights and reliability. A review is someone else’s interpretation, not a production record. A contract may be confidential. A photograph may be subject to performer and photographer permissions. The archive should separate production evidence from commentary and mark access restrictions clearly.

Describe the record: metadata and cataloguing

Description is where many multilingual archives fail. A file called final_video.mp4 does not tell a future user which languages were spoken, which text was used, or whether the translation was authorised. At a minimum, a production record should include the title in each relevant language, the company, venue and date, the languages spoken and signed, the source and target languages of any translation, the translation type, the translator or adaptor, the director and dramaturg, the cast and creative credits, the recording date and format, rights status and access conditions.

Use consistent language names and, where possible, standard language codes. Record the presence of interpreting, surtitles, captions and audio description as separate access features. Link related assets to one production record rather than scattering them across folders. Controlled vocabularies and persistent identifiers make the record easier to reuse and exchange; this is the practical meaning of the reusability, findability and interoperability standards that theatre archives have been slow to adopt (International Journal of Performance Arts and Digital Media, 2018). Zammit’s emphasis on accession and description is relevant here: deciding what to keep is only half the task; the other half is organising and describing it so that it can be found and understood (Zammit, 2025).

For multilingual productions, search should not depend on English or on the majority language of the production. A user may look for a translator’s name in one script, a title in another language, or a language combination. Catalogue entries should therefore include alternative titles, transliterations where appropriate, and names in the form used by the practitioners. If resources allow, provide a short abstract in more than one language.

Rights, consent and access

Multilingual productions create layered rights. There may be copyright in the play text, the translation or adaptation, the music, the recording, the photographs and the surtitle script. Performers, translators, dramaturgs and interviewees may have separate consent arrangements. The National Theatre’s guidance on digital archive projects identifies copyright protections and digital distribution as core planning issues, alongside funding, staffing, organisational buy-in and sustainability (National Theatre, 2026). Those issues should be settled before public access is offered, not after a tour has ended.

An archive can hold a preservation copy that is not publicly available and an access copy with cleared rights. Sensitive rehearsal material, unperformed translations or interviews may need an embargo. Consent should specify the purpose, platform and duration of access where possible. This is not legal advice; contracts and copyright law vary by jurisdiction, so companies should check the relevant national law and their agreements with rightsholders. Attribution matters too: translators, adaptors, interpreters and language consultants should be credited in the catalogue record as well as in the production.

Digital archive choices and sustainability

A digital archive is more than a website. The National Theatre guidance describes digital archive projects as projects that catalogue and remember performance online, and it covers discovery, building, marketing, additional resources and sustainability (National Theatre, 2026). For a small company, a realistic minimum might be a controlled folder structure, a catalogue spreadsheet with consistent fields, preservation masters, access copies, transcripts, a rights register and at least two backups. For a larger consortium, an institutional repository or shared platform may be more appropriate.

Plan for formats and migration. Keep high-quality preservation masters and make lower-resolution access copies. Store transcripts and surtitle files as separate documents as well as embedded captions. Record checksums where the system supports them, and document who is responsible for backups. Digital storage is not passive: files need migration, staff time and budget. The National Theatre guidance places sustainability and organisational buy-in early in the planning process, which is a useful corrective to the idea that an archive is finished once the files are uploaded (National Theatre, 2026).

A practical checklist

1. Define the production, tour or residency you are documenting, and list every language and access mode involved.
2. Appoint a documentation lead and agree who will collect, describe and clear rights.
3. Create a rights and consent register before rehearsals.
4. Collect script and translation versions with dates, credits and status.
5. Record selected rehearsals, interviews and language coaching with consent.
6. Capture performances, surtitles, captions and audio in a planned format.
7. Write a catalogue record with languages, translation type, credits and access conditions.
8. Store preservation masters and access copies separately, with backups.
9. Review sensitive material and embargoes before publication.
10. Plan deposit, migration and review dates so the archive does not become orphaned.

Common problems

The most common problem is treating video as the archive. A video is one document among many, and it rarely records translation choices, rehearsal debates or rights. Another problem is missing translation credits: a production may list the playwright and director but omit the translator or adaptor, making the language work invisible. Unlabelled language use is also common, especially in devised or bilingual work. Surtitle files are often lost because they are treated as technical cues rather than production documents. Finally, archives can over-collect and under-describe: hundreds of files without metadata are harder to use than a smaller, well-described set.

Multilingual theatre rewards documentation that is planned, credited and described. The aim is not to capture everything, which is impossible, but to preserve enough evidence for future practitioners and researchers to understand how a production worked across languages, who made it, and how it can be used.