How to Document Decisions in a Collaborative Theatre Production

In collaborative theatre, a decision is rarely just a conversation. It becomes a cue change, a translation choice, a costume purchase, a credit, a rights position or a promise to a partner. The practical answer is to keep a dated decision log that separates proposals from agreed actions, records who decided and why, and links each choice to the documents it changes. Around it, keep rehearsal notes, versioned scripts and translation files, and a contribution and consent record. The aim is a shared, traceable memory that can survive a change of cast, a tour, a translation or a revival.

What counts as a decision?

A suggestion, an experiment and a decision are not the same thing. The A Million Minutes guidance on decision logs warns that confusing a suggestion under discussion with a decision people are expected to act on can make a project appear settled when agreement is still missing. A useful test is to ask whether anyone will now spend money, change a cue, learn a line, cut a scene, approve a translation or promise a credit because of the choice. If so, it belongs in the record.

Devised work makes this especially important. The AACT resource on devised theatre describes it as a collaborative system in which a group of artists work together to create a work, sometimes intending to reduce it to a formal script. The script may be late, provisional or distributed across notebooks, and decisions about structure, text, movement and music can be remembered differently by different participants.

Documentation should also cover casting and staging, budget and schedule changes, access arrangements, translation and surtitle approvals, credit wording, consent for personal material, and rights discussions. Not every item needs the same detail, but the record should show where the decision was made and who carries it forward.

Build a decision log that people will use

Start with a simple log before the first rehearsal. A spreadsheet or shared document is enough, provided it is accessible and has a named custodian. The A Million Minutes guidance recommends recording the question, the chosen option and the people responsible, then noting the reason and any condition that still applies. Keep the working record close to the activity it describes: a short note made after a session can preserve a change of plan more accurately than a polished account written much later.

Keep entries short. A log that tries to reproduce every conversation will be abandoned; one that records only final actions will be useless when someone asks why a scene was cut or a translation changed. Record the question, decision, decision-maker, reason and any condition.

Link the log to rehearsal notes

Rehearsal notes and decision logs overlap but do different jobs. The production handbook style guide from Toronto Metropolitan University describes rehearsal reports as numbered and dated primary documents that inform all departments of notes from rehearsal, with sequential numbering and categorised requests. That is a record of the day’s work and its operational consequences. A decision log records choices that may outlast the day.

The two should cross-reference each other. A rehearsal report might say that a transition was cut and a costume change simplified; the log records the reason, the person or forum that agreed it, and whether the change affects the script, score, lighting plan or touring version. Use the same decision ID where possible.

Make access routine. Read previous decisions at the start of a rehearsal or production meeting, or circulate a short digest. Agree which channel is authoritative and which is conversational, so the record reaches the people who must act on it.

Version scripts, scores and translation files

Decisions become difficult to trace when the documents they change are not versioned. Give every script, score, cue sheet, surtitle file and translation a clear name with a version number, a date and a status. The exact convention matters less than consistency; one current approved version should be identifiable, and superseded versions should be archived rather than deleted.

A devised production may move from an improvised structure to a written script, as the AACT resource notes, and that transition needs a visible paper trail. If a scene is cut and later restored, the earlier decision should still be findable. For multilingual work, record the source language, target language, translator or adapter, approval status and whether a choice was literal, adapted or pending. Surtitle files deserve the same treatment as spoken text.

Recorded voice, video, captions and digital elements belong in the same system. A decision about a recorded sequence is incomplete if the approved recording cannot be identified later.

Record authorship, consent and credit

Collaborative theatre often raises questions that a decision log alone cannot settle. The Writers’ Guild of Great Britain guide to devised and collaborative theatre notes that in devised work it may not be obvious who the writer is, or if there is a writer at all. It sets out models including joint authorship, co-authorship and assigning rights to a single entity, and discusses copyright within collaboration, underlying rights and common misunderstandings about contributions and performance rights. These are legal and contractual questions, not merely administrative ones.

A production can still keep a useful contribution record: who contributed text, movement, music, research, translation or dramaturgical structure; the dates and context; how the material was used; and any agreed credit wording. Record consent for personal stories, recordings, images or community material, with any limits. In cross-cultural work, note who was consulted about culturally specific material and whether a proposed use was approved, adapted or refused. A consent note is not a contract, but it is better evidence than a general memory of goodwill.

Be explicit about limits. The log supports good practice; it does not replace a contract, rights assignment, licence or legal advice. The relevant law and advice depend on jurisdiction and the parties’ arrangements. In the United Kingdom, the Writers’ Guild of Great Britain is one industry route; elsewhere, a local writers’ guild, union or qualified lawyer may be appropriate. For international co-productions, check which law governs the agreement.

Work across languages, time zones and distances

International and multilingual productions add layers. A decision may be made in one language, interpreted in another and reported in a third. Record the language of the meeting, who interpreted, and which text was approved. If a translation is revised after a table read, note whether it changes meaning, humour, rhythm or cultural reference, and who signed it off. ‘Approved for rehearsal, pending back-translation check’ is more useful than a general label of ‘translated’.

Remote participants need deliberate inclusion. Circulate a written summary after a call, state the date and time zone of any deadline, and give people a clear way to correct the record. Silence in a video meeting is not reliable evidence of agreement. If a decision is made asynchronously, record where and when confirmation arrived. These habits make assumptions visible across different theatrical conventions and resources.

Handle changes, disagreements and endings

Decisions change. The record should show that they changed, not pretend the first choice was always final. Mark superseded entries, keep the old version and add a short note explaining the replacement. The A Million Minutes guidance recommends separating observation from interpretation and marking anything that needs checking before it becomes part of the public story. That is useful for press materials, funding reports and archival descriptions as well as rehearsal.

Disagreement should not be smoothed out of the record if it affects the work. A note that a decision was contested, or that one department registered a concern, may matter for a later revival or co-production partner. The Writers’ Guild guide addresses irreconcilable differences and their consequences, a reminder that collaboration agreements should consider what happens when the creative team can no longer agree. A decision log can provide a chronology, but it cannot substitute for a dispute-resolution clause or a contract.

At the end of a production, prepare a handover pack: the final decision log, approved script and score, translation and surtitle files, production credits, rights contacts, consent records, technical plans and a short note on unresolved questions. This serves a tour, revival, archive or partner organisation.

A practical checklist

1. Name a custodian for the decision log before rehearsals begin.
2. Define what counts as a decision and distinguish it from a suggestion or an experiment.
3. Use stable decision IDs and record the date, context, question, options, decision, decision-maker, reason and conditions.
4. Link each decision to the script version, rehearsal note, translation file, budget line or contract it affects.
5. Number and date rehearsal reports, and cross-reference the log rather than duplicating it.
6. Version scripts, scores, surtitles, recordings and translations; archive superseded files.
7. Keep a contribution, consent and credit record for text, movement, music, research and personal material.
8. Review the log at agreed intervals and mark superseded, pending and contested items.
9. Circulate summaries to remote and multilingual collaborators, with dates and time zones where relevant.
10. Prepare a handover pack for touring, revival, archive or co-production partners.

Limits and verification

Documentation is a practical support, not a guarantee of legal or ethical compliance. Rights, credit, consent, data protection and contracts must be checked against the relevant jurisdiction and the specific agreement. A decision log can show what a company intended, but it cannot by itself transfer copyright, grant a licence or prove that a community consented to a particular use. Treat it as one part of a wider production record, and verify changing or jurisdiction-specific details with the appropriate official or professional source.