| Course | HLTH 6300 Disaster Response and Recovery |
|---|---|
| Week | Week 10 |
| Paper type | After-action review paper |
| Length | About 1,000 words, 6 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | MS in Emergency Management |
| Updated | October 2026 |
Free sample paper for HLTH 6300 Week 10
After-Action Review of the April Mill River Flood Response: What Held, What Failed and What the Record Supports Changing
Student Name
Walden University
HLTH 6300: Disaster Response and Recovery
Instructor Name
Month Day, Year
After-Action Review of the April Mill River Flood Response: What Held, What Failed and What the Record Supports Changing
Scope and Method
This review evaluates the county's response to the April Mill River flood from the flood warning through the end of sheltering. It follows the structure of the national exercise and evaluation program, which judges performance against objectives, records strengths and areas for improvement, identifies root causes and assigns corrective actions to organizations (Federal Emergency Management Agency, 2020). Each finding is stated against an objective that existed in the county's emergency operations plan before the flood, not against hindsight. The evidence comes from the emergency operations center log, situation reports, call records, shelter registrations and interviews with agency leads. The review names systems and functions and does not assign fault to individuals. Its setting, like the rest of this term's work, is an invented county.
Objectives and Results
Table 1 sets out the six objectives the plan contained and how the response performed against each.
Table 1
Response Objectives From the County Plan and Results (Composite County)
| Objective in plan | Result | Evidence |
|---|---|---|
| Open a shelter within 4 hours of an evacuation advisory | Met | Shelter opened at 18:00, about 2 hours after the advisory |
| Evacuate long-term care facilities before access roads close | Met, with a narrow margin | 96 residents moved by 09:30; road closed about 40 minutes later |
| Issue coordinated public information within 1 hour of a significant change | Not met | Conflicting water messages for about 21 hours before joint information center opened |
| Track all resource requests through the emergency operations center | Partly met | Contractor requests by public works not logged; duplicate pump orders |
| Account for all sheltered residents | Partly met | Two informal shelters unreported until Day 4 |
| Contact all medical needs registry residents within 24 hours | Partly met | 52 of 61 reached by Day 4 |
What Held
Early activation and declaration. The emergency operations center activated three hours after the flood warning, before any road had closed, and the afternoon emergency declaration let the county close roads and spend quickly ahead of the crest. Sheltering. The shelter opened well ahead of the objective, staffed by the Red Cross with county support. Long-term care evacuation. All 96 nursing home residents were moved without injury. The regional health care coalition located receiving beds within hours, reflecting the coordination that national health care preparedness guidance expects of coalitions (Office of the Assistant Secretary for Preparedness and Response, 2016). Mutual aid. Swift water teams from neighboring counties arrived within three hours of the request.
What Failed
Public information. The objective of coordinated messages within one hour was not met. For about 21 hours, the county, the city and the wastewater utility issued messages separately, and the city's incorrect statement that tap water was unsafe went uncorrected until the joint information center opened. Resource tracking. Public works requested pumps directly from contractors, outside the emergency operations center's tracking, producing a duplicate order and an idle crew. Shelter accounting. Two church shelters opened informally and did not report to mass care for two days. Registry contact. Nine residents on the medical needs registry were not reached by Day 4; four had outdated phone numbers.
Root Causes
The failures share a pattern: related work happened outside the function responsible for it. The joint information system existed in the plan but had no activation trigger, so it waited for a decision no one was assigned to make. Public works had standing authority to call contractors in routine operations and no rule requiring emergency requests to be logged. The churches had no agreement with the county and no way of knowing they should report. The medical needs registry had not been updated in fourteen months. National incident management guidance stresses common processes for public information and resource management precisely because work done outside them is invisible to coordinators (Federal Emergency Management Agency, 2017).
The Nursing Home Margin
The nursing home evacuation met its objective, but by about forty minutes. The evacuation order came at 02:00, after a revised crest forecast, because the facility's plan tied evacuation to a forecast threshold that the earlier forecast had not reached. Had the revised forecast come two hours later, residents would have been moved through floodwater or sheltered in place on an upper floor without power. The record supports changing the trigger from a single forecast threshold to a combination of forecast and road conditions, and starting transport arrangements at the earlier threshold so that a later order can be executed faster. Treating the success as complete would miss the near miss inside it.
Corrective Actions
Table 2 lists corrective actions.
Table 2
Improvement Plan
| Area | Corrective action | Responsible organization | Due |
|---|---|---|---|
| Public information | Add an automatic trigger to activate the joint information system at partial activation of the emergency operations center | County emergency management | 3 months |
| Resource tracking | Require all emergency procurement to be logged in the emergency operations center within 1 hour | County administrator; public works | 3 months |
| Shelter accounting | Sign reporting agreements with congregations likely to open shelters | Mass care lead; long-term recovery group | 6 months |
| Medical needs registry | Update registry twice a year and add alternate contacts | County health department | 6 months |
| Long-term care evacuation | Revise nursing home trigger to combine forecast and access conditions; pre-arrange transport at lower threshold | Nursing home; health department; health care coalition | 6 months |
What the Record Does Not Support
The record does not support some changes proposed after the flood, and the review says so because unsupported changes can crowd out the ones that matter. A call to order mandatory evacuation of the river neighborhoods on Day 1 is not supported: the forecast then did not justify it, and the voluntary advisory produced no deaths in homes. A proposal to replace the Red Cross as shelter operator is not supported by any shelter performance finding. The one death, a driver on a flooded road, occurred on a road that had been closed with barricades; the record supports reviewing barricade placement but not a conclusion about the driver's decision.
References
Federal Emergency Management Agency. (2017). National Incident Management System (3rd ed.).
Federal Emergency Management Agency. (2020). Homeland Security Exercise and Evaluation Program (HSEEP).
Office of the Assistant Secretary for Preparedness and Response. (2016). 2017-2022 health care preparedness and response capabilities. U.S. Department of Health and Human Services.
The Walden HLTH 6300 Week 10 instructions
After-action reviews typically ask you to evaluate a response against objectives that existed at the time. List those objectives and the result for each, with evidence. Record strengths as well as failures. Trace each failure to a root cause in systems, plans or procedures, not to individuals. Examine near misses inside apparent successes. Assign corrective actions to organizations with due dates, in an improvement plan. State which proposed changes the record does not support, which guards against hindsight. Follow the national exercise and evaluation structure where your course expects it, and cite the evidence sources you used. Keep the narrative short; the tables carry most of the evidence a reader needs.
How this HLTH 6300 Week 10 example is built
The scope section describes the method, evidence sources and the rule against individual fault, citing the HSEEP guidance. A table lists six objectives from the plan with results and evidence. The strengths section credits early activation, sheltering, the nursing home evacuation with health care coalition support and mutual aid. The failures section covers public information, resource tracking, shelter accounting and registry contact. The root causes section traces each to a system gap, citing the National Incident Management System. A section examines the forty-minute evacuation margin. A second table assigns corrective actions. The closing lists changes the record does not support. Every finding in the narrative points back to a row in the first table, and every corrective action in the second names an organization and a date.
HLTH 6300 Week 10 rubric: what earns full marks
The discipline is in the evidence. Graders look for findings stated against objectives that existed before the event, each supported by the record. Strengths should be recorded alongside failures. Root causes should be located in systems, plans and procedures, and reviews that assign fault to individuals lose substantial credit. Examining near misses shows depth. Corrective actions should be specific, assigned to organizations and dated. Stating what the record does not support guards against hindsight and earns credit. Following the national exercise and evaluation structure and citing it accurately rounds out the evaluation. A review that a skeptical agency head could read without feeling blamed, yet still act on, has struck the right balance.
Common HLTH 6300 Week 10 mistakes, and how to avoid them
After-action reviews often list what went wrong with the benefit of hindsight, judge people rather than systems or recommend broad changes without owners. Others record only failures. Some treat every success as complete, missing the near misses inside them. Find the plan's objectives before reading the event record, and write each as a row in a table. Fill in the result and evidence for each before writing any narrative. Then ask, for each shortfall, what in the system allowed it. For your scenario, we can draft an after-action review, built on pre-existing objectives and evidence. Name the organization responsible for every corrective action, never a person.
Get a HLTH 6300 Week 10 example written to your instructions
After-action reviews get written from the review task as the classroom set it, the opening request free of charge, 24 to 48 hours after it arrives. What repays study is a finding carrying its evidence all the way into a recommendation. A review an organization ran is that organization's document and stays that way.
More HLTH 6300 papers and MS in Emergency Management samples
- HLTH 6300 Week 1: Incident Decision Overview
- HLTH 6300 Week 2: Coordination Failure Post
- HLTH 6300 Week 3: Function Coordination Analysis
- HLTH 6300 Week 4: Agency Situation Report
- HLTH 6300 Week 5: Resource Request Memo
- HLTH 6300 Week 6: Response Partner Peer Reply
- HLTH 6300 Week 7: Disaster Damage Assessment
- HLTH 6300 Week 8: Disaster Recovery Framework
- HLTH 6300 Week 9: Recovery Unmet Needs Brief
- HLTH 6300 Week 11: Recovery Obligation Paper
- HLTH 6200 Week 10: Flood Mitigation Plan
- HLTH 6100 Week 10: Need-Based Recovery Aid Paper
HLTH 6300 Week 10 questions, answered
Where can I find a free HLTH 6300 Week 10 sample paper?
The complete after-action review and its improvement plan are posted on this page free.
What objectives does the HLTH 6300 Week 10 review use?
Six objectives from the county plan, covering sheltering, long-term care evacuation, public information, resource tracking, shelter accounting and registry contact.
Which objective was clearly not met?
Coordinated public information within one hour, which went unmet for about 21 hours.
What root cause links the failures?
Related work happened outside the responsible function, such as messages issued without the joint information system and contractor calls outside resource tracking.
Why does the review examine the nursing home evacuation?
It met its objective by only about forty minutes, a near miss that supports changing the evacuation trigger.