Sound Design Timeline for a Theatre Production
Ask a producer when the set needs to be finished and they'll usually have an answer close to opening night. Ask when sound design needs to be finished and the honest answer is less clean: parts of it are done weeks before tech, parts of it aren't settled until previews, and the department most visibly "working" — cues being run, levels being set — is often the one that started earliest and least visibly.
That mismatch between how sound looks scheduled and how it actually needs to be scheduled is where most timeline problems start. Treat sound as something confined to tech week and you compress a process that needed weeks into days, with predictable results: a tech week that overruns, cues that feel bolted on rather than integrated, and a designer working reactively instead of with the show. None of that is inevitable. It's a scheduling error, and it's avoidable once you know what actually needs to happen and when.
Why sound's schedule doesn't map onto other departments
Most physical departments — set, costume, props — build to a fixed design that's largely settled before rehearsals begin, then arrive close to finished. Sound design has an unusual dual nature: it needs the lead time of an upstream department, because building a sonic world and testing how reinforcement works in a specific space takes real time, but a meaningful portion of its content can only be finalised once blocking, pacing and the director's read on key moments have settled — which happens well into rehearsal.
That's the scheduling consequence of the working relationship covered elsewhere: early collaboration isn't just good practice, it's what makes an unusual, two-part timeline possible in the first place. A production that treats sound like set — commission it, wait, receive it finished — will find that the finished thing doesn't fit, because half of what it needed to respond to didn't exist yet when the work was done.
The timeline below is organised by phase relative to opening rather than fixed calendar weeks, because production schedules vary too much in length for calendar weeks to mean anything consistent across a two-week community run and a six-week funded production. How the phases compress or stretch by scale is addressed at the end.
Early phase: concept and world-building
This phase runs alongside early rehearsals and typically overlaps the first production meetings. Nothing audible exists yet. What's happening instead is the groundwork covered in the collaboration piece — the director and designer agreeing on the sonic world of the production, its priorities (what sound is there to protect, what it must never compete with), and the emotional beats most likely to need sound's involvement.
Skipping or rushing this phase is the single most common cause of late-stage problems. A designer who starts building cues without this groundwork is designing against guesses, and guesses generally surface as notes in tech week — the most expensive point in the schedule to discover a wrong assumption.
Development phase: building against the show
Once rehearsals have enough shape — blocking roughly set, pacing emerging, key scenes staged even if not polished — the designer starts building in earnest: drafting transitions, constructing ambiences, sourcing or creating effects, working out reinforcement needs for the specific venue. This phase produces most of the actual content, and it happens in parallel with continued rehearsal rather than after it, which is why early involvement matters practically and not just relationally: a designer with no visibility into rehearsal during this phase is building against a script rather than against a production, and the gap between the two is exactly what tech week exists to expose.
Drafts from this phase typically get shared and adjusted well before tech — a transition tried in a stumble-through, a note taken, a revision made — so that tech week is refining decisions rather than making first attempts at them.
Pre-tech phase: preparing for integration
Shortly before the full company and other departments come together, sound needs to reach a specific state of readiness distinct from "finished": every cue built and organised, playback systems tested in the actual venue if at all possible, and a clear plan for how cues will be triggered and by whom. This is preparation for integration, not completion — the content can still change, but the infrastructure running it needs to already work.
Skipping this phase compresses badly into tech week, because problems that belong here — a cue system that isn't reliable, reinforcement that hasn't been tested in the room — surface at the same time as every other department's first attempt at integration, competing for the same limited hours.
A brief, invented illustration of what that compression actually costs: a production skips a proper pre-tech check because the venue wasn't available until the day tech began. On the first run, half the cues fire late because the playback system's routing was never tested against the actual venue's speakers, and the designer spends the first several hours of tech week doing setup work that should have happened days earlier — work invisible to everyone else in the room, who are waiting on sound to be ready before their own integration can be properly tested. The schedule doesn't show "pre-tech was skipped." It shows "tech week overran," which gets read as a tech week problem rather than what it actually was: an earlier phase's cost, paid late and by everyone.
Tech week: sound in the room with everything else
This is the phase most people picture when they think about theatre sound design, largely because it's the only part that's visible to a full room of people. It's also usually the most schedule-vulnerable phase, for a structural reason: tech week is where every department's separately developed work meets simultaneously, and sound depends on more of the others — lighting, blocking, the actual venue acoustics — than most.
Practically, this phase is cue-to-cue work: running the show (or sections of it) stop-start, setting and adjusting levels against a live space rather than a rehearsal room, checking that transitions land against the lighting and staging they were designed to support, and catching problems that only exist once everything is together — a cue that's a beat too early against blocking that's changed since it was built, a level that's wrong once actors are voicing at performance energy rather than rehearsal energy.
The reason early phases matter so much becomes concrete here. A designer who used the development phase to build against a genuinely observed production is fine-tuning known-good material. A designer building for the first time in tech week is doing the development phase's work under the worst possible time pressure, competing with every other department for the same hours, with an audience arriving in days. Most tech weeks that overrun are not failures of tech week itself — they're the deferred cost of an earlier phase that was skipped or compressed.
Previews and run: what's still being adjusted
Sound design frequently isn't finished when tech week ends, even on well-run productions. Real audiences change a room's acoustics, and they change pacing — a scene that ran a certain length in an empty rehearsal room lands differently in front of two hundred people. Previews are often where small but real adjustments happen: a level that needs to come up slightly now the seats are full, a transition that plays too long once real laughter or silence is factored in. This isn't a sign that tech week failed. It's a normal part of a live process that only fully reveals itself in front of an audience.
What to check at each phase, as a producer
A producer doesn't need to understand sound design technically to keep a schedule honest — but knowing roughly what should exist by the end of each phase makes it possible to notice drift before it becomes a tech-week problem.
By the end of the early phase, there should be a shared understanding — not necessarily written down, but genuinely agreed between director and designer — of the production's sonic priorities and its non-negotiables. If a producer asks the designer what the show's priorities are and gets a vague answer, that's a sign the early phase didn't happen properly, regardless of how much calendar time has technically passed.
By the end of the development phase, there should be a working draft of the show's sound: not every cue finalised, but the bulk of the content built and at least partially tried against rehearsal. A designer who is still building from a cold start once rehearsals are in their final stretch is behind in a way that will surface in tech week, not before it.
By the end of the pre-tech phase, the technical infrastructure — playback, routing, reinforcement — should be tested and working, ideally in the actual venue. This is the easiest checkpoint for a non-specialist producer to verify directly: ask whether the system has been tested in the room yet, and if the honest answer is no with only days left before tech, that's worth addressing immediately rather than hoping it resolves itself.
None of this requires a producer to evaluate the creative quality of the work — that's not their role, and a designer's creative choices deserve the same trust given to any other department. It's simply a way of checking that the schedule is being used as intended, which is squarely a producer's responsibility.
How this compresses or stretches by production scale
The phases above hold regardless of production size, but their duration doesn't. A well-funded production with a six-week rehearsal period might spend two of those weeks in genuine development before a dedicated multi-day tech process. A two-week community production is working with the same phases compressed into days, which is workable, but only if nothing is skipped outright — a compressed early phase is a schedule adjustment; a skipped one produces the same tech-week problems regardless of how much time is nominally available. Where a specific production sits on that spectrum, and what level of sound design involvement makes sense for it, is covered in more detail elsewhere on this site.
Planning a schedule around this
None of this needs to be rigid. What it needs is honesty about which phase a production is actually in, and enough lead time in the early phases that tech week is refinement rather than a first attempt. If you're building a schedule and want to work out realistically where sound design should sit within it, that's a straightforward conversation to have early — considerably easier than solving it once the schedule is already fixed around a gap. Get in touch if it would help to talk through the timeline for a specific production.
