Four problems from a composite April flood become owned corrective actions, each with a responsible position and a completion date, in the PU545 Unit 9 after action report. Searches like "pu 545 unit 9 assignment example", "pu545 unit 9 sample" and "pu545 unit 9 example" land here.
What a finished PU545 Unit 9 after action report looks like
At nine pages or so, the report uses the after action and improvement plan format from federal exercise doctrine, known as HSEEP, which many jurisdictions apply to real events as well as exercises. A one-page overview gives dates, the hazard, the areas affected and the agencies involved. The analysis is organized by capability rather than by chronology. For each capability, the report states what was expected, what happened, the strengths observed and the areas for improvement, each with a root cause. Four areas for improvement dominate: the middle school shelter opened four hours late, Spanish and Vietnamese warnings went out three hours after English ones, the hospital received no situation report for fourteen hours, and door-to-door notification missed two manufactured housing parks. The improvement plan table closes the report, one row per corrective action.
How a PU545 Unit 9 example is structured
Capabilities organize the analysis because a timeline invites storytelling while a capability frame invites judgment. Each section follows the same order: expectation, observation, strength, area for improvement, root cause. The expectation line matters most, since a finding means little until the reader knows what the plan said should happen; the report quotes the sheltering annex's trigger and its keyholder list. Root causes are written as system conditions, not personal failures. The late shelter traces to a keyholder list that had not been updated since its holder retired, not to the person who failed to answer. Strengths are recorded with the same care, because practices that worked, such as the forecast-based standby, need protecting in the next plan revision. The improvement plan table converts each root cause into an action, a responsible position, start and completion dates, and the method that will verify completion.
Forecast triggers that worked
The standby threshold gave shelter teams about 30 hours of warning. The report records this as a strength so the next revision of the annex keeps it intact.
A shelter four hours behind schedule
The listed keyholder had retired months earlier. The root cause is a roster with no update cycle, and the corrective action assigns a quarterly check to the shelter branch director.
Three hours between languages
Translated warnings waited for a volunteer interpreter. The report traces the delay to the absence of pre-approved message templates and a standing translation contract.
Fourteen hours without a situation report
The hospital was never assigned a liaison in the operations center. The corrective action adds a health care liaison position to the base plan's staffing chart.
Improvement plan, row by row
Each row names the capability, the corrective action, the responsible position, a start date, a completion date and how completion will be verified, such as a test call or a drill.
Where marks go in PU545 Unit 9
After action report criteria in PU545 usually cover an accurate event overview, analysis organized by capability, strengths as well as areas for improvement, root causes, and an improvement plan with owners, dates and verification. Analysis marks are earned by comparing observation against the plan's stated expectation in every section. Root cause credit comes from system conditions such as stale rosters and missing contracts, rather than blame. Improvement plan credit requires actions specific enough to verify. Deductions typical of this assignment include a chronological narrative with findings buried inside it, individuals named as the cause of failures, recommendations like improve communication that no one could complete or check, strengths omitted entirely, and corrective actions assigned to departments without a responsible position or a date.
Get a PU545 Unit 9 example written to your instructions
Your PU545 Unit 9 report may follow a real event, a composite scenario or the exercise designed in the previous unit. Share the prompt, the rubric, and any exercise notes or incident summary you have. The first custom sample comes free, within 24-48 hours, with each root cause traced to a system condition and an owned action.
PU545 Unit 9 questions, answered
What is the difference between a hotwash and an after action report?
A hotwash is the immediate discussion at the end of an exercise or response, where participants record what they noticed while it is fresh. The after action report comes later, drawing on the hotwash, evaluator notes and records to analyze performance against the plan and set out corrective actions. The hotwash is raw material; the report is the analysis.
Should the report name the people involved?
Refer to positions, not individuals. An after action report aims to fix conditions, and naming people tends to make participants defensive in later reviews, which reduces honest reporting. Where a person's action matters to the finding, the report describes the position and the circumstances, and traces the problem to the training, roster or procedure behind it.
Does the report need to include strengths?
Yes. Recording what worked protects it, since practices that are never documented tend to be lost when plans are revised or staff change. Strengths also give the report balance and credibility. Many evaluation formats ask for them explicitly, and a report listing only failures can lose marks on the analysis criterion.