D916 is the MHA Capstone, carried at WGU as MHA 4957 and worth four competency units. It is the culminating integrative course of the Master of Healthcare Administration, which means it asks you to pull research, management, law and ethics, quality, risk, economics, technology and resource management into one project that stands up. Students who struggle usually do so for one of two reasons: they chose a problem that no single document can resolve, or they wrote eight competent chapters that never agreed with each other about what the problem was.
Integration means one thread, not eight topics
Integration is frequently misread as coverage. A student takes each course from the program and writes a section on it, producing a document with a quality paragraph, a finance paragraph, a legal paragraph and so on. Every part is accurate. Nothing is integrated, because the sections are parallel rather than connected.
Real integration looks different. The problem is chosen, and then each discipline is used only where it changes the answer. Finance sizes the loss. Quality supplies the measure and the improvement method. Law defines what the organization is required to do regardless of cost. Risk explains what could go wrong with the fix. Technology says whether the fix is feasible with the systems in place. Resource management prices the staffing. Ethics addresses who bears the cost of the change. Nine tools, one problem, and every tool earns its paragraph by moving the recommendation.
A quick test before drafting: for each discipline you plan to include, write one sentence saying what it changes about the recommendation. If you cannot write that sentence, the section is coverage and it should be cut or reduced to a line.
Pacing a graduate capstone against the aspect list
The capstone rubric in your Course of Study is longer and more interdependent than the ones you have worked from. Read the whole list before choosing a project, because certain aspects, particularly those asking for financial justification or measurable outcomes, will quietly rule out projects that cannot supply numbers.
The word budget, worked. Take a capstone of roughly 5,000 words against sixteen scored aspects. Reserve 300 for an executive summary written at the end and 150 for a conclusion, leaving 4,550 for scored content, or about 284 per aspect at a flat split. Then weight by dependency. The problem statement, its evidence and the baseline get 450 each, because every later aspect inherits their quality. Analysis and recommendation aspects sit at 350. Implementation, financial justification and evaluation sit at 320. Contextual and descriptive aspects drop to 180. Track the running total weekly rather than at the end, since a graduate capstone that arrives 1,500 words over is not trimmed easily; the length is usually load bearing by then.
Sequence matters as much as size. Settle the problem and its measure in week one, build the evidence in week two, then draft outward. Students who write background first almost always have to rewrite it once the problem sharpens.
The evidence chain, and where it usually snaps
Where your directions specify a structure, follow it precisely. This table is not a substitute for that structure. It is a self check you run on the finished draft, reading only the middle column, to confirm the document argues one case.
| Stage | What your draft says | The snap to look for |
|---|---|---|
| Problem | One measurable gap in one organization | Two problems described as one |
| Evidence of the gap | Internal or published figures with periods stated | A gap asserted from experience alone |
| Contributing causes | Ranked, with the method that ranked them | Causes drawn from assumption rather than analysis |
| Literature | What has worked elsewhere, appraised for transferability | A review that never returns to your organization |
| Recommendation | The intervention, aimed at the top cause | An intervention chosen before the causes were ranked |
| Financial case | Cost, benefit and payback with assumptions listed | Benefits that assume perfect adoption |
| Implementation | Phases, owners, dependencies and dates | A timeline with no dependency between steps |
| Evaluation | The same measure as the baseline, with a target and review date | A new measure appearing at the end |
Two snaps account for most capstone rework. The intervention that does not target the ranked cause, and the evaluation measure that differs from the baseline. Both are visible in ten minutes if you read the document backwards, and both are expensive if an evaluator finds them first.
Evidence craft across a long integrative document
A capstone is the one submission where a reader can compare your claims against each other, so internal consistency becomes an evidence question.
- Keep a figure register while you draft: every number, its source and the section it appears in. Capstones fail consistency checks because a figure changes between the summary and the body.
- Appraise transferability whenever you borrow a result. A study from a large academic system may not apply to a community hospital, and saying so is an appraisal aspect answered.
- Label estimates as estimates in the sentence, every time, not once in a footnote.
- Cite the specific measure specification you used, since the same named measure often has several definitions.
- Keep confidential and identifiable material out entirely, and describe your organization at a level of detail you would be comfortable presenting publicly.
- Follow APA throughout including exhibits, and cite at the claim rather than at paragraph end.
One paragraph does disproportionate work in a graduate capstone: an honest limitations section. Naming what your analysis cannot establish, and why the recommendation still stands within those limits, is the marker of a professional document and it usually corresponds to an aspect.
What separates Competent from a submission sent back
Capstone returns are rarely about writing quality. They are about a chain with a broken link: a recommendation that does not follow, a financial case built on an unstated assumption, an evaluation plan measuring something new, or a problem stated broadly enough that no recommendation could resolve it.
Work that passes on the first read is disciplined rather than impressive. One organization named on page one and never replaced. A problem sentence containing a measure, repeated almost word for word in the recommendation and the evaluation. Causes ranked with a method. A financial case with its assumptions listed in one place. An implementation plan with dependencies. And an executive summary written last whose every figure matches the body.
Performance assessment work at WGU can be revised and resubmitted with no grade penalty, which matters here because capstone feedback tends to name specific aspects rather than the whole document. Rebuild what was named. In a six month flat rate term the practical advice is to open the capstone with at least eight weeks remaining, since a graduate document of this length usually takes one revision cycle even when it is done well.
Where your program pairs the 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 D916
- Coverage instead of integration. A section per course produces parallel essays. Use a discipline only where it changes the recommendation.
- A problem too large to resolve. If no single organization could fix it inside a year, it is a subject rather than a capstone problem.
- Benefits assuming full adoption. Discount the projected benefit for realistic uptake and say what rate you assumed.
- Literature that never comes home. Every source cited should be followed by a sentence about your setting.
- Numbers that drift. Keep a figure register. Mismatches between summary and body are the fastest credibility loss available.
- Executive summary written first. Write it last, from the finished document, and verify every claim in it.
How we work this course with you
Send your capstone directions and rubric and we start with the problem, because a graduate capstone is decided there. You get two or three candidate problems that are measurable, resolvable at an organizational level and supportable with data you can actually obtain. Then a section plan with word budgets against the aspect list, a figure register template, and a backwards read of your draft that checks the chain from evaluation to problem before it goes anywhere near an evaluator. Most capstone students come to us halfway through with a document that is already long and already drifting, and the fastest repair is almost never more writing. It is deciding what the problem sentence actually says and then making eight sections agree with it.
Questions D916 students ask
How is the MHA capstone different from a long assignment?
Can I reuse work from earlier MHA courses?
What if my organization will not share the data I need?
Starting the D916 capstone?
Send the MHA 4957 directions. You get measurable problem candidates and a chain audit back.
Where D916 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.