D226 BSNU Capstone carries catalog number NURS 3660 and is worth three competency units. It is the RN-to-BSN synthesis capstone, where you demonstrate the program's outcomes by facilitating an evidence-based change in a healthcare setting. One catalog quirk worth knowing: the printed banner number NURS 3660 is shared with D224 Global and Population Health, so searching the catalog number alone returns two very different courses. The capstone is the one under code D226.
What the BSNU capstone is really measuring
A capstone is not a longer paper. It is a demonstration that the separate competencies you collected over a program can be operated together on one real problem. Scholarship, leadership, informatics, population health, organisational systems and professional role are all supposed to appear, not as a list of courses revisited, but as the tools you reached for while doing something.
The verb in the catalog description is facilitating, and that word is doing a lot of work. You are not asked to invent a solution and hand it over. You are asked to identify a real practice problem in a setting, build the case for a change from evidence, bring the people who would be affected into it, and set up a way to tell whether it worked. Facilitation includes the parts nobody enjoys: finding out who objects, understanding why they are right to object, and adjusting.
The single largest predictor of a capstone that finishes is scope. Nurses choose problems they care about, and problems worth caring about tend to be enormous. Staffing, burnout, discharge coordination across a whole system: all real, all unusable in a three unit capstone. A problem that fits is narrow, local, measurable and inside the influence of one nurse. One handover, one form, one step in one pathway, on one unit.
The second predictor is measurement chosen early. A capstone that decides at the end how it will demonstrate impact has no baseline to compare against, and no amount of writing recovers that. The measure and its baseline belong in the first week of work rather than the last.
Turning a rubric into a plan you can work to
Capstone rubrics are the longest you will meet at WGU, and the scoring detail sits in your Course of Study rather than in the catalog. Open it and count. Each aspect is scored independently against a three point scale and each needs a 2, so a capstone with excellent evidence work and a thin sustainability section is a capstone that comes back.
Because the document is long, the aspect-to-heading discipline matters more here than anywhere else. An evaluator working through a long aspect list across many pages should never have to search. Use the rubric's own nouns as headings, in the rubric's own order, even where a different order would read better. Readability is not being scored. Locatability effectively is.
The word budget, worked. Take a rubric with twelve scored aspects and directions indicating a project report of roughly 4,000 words. Reserve 250 for an executive summary that states the problem, the change and the result, and 200 for a conclusion. That leaves 3,550 across twelve aspects, just under 300 each. Then weight by risk rather than by interest: the problem statement and the literature synthesis will try to take 600 apiece because they are the parts that feel like real academic work, while implementation, measurement, stakeholder engagement and sustainability get 150 each and fail. Cap the front sections at 300 and push the recovered words into the back half. Capstones are returned from the back half.
Then plan the calendar backwards from the term. Terms run six months at a flat rate, and a capstone consumes calendar time in ways a normal course does not, because it waits on other people. Work back from your term end date: submission, revision buffer, writing, measurement window, engagement, approval, scoping. If that chain does not fit, the scope is too large and the fix is to shrink it now rather than to work faster later.
A structure that fits a capstone project report
Where the task directions provide a structure, use it exactly, including their section names. Where anything is left open, this order carries a change project through its natural sequence.
| Section | Required content | The common point of loss |
|---|---|---|
| Problem statement | One practice problem, in one setting, with the figure that shows it exists | Broad problems produce unmeasurable projects; this is the decision that fixes everything downstream |
| Setting and stakeholders | The unit, the people affected, and what each group gains or loses from the change | Scored for interests, not for a list of roles |
| Evidence synthesis | What the literature supports, appraised rather than summarised, with quality noted | An annotated bibliography in prose form is the classic weak version |
| Proposed change | The specific intervention, its scale, and why this one rather than the alternatives | Alternatives considered and rejected is what makes it a decision |
| Implementation plan | Steps, sequence, who does what, and what had to be approved | Frequently vague; specificity here is cheap to write and heavily scored |
| Measurement | Baseline, target, indicator definition, collection method and timing | Without a baseline collected before the change, no result can be claimed |
| Results or expected results | What happened, or what is projected, with the honest limits of either | Overstated results are worse than modest ones; evaluators read for candour |
| Sustainability | What keeps the change alive after the project ends and after you leave | Regularly omitted, regularly scored |
| Reflection on outcomes | Which program competencies you used and where, with evidence from the project | Naming competencies without pointing at where they were used earns little |
| References and appendices | Literature, tools, forms and data displays, APA formatted | Scored wherever citation and formatting are named |
The reflection section is worth writing last and planning first. Keeping a short log of decisions during the project turns that section from an act of memory into an act of retrieval, and it reads completely differently to an evaluator.
Evidence craft in a project that touches a real workplace
A capstone gathers evidence from literature and from an organisation at the same time, and the organisational half carries obligations the literature half does not.
- Get permission through the proper channel before collecting anything, and record that you did. Approval requirements differ between organisations and a capstone that skipped them is a capstone with a problem no rewrite fixes.
- Appraise the literature rather than listing it. Study design, sample, setting and limitation, then what it supports here. Synthesis means saying what the body of evidence collectively supports.
- Keep organisational data aggregated and non-identifying. Counts and rates over a period, never individual records, never anything traceable to one patient or one staff member.
- Define every indicator fully. Numerator, denominator, source, frequency, and who collects it. A capstone measure that a reader cannot reproduce cannot be credited.
- Record the baseline with a date and a method, before the change starts. Reconstructed baselines are visible and they undermine every result built on them.
- Report what did not work. Projects that ran into resistance, delay or a failed step and say so score better than tidy narratives, because the evaluator is assessing facilitation rather than luck.
The most valuable sentence in many capstones is the one distinguishing what the project showed from what it merely suggests. Small local projects rarely prove anything. They demonstrate a competent process, and claiming the smaller thing accurately is stronger than claiming the larger thing loosely.
What separates Competent from a submission sent back
WGU records work as Competent or Not Competent, with no letter grade and no ordinary GPA, and each aspect is scored on its own. Capstones come back for structural reasons far more often than for intellectual ones: a missing baseline, an unaddressed sustainability aspect, or a reflection that names competencies without evidence.
- The problem is narrow enough to measure and the same measure appears in the results.
- Every scored aspect has its own heading in the rubric's language and in the rubric's order.
- Stakeholder work shows engagement that happened, including objections raised.
- The baseline predates the change and its collection method is stated.
- Sustainability and reflection are full sections rather than closing paragraphs.
Capstone work can be revised and resubmitted without a grade penalty like any performance assessment, but the calendar is unforgiving in a way that ordinary courses are not: revisions late in a term collide with the term boundary. Building a buffer before the end of the term is the single most practical thing you can do, and it costs nothing but planning.
Six mistakes that cost time in D226
- Choosing a problem the size of the organisation. Ambition is the leading cause of unfinished capstones. Narrow it until it fits one unit and one measure.
- Starting measurement after the change. Without a pre-change baseline there is nothing to compare, and no writing recovers a baseline that was never collected.
- Summarising literature instead of synthesising it. Study by study description is a list. Synthesis states what the evidence collectively supports and where it disagrees.
- Skipping approvals. Every organisation has a process for projects that touch practice or data, and going around it puts the whole capstone at risk.
- Writing sustainability as a hope. Naming who owns the change afterwards, what documentation embeds it, and what would signal decay, is what the aspect asks for.
- Leaving reflection to the final night. Reflection written from a decision log is specific and evidenced. Reflection written from memory at the end reads like a list of course titles.
How support works on this course
Send the rubric from your Course of Study with the task directions and, if you have one, your problem idea. The first useful work is usually scoping: cutting a large problem down to something a three unit capstone can finish. After that you get the aspect map in rubric order, a word budget weighted toward the back half where capstones fail, a literature synthesis rather than a summary, fully defined measures with a baseline plan, and a reflection built from your own decision log.
The boundaries are firm and they matter more here than in any other course. We do not contact your workplace, your preceptor or any site, we do not complete clinical or practice hours, we do not sign placement paperwork and we do not fill in hour logs. We do not collect data from an organisation on your behalf. Proctored objective assessments are yours alone: preparation is all we contribute, we play no part during one, and we neither ask for nor handle a portal login.
Questions students ask about D226
Why does the catalog number match D224?
How small is too small for a capstone problem?
What if my organisation will not approve my project?
Capstone scope still too big to finish this term?
Send the rubric and your problem idea. First job is cutting it to something measurable, then the aspect map, the measures and the sustainability plan.
Where D226 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.