DOCTOR AUDIO / TALK / AUDIO PRODUCTION
Developing an Anti-Crunch Audio Pipeline
How audio leads can predict downstream work, prepare integration earlier and distinguish late discovery from genuine capacity limits.
Audio production · Project planning · Presented by Victor Hime, Flutu · gamescom dev, Cologne · August 2026
A feature can be planned for weeks and still reach audio two days before content lock. The problem is not always workload. It is when the workload becomes visible.
In this approach, audio reads the production signals that precede its own tickets: design changes, programming hooks, animation sets, levels and narrative milestones.
Two dependency maps and a recurring three-question review turn those signals into an audio backlog before the final assets arrive. This article is a written adaptation of Victor Hime's talk at gamescom dev 2026 in Cologne, Germany.
TL;DR
- 01A late request can originate in a feature that was visible in production for weeks.
- 02Visibility creates planning options. Capacity adds delivery bandwidth when volume genuinely exceeds the team.
- 03Map the development phase and each discipline's upcoming audio dependencies.
- 04Ask weekly: where is the game, what are they building, and what will audio need next?
What audio crunch looks like
A build heads toward content lock. A feature needs sound, integration and QA, but audio sees the request only now. What looked manageable in another department becomes an emergency for audio.
The feature was not new. The audio dependency was identified too late to schedule properly.
Across production sizes and pipelines, late discovery is a recurring pattern in our experience. The operational question is which project signals would let audio prepare sooner.
When audio is treated as a final production layer, upstream teams can commit scope without exposing the audio cost. That turns normal dependencies into schedule pressure and leaves less time for iteration.
Producers need reliable dependency planning. Audio leads need access to decisions before requests become tickets. Both benefit from the same shared production view.
The approach: think upstream
Most audio tasks begin elsewhere: a mechanic needs feedback, a gameplay system needs hooks, a level needs ambience, a character needs VO, or an animation needs synchronized events.
Illustrative diagram. Most of audio's future workload is created in these departments before it reaches audio.
Each department's work creates downstream audio dependencies. The earlier those dependencies are visible, the more decisions audio can make before asset delivery.
We keep asset production downstream where necessary, but move planning upstream. Audio reviews the relevant design work, implementation milestones and delivery risks before waiting for finished content.
For a new animation set, the audio lead can confirm trigger ownership and the expected event timing, define event and parameter structure, and plan implementation QA before the animations are final. The remaining production window then focuses on content and integration.
For examples of defining animation, VFX and gameplay trigger contracts, read Sound Call Models.
This is the central engineering decision: forecast dependencies, then schedule preparation separately from final asset delivery.
Production keeps scope and milestone ownership. Audio makes the dependencies explicit and negotiates readiness dates with the owning teams.
Visibility: capacity, maps and signals
Forecasting starts with two questions: is the team overloaded, or did the work arrive without lead time? The answer changes the intervention.
Capacity versus visibility
Capacity adds delivery bandwidth. Visibility creates time to sequence work, clarify contracts and expose dependencies.
| Capacity | Visibility | |
|---|---|---|
| What it answers | How much work can audio absorb? | How early can audio see the work? |
| What it gives | A way to deal with the workload | Time to change how the workload arrives |
| What it usually costs | Money: more people, outsourcing, hours, and often more pressure on the team | Attention: routine, conversations, reading other departments' work |
| Effect on the project | Handles the emergency | Can reduce avoidable late work and improve planning |
| When it is unavoidable | When the volume of work genuinely exceeds the team | Never a substitute for capacity when volume is the real issue |
Early signals let audio prepare events, routing, integration points and review windows. When the forecast still exceeds available hours, additional capacity or reduced scope is the appropriate decision.
The maps below locate the work and identify its upstream owners.
The two maps
Map 1 gives the project phase. Map 2 identifies incoming work by department. Together they support an audio forecast.
Map 1: audio across the development cycle
The current phase changes what audio should prepare and who owns the next dependency.
| Phase | What audio is doing | Who to talk to | What to expect next |
|---|---|---|---|
| Pre-production | Sonic identity, core systems, pipelines | Creative direction, lead programmer, producers | Systems decided here define the asset work in production |
| Production | Asset creation, cinematics, level building | Level design, animation, narrative, cinematics | Volume rises; each department's output becomes audio tasks |
| Content lock and polish | Finishing, fixing, validation | Production, QA | Late dependencies surface as fixes or missing deliverables |
Adapt the phase names to the actual studio. A useful map reflects real milestone gates and handoffs.
Map 2: audio and each department
Turn each department's deliverables into expected audio work and a signal to monitor.
| Department | What they build | What audio will need from it | Signal to watch for |
|---|---|---|---|
| Game design | Mechanics | Feedback sounds for player actions and system states | New mechanic in the design docs or backlog |
| Programming | Systems and hooks | Implementation points, events, parameters | New system in the commit history or sprint |
| Level design | Spaces | Ambiences, reverb zones, spatial setup | New area blocked out |
| Narrative | Characters | Voice production: casting, recording, implementation | New character in the narrative docs |
| Animation | Sets of actions | Sound for each action, synced to animation events | New animation set in progress |
An early level blockout suggests spatial setup; a new character suggests VO scheduling; an animation set suggests synchronized triggers. Confirm each dependency with its owner.
Crossing the two maps
Cross the phase and department maps to identify which dependencies are approaching the next milestone.
Available time can be used to prepare event structures, voice requirements or scene implementation before final assets arrive.
Workload becomes a crisis when dependencies are discovered after the schedule can absorb them.
Your backlog should predict work
Use existing design docs, backlogs, code history, dailies, milestone plans and feature discussions. Watch for decisions, not just assigned audio tickets.
| Source | What it tells audio | When it is most useful |
|---|---|---|
| Main project documentation | What was planned during pre-production | Any time, especially when joining a project already in progress |
| Backlog and task boards | What other teams are building now and next | Production |
| Commit history | What has actually been changing in the project | Production, when documentation lags behind the build |
| Daily meetings | Day-to-day shifts in priority | Throughout |
| Milestones | What must exist by when, and therefore what audio must have ready | Throughout |
| Design documents | How a mechanic, level or character is meant to work | Pre-production and early production |
| Feature discussions | Decisions before they reach the backlog | Throughout |
A useful audio backlog records the upstream signal, expected audio deliverable, responsible team, readiness date and integration check.
- 01 · SignalAnimation set plannedBacklog / milestone
- 02 · DependencyOne-shots and sync pointsAudio requirements
- 03 · OwnershipTrigger contractAnimation + programming
- 04 · PreparationEvents and parametersBefore final assets
- 05 · CheckPlayback in buildIntegration QA
The anti-crunch audio pipeline: three questions
The three-question review turns external development signals into decisions the audio team can act on. Run it at the sprint or milestone cadence.
Locates the project in the development cycle (Map 1) and surfaces what happened before audio got there.
Gives visibility outside the audio department: what each discipline is working on this milestone (Map 2 and the signal sources).
Turns that visibility into a plan: tasks, systems and preparation scheduled before the work arrives.
The review is useful only if it changes the backlog. Assign an owner, anticipated delivery window and next integration check to each predicted item.
Production decisions and checks
Visibility becomes useful when it changes a production decision. We review four things: what is coming, whether audio can act on it, who owns the dependency and when integration can be checked.
- Signal
- Which feature or asset changed upstream?
- Audio dependency
- Which sound, event, parameter, VO or spatial work follows?
- Owner and lead time
- Who delivers the hook or content, and when must audio be ready?
- Verification
- What can be checked in the next playable build or milestone?
| Production signal | Audio decision | Why decide early | Risk if missed | Review point |
|---|---|---|---|---|
| Game mechanic enters the backlog | Scope feedback states and parameters | Sound behavior needs a gameplay contract | Events created without useful triggers | Playable mechanic review |
| Programming defines new systems | Agree on event calls and ownership | Implementation cannot depend on a late hook request | Finished assets with no trigger path | Integration build |
| New area reaches blockout | Prepare ambience, reverb and spatial plan | Level structure affects emitters and routing | Spatial rework near content lock | Level walkthrough |
| Narrative adds a character | Forecast casting, recording and integration needs | VO has dependencies outside the audio editor | Late recording or missing dialogue hooks | Narrative milestone |
| Animation set enters production | Specify one-shots, sync points and events | Trigger timing can be planned before final motion | Animation arrives without audio contracts | Animation integration QA |
If the forecast exceeds available capacity, staffing or scope must still change.
Making the planning routine work
Match scope to capacity
Some changes arrive genuinely late. Forecasting cannot replace capacity when the committed scope exceeds the available team.
Reserve a recurring review slot
Scanning planning signals takes time. Give a solo audio lead a recurring, bounded slot instead of adding untracked meetings.
Share production signals
Without access to boards, feature decisions and relevant integration changes, audio cannot reliably forecast dependencies. Production must authorize that visibility.
Review the maps as production changes
The maps become stale unless the team reviews them as scope and milestones change.
Applying this to your project
A practical sequence to connect project signals with backlog ownership and integration checks.
01 · Locate the project
Where is the game?
Identify the current milestone and inherited decisions from project documentation.
02 · Draw the department map for this team
What are they building?
Identify each team's next deliverables and the expected audio dependencies.
03 · Get access to the signals
Can audio see the information?
Secure access to the backlog, relevant commits, design changes and milestone reviews.
04 · Build the audio backlog from the department map
What will audio need next?
Record anticipated audio tasks with an owner, readiness date and known technical dependencies.
05 · Prepare systems before assets arrive
What can be set up now?
Prepare naming, event structures, parameters and trigger contracts before content delivery.
06 · Ask the three questions on a fixed cadence
How often?
Review the three questions weekly or at each sprint boundary.
07 · Review the surprises
Which signal was missed?
Record missed signals and adjust the next forecast.
Why this matters beyond the schedule
When audio enters production late, iteration is often the first thing to disappear. The team ships the first workable version instead of testing alternatives and refining feedback.
Earlier dependency planning protects time for integration QA, experimentation and player-facing polish. This is a production responsibility, not an overtime strategy.
A sustainable schedule makes better creative decisions possible.
Questions We Can Answer
Why does Flutu publish technical whitepapers?
Client confidentiality limits the production details Flutu can publish.
Doctor Audio shares methods, engineering decisions and production frameworks that can be evaluated without exposing protected projects.
Does this work for a one-person audio department?
Yes. A solo audio lead can maintain the two maps and three questions in a weekly review, provided production shares the necessary information.
Does this replace hiring or outsourcing when the team is overloaded?
No. When forecast effort exceeds team capacity, adjust scope, staffing or delivery dates. Visibility helps identify that decision sooner.
Is there a tool or template for the maps?
Use the two maps in your existing project board. Keeping them beside production tickets avoids another disconnected system.