When Temporary Infrastructure becomes permanent risk

Temporary infrastructure is one of the biggest confidence tricks in live events.

Because the word temporary makes it sound optional. Like an overlay. Like something you can “work around” if needed.

In reality, the moment a structure is installed, it becomes a fixed constraint that reshapes access, egress, crowd behaviour, wind exposure, sightlines, and emergency response. The schedule may call it temporary. Operationally, it is permanent for as long as it’s there.

And that’s where risk creeps in: not because people ignore safety, but because teams keep treating temporary build elements as if they sit outside the core design.

The difference between “installed” and “integrated”

Most temporary structures are procured and installed by specialists, often under tight timelines. That part tends to be handled well.

The failure point is usually integration.

Integration means the structure is treated as part of the site’s “truth”, with consequences fully carried through:

• site drawings and access plans

• emergency routes and response paths

• crowd modelling and queuing space

• wind management and action levels

• lighting, audio, broadcast, branding, and power runs

• ops staffing and control positions

Temporary structures fail in predictable ways

When temporary infrastructure causes serious harm, it usually happens via a small set of predictable pathways.

1) Wind becomes a load case, not “weather”

Wind is one of the most common drivers in temporary structure incidents, especially for stages, roof systems, and fabric structures.

A well known example is the 2011 Indiana State Fair stage collapse, where a severe thunderstorm wind gust hit a temporary roof structure during a concert, killing 7 people and injuring 58.

That tragedy is not “bad luck”. It’s a reminder that temporary structures are engineered systems with operating limits, and wind is a primary input.

This is why good practice includes a wind monitoring plan with defined action levels, and procedures for escalation and evacuation before design limits are approached. The Australian Building Codes Board’s temporary structures guidance explicitly references on site wind monitoring plans, wind action levels, and evacuation procedures where design wind speeds may be exceeded.

The key point: wind management is not just a supplier issue. It is an event operations issue. Someone on the event side must own “what happens when we hit action level 1, 2, 3”.

2) Small geometry changes quietly remove safety margin

Temporary infrastructure loves to “borrow” space:

• a barrier line nudges out for cable management

• a scaffold stair lands where your queue was meant to form

• a tower base blocks a corner turning radius

• a merch unit expands its footprint because “we had to fit the fridge”

None of these changes look dramatic. That’s why they are dangerous.

They reduce usable circulation width, push crowds into new desire lines, and create pinch points that were not tested. The risk is cumulative and often invisible until peak load.

3) The structure works, but the site stops working

This is the sneaky one.

A structure can be correctly engineered and competently installed and still create operational risk because it breaks the site logic:

• emergency egress route no longer aligns with the crowd’s natural movement

• responder access is blocked by a build boundary or security line

• sightlines change crowd behaviour and cause clustering

• queuing space spills into a main circulation spine

In other words, the structure doesn’t “fail”. The event system fails around it.

“Tent book” is not paperwork theatre

One of the easiest places to see the industry acknowledging “temporary can still be serious” is standards for tents.

EN 13782:2005 covers safety requirements for mobile, temporary installed tents (more than 50 m² ground area), across design, manufacture, installation, maintenance, operation, examination, and testing. It also notes that for tents less than 50 m², it is not necessary to produce the tent book.

That concept matters even if you never touch the standard directly:

• there is a defined scope

• there is documentation expected

• the structure is treated as engineered, not improvised

If your event has multiple small tents clustered closely, it is worth remembering that draft updates and interpretations can cover aggregated area too.

The larger lesson: temporary structures are not “just equipment”. They have design assumptions, inspection regimes, operating limits, and conditions for safe use.

Wind action levels are not optional if wind is critical

A recurring feature across guidance is the need for a wind management plan, including monitoring, thresholds, and pre planned actions.

You will see this reflected in multiple places:

ABCB temporary structures guidance referencing wind monitoring plans, action levels, and evacuation procedures.

Event safety guidance and industry safety documents emphasising wind management plans and wind speed monitoring where wind is critical to structural safety.

A concrete example of threshold based design thinking shows up in reporting around the Ottawa Bluesfest stage collapse (2011). Later reporting cited design specifications where fabric wind walls should be released when winds exceed 80 km/h, and that with walls released the structure should withstand winds up to 120 km/h.

Two important takeaways for event producers:

Operating modes matter. A structure can have different safe states depending on configuration (walls attached vs released, ballast arrangements, roof trims, etc.).

Action must be pre planned. If your wind plan requires a wall release at a threshold, that needs time, labour, authority, and a rehearsed trigger. Not a panicked conversation in event control.

When “temporary” becomes permanent risk: the real mechanism

The risk becomes “permanent” when any of the following are true:

You cannot change it without major disruption

Once a stage, grandstand, marquee, tower, or scaffold system is installed, relocating it is rarely a quick fix. At that point, the structure is effectively permanent for the event.

Multiple teams assume someone else owns the constraint

This is the classic gap:

• supplier assumes the event team is managing site wide implications

• event team assumes the supplier is covering everything structural

• security assumes ops has updated crowd routes

• ops assumes production has updated the latest drawings

That’s how you get coherence failures, the kind that increase scrutiny and slow approvals. HSE’s work on temporary demountable structures exists because management frameworks and sector practices are central to safety outcomes.

Design assumptions are not translated into operational triggers

A structure might be engineered for certain loads, with conditions attached. If those conditions are not converted into clear operational triggers (monitor, escalate, pause, evacuate), you’ve got a gap.

That’s not a structural problem. That’s an event leadership problem.

A practical integration checklist for event producers

If you want temporary infrastructure to stop being “permanent risk”, treat it like a core site element from day one.

1) Lock a single source of spatial truth

One current site model and version controlled drawings that all documents reference (risk, emergency plan, crowd routes, traffic, production pack).

2) Translate supplier limits into an event wind action plan

• what is monitored

• who monitors it

• what are the action levels

• what is the exact action at each level

• who has authority to pause, make safe, or evacuate

Use formal guidance as your backbone for this approach, not vibes.

3) Stress test the footprint under peak assumptions

Do not test the layout at “average”. Test it under:

• peak arrival bunching

• peak amenity demand

• partial gate closure

• emergency vehicle access requirement

• simultaneous egress and service movements

4) Treat temporary structures as crowd behaviour shapers

Ask: “What do people do when they see this?”

Structures create gathering, sheltering, bottlenecks, and shortcuts.

5) Build a formal sign off moment for integration

Not “the structure is up”.

But “the structure is integrated into the site system”.

Temporary infrastructure is only temporary in the programme.

In the real world, once it’s installed, it is a fixed constraint with real physics, real behavioural impact, and real consequences.

Treat it as an overlay, and you inherit permanent risk for the life of the event.

Treat it as a core spatial element, and you buy back margin, clarity, and control.

Which, in live events, is about as close as we get to magic.