Building a Repertory-Ready Flow Standard for Touring Productions
The Show That Worked in Bristol Didn't Work in Glasgow
The technical rider was identical: rigging points, speaker placement, projected surfaces, set pieces. The stage manager ran the same call sheet. The director flew in for opening night of the Glasgow run and watched Act 2 die in a room that was twice the width of the corresponding Bristol space. The audience had dispersed into the corners. The intimacy that the blocking depended on wasn't a function of the set — it was a function of the corridor that funneled audience members into a compact cluster before they entered the scene. Glasgow's corridor was 40% wider. The funnel effect was gone.
Touring immersive shows face space, logistics, and audience flow choreography challenges that compound at each new venue (Future of Touring Theatre, Captitles) — the logistics challenge is solvable with a good technical rider. The flow choreography challenge requires something different: a flow standard that translates not just the physical requirements but the behavioral outcomes those requirements are designed to produce.
Stage managing immersive theater requires tracking audiences venue-by-venue; each touring space resets the challenge (Stage Managing Immersive Theatre, HowlRound) — experienced SMs who have toured multiple venues describe the reset process as intuitive but unreliable. Intuition built on one venue may misread the new venue's corridor dynamics entirely.
What a Repertory-Ready Flow Standard Looks Like
A technical rider specifies physical requirements. A flow standard specifies behavioral outcomes and the physical parameters needed to achieve them. The distinction is critical for touring productions: the physical parameters will change venue to venue, but the behavioral outcome — the distribution of audience members across scenes within specified sightline ranges — must stay consistent.
Technical riders standardize requirements across venues; LORT templates establish baseline documentation (Rider, Grokipedia) — the flow standard is an extension of this model. It specifies, for each scene: the intended sightline count range, the maximum density ceiling, the corridor resistance parameters required to achieve the intended distribution, and the fallback adjustment protocols for when the venue can't meet those parameters.
The corridor resistance parameters are the translatable unit. If Act 2 Scene 3 requires 20-30 sightlines and the Bristol venue achieved this through a 4-foot funnel corridor with residual audio bleed from the adjacent scene, the flow standard documents those parameters explicitly: funnel width of 4 feet ± 6 inches, audio bleed level of 65-70 dB at corridor mouth, 15% ambient lighting increase in the funnel relative to the adjacent hallway. A production designer entering a Glasgow warehouse can then assess whether the space meets those parameters or requires compensation measures.
PressurePath translates this framework into a venue-comparison model. The production team inputs the origin venue's geometry and the flow standard parameters. Before each touring installation, they input the new venue's geometry. PressurePath generates a difference map: which corridors are wider, which scenes have different acoustic profiles, which transitions have altered sightline geometry. The difference map drives a targeted list of compensating adjustments rather than a complete re-blocking.
This is the pressurized-water-in-pipes model applied to multi-venue touring: the pipe diameters and junction geometries change venue to venue, but the desired pressure levels at each scene are fixed. The task is to adjust the valves — corridor resistance parameters — to maintain the target pressure regardless of the pipe configuration.
Digital twin simulation tests venue-specific layouts and identifies bottlenecks before moving to a new space (Simulation for Venue Design, InControl) — for touring productions, this is the advance recce tool: run the new venue's geometry through the simulation before the production arrives and identify the flow problems before the truck is unloaded.
Frameworks for adapting site-specific work to new spaces while maintaining integrity (Preparing Site-Specific Immersive Work, HowlRound) provide the artistic methodology; the flow standard provides the quantitative infrastructure that makes that methodology executable by a production team that didn't build the original.
Building the Standard Before the First Tour Date
The flow standard needs to be built during the origin run, not retroactively before the touring installation. The origin run is when the behavioral data exists to validate the standard: SM logs showing actual scene populations, blocking arc integrity scores across performances, corridor dynamics under different ticket batch profiles.
The director case study demonstrates the principle in a single-venue context: quantified flow data produces better design decisions than intuition. For touring, that quantified data becomes the source document for the flow standard.
Non-traditional venues lack infrastructure; each site requires flow re-engineering (Making Theatre in Non-Traditional Venues, HowlRound) — the flow standard reduces re-engineering time by specifying what parameters need to be re-engineered and what compensating adjustments are acceptable substitutes. A touring production manager who knows that the Glasgow venue's wide corridor needs a partial baffle to replicate Bristol's funnel has a solvable problem. A touring production manager who only knows "something felt different" does not.
The scaling decisions from 80 to 400 audience members interact with the touring standard when productions scale at new venues. If Bristol ran at 120 and Glasgow opens at 180, the flow standard needs to account for the capacity difference alongside the geometry difference. PressurePath handles this as a compound simulation: new venue geometry plus new capacity level, generating a combined difference map.
Cross-format comparison: franchise-wide flow standards for escape room chains face the same venue-variation problem at scale — dozens of locations rather than a touring schedule, but the same translation challenge. The flow standard methodology is identical; the immersive theater version has additional complexity from non-linear audience movement and sightline-specific design requirements.
The Flow Standard Is the Show's Second Technical Rider
Productions that have toured successfully describe the moment a venue-specific problem was solved efficiently as the result of institutional knowledge — an SM who had seen the problem before, a production manager who knew the right compensation measure. The flow standard encodes that institutional knowledge into a document that survives staff turnover and scales to unfamiliar venues.
A point about where the flow standard fits in the production timeline: the document is distinct from the technical rider, but it should be distributed alongside it. When a venue production manager receives the technical rider six weeks before opening, they receive a list of physical requirements. They do not currently receive any behavioral requirements — no specification of what the space needs to achieve at a flow level, no documentation of which physical parameters drive that achievement. Adding the flow standard to that package means the venue production manager assesses both the physical and behavioral requirements simultaneously, which is when the compensating adjustments are cheapest to implement.
The Repertory Theatre framework (Wikipedia) emphasizes resource reuse and consistency as core operational challenges — the flow standard is the audience-behavior equivalent of the repertory technical package: a pre-built, reusable specification that reduces the rehearsal and reconfiguration time at each new venue. Productions that have built a flow standard report that the venue-opening process becomes more predictable: rather than discovering problems during technical rehearsal, the production arrives knowing the gap list and having pre-planned responses.
This matters particularly when the touring schedule is tight. A production opening in Glasgow on Friday that was in Bristol until Sunday has five days to identify and fix venue-specific flow problems. Without a flow standard, those five days are spent discovering problems. With a flow standard, they're spent implementing pre-planned compensating adjustments from a difference map generated a week earlier.
The flow standard also provides a feedback loop to the show's artistic development. If the Glasgow venue requires a corridor baffle to replicate Bristol's funnel, and the baffle works, that baffle becomes a production element that travels with the show. If the baffle improves the scene population over Bristol's baseline — because the controlled geometry turns out to be tighter than Bristol's organic funnel — the director may specify the baffle as a permanent technical element rather than a venue-specific compensation. This is how touring productions improve: each venue's constraint becomes a potential design innovation.
PressurePath generates the flow standard as a structured output from the origin-run simulation, formatted for production manager use at each touring installation. Touring immersive theater companies preparing their first or next multi-venue run are invited to apply for PressurePath's touring simulation program — build the standard before the truck leaves, not after the second venue opening night.
The ROI case for investing in a flow standard is clearest when calculated against the cost of a failed venue opening. A touring production that travels to a new venue and spends the first two weeks of its run recovering from audience-distribution problems has paid for flight tickets, accommodation, advance marketing, and pre-show press coverage — all against a production that doesn't work yet. Venue rent during that two-week correction period continues regardless of whether the show is performing at its intended quality. The flow standard, built over one to two weeks during the origin run, costs a fraction of a single underperforming venue opening.
For companies that have already toured and experienced venue-specific flow failures, a retrospective flow audit is possible: PressurePath can model the origin venue and the failed venue in parallel, identifying the corridor geometry differences that caused the failure and generating a set of compensating adjustments that would have prevented it. That retrospective model becomes the baseline for the next touring installation, reducing the probability of repeating the same class of failure.
The touring immersive theater sector is small enough that production quality reputation travels quickly. A production that opens successfully in three consecutive cities builds a track record that generates advance press and stronger ticket pre-sales at each new venue. A production that consistently struggles in its first week at new venues builds the opposite reputation — and that reputation is difficult to reverse. The flow standard is the infrastructure that protects the touring quality record.