The results stage of NR-632 is where most capstone credibility is won or lost. The territory is evaluation: comparing the post-implementation period against the baseline you defined, reporting the change in counts before proportions, and then doing the harder work of asking what else could explain it. A results section that reports a favorable number and stops has answered half the question a nurse executive is paid to answer. Your section may print this as NR 632 or NR632; it is the same course. Chamberlain publishes no syllabi outside Canvas. The placement here is our teaching judgment from the course's catalog arc; your section's rubric decides what your week actually asks.
What NR-632 Week 5 asks for
What is the first question a chief nurse asks when a project reports improvement? Not how large the change was. What else was going on. A prenatal outreach project at a community health center reports that documented first-trimester entry to care rose over its implementation period, and the room immediately wants to know whether a new bilingual scheduler started in the same window, whether the neighboring clinic closed its walk-in hours, and whether the count was pulled the same way both times. Every one of those is a rival explanation, and the graded skill at this stage is naming them before someone else does.
The written deliverable is usually an evaluation or results section, sometimes with a table or a simple run chart, and it has a strict order of operations. Restate the indicator exactly as it was operationally defined. Report the baseline and the post-period as counts with their denominators and windows. State the change in absolute terms first. Only then interpret. Students who interpret before they report end up writing conclusions their numbers cannot carry, and the correction usually requires rewriting the whole section rather than a sentence.
Honesty about magnitude is the other demand here, and it is where community projects most often overreach. A move from 41 of 168 to 58 of 174 is a real, describable change and it is also small in absolute terms, sensitive to a handful of clients, and entirely capable of having occurred without your intervention. Writing that sentence yourself, in your own results section, is not weakness. It is the thing that makes the rest of your interpretation believable, and executive faculty read for it specifically.
Finally, this stage is where process and outcome must be reported separately and clearly. Your project almost certainly produced a process change you can document with confidence, and an outcome change you can document with less. Report both, label which is which, and resist the temptation to let a strong process finding carry an outcome claim it cannot support. That single discipline lifts more capstone results sections than any statistical technique.
Where our help stops and your practicum begins
The practicum hours attached to this course, and every record the school or your site verifies, belong to you. We do not complete hours, attend meetings, contact your mentor or your organization, or produce site documentation. Hour logs, activity and encounter records, mentor and preceptor evaluations and any signed or verified form are never drafted, reconstructed or estimated with our help. Nor do we obtain, extract or manipulate your organization's data; getting the numbers, with whatever permission your site requires, is your responsibility.
Where we work is the writing that surrounds the numbers you already hold: how a results section is ordered, how a change is stated so it cannot be misread, how rival explanations are written as analysis rather than as apology, how a table is built so it does not repeat the prose, and how the discussion connects a local finding to published evidence without overclaiming. The value on offer is clearer written reasoning about work you genuinely did.
Small numbers make de-identification harder, not easier, and results sections are the place students slip. A table cell containing one or two clients can identify a person in a program of forty. Suppress or aggregate small cells, keep dates coarse where precision is not analytic, describe staff by role, and add a sentence to your methods saying you did all of this. If the only way to make a finding legible would be to print a cell that identifies someone, the finding is described in prose instead.
The NR-632 Week 5 method, step by step
Six moves for writing a results section that survives an executive reading.
-
Restate the operational definition verbatim before the first number
Copy it from your own measurement section rather than paraphrasing. A definition that drifts by one word between the baseline and the results invalidates the comparison, and paraphrase is how the drift happens.
-
Report both periods as counts over denominators, with dates
Pre-period, post-period, same rule applied to both, windows stated. Proportions may follow; they may not lead. This one ordering fixes more weak results sections than any other single change.
-
State the change in absolute terms, then in relative terms
An increase of seventeen clients, which is a rise from roughly a quarter to a third. Relative change alone flatters small numbers, and reporting it first is the oldest way to make a modest project sound larger than it was.
-
Write the rival explanations you named at baseline, with what happened to them
Take the threats you listed before you had results and report on each: whether it occurred, and what direction it would have pushed the indicator. Doing this from a pre-written list is the strongest credibility move available to you.
-
Separate process findings from outcome findings under their own headings
Referrals placed, sessions delivered and checklist completion are process. Visits attended, readings improved and admissions avoided are outcome. Mixing them in one paragraph is how overclaiming enters a paper unnoticed.
-
Close with what the result licenses and what it does not
One sentence each. This finding supports continuing the pathway on the two pilot sites; it does not support a system-wide claim about clinical outcomes. Naming the ceiling yourself is what makes the floor believable.
A layout and word budget for a capstone results section
Our frame for a results and evaluation section of roughly 1,200 to 1,500 words. It is our own outline rather than anything the university issues, and your scoring guide outranks it wherever they disagree.
| Section | What belongs in it | Word target |
|---|---|---|
| Definition restated | The indicator exactly as operationally defined earlier, with any exclusions carried forward unchanged. | 90 to 120 |
| Delivery of the intervention | What was actually implemented and to what dose: sessions held, staff trained, weeks live. | 170 to 210 |
| Process findings | The measures of whether the change happened, in counts with denominators for both periods. | 200 to 250 |
| Outcome findings | The indicator itself, both periods, absolute change first, with any table doing work the prose does not repeat. | 250 to 300 |
| Rival explanations | Each pre-named threat revisited, with whether it occurred and the direction of its likely effect. | 250 to 310 |
| What the result licenses | The claim you are entitled to make and the claim you are explicitly not making. | 120 to 160 |
Evidence craft for results writing
Do not let a table and the prose say the same thing twice. A table carries the full comparison; the prose points at the two numbers that matter and explains them. Duplication wastes a third of your word count and reads as padding to a grader who has seen it often.
Keep statistical language precise or leave it out. Most capstone projects are not powered for inference, and the honest sentence is that no statistical test was applied because the sample does not support one. That is a stronger position than a misused p value, which is easy to spot in a graduate program.
Compare your finding against published effects. If the literature behind your intervention reports gains of a certain order, say where yours sits relative to them. A local result placed in that context is analysis; the same result reported alone is a fact without a meaning.
Report what dropped as well as what rose. Projects have side effects: a step that got skipped elsewhere, a queue that lengthened, staff time pulled from another task. Naming one honestly costs nothing at this stage and buys the reader's trust for the recommendation to come.
Five mistakes that cost points in this week's territory
- Relative change reported first. A forty percent improvement built on seven clients is technically true and rhetorically dishonest, and executive readers are trained to catch it.
- Interpretation before reporting. Once a conclusion is on the page, every number after it reads as recruited to support it.
- Rival explanations invented after the fact. Threats named at baseline are analysis; the same items appearing only in the discussion read as damage control.
- Process results dressed as outcomes. More referrals sent is not more care received, and a section that blurs them loses the credibility row.
- Silence about the null result. A project that did not move its indicator is a legitimate capstone; concealing it is not, and the concealment is usually visible in the numbers anyway.
Before you submit
- The operational definition is reproduced word for word from your measurement section
- Both periods appear as counts over denominators with their windows
- Absolute change is stated before any relative change
- Every rival explanation named at baseline is revisited by name
- Process and outcome findings sit under separate headings
- No table cell is small enough to identify a client, and the method says so
Writing up your capstone results?
Send the scoring guide, your definitions and your de-identified numbers. A premium original draft comes back in 24 to 48 hours with counts before proportions and every rival explanation named, and revisions run until the grade lands.