Emergency plan: testing dependence on one person or resource

An equipment list does not show who can use it, where it is or what it needs to function. A plan may assign communication, position information and decisions to one person without recognising that dependency.

It may also count two information paths sharing one electrical supply. This lesson’s exercise does not simulate a real emergency: discussion, without activating systems, examines which functions would become unavailable in a declared scenario.

RNLI recommends an emergency action plan and onboard briefing. MCA emphasises shared understanding of tasks, roles and resources.

Our dependency analysis is an editorial application of those principles, not an officially certified model. The distinction matters: finding a gap in discussion is useful, but does not establish that a practical response has been trained or that everyone can perform their roles in actual conditions.

To make reasoning checkable, the scenario needs one concrete change. For example, person A becomes unavailable, or one power resource is lost.

That must not be treated as equivalent to every failure occurring at once. Retaining the remaining conditions makes the mechanism visible.

If scenario, crew and equipment continually change, it becomes difficult to identify which dependency was actually found.

Two devices are not necessarily two independent alternatives. They may depend on the same battery, antenna, accessible compartment or familiar person.

The figure shows one shared resource connected to two functions. Lines represent dependency rather than wiring or a recommended architecture.

If the central resource becomes unavailable, two boxes to its right do not themselves provide continuity for both functions.

An alternative may have different limitations: endurance, coverage, access, training or available information. The exercise should record them instead of calling any similar-looking object equivalent.

No alerts are transmitted or circuits disturbed to prove a hypothesis. Such tests have their own requirements and risks.

Tabletop analysis identifies questions for competent familiarisation and verification, remaining separate from execution.

If one person takes on previously shared tasks, workload changes. Saying B will do everything describes neither time, attention nor competence.

Some needs may occur simultaneously while others require access to different places. The record must expose that competition.

The aim is not a universal priority sequence, because emergency type and actual conditions change what is urgent.

A useful conclusion identifies the gap and confirmation status: information inaccessible without A, an unfamiliar alternative or an unverified shared electrical dependency. “Plan approved” would be excessive after this exercise.

Even if discussion resolves a question, explaining an action remains different from performing it in suitable training. Documentation should preserve who verified what and when.

A second round can remove a different resource while retaining the first. Compare affected functions to discover whether the scenarios genuinely share a dependency.

Describing both only as “general failure” loses that information. Exercise quality comes from a bounded change and explained consequences, not adding dramatic failures to make discussion more impressive.

Distinct records allow a later review to see which assumption was actually tested.

The diagram is not an abandonment, fire, recovery or treatment plan. It is a way of critically reading preparation for those subjects without pretending they share one response.

Subsequent review may lead to training, maintenance or clarified roles according to the finding. Value lies in a demonstrated concrete dependency, not filling an emergency grid with words nobody aboard can connect to current resources.