CAST: causal analysis based on systems theory

CAST analyses accidents as system control problems, reconstructing decisions, information and conditions that allowed the loss.

In brief

Learn across the system instead of stopping at the final visible error.

Contents
  1. Investigating how the loss became possible
  2. Reconstruct responsibilities and context
  3. Avoid conclusions dictated by the outcome
  4. Traceable recommendations
  5. Related concepts
  6. References

A–Z dictionary →

Investigating how the loss became possible

CAST, Causal Analysis based on System Theory, applies the STAMP model to learning after accidents or incidents. It examines why existing controls failed to prevent the loss and which changes could strengthen the system’s safety controls.

It differs from root cause analysis reduced to a search for one explanation. Investigation considers interactions and decisions across levels, without assuming that the final visible action contains the complete explanation of the event.

Reconstruct responsibilities and context

The loss, system boundaries and necessary safety constraints are defined. Analysis then examines the control structure: responsibilities, actions, available information and feedback channels, including external organisations where they are relevant to the case being investigated.

The question is not only what an actor did, but why it could appear appropriate given available information. Pressures, objectives, resources and ambiguous signals help explain decisions without turning every explanation into an excuse or replacing separate legal responsibilities.

Avoid conclusions dictated by the outcome

Knowing how an accident ended makes earlier signals appear obvious. CAST seeks to reduce that bias and document what people could know at each moment, separating it from information discovered during the subsequent investigation.

For example, authorisation based on incomplete information calls for examination of how that information was assembled and verified. Simply concluding that someone should have checked more carefully fails to explain why decisions could rest on an incorrect picture of the operation.

Traceable recommendations

Recommendations should address specific control weaknesses, such as incompatible responsibilities, missing feedback or inadequate decision criteria. Follow-up should check implementation and whether changes actually improve the ability to maintain the necessary safety constraints.

CAST is neither a template that automatically produces answers nor a mechanism for assigning blame. It requires evidence, access across organisational levels and competent analysis. A useful report preserves unresolved questions and states its limitations rather than presenting untested hypotheses as established facts. The strength of each conclusion should remain proportionate to its supporting evidence.

References

  1. Nancy Leveson: CAST Handbook. Official source
  2. MIT: aplicación de STPA y CAST a mantenibilidad. Official source

Editorial information

Publication date: 2 November 2026.

Editorial responsibility: Sabentis Editorial Team.

Author: Pablo RodríguezLinkedIn

Executive Vice President of the ORP International Foundation and Chief Financial Officer of Sabentis.

Request a Demo

Discover all that Sabentis can do for your organization.

Try Sabentis

request a demo
stars 5
GetApp Software Advice Capterra