Community Recovery Plan¶
Governance plan — instantiates Recovery Trajectory Management
The governing charter for a whole population's recovery — it settles what "recovered" should mean, distributes the burden fairly, and braids outside aid into one accountable trajectory.
A Community Recovery Plan is the charter an affected population adopts to steer its own recovery. Its distinctive job is not to sequence work but to answer the political questions a purely technical recovery leaves open: recovered to what, at whose cost, and paid for by which outside help. It is the mechanism that turns "recovered to what?" into a decision the community owns rather than a default that drifts toward whoever is loudest or best-insured. Where an operational plan schedules tasks, the community plan settles the endpoint (rebuild the old neighborhood, relocate it, or build it back differently), names who carries which burden, and braids the tangle of external aid — mutual aid, philanthropy, insurance, state and federal programs — into a single accountable line. Its authority comes from legitimacy, not from a Gantt chart: it binds because the people it governs helped set it.
Example¶
A river town of roughly 30,000 loses a third of its housing and most of its downtown to a once-in-500-years flood. Within weeks three futures compete: rebuild exactly as before, buy out the floodplain and relocate, or elevate-and-adapt in place. Left to inertia, the best-insured homeowners rebuild first while renters and a mobile-home park wait indefinitely. The community recovery plan is where the town decides instead of defaulting. Through neighborhood assemblies and a standing recovery committee it fixes an explicit endpoint portfolio: managed-retreat buyouts for the deepest floodplain, elevated reconstruction in the mid-zone, and near-baseline rebuild uphill. It stands up a burden ledger that tracks whether renters, the uninsured, and non-English-speaking households are being served on the same clock as everyone else. And it opens one coordinated channel onto federal, state, and philanthropic funding so money is mapped to phases rather than chased ad hoc.
The outcome is a published, adopted document with teeth: an endpoint each affected group can see themselves in, a named body accountable for the equity ledger, and a funding map that says which stream pays for which phase. The argument stops being "are we back to normal?" and becomes "are we on the trajectory we chose, and is anyone being left off it?"
How it works¶
- Set the endpoint participatorily. The plan convenes affected stakeholders to choose and justify a recovery endpoint — baseline, minimum viable, or transformed — often differently per neighborhood or function, and records the reasoning so the choice can be revisited but not quietly abandoned.
- Keep a burden ledger. It maintains a running account of who bears costs and who receives benefits, disaggregated by the groups most likely to be left last, and treats an imbalance as a condition to fix, not a footnote.
- Run one front door for aid. External support is mapped onto the trajectory through a single accountable interface, so funding streams with different rules, timelines, and reporting arrive when each phase needs them.
- Renegotiate as evidence lands. Because legitimacy decays if the plan stops matching reality, it is re-ratified as damage, funding, and stakeholder needs become clearer.
Tuning parameters¶
- Participation depth — from a comment period to co-authored, veto-bearing assemblies. Deeper participation buys legitimacy and local knowledge but slows the plan and can amplify well-organized factions.
- Endpoint granularity — a single town-wide endpoint versus a per-neighborhood portfolio. A portfolio fits uneven damage but multiplies the coordination and equity bookkeeping.
- Burden-sharing rule — equal shares versus needs-weighted allocation. Needs-weighting protects the vulnerable but is contestable and demands defensible data.
- Aid-integration tightness — loose signposting versus a binding funding map with named owners per stream. Tighter integration prevents gaps and double-funding but is brittle when a program's rules change.
- Revision cadence and sunset — how often the charter is re-ratified and when it formally closes. Frequent revision keeps legitimacy fresh; too frequent invites endless re-litigation.
When it helps, and when it misleads¶
Its strength is legitimacy: it converts a contested, capture-prone situation into a shared, revisable commitment, and it is the one mechanism positioned to stop recovery from advancing on the backs of the people with the least voice. When the endpoint itself is disputed — rebuild versus retreat — nothing else in the archetype can substitute for it.
Its signature failure mode is transformation capture: recovery becomes cover for an agenda unrelated to the disruption — a favored redevelopment, a land grab — while displaced residents stay unstable.[n1] A close cousin is the symbolic plan with no equity ledger and no teeth, adopted to signal progress while the real allocation happens elsewhere. The discipline that guards against both is to bind the endpoint to the burden ledger and to genuine, continuing participation by the affected — so any drift toward capture shows up as an equity gap someone is accountable to close, and the charter can only be changed in the open.
How it implements the components¶
recovery_endpoint_definition— its central act: a participatory, justified choice of endpoint (baseline / minimum viable / transformed), recorded per neighborhood or function so recovery cannot drift or quietly redesign.equity_and_burden_monitor— a standing ledger of who bears cost and who benefits, disaggregated so recovery does not advance by leaving the least powerful last.external_support_interface— one accountable channel that maps mutual-aid, philanthropic, insurance, and government streams onto the trajectory's phases.
It does not record any single system's disruption or run its phase gates — disruption_and_displacement_record, phase_map, and phase_gate_and_reentry_rule belong to Incident Recovery Plan, its nearest twin. The separation is sharp: a community recovery plan settles what "recovered" should mean for a whole population and who pays for it, while an incident recovery plan takes the endpoint as given and governs one bounded system's technical path back.
Related¶
- Instantiates: Recovery Trajectory Management — this plan is the governance-and-legitimacy layer that makes the endpoint a chosen, owned decision.
- Consumes: Damage Assessment Survey supplies the damage-and-capacity picture a credible endpoint must be grounded in.
- Sibling mechanisms: Incident Recovery Plan · Critical Function Triage Matrix · Phased Restoration Schedule · Recovery Dashboard · Recovery After-Action Review · Damage Assessment Survey
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: The governing charter for a whole population's recovery — it settles what 'recovered' should mean, distributes the burden fairly, and braids outside aid into one accountable trajectory, making its operative form a non-executable information artifact that externalizes static or prospective structure.
Independent corroboration: The frozen evidence defines Community Recovery Plan as 'The governing charter for a whole population's recovery — it settles what 'recovered' should mean, distributes the burden fairly, and braids outside aid into one accountable trajectory', so its operative form is Representation, Specification & Plan.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Disaster Management & Risk Reduction
Origin pattern: Single lineage
Present-day reach: Specialized
Rationale: Disaster-recovery practice cohered whole-community plans that define the recovery endpoint, coordinate outside aid, and allocate burdens after a shock.
Related originating lineages:
- Public Administration & Policy — Public planning contributes legitimacy, distributional choice, intergovernmental coordination, and accountability.
Review resolution: The source is a population-owned recovery charter deciding endpoint, burden distribution, and use of outside aid after disaster. Community recovery planning cohered in disaster management; public administration supplies accountable implementation but does not require a separate synthesis classification.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The plan's legitimacy is a wasting asset: the further reality drifts from the adopted charter, the less it binds. That is why re-ratification is a feature, not an admission of failure — a community plan that is never reopened has usually stopped governing the recovery and started decorating it.
[n1] FEMA's National Disaster Recovery Framework organizes recovery around Recovery Support Functions and a "whole community" mandate precisely because unmanaged recovery tends to concentrate benefit and displace the vulnerable; its accountability structures are a real-world guard against transformation capture. ↩