How Sound Shapes Storytelling on Stage

No one walks into a theatre expecting to see a real room. The walls are painted, the furniture is arranged for sightlines rather than comfort, and the actor a few metres away is speaking at a volume and clarity no real conversation would ever reach. Audiences accept all of this instantly, without being told to. Theatre has never asked to be mistaken for reality — it asks to be believed as a version of it, shaped deliberately for the people watching.

Sound is usually the last department expected to follow that logic. Sets are openly artificial. Lighting is openly a design choice. But sound, because it can be so easily built from real-world recordings, tends to get held to a different standard — as though its job were to reproduce what a room would actually sound like, rather than what the moment needs the audience to feel. That standard is wrong, and worth examining, because getting it right changes what atmosphere requires, and what makes a soundscape feel alive rather than assembled.

Emotional truth, not documentary accuracy

A useful way to test this is to imagine a scene that calls for a storm outside a window during a quiet, devastating conversation between two characters. The literal version is easy to build: rain at a realistic level, distant thunder, wind against glass, mixed at whatever volume a real storm would produce. It's accurate. It's also very likely wrong for the scene, because a real storm's actual loudness would compete with two actors trying to hold an audience's attention on something quieter and more important than the weather.

The choice that usually serves the moment better is a storm that's been shaped rather than reproduced — pulled back, textured rather than loud, present enough to register as true without asking the audience to split their attention. That version isn't less real in any way that matters to the audience. It's more true to what the scene needs them to feel: the weather as pressure and atmosphere, not as competition for focus. Realism, tested against a tape measure, would say the pulled-back version is wrong. Theatre, tested against what an audience actually experiences, says it's the only version that works.

This is the standard sound design in theatre is actually held to, whether or not anyone states it explicitly: does this serve what the audience needs to feel in this moment, not does this match what a microphone in that room would have captured. Once that's the standard, several things that look like limitations turn out to be design decisions with more freedom in them than they first appear.

There's a common assumption worth naming directly, because it runs the other way: that more realistic sound is automatically more professional sound — that fidelity to the real world is itself a mark of quality. It isn't. A hyper-accurate storm that drowns two actors is a technically impressive failure, not a restrained success. Realism is a tool, not a virtue, and treating it as the latter leads designers toward choices that are defensible in isolation but wrong for the scene they're actually in.

The reframing does carry a risk worth stating plainly, though, rather than glossing over: "emotional truth over accuracy" can become an excuse for imprecision if it's not held to its own discipline. The storm example only works because the pulled-back version was a deliberate choice about what the scene needed, made with the same rigour a literal version would have required — not a shortcut taken because building the accurate version was harder. The standard is still a standard. It just isn't the one realism assumes.

What this means for atmosphere without music

Music is the default answer to "how do we make this scene feel like something" — a licensed track under a transition, a mood-setting cue to open a scene, a needle-drop to signal a shift in tone. It works, and there are good reasons to use it deliberately. But it's also frequently reached for by default, not because it's the right tool for a specific moment, but because it's the familiar one — and defaulting to it carries real costs worth naming plainly: licensing and rights exposure that scale with how a production is used (recorded, streamed, restaged), a generic fit rather than a bespoke one, and a missed opportunity, because atmosphere doesn't actually require a recognisable piece of music to land.

If the standard is emotional truth rather than realism, atmosphere can be built from constructed sound — layered ambience, textured drones, processed field recordings, sound that has no real-world source at all — shaped specifically for the scene rather than borrowed from somewhere else. This isn't an argument against music in theatre; there are moments only a needle-drop or a live score genuinely serves. It's an argument against reaching for music as the default mechanism for atmosphere, when a bespoke soundscape, built for exactly this scene, often does the job with more precision and none of the rights complexity that comes with licensed material — particularly once a production has ambitions beyond a single run.

The distinction worth holding onto is what the moment actually needs. Music brings recognisability and cultural association with it — a well-chosen track can signal an era, a mood, or a reference the audience already carries, and no constructed soundscape replicates that shorthand quickly. That's a genuine advantage in the right moment, not something to dismiss. What it isn't is a general-purpose atmosphere tool reached for because building something bespoke takes longer. The question worth asking before any music cue is whether the scene needs what only music provides, or whether it needs a feeling that a purpose-built soundscape could serve just as well, with more control over exactly how it evolves and no external rights attached to it.

What makes an ambience feel alive

