How to Build a Theater Tech Week Schedule

Start with opening night and work backward

Put the first performance, any required venue handover, and the final authorized checks on the calendar first. Then ask each department what must be complete before the next kind of rehearsal can happen. A cue-to-cue depends on cues being sufficiently prepared; a dress rehearsal depends on costume and backstage traffic being workable. The stage manager or schedule owner can assemble these dependencies, while department leads confirm the readiness of their own areas.

Leave room for breaks, meals when applicable, notes, resets, and an end-of-call wrap. Avoid scheduling every minute as if nothing will run late. If your production has a fixed access window or a limit on volunteer availability, treat it as a real constraint, not a detail to solve on the day.

• Confirm performance dates, venue access, permitted call times, and any required turnaround or rest periods.
• List the readiness dependencies for scenery, props, costumes, lighting, sound, performers, and front of house.
• Mark which work needs the full company and which can be completed by a smaller department call.
• Ask department leads to flag dependencies, unavailable people, and work that requires qualified or authorized staff.
• Protect time for breaks, meal arrangements, notes, and schedule changes.

Before tech week: close the rehearsal-to-tech handoff

The best tech calls begin before the first technical session. Confirm that everyone has the same current schedule, script or prompt book, contact process, and expectations for calls and updates. Share a clear list of open technical questions so the team can assign each item to the person responsible for assessing it.

Review the venue's communication and safety procedures with the people responsible for them. The stage manager coordinates the schedule and agreed calls; technical operators and department leads determine whether their own equipment and work are ready. Do not treat an unresolved safety issue as a scheduling inconvenience.

• Publish one current schedule with call times, locations, required people, planned work, and expected release or end-of-call process.
• Confirm the current script, cue information, scene shifts, preset needs, and any approved changes.
• Check that borrowed, rented, or venue-owned equipment has an identified responsible operator.
• Assign each open note to a department lead and agree how completion will be confirmed.
• Review the authorized process for a hold, emergency, or stop-work instruction.

Use a sequence that builds from space to cues

A practical schedule often moves from establishing how people and scenery travel through the space to checking technical moments, then integrating the whole performance. The exact order depends on your production and venue. A small straight play may combine steps; a production with complex changes or many departments may need separate calls.

• Orientation and access: review the room, backstage routes, communication method, and venue procedures with the people who need them.
• Load-in and setup: schedule assigned crews to place or prepare equipment and scenery under their department leads' direction.
• Spacing and transitions: walk through entrances, exits, scene changes, and traffic patterns so the team can identify conflicts.
• Technical cue work: focus on cue sequence and coordination as agreed by the director and technical leads; call only the people needed for that work.
• Integrated run: move through the show with the relevant departments and record notes without trying to resolve every item in the moment.
• Dress and performance preparation: practice the agreed pre-show process, costume transitions, backstage communication, and audience-facing timeline.

Write calls people can act on

A schedule is only useful when each person can tell whether they are needed and what the call is for. Avoid a vague all-company message when only one department is required. Include the location, start time, expected work, what to bring or prepare, and how updates will be sent. If a call changes, update the authoritative schedule and notify the people affected directly.

For conflict-aware planning and clearer rehearsal calls, see how to create a rehearsal schedule. The same discipline applies during tech: call the people whose work is needed and respect the volunteer time of those who are not.

• State the date, call time, location, and the roles or departments required.
• Name the planned work in plain terms, such as spacing, cue sequence, scene changes, dress, or notes.
• Include preparation details and the appropriate contact for questions.
• Show breaks and expected end-of-call or release process where they are known.
• Mark changes clearly and remove outdated copies or messages where practical.

Manage notes and changes without derailing the schedule

Technical sessions generate more observations than can be fixed immediately. Keep a central note list with the issue, scene or location, owner, priority as agreed by the team, and status. The stage manager can keep the list visible and route notes, but should not assign technical solutions outside their authority or mark work complete without confirmation from the responsible lead.

At the end of a call, review unresolved items with the relevant leads and identify what must be ready before the next scheduled step. If the schedule must change, confirm the adjustment with the people empowered to make that decision, then communicate the new call rather than relying on hallway updates.

• Record notes factually and identify the scene, cue, area, or department involved.
• Route each note to the person responsible for evaluating it.
• Separate confirmed fixes from ideas, questions, and items awaiting a decision.
• Review readiness dependencies before moving from cue work to a run or dress.
• Share approved changes promptly with everyone affected.

Build a humane and safety-aware tech week

Tech week can be demanding, especially for a volunteer company, but exhaustion is not a planning strategy. Schedule realistic work, publish calls early, provide the breaks and facilities required by your venue and local rules, and make it possible for people to raise concerns. If the schedule cannot fit the work safely, bring that problem to production leadership rather than silently extending the call.

Follow venue policies and directions from the people assigned authority. Stop or pause work when required by the applicable procedure or an authorized person. Never ask an untrained volunteer to repair, rig, lift, or operate equipment beyond their training and assigned role.

A simple tech week schedule review

Before sharing the schedule, review it with the director, stage manager, technical leads, and venue contact as appropriate. This is a final coordination pass, not a substitute for each department's own readiness checks.

• Does each call have a clear purpose and the right people assigned?
• Are dependencies sequenced so a later rehearsal does not rely on unfinished earlier work?
• Are venue access, breaks, meal arrangements, and authorized work hours accounted for?
• Are holds, emergency communication, and technical responsibility clear?
• Is there a single current version and a way to notify people of changes?
• Is there enough time to address open notes without treating safety or rest as optional?

Connect tech week to the wider production plan

Tech week is a handoff from rehearsal and preparation into the public run. The stage manager checklist covers repeatable calls and closeout routines, while what a stage manager does explains the role and its boundaries. For the larger sequence from auditions through strike, see the community theater season guide.

A shared rehearsal schedule can keep calls and updates in one place. The tool is only useful if the production team maintains one authoritative plan and the people with responsibility confirm their own work.