Tech Week Reports in Ten Minutes: A Practical Template and Tool Workflow
Short answer. A useful tech week report records what happened, what changed, what remains unresolved and who owns the next action. A structured template and carefully limited use of AI can reduce the time spent writing reports to around ten minutes, provided the stage manager retains responsibility for accuracy and distribution.
- Write reports around decisions and outstanding actions, not a chronological account of every interruption.
- Separate confirmed changes from suggestions and unresolved questions.
- AI can organize rough notes, but it cannot establish whether a technical cue is safe or approved.
- Accessibility arrangements deserve their own visible reporting category.
- A consistent reporting deadline helps departments prepare for the next call.
The report has one job: prepare the next call
Tech week generates information faster than most small theatre teams can process it. A lighting adjustment discussed at the prompt desk, a sound problem discovered during a transition and a costume repair requested after a dress rehearsal may all require attention before the next performance. A report should make those obligations visible without becoming a transcript of the evening.
Set a reporting deadline that suits the production schedule. For example, a stage manager might aim to distribute the report within 30 minutes of the final rehearsal, using ten minutes for the actual writing. The distinction matters: the reporting process should be prepared in advance, not improvised after everyone has gone home.
- Record the rehearsal or performance date and the call covered.
- Identify departments affected by each issue.
- Distinguish completed work from outstanding actions.
- Give every action an owner and a practical deadline.
- Identify anything that could affect the next rehearsal or performance.
A template built around production decisions
Keep the template short enough to use consistently. Start with production details, followed by a brief overall status and separate entries for departments. Each entry should contain the issue, its current status, the responsible person or department and the next required action. A single sentence can be sufficient when the information is precise.
For example: Sound - transition from scene four remains uneven; sound operator to adjust the playback level before the next spacing rehearsal. This is more useful than writing that the transition was discussed at length. If the adjustment has already been approved and completed, record that separately so nobody repeats the work.
- Production and call details.
- General rehearsal or performance notes.
- Lighting, sound, set, props and costume updates.
- Safety and access issues.
- Outstanding decisions and responsible departments.
Using AI to turn rough notes into a readable report
An AI writing assistant can organize shorthand notes into departmental sections, identify repeated subjects and turn fragments into complete sentences. Give it the report headings and a clear instruction to preserve names, cue identifiers, deadlines and uncertainty. Ask for a draft that separates confirmed decisions from questions still awaiting approval.
For example, notes reading 'LX 24 late, director wants hold, SM to confirm' should not become an instruction stating that the cue has been delayed. The director's preference and the stage manager's outstanding confirmation are two different pieces of information. A useful drafting instruction is to preserve that distinction and flag ambiguous entries instead of completing them by inference.
Do not paste confidential personnel information, private contact details or sensitive production material into an external AI service without appropriate permission. Check the provider's data handling terms and any organizational restrictions before using a shared account.
Accessibility belongs in the technical report
Accessibility arrangements can involve lighting, sound, audience movement, front-of-house staffing and advance communication. They should appear in the same production reporting process as other technical requirements. For an audio description performance, the report might identify the describer's position, microphone requirements, headset distribution, communication arrangements and any outstanding changes to the running order.
A relaxed performance may require a different set of operational notes. Depending on the agreed format, these could include maintaining low auditorium lighting, allowing audience members to leave and re-enter, providing a quiet space and adjusting startling sound or lighting effects. A relaxed performance guide should explain the actual arrangements to audiences. The stage manager's report should identify who is responsible for implementing them.
Do not assume that every relaxed performance uses identical adjustments. The production team should agree the format with relevant access representatives and communicate the practical requirements to front of house and technical departments.
The handover that makes the report useful
A report is only useful if the next person can act on it. Assign actions to roles or named team members, and avoid vague instructions such as 'department to look at this'. Record whether a decision is approved, proposed or awaiting a response. If a matter affects the safety of performers or crew, escalate it through the production's established safety process rather than relying on an email attachment.
Use a shared location with appropriate permissions and a consistent naming convention. Retain earlier reports when they provide a production record, but make the current outstanding actions easy to find. For a volunteer team, a shared document and a spreadsheet action tracker may be enough. Dedicated production software is useful when several departments need simultaneous updates, but it introduces training and access requirements of its own.
The ten-minute writing routine
A realistic routine divides the writing into short stages. Spend two minutes sorting notes into departments, three minutes drafting the entries, two minutes checking owners and deadlines, two minutes reviewing technical and accessibility details, and one minute preparing distribution. The total is ten minutes, excluding the time needed to resolve actual production decisions.
The final review should compare the report with the prompt book and current cue documentation where relevant. A report can record that a cue needs attention, but it should not silently become the authoritative cue sheet. Approved changes must reach the correct working document and the people responsible for operating the show.
- 2 minutes: organize notes.
- 3 minutes: draft departmental entries.
- 2 minutes: assign actions and deadlines.
- 2 minutes: review technical and access information.
- 1 minute: prepare and distribute the report.
Questions readers ask
Who should receive a tech week report?
Send it to the production personnel who need the information to prepare their work. The distribution list may change between technical rehearsals, invited dress rehearsals and public performances.
What happens when a department disputes an entry?
Correct factual errors promptly and preserve the distinction between an observation and an agreed decision. The stage manager can record a disputed item as awaiting resolution.
Can a spreadsheet replace the written report?
A spreadsheet works well for tracking owners, deadlines and completion status. A short narrative report remains useful for explaining context that individual cells cannot communicate clearly.
How long should production reports be retained?
Follow the organization's document retention policy and any contractual or institutional requirements. Keep records that may be needed for production continuity, incident documentation or future remounts.