There's a specific failure mode worth naming directly: a looped ambient bed, however well-sourced, starts to read as artificial the moment an audience unconsciously registers the pattern. It doesn't matter how realistic the individual sounds are — birdsong, distant traffic, a forest at night — if the loop point becomes audible, or the same swell repeats at a predictable interval, the illusion breaks not because the content was wrong but because it stopped behaving like something alive.

What makes an ambience read as alive is closer to what makes anything read as alive: it changes, unpredictably but plausibly, over time. A forest ambience that occasionally introduces something unexpected — a closer rustle, a bird that wasn't there a moment ago, a shift in the wind's texture — reads as a real, continuing environment rather than a soundtrack playing under the scene. This is a craft decision with a direct cost: building or programming for that kind of variation takes longer than looping a clean four-bar bed, and it's exactly the kind of invisible labour that a rushed schedule tends to cut first, without anyone downstream realising what was lost.

The connection back to emotional truth is direct. An ambience that feels alive isn't more accurate than one that loops — it's more true, in the sense that matters to an audience sitting in a dark room accepting an invitation to believe in a world that isn't really there. Aliveness, like the storm example earlier, is a perceptual quality, not a technical one. It's achieved by attention to how something is experienced over time, not by how faithfully any single moment was captured.

Live performance adds a dimension to this that recorded media doesn't have to deal with. A film's ambience plays identically every time the film is watched, so a well-built loop, edited carefully enough that its seams stay hidden, can genuinely be good enough — the audience only experiences it once, in one configuration. A theatre ambience runs every night of a production, often for the length of a scene that itself varies slightly in pacing from performance to performance. A loop that stayed convincing on a single playthrough starts to feel mechanical to a designer or operator who's heard it forty times, and more importantly, its fixed length has to somehow accommodate a scene that isn't fixed. Building for genuine variation isn't an aesthetic preference in that context — it's a practical response to sound having to hold up under repetition in a way a single recorded playback never will.

Where this connects to the rest of the work

This argument sits alongside two others made elsewhere on this site, and it's worth being precise about how they differ rather than treating them as the same idea restated. The case for invisibility is about achievement — sound design succeeding by not drawing attention to itself. The case for sound constructing space is about presence — how sound builds an audience's sense of where they are. This piece is about a different question: once sound is invisible and has built a space, what standard should shape the content inside it? The answer — emotional truth over literal accuracy — is what makes both of those other arguments possible to execute well. Invisible sound design still has to decide what to say; a soundscape still has to decide what world it's constructing. This is the reasoning behind those decisions, not a restatement of why they matter.

The reframe, in practice

None of this suggests literal accuracy has no place in theatre sound — plenty of moments are served by exactly the sound a real room would produce, and knowing when realism is the right choice is part of the same judgement. What changes is the default assumption. The question worth asking of any sound design choice on stage isn't "is this what this would really sound like" but "is this what the audience needs to feel right now" — and answering that honestly, scene by scene, is where the actual craft lives.

Does Your Production Need Dedicated Sound Design?

The usual way this question gets asked is as a straight yes or no: do we hire a sound designer or not. It's the wrong shape for the decision, because it treats sound design as a single fixed thing you either buy or don't, when in practice it's a spectrum of involvement that should be scaled to what a particular production actually demands. A better first question is: what does this production ask of its sound? Answer that honestly, and whether you need a dedicated designer — and what that would cost — largely answers itself.

This piece is about how to reason through that, rather than a case for always hiring someone. Some productions genuinely don't need dedicated sound design, and it's worth being clear about which ones, because a framework that only ever points toward spending money isn't a framework — it's a sales pitch. What follows is the actual set of factors that determine how much sound design a production needs, and therefore what it's likely to cost.

What actually drives the scale and cost

There's no standard price for theatre sound design because there's no standard production. The cost is driven by a handful of factors, and understanding them lets you estimate roughly where your own production sits before you ever approach anyone.

How much the show depends on sound for its storytelling. This is the single biggest driver. A production where sound carries real narrative or emotional weight — establishing worlds, marking time, shaping how scenes land — needs design in a way a dialogue-driven piece with a handful of practical effects simply doesn't. The more the storytelling leans on sound, the more design judgement the production requires, and the more it costs to do well.

The venue and its acoustics. A clean, well-behaved space with predictable acoustics is straightforward. A difficult venue — long reverberation, awkward shape, poor natural intelligibility, or a space never designed for performance — demands more work to make dialogue and effects land, and that work is a real cost regardless of how simple the creative side is.

The number and complexity of cues. A show with a dozen simple cues is a different proposition from one with dozens of layered, precisely timed cues that interact with lighting and staging. Cue count alone is a weak measure — one complex transition can be more work than twenty simple effects — but complexity scales cost directly.

