D580 is the Healthcare Administration Capstone, listed at WGU as HCA 5110 and carrying four competency units. The catalog calls it a culminating assessment integrating managerial skill with healthcare knowledge, which in practice means one substantial project in which you identify a real problem in a healthcare organization, analyze it with the tools from the rest of the major, and defend a recommendation you could actually carry out. Nothing new is being taught. What is being tested is whether the pieces you learned separately hold together when they have to point at one decision.
The scoping decision that determines everything
Capstones fail at the topic, not at the writing. The pattern is predictable: a student picks something important, such as reducing readmissions across a health system, and discovers three weeks in that the data does not exist, the causes are contested, and the recommendation would need authority nobody in the paper has.
Apply four tests before committing. Can you measure the problem with information that is either published or reasonably estimated. Can one person in a named role authorize the fix. Can the effect be seen inside one budget year. And can you describe the problem in a single sentence that includes a number. A topic that clears all four is small enough to finish and large enough to score.
Small is the right instinct here. Cutting the average wait for release of information requests in an outpatient clinic from twelve days to five is a capstone. Fixing population health is a slogan. Evaluators are not scoring ambition, they are scoring whether the analysis supports the conclusion, and a narrow problem gives you room to do that properly inside the length you have.
Working the scored aspects across a long deliverable
The rubric for your capstone lives in the Course of Study and is longer than the ones you have been working from. Read it twice. Aspects in a capstone often depend on each other, so the order you draft in matters as much as the coverage.
The word budget, worked. Take a capstone report of roughly 4,000 words with fourteen scored aspects. Set aside 250 for an executive summary written last, and 150 for a conclusion, leaving 3,600 across fourteen aspects, or about 257 words each. Then group. Problem definition and the evidence behind it deserve 400 apiece, because everything downstream inherits their weakness. The analysis aspects, usually three or four, sit at 300. The recommendation, implementation and evaluation aspects sit at 300 as well, because that is where the integration is visible. That leaves the descriptive and contextual aspects near 150, which is enough for a graduate reader who does not need the sector explained to them. Write those numbers next to your headings and check the running total at every drafting session, because capstones do not overrun gradually, they overrun in one section that turned into a literature review.
Draft in this order: problem and measurement, then analysis, then recommendation, then implementation and evaluation, then background, then executive summary. Background written first always turns into a term paper.
Keeping the through line intact
The characteristic capstone defect is not error, it is drift: a paper whose problem statement, analysis and recommendation are each fine but are not obviously about the same thing. This table is a self audit. Fill the middle column with your own content, then read the column top to bottom and check that it tells one story.
| Link in the chain | What you write there | The break to look for |
|---|---|---|
| Problem | One sentence with a measure, a setting and a gap | A problem stated as a topic rather than as a gap |
| Baseline | The current number and where it came from | No baseline, which makes improvement unprovable |
| Causes | Two or three supported explanations, ranked | Causes listed but never ranked, so the fix targets nothing |
| Options | At least two real alternatives, costed | One option presented as if no choice existed |
| Recommendation | The chosen option and the reasoning that picked it | A choice that does not address the ranked cause |
| Implementation | Steps, owners, sequence, resources, timeline | Steps with no owner or no cost |
| Evaluation | The measure, the target and the review date | A measure different from the baseline you opened with |
| Risk | What could go wrong and the response | Risk section that lists risks nobody will act on |
The most common break is the last row of the middle column not matching the second row. If your evaluation measures something other than the baseline you established, an evaluator reading backwards will find it immediately, and the recommendation aspect goes with it.
Evidence craft in an integrative project
A capstone draws on more source types than any earlier course, and mixing them without labeling is where credibility leaks away.
- Give each number a provenance in the same sentence: published data, organizational report, industry benchmark or your own estimate. Estimates are allowed. Unlabeled estimates are not.
- Cost your recommendation in ranges rather than false precision. An annual cost between forty and sixty thousand dollars with the assumptions listed is more credible than a single figure with none.
- Use benchmarks to establish that a gap exists. A wait time only becomes a problem when compared with something.
- Bring earlier coursework in explicitly where it applies: policy constraints, quality method, financial analysis, leadership approach. Integration is a scored idea and it has to be visible, not implied.
- Keep confidential material out. Describe your organization at the level of published operational fact, and use aggregate figures with no patient or employee identifiable in them.
- Follow APA throughout, including for organizational documents, and put citations at the claim rather than at the end of the paragraph.
One paragraph reliably strengthens the whole project: a short statement of what your analysis cannot show. Naming the limitation, then explaining why the recommendation still holds within it, is the difference between a student paper and a professional one.
What separates Competent from a submission sent back
Capstone returns tend to be about coherence rather than content. The recommendation does not follow from the ranked causes. The implementation plan requires authority the paper never established. The evaluation measure is new. Or the executive summary, written first and never revised, promises a paper that no longer exists.
Work that passes on the first read reads as one document. The problem sentence appears almost verbatim in the recommendation. Every cause that gets ranked gets addressed or is explicitly set aside. Every step has a name attached to it, in role form. And the numbers in the summary match the numbers in the body, which sounds obvious and fails more often than any other single check.
Performance assessment work at WGU can be revised and resubmitted with no grade penalty, which matters more in a capstone than anywhere else, because these are long documents and evaluator feedback tends to name a specific aspect rather than the whole. Rebuild what was named. Leave what scored alone. In a six month flat rate term, a capstone that goes back once is normal and a capstone that goes back three times has usually been drifting since the problem statement.
If your program pairs this capstone with a proctored objective assessment, our line does not move: preparation only, never sitting or assisting during an assessment, and never any request for portal credentials.
Six mistakes that cost time in D580
- A problem with no number in it. If the opening sentence has no measure, there is no baseline, no target and no way to evaluate anything later.
- Options that are not real. Presenting one serious choice against two obviously bad ones is visible from a distance and costs the analysis aspects.
- Recommendations that need a board. Match the fix to the authority of the role you are writing as, or explain how approval is obtained.
- Background that ate the paper. Sector context is scenery. Keep it under a tenth of the length.
- Implementation without money. Time, staffing and licensing all cost something. A plan with no resource line has not been tested against reality.
- Executive summary written first and never updated. Write it last, from the finished body, and check every figure in it against the source paragraph.
How we work this course with you
Send your capstone directions and rubric and we start where the risk is: scoping. You get two or three problem statements that pass the four tests, each with the measure that would anchor it, so the project you commit to is one you can finish. From there, a section plan with word budgets, a through line audit you can run yourself at every draft, and a final review that reads the document backwards from the evaluation section to catch drift before an evaluator does.
Questions D580 students ask
Can I write the capstone about a problem at my own workplace?
How much of the capstone should be new research?
How long does the capstone realistically take?
Scoping the D580 capstone?
Send the HCA 5110 directions. You get problem statements that pass the four tests and a through line audit back.
Where D580 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.