What Does a Theatre Sound Designer Do?
Most theatre productions have someone responsible for sound. Fewer productions can say clearly what that person actually decides, when they need to be involved, or why the role is different from simply operating a playback system on the night. This isn't a criticism of the people doing the work — it's a structural problem. Sound in theatre is usually invisible when it's done well, which means the decisions behind it are invisible too. If you've never worked with a dedicated sound designer, it's genuinely difficult to know what you'd be commissioning.
That gap matters more than it looks. A director or producer who doesn't understand what the role covers will typically either under-resource it — treating sound as something to sort out during tech week — or over-resource it, hiring a designer for tasks a competent operator could handle alone. Both are avoidable, and both come down to the same missing piece of information: a clear account of what the job is.
Design and operation are not the same job
The most useful distinction in theatre sound is between design and operation, and conflating the two is where most confusion starts.
Sound design is the set of creative decisions made in advance, usually in collaboration with the director, about how the production should sound: what atmospheres exist in each scene, how transitions between scenes are handled, where music enters and exits, what needs reinforcing so the audience can hear it, and how all of that supports what the production is trying to say. These decisions get made in rehearsal rooms and production meetings, often weeks before an audience sees anything.
Sound operation is the execution of those decisions live, night after night: running the cues, adjusting levels in the room, catching problems in real time, keeping the show consistent across a run that might include a matinee with a smaller audience and different acoustics from the Saturday night crowd. It requires its own skill — reading a room, reacting under pressure, knowing the show well enough to recover cleanly from a missed cue — but it isn't the same skill as designing what those cues should be.
On a well-resourced production, these are two different people. On smaller productions, one person often does both — which is perfectly workable, but worth naming explicitly, because it changes what you're paying for and when. If you're commissioning a sound designer and expecting them to also run the desk every night of the run, that's a different scope and cost than commissioning design alone. Producers who don't separate these two functions in their own head tend to under-budget the operating side, on the assumption that "the sound person" is a single flat-rate line.
This is also where the operator/designer distinction differs from the recorded-media equivalent. In film or video work, the comparable question is usually about which service you need — sound design versus general audio post-production, handled separately in an earlier article. In live theatre, it's about which phase of the same job you're commissioning: the decisions, the execution, or both.
What a designer actually decides
Stripped of jargon, a theatre sound designer is making decisions across a handful of areas, each with a direct effect on how the audience experiences the show.
The sonic world of the production. Every play implies a world, and that world has a sound — a kitchen-sink drama set in a specific decade sounds different from a stylised, non-naturalistic piece, even before a single sound effect plays. The designer works out what that world sounds like and keeps it consistent.
Atmosphere and transitions. How a scene opens, how it closes, and how the audience is moved from one time or place to the next without the mechanics of a scene change breaking the mood. This is one of the more undervalued parts of the job precisely because, done well, the audience never consciously registers it happening.
Music, where it's used. Not composition necessarily, but decisions about where music supports emotion versus where it would compete with dialogue or undercut a moment that works better in silence.
Reinforcement, where it's needed. Making sure the audience can actually hear what's happening — dialogue in a large or acoustically difficult venue, an actor singing without a mic in a space that swallows their voice, a scene played at the back of a deep stage. This is a technical necessity that still requires design judgement: over-amplify and you lose the honesty of a live performance; under-amplify and you lose the story.
Cues. The individual, timed moments where a sound event happens — a phone ringing, a door slamming, a shift in ambience. Cues are the visible, countable output of the job, which is why they're often mistaken for the whole of it. They're closer to the sentences of the design than the design itself.
Each of these is a decision made for a reason — in service of what the production is trying to communicate — rather than a technical task performed because a script calls for it. A short example makes the point more clearly than the list does on its own.
Take a scene change written simply as "the lights go down, and when they come up we're in a different room, some time later." On paper, that's a lighting and staging problem. In practice, the sound designer is making several decisions inside those few seconds. What's the sonic world of the new scene, and does it need to be established before the lights reveal it, so the audience arrives already oriented? Does the transition itself carry any emotional weight — is this a hard cut that should feel abrupt, or a dissolve that should feel like time genuinely passing? Is there dialogue or a sound effect at the top of the new scene that needs to be audible the instant it starts, meaning levels have to be right before the cue even fires? And is the transition built from a single cue, or several stacked and timed against the lighting and the actors' movement, so nothing arrives a beat too early or late?
None of that shows up if you just read the script. It only becomes visible when someone has thought through how the audience experiences those few seconds — which is the difference between a designer making decisions and an operator executing someone else's.
When they join, and who they work with
Sound design in theatre isn't a solitary process. It develops in conversation with the director, and it intersects constantly with lighting, since both departments are shaping the audience's sense of time, place and mood simultaneously — a lighting shift with no matching sound cue, or vice versa, tends to feel unfinished even when neither department has technically done anything wrong.
The practical detail of how that collaboration works — when a designer should be brought in relative to rehearsals, what they need from a director, how creative disagreements get resolved — is worth its own article rather than a rushed paragraph here. The short version for now: the earlier a designer joins a production, the more their decisions can shape it, rather than simply illustrate decisions already made elsewhere.
The spectrum from volunteer to professional
Not every production needs the same level of sound design, and pretending otherwise would be dishonest. A low-budget community production with a handful of pre-recorded effects triggered from a laptop can work perfectly well without a dedicated designer, provided someone competent is running it and expectations are modest.
The point where this stops being true is usually where one or more of the following applies: the show depends on sound for a significant part of its storytelling rather than as decoration; the venue has variable or difficult acoustics; the production is being reviewed, funded, or entered into a festival where craft is being assessed alongside performance; or the show is being recorded, streamed or restaged, where inconsistent live sound becomes a permanent, visible flaw rather than a one-night imperfection. Where a specific production sits on that spectrum, and what that means for budget, is its own question worth working through directly rather than answering in general terms.
The part that's easy to underestimate: there are no retakes
The single biggest practical difference between designing sound for theatre and designing it for film or interactive media is that theatre offers no second take. A film mix gets refined in post-production, indefinitely, until it's right. An interactive audio system is built to respond correctly regardless of what the player does, tested and iterated before anyone hears it. A theatre sound design has to work, correctly, live, in front of an audience who will notice if it doesn't — every performance, for the length of the run.
That constraint changes what "good" means. It's not just about the quality of a sound choice; it's about whether that choice can be executed reliably by a human being, under pressure, at 8pm on a Tuesday and again on a Saturday matinee, without the safety net of an edit. Designers who haven't worked in a live environment sometimes make choices that are correct on paper and fragile in the room. This is the kind of judgement that only comes from having sat through enough live sound checks and technical rehearsals to know where things actually go wrong — and it's a large part of what separates an experienced theatre sound designer from someone competent with a DAW who hasn't yet worked to a live cue.
The role doesn't stop at the final performance
Increasingly, a production's life doesn't end when the run closes. Shows get recorded for archive or marketing, streamed to reach an audience beyond the venue, staged again at a festival, or built with an immersive or promenade element that adds a further layer of sonic complexity. The sound designer who understood the show well enough to shape its live sound is usually the person best placed to carry that understanding into a recorded or streamed version, rather than handing it to someone encountering the production for the first time through a camera feed. This isn't a different job so much as the same judgement applied to a different context — worth knowing about even if it isn't relevant to every production.
Working out what your production needs
None of this reduces to a formula, and any article that promised one would be oversimplifying a genuinely case-by-case decision. What's true for a two-hander in a fifty-seat studio space isn't true for a large-cast production in a nine-hundred-seat house, and what's true for a single-run community show isn't true for something being filmed for later release.
If you're weighing up what a specific production needs — design only, design and operation, or something closer to a full sound package including recording or streaming — that's a conversation worth having early, before the budget and schedule are fixed around an assumption that turns out to be wrong. Get in touch if it would help to talk through where a particular production sits.