Reinforcement needs. Whether the production needs to make voices or instruments audible — through microphones, amplification, or careful system design — adds a technical layer with its own cost, distinct from the creative design work. A play needing no reinforcement and a musical needing full radio-mic management sit at opposite ends of this.

Run length and repeatability. A design that has to run reliably for a six-week run, night after night, carries different demands from a two-night community show. Longer runs raise the premium on reliability and on systems that an operator can run consistently without the designer present.

Whether the production has a life beyond the room. If the show will be recorded, streamed, filmed, or restaged at a festival, the sound has to meet a higher and more permanent standard, because inconsistencies that a live audience forgives become fixed flaws on a recording. This is where a production that seemed to need only modest sound design can turn out to need considerably more — a factor worth identifying early, because it changes the budget rather than adjusting it.

Read together, these factors let you place a production on a spectrum from "minimal sound needs, low cost" to "sound-critical, complex, higher investment" — without anyone needing to quote a figure yet. Most productions know more about where they sit than they think; they just haven't been given the factors to check against.

To make that concrete, consider two productions run through the same factors. The first is a two-hander in a small studio space with good acoustics, a handful of practical sound effects, no reinforcement needed, a two-week run, and no plan to record it. On every factor, it sits at the low end: it needs sound handled competently, but not designed extensively, and its cost should reflect that. The second is a large-cast production in a difficult, reverberant hall, where sound establishes several distinct locations, the score and effects are tightly woven into the staging, some voices need reinforcement to carry, the run is six weeks, and it's being filmed for later release. That production sits at the high end of almost every factor — and the gap between the two isn't a matter of one being a "better" show, but of them making genuinely different demands of their sound. A single quoted price could never fit both, which is exactly why the factors matter more than a figure.

Design, operation, or both — the cost lever people miss

One distinction does more to explain sound design cost than any other, and it's covered in more depth in the pillar article on this site: the difference between designing the sound (the creative decisions, made in advance) and operating it (running the show reliably, live, every night). They're separate functions, and conflating them is where budgets most often go wrong.

The reason it matters for cost is that you may need one, the other, or both. A production might commission design and then have a competent in-house operator run it — lower cost than commissioning both. Another might have a clear sound concept already and need only reliable operation. Working out which of these you actually need, rather than assuming "a sound person" is one flat line in the budget, is often where a production either saves money it didn't need to spend or, more damagingly, under-budgets the part it can't do without.

How the cost is usually structured

Knowing what drives cost is more useful alongside a rough sense of how sound design tends to be priced, since the structure affects how the factors above translate into a budget line.

Theatre sound design is commonly quoted as a project fee for the design work — a single figure covering the creative process from concept through to a production ready to run — rather than an hourly rate, because the work doesn't map neatly onto hours and a fixed fee gives a production budget certainty. Operation, where it's a separate function, is more often costed against the run: the number of performances, plus tech and rehearsal time the operator needs to attend. Reinforcement-heavy productions may carry additional cost for the technical management that involves, and equipment hire, where a venue doesn't already have what's needed, is usually a separate line again rather than folded into the design fee.

The practical implication is that the factors driving scale don't just make a production "more expensive" in the abstract — they load onto different parts of the quote. A sound-dependent show raises the design fee; a long run raises the operation cost; a difficult venue or heavy reinforcement raises the technical side. Understanding which part of your production is driving the cost makes it far easier to have a productive conversation about the budget, because it shows where the money is actually going and where, if anywhere, there's room to scale back without undermining the show.

When a production genuinely doesn't need dedicated design

This is the honest part, and it's what makes the rest of this worth trusting. Plenty of productions are well served without a dedicated sound designer.

If a show uses sound sparingly and functionally — a few pre-recorded effects, some scene-change music, nothing that carries real storytelling weight — and a competent, reliable person can prepare and run it, then dedicated design would be spending money on capability the production won't use. A straightforward play in a friendly acoustic, with modest sound needs and no recording planned, can be entirely well served this way. Choosing not to hire a designer in that situation isn't cutting a corner; it's a proportionate decision, and a good designer would tell you the same rather than talk you into a service you don't need.

The mistake in the other direction is assuming this describes your production when it doesn't — that "we'll sort the sound out ourselves" holds for a show that actually depends on sound more than the team has recognised. Which is the real risk worth naming.

When it does — and what skipping it costs

The point where under-resourcing sound stops being thrift and starts being a visible problem is usually one or more of these:

