Event Lifecycle Phases¶
Core Idea¶
A hazard-bearing event is decomposed into a pre-event / event / post-event trichotomy, and each phase becomes the primary unit of intervention design — because the same event needs three distinct intervention systems with different tempo, decision logic, and political economy, not one.
How would you explain it like I'm…
Before, During, After
Anything risky, like a storm, has three parts: before it happens, while it's happening, and after it's over. Each part needs its own kind of plan, because getting ready, staying safe during, and cleaning up afterward are all really different jobs. If you try to use one plan for all three, you'll mess it up.
Three Plans, One Event
Event Lifecycle Phases means breaking a risky event into three parts, before, during, and after, and treating each part as its own thing to plan for, instead of treating the whole event as one. Each phase works differently: before is slow and about lowering the chances, during is fast and urgent, and after is about repairing and learning. So one event actually needs three different plans, not one, and squishing them together wastes effort and money. The three are connected in a loop: what you learn cleaning up after one event should make you better prepared for the next one. If you cut that learning loop, the system can't get better from its own mistakes. The most common mistake is not telling the three phases apart clearly.
The Pre/During/Post Split
Event Lifecycle Phases is the structural pattern of decomposing a hazard-bearing event into a pre-event / event / post-event trichotomy and treating each phase as the primary unit of intervention design rather than treating the event as a single object. Each phase has a characteristically different tempo (slow / fast / medium), decision logic (probabilistic / urgent / restorative), intervention shape (preventive / responsive / reparative), success metric (events not occurring / events controlled / capacity restored), and political economy (invisible payoff / visible heroics / contested recovery). The structural commitment is that the same event needs three distinct intervention systems, not one; collapsing them into a single planning frame mis-allocates effort, attention, and budget. It has four load-bearing parts: a class of hazard-bearing events with a recognisable onset and end, a pre-event regime where probability and severity can still be reshaped by present investment, an event regime where action is constrained and dominated by previously deployed capacities, and a post-event regime where damage and signal are processed to restore the system and update the pre-event regime. The cycle is itself load-bearing, since today's recovery is tomorrow's preparedness, so cutting the post-event feedback severs the system's ability to learn from its own events.
Event Lifecycle Phases is the structural pattern of decomposing a hazard-bearing event into a pre-event / event / post-event trichotomy and treating each phase as the primary unit of intervention design rather than treating the event as a single object. Each phase has a characteristically different tempo (slow / fast / medium), decision logic (probabilistic / urgent / restorative), intervention shape (preventive / responsive / reparative), success metric (events not occurring / events controlled / capacity restored), and political economy (invisible payoff / visible heroics / contested distribution of recovery). The structural commitment is that the same event needs three distinct intervention systems, not one; collapsing them into a single planning frame mis-allocates effort, attention, and budget. The pattern has four load-bearing parts: a class of hazard-bearing events with a recognisable onset and end; a pre-event regime where the event has not happened but its probability and severity can be reshaped by investments made now; an event regime where the event is unfolding and the action space is constrained, time-pressured, and dominated by previously deployed capacities; and a post-event regime where the event is over but its damage and signal must be processed to restore the system and update the pre-event regime for the next cycle. The three regimes are connected: post-event learning feeds back into pre-event design, pre-event readiness shapes what is possible during the event, and event experience shapes both. The cycle structure is itself load-bearing, since today's recovery is tomorrow's preparedness and today's incident is tomorrow's hardening priority, so the post-event phase carries a structural responsibility to feed the pre-event phase through lessons-learned databases, after-action reviews, and control updates, and cutting that feedback severs the system's ability to learn from its own events. Failing to draw the phases distinctly is the most common diagnostic failure.
Broad Use¶
- Disaster management: mitigation / response / recovery, each with its own funding stream and profession.
- Cybersecurity: hardening / incident response / post-incident review.
- Medicine: prevention / acute care / rehabilitation, organising budgets and specialties.
- Software reliability: reliability engineering / on-call response / blameless post-mortem.
- Climate policy: mitigation / adaptation / loss-and-damage, splitting along distinct politics and horizons.
- Workplace safety: hazard reduction / emergency response / return-to-work.
- Conflict and security: prevention / crisis response / post-conflict reconstruction.
Clarity¶
Forces three questions that single-object framing conflates — what investments bend the probability now, what capacities deploy during the event, what processes repair and learn after — and names the chronic over-investment in the visible response phase.
Manages Complexity¶
Separates decision regimes that cannot be evaluated under one framework — probabilistic on decade horizons, urgent on minutes, restorative on months — and makes the cycle feedback from recovery into preparedness an explicit design object.
Abstract Reasoning¶
Licenses reasoning about phase-specific intervention catalogues, handoff design at the seams where chronic failures live, and the political-economy asymmetry that predicts budget skew toward the heroic middle phase.
Knowledge Transfer¶
- Disaster mitigation → cybersecurity: under-investment in mitigation predicts larger response costs, with return-on-mitigation porting cleanly.
- SRE → workplace safety: the blameless post-mortem — insulating the post-event phase from blame — is borrowed wholesale.
- Three-phase budgeting → climate: drawing separate funding lines per phase is what loss-and-damage rediscovered.
Example¶
Hurricane management runs mitigation (decade-horizon, invisible payoff), response (minute-horizon, visibly heroic), and recovery (month-horizon, contested), with recovery's lessons feeding the next mitigation cycle — and predictable over-investment in the heroic middle.
Relationships to Other Primes¶
Parents (1) — more general patterns this builds on
- Event Lifecycle Phases is a kind of, typical State and State Transition — A specific, normatively-loaded specialisation: the states are pre-event/event/post-event, the transitions onset and termination, and each state carries its own intervention logic, time horizon, stakeholder, and political economy that the bare abstraction does not supply. The file: 'a specific, normatively-loaded specialisation of that skeleton'.
Children (1) — more specific cases that build on this
- Incident Response is a kind of Event Lifecycle Phases — The file states it outright: incident_response IS "that middle phase specifically, examined from within" — the acute phase of the pre/event/post trichotomy that event_lifecycle_phases (valid candidate, CAND-R25-015-02, already a Phase-C link) spans. event_lifecycle_phases allocates effort ACROSS the three regimes; incident_response is the acute regime's internal structure. Clean part-of/child-of (a phase within the lifecycle), explicitly the "broader frame incident response sits inside." High conviction. Distinct from controlled_reentry (the adjacent return phase, not a parent) which Phase-C correctly kept separate.
Path to root: Event Lifecycle Phases → State and State Transition
Not to Be Confused With¶
- Event Lifecycle Phases is not Temporal Dynamics because it imposes a discrete trichotomy with a regime-change at each boundary, whereas temporal dynamics describes how a system evolves continuously over time.
- Event Lifecycle Phases is not State and State Transition because it is a normatively-loaded specialisation with characteristic tempo, stakeholder, and politics per phase, whereas state-and-transition is the bare abstraction of states and the moves between them.
- Event Lifecycle Phases is not FMEA because it spans all three regimes and allocates across them, whereas FMEA enumerates and rates failure modes within the pre-event phase only.