D548 is Emergency Management and Planning in Healthcare, listed at WGU as HCA 3120 with four competency units. It covers assessing, planning for and responding to emergencies inside healthcare organizations, which sounds dramatic and is mostly administrative. Hospitals do not improvise during a disaster, they execute a document written months earlier by somebody who thought carefully about what would break. The scored skill in this course is producing that document: hazard identified, likelihood and impact estimated, roles assigned, communications specified, and recovery planned for the week after the cameras leave.
Four phases, and why students skip two of them
Emergency management is conventionally split into mitigation, preparedness, response and recovery. Student submissions are usually strong on response, adequate on preparedness, and nearly silent on the other two, which is a problem because rubrics in this subject tend to spread aspects across all four.
Mitigation is the work that reduces the hazard before anything happens: moving a server room out of a basement that floods, contracting a second oxygen supplier, hardening a generator connection. It is unglamorous and it is where administrators actually have authority, which is exactly why it is scored. Recovery is the phase that starts once the immediate danger has passed and runs for weeks: restoring deferred services, reconciling documentation created on paper, processing staff who have been working double shifts, and paying for all of it. A plan that ends when the incident ends has left a third of the subject unwritten.
The other structural idea the course expects is an incident command structure, meaning a defined chain of authority that activates when the normal one is too slow. What matters in your writing is not naming a framework but showing that somebody specific holds each responsibility and that the plan says how authority transfers when that person is unreachable.
Reading the aspects, then sizing the plan
Scored aspects for your version of this course live inside the Course of Study. Read them before choosing a hazard, because the hazard you pick has to be able to answer every aspect. A cyber incident supports beautiful communication and continuity sections and awkward evacuation ones. A severe weather event does the opposite. Choosing to fit the aspect list is not gaming the rubric, it is scoping a project.
The word budget, worked. Suppose the directions ask for a plan of roughly 3,000 words and the rubric lists twelve scored aspects. Take 200 for a scope and assumptions section, which an emergency plan needs anyway, and 100 for a document control note, leaving 2,700 across twelve aspects, or about 225 each. Then reweight by phase, because the phases are not equal work. Hazard assessment and response typically justify 350 each, since one carries a ranked analysis and the other carries a sequence of actions. Mitigation, communications, continuity and recovery sit near 250. The remaining descriptive aspects run at about 150. Add the numbers up before drafting, because plans overrun their length faster than essays do, and a plan that runs long usually does so in the response section that was already the strongest.
Write section headings that match the aspect language, then write the plan under them in operational voice: short paragraphs, numbered steps, named roles. Nobody has ever been helped in an emergency by a flowing paragraph.
What an emergency operations plan has to contain
If your task supplies a template, that template is the specification. Where it does not, this arrangement covers the material rubrics in this subject usually ask for, and it reads the way real plans read.
| Component | The content that scores | The test to apply |
|---|---|---|
| Scope and assumptions | Facility type, bed or visit volume, services, staffing pattern, what the plan does not cover | Could a reader picture the building |
| Hazard assessment | Hazards ranked by probability and by impact on people, property and operations | Is there a ranking, not just a list |
| Mitigation measures | Actions taken before an event, each with a cost and an owner | Does anything here cost money or change a building |
| Activation and command | Who declares an emergency, who leads, and how authority passes down | Name a role, never a person |
| Response procedures | Ordered actions for the first hour, the first shift and the first day | Could an unfamiliar charge nurse follow it |
| Communications | Internal alerting, staff recall, patient and family messaging, media, external agencies | Is there a backup for every channel |
| Continuity of operations | Which services continue, which pause, and how records are kept if systems are down | Is downtime documentation addressed |
| Recovery and after action | Return to normal service, staff support, cost capture, review timeline | Is there a date attached |
The test column matters more than the content column. Emergency writing fails on usability rather than on knowledge, and a plan that survives those eight questions will survive an evaluator.
Evidence craft in emergency planning
This subject has better sources than most, because emergency management is heavily documented by public agencies, and it has one specific trap: writing a plan for a generic hospital in a place with no weather.
- Ground the hazard assessment in the actual geography of your chosen facility. Coastal, seismic, wildfire, tornado and flood exposure differ by region, and a ranked hazard list with no location behind it cannot be defended.
- Use agency and professional sources for standards and definitions, and cite them at the claim. Federal emergency management guidance, public health preparedness materials and accreditation standards all publish openly.
- Attach numbers to capacity claims. Surge capacity of an additional forty patients means something. Increased capacity does not.
- Include the resource you will run out of. Every honest plan names a limit: staff, isolation rooms, ventilators, blood products, water, fuel for the generator. Naming it is what makes the mitigation section real.
- Reference real interoperability. Healthcare organizations do not respond alone, so name the outside partners by function: emergency medical services, public health department, other facilities in a transfer agreement.
- Keep any real incident description general and public. Write about published events, not about an unpublished incident at your employer.
The most persuasive thing a student can put in this paper is a failure mode. State what happens if the primary alerting system is down when the event begins, then say what the plan does instead. Evaluators read a lot of plans in which nothing ever goes wrong.
What separates Competent from a submission sent back
Returns here are usually mechanical rather than intellectual. The plan names a hazard but never ranks it. Roles are described but never assigned. Communications are listed as a channel with no backup. Recovery gets two sentences. And most commonly, the whole document is written in narrative prose when the aspect asked for a procedure.
A first pass submission tends to look like this. Every aspect has a heading and the headings use the rubric's words. The hazard assessment shows its scoring method so the ranking can be checked. Every action has a role attached in the same line. Timeframes appear as clock time or elapsed time rather than as promptly. And the document has a version note, which is a small professional signal that costs twenty words and reads as competence.
Work submitted for a performance assessment can be revised and resubmitted at WGU with no grade penalty, so a return is time rather than damage. Inside a flat rate six month term, though, time is the whole currency, and emergency plan tasks are long enough that one round trip can cost a fortnight.
If this course carries a proctored objective assessment in your plan, we prepare only. We build the study schedule, drill the terminology and command structure vocabulary, and give you an honest read on readiness. We never sit or assist during an assessment, and we never ask for portal credentials.
Six mistakes that cost time in D548
- The hazard list with no ranking. Assessment means comparing probability and impact, then ordering. A list is the input to that work, not the output.
- Planning for a facility with no address. Location drives hazards, mutual aid partners and evacuation options. Fix the setting in the first paragraph.
- People instead of roles. Plans outlive staff. Write incident commander and house supervisor, never a name.
- One communication channel. If the phone system is the plan, the plan fails in the incident that takes out the phone system.
- Skipping downtime documentation. When systems are unavailable, care still has to be recorded and later reconciled. This is the continuity detail most students miss.
- No after action review. The learning loop is part of emergency management and it is easy points, but only if you give it a date and an owner.
How we work this course with you
Send the task directions and your rubric and we start with hazard selection, because picking one that can answer every aspect saves more time than any other decision in this course. From there you get a plan skeleton in operational format, a hazard scoring table you can fill for your chosen facility, word budgets by section, and a review that reads your draft the way an incident commander would: looking for the step that has no owner.
Questions D548 students ask
Should I write about a real facility or invent one?
How technical should the clinical side of the plan be?
Do I need to use a specific emergency management framework?
Building the D548 emergency plan?
Send the HCA 3120 directions. You get hazard selection help, a plan skeleton and a scoring table back.
Where D548 sits in WGU's programs
The July 2026 catalog places this code in 1 current WGU program. Open a program page for the complete standard path and term positions. The live Degree Plan remains authoritative after transfer credit, substitutions, and mentor planning.
The assessments, one by one
The public catalog does not publish this course's PA/OA identity or task count. WGU Tutors publishes at most one PA manual per course and only from a WGU-controlled public rubric. Until that source exists, PA help begins from the student's real Course of Study and OA support remains preparation only.