The show depends on sound to tell its story. Where atmosphere, transitions, or emotional register are doing real work — the territory covered in the storytelling article on this site, sound isn't decoration that can be handled casually. Getting it wrong doesn't just sound worse; it weakens the production's actual storytelling, which the audience feels even if they can't name why.

The venue is working against you. A difficult acoustic that makes dialogue hard to follow costs you the audience's comprehension, and there is no more fundamental failure in live performance than an audience unable to hear the show. This is rarely solvable by a well-meaning volunteer without the relevant experience.

The production is being assessed. Funded work, reviewed productions, and festival entries are being judged on craft alongside performance. Sound that would pass unremarked in a low-stakes context becomes a weakness a reviewer or assessor notices, at exactly the moment the stakes are highest.

The show will be recorded, streamed, or restaged. As above — the moment sound becomes permanent, the tolerance for live imperfection disappears, and a modest live design that would have been fine in the room reveals every weakness on a recording that outlives the run.

In each of these, the cost of skipping dedicated design isn't hypothetical. It's a specific, foreseeable outcome — a lost audience, a weaker review, a recording that undersells the work — that tends to cost more, in money or reputation, than the design would have.

Once you've decided

If the reasoning above points toward dedicated sound design for your production, the useful next steps are practical: work out roughly where your show sits on the factors above, whether you need design, operation or both, and when in your schedule sound needs to be involved. The article on working with a sound designer covers how to brief one, and the one on production timelines covers when to bring them in — both worth reading before you approach anyone, because arriving with a clear sense of your production's actual needs makes for a far more useful first conversation than starting from scratch.

If it would help to talk through where a specific production sits — including an honest view on whether dedicated design is warranted at all — get in touch. Working that out early, before the budget and schedule are fixed around an assumption, is considerably easier than revisiting it later.

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.

Working With a Theatre Sound Designer

Some of the most useful feedback I've had on a sound design pitch came from a production team working on a script-driven piece, built around performed text with very little else on stage. Their concern wasn't cost, or whether sound design was a legitimate discipline. It was more specific: they were worried that sound would get in the way of the script — that it would pull focus from the words the production was built entirely around.

That's not a misconception to correct. It's a reasonable instinct, and for that kind of production, a legitimate risk if the sound design is handled badly. Sound can compete with dialogue for attention. It happens when a designer works in isolation from what the production actually prioritises, guessing at what matters instead of being told. The failure in that scenario isn't sound design itself — it's sound design without a clear brief about what it isn't allowed to compete with.

Which is really the argument for this whole article. Whether sound design serves a production or undermines it has less to do with talent and more to do with how the working relationship between director and designer is set up. Get that right, and a text-driven production ends up with sound design that protects the primacy of the script rather than threatening it. Get it wrong — bring a designer in late, hand them a finished show, and hope for the best — and the risk that team was right to flag becomes a lot more likely.

Why this collaboration needs deliberate management

Most creative departments in theatre sit either clearly upstream or clearly downstream of the text. A set designer's decisions are largely fixed before rehearsals begin. A lighting designer typically works from a mostly settled show. Sound sits awkwardly across both positions: it needs the same lead time as an upstream department, because building a sonic world and testing reinforcement takes time, but many of its decisions can only be finalised once blocking, pacing and the director's read on key moments have settled — which happens well into rehearsal, if not later.

That in-between position is exactly why the relationship needs managing rather than assuming it. Left to default timing, sound design tends to slide toward the end of the process, arriving once everything else is fixed. At that point the designer is reacting to a finished show rather than shaping it — which is precisely the scenario that produces sound design detached from the production's actual priorities.

When to bring a designer in

Early involvement doesn't mean a designer needs to sit in on every rehearsal from day one. It means being in the room, or at least in conversation, while the director's read on the text and its emotional shape is still forming — before decisions calcify to the point where sound can only illustrate them rather than inform them.

Practically, that means involvement from early rehearsals or production meetings, not tech week. Leaving it later doesn't just compress the schedule. It removes the opportunity to agree the kind of boundary that team wanted for their script-driven production — an explicit understanding that dialogue takes precedence, established early enough to shape every subsequent decision, rather than negotiated defensively once a sound cue has already been flagged as intrusive in a run-through.

What a designer needs from a director

The single most useful thing a director can give a sound designer isn't a list of tasks — it's a clear account of what the production is actually prioritising, and what it explicitly isn't. For a text-forward piece, that might be as direct as: dialogue is never to be obscured, and any sound that risks pulling focus from a speech needs a strong justification to survive.

Beyond that priority-setting, a useful brief typically covers:

