A tabletop exercise becomes useful when something happens that forces the team to reconsider its response. 

The following example comes from a recorded STRX Tabletop exercise built around an oil and gas facility. It is an exercise scenario, not a real emergency or claimed client outcome.  

It started simply. 

CCTV showed smoke near a pump skid. 

That was enough. 

1. First, establish what is actually happening 

The first challenge was not suppression. 

It was information. 

Where was the fire? 

Who needed to know? 

What information was still missing? 

The exercise recorded the pump skid as the incident location and prompted participants to establish a shared understanding before moving forward. 

That matters because teams cannot coordinate effectively if they are responding to different versions of the same incident. 

2. Then make the first response decisions 

Once the situation was understood, resources began to move. 

Fire team deployment positions were identified. Response vehicles were placed. A downwind area was marked as unsafe. 

Then the first real complication arrived: 

The automatic shutdown partially failed. 

Now the team had a decision to make. 

Do they initiate a full shutdown or a partial shutdown? 

That single inject changed the exercise from a straightforward response into a decision problem. 

3. Escalation changes the priorities 

The wind direction changed. 

The incident then escalated into a full surface tank fire. 

Additional resources were requested and communications overload was reported in the control room. 

This is where the value of the exercise becomes clearer. 

The facilitator is no longer asking participants what the emergency plan says. 

The team has to apply that plan while the situation becomes less convenient. 

Which resources matter most? 

What information needs to move first? 

Who needs to make the decision? 

What happens if the original response is no longer enough? 

4. Stabilisation introduces a different kind of pressure 

Once the fire response was established, the exercise did not simply end. 

Spare equipment was delayed. 

Crew fatigue became a concern. 

One response asset became non-operational. 

The full surface tank fire was eventually suppressed and teams repositioned to deal with the remaining pump skid fire. 

These are less dramatic problems than a large fire. 

They are also exactly the type of problems that can expose whether a response is sustainable. 

The question changes from: 

Can we respond? 

to: 

Can we keep responding effectively? 

5. Recovery turns activity into learning 

Once the immediate scenario was controlled, participants reviewed what had happened. 

What worked well? 

What gaps appeared? 

Which teams were involved? 

Which teams were not? 

The exercise record noted, for example, that medical and security resources had not been deployed during the scenario. 

That observation does not automatically mean the response was wrong. 

It gives the facilitator and organisation something specific to review. 

Was their absence appropriate? 

Should they have been involved? 

Does the emergency plan make that clear? 

That is where the learning begins. 

The scenario was not the real product 

The fire looked dramatic. 

But the useful output was the chain of decisions around it. 

Smoke was detected. 

Resources were deployed. 

A shutdown failed. 

The fire escalated. 

Communications became overloaded. 

Equipment was delayed. 

Fatigue developed. 

Assets failed. 

The incident was controlled. 

Then the response was reviewed. 

STRX Tabletop recorded those injects, decisions, checkpoints, annotations and facilitator observations as the exercise progressed, producing a structured exercise record at the end.  

That record gives the debrief something concrete to work from. 

Why this matters 

A tabletop exercise does not need to predict the exact emergency that will happen. 

It needs to expose how the organisation behaves when its assumptions stop working. 

That is the value of controlled escalation. 

Start with a believable incident. 

Introduce a realistic problem. 

See what the team does. 

Then introduce the next one. 

The objective is not to make the scenario as complicated as possible. 

It is to make the response reveal something worth learning from. 

Try STRX Tabletop: 

 https://structurus.com/en/strx-tabletop 

For more information, email info@structurus.com.