• The tone and world of the production — realistic, stylised, minimal, or something in between.
• Key emotional beats — the moments the director considers pivotal, where sound is more likely to be asked to do real work.
• Non-negotiables versus open ground — what must never happen (a phone ringing a beat too early, dialogue being masked) versus where the designer has genuine creative licence.
• Existing reference points, if any — though these are a starting conversation, not a brief to imitate.

None of this needs to be formal or written. What it needs is to happen early enough that the designer is working from the production's priorities rather than inferring them from a finished run-through.

What to ask before you commit

Because so much of this depends on process rather than talent alone, it's worth evaluating a designer on process before signing off on the collaboration — particularly for a production where getting the balance with text wrong would be costly. A few questions do more work than a portfolio review:

• How do you handle a note that a sound choice is pulling focus? The answer worth hearing is something like a quick, unresisting adjustment, not a defence of the original idea. Designers who treat every note as a negotiation are harder to work with under tech-week pressure.
• How do you approach a production where dialogue has to take priority over everything else? This tests whether they've actually worked on text-forward pieces or are assuming every show wants a fuller sonic treatment by default.
• What do you need from me, and by when? A designer without a clear answer to this either hasn't thought about the collaboration structure or is used to working in isolation — both worth knowing before rehearsals start, not during them.

None of these questions require technical knowledge to ask or evaluate. They test working style, which is the thing most likely to determine whether the collaboration goes well.

Where creative authority sits

The clean version of this is straightforward: the director holds final authority over the story being told; the designer holds authority over how sound achieves whatever the director has asked for. In practice, friction rarely comes from a genuine artistic disagreement between those two positions. It comes from vague direction — a note like "make this bit feel more atmospheric" that hasn't specified what the atmosphere needs to protect.

A brief, invented example: a designer proposes a low ambient bed under a monologue, intended to add tension. The director cuts it in the run-through, not because the idea was wrong, but because it was drawing attention to itself at a moment where the production needed the audience's attention entirely on the actor's face. Read as conflict, that looks like the designer's judgement being overruled. Read accurately, it's a brief that was never quite specific enough about where the line sat — resolved quickly, because the relationship allowed for a note and a fix rather than a defence of the original choice. The same disagreement arriving for the first time in tech week, with no working relationship to fall back on, tends to take longer to resolve and costs more goodwill on both sides.

Sound and lighting

The pillar article on this site notes that lighting and sound shape the audience's sense of time and place simultaneously, and that a mismatch between the two tends to feel unfinished even when neither department has done anything wrong in isolation. The collaboration mechanics behind that point are simple in principle: sound and lighting designers benefit from knowing what the other is doing at the same production meetings, rather than each working from the script independently and reconciling differences only once both are in the room together. On smaller productions without a formal system for this, the director is often the one holding that connection — worth being deliberate about rather than assuming it happens by osmosis.

In practice, the dependency shows up most clearly at transitions — the moment discussed in the pillar article's worked example, where a scene change relies on lighting and sound landing together. If the two designers haven't compared notes, the common failure is a lighting cue that completes half a second before or after the sound does, which reads to an audience as a rough edit even when both elements are individually well designed. Fixing that in tech week is a matter of minutes once someone notices it; the value of earlier coordination is that fewer of these small mismatches make it to tech week in the first place, leaving more of that limited time for problems that actually need it.

What this looks like in tech week

By tech week, the working relationship should already be established — this isn't where it starts. What changes is the mode of communication: notes become faster and more specific, tied to what's just been seen rather than what's anticipated. A director who has been in dialogue with the designer throughout rehearsals can give a note like "that transition is too long against the blackout" and expect it to be understood immediately, because the designer already knows the production's priorities. A director meeting the designer's choices for the first time in tech week is giving the same note without that shared context, which is slower to resolve and more likely to produce exactly the kind of friction the relationship, done earlier, would have avoided. The scheduling mechanics of tech week — what happens when, and in what order — are covered separately; what matters here is that the quality of communication in that week is set by everything that happened before it.

Where this leaves a text-driven production

None of this requires sound design to be minimal, and minimal isn't automatically safer — an underused sound design can also fail a production, just less visibly. What it requires is that "does this serve the text or compete with it" is a standing question the designer is answering with the director, throughout, rather than a concern raised once and then left to hope for the best. Productions built entirely around performed text are not a case where sound design doesn't belong. They're a case where the brief needs to be unusually clear about what sound is there to protect.

If you're weighing up how sound design would sit against a particular production — especially one where the text is doing most of the work — that's worth talking through early. Get in touch before the schedule and expectations are set around an assumption that turns out not to fit.

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.