The closing stage of NR-670 is assembly and handoff. The written work is a final synthesis that carries the whole project in one document, usually paired with a dissemination artifact such as a presentation or an executive summary aimed at the people who will decide whether the change continues. Two audiences, one body of evidence, and no new claims that the earlier stages cannot support. Your section may print this as NR 670 or NR670; 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 the closing deliverable must leave behind
The last document produced by a good capstone is often the shortest one. A nurse leader closing a transitions-of-care practicum reduced 4,000 words of accumulated work into a single page for a governance committee: the gap in counts, the standard adopted, what the small test showed, what it cost in staff minutes, and the one decision she needed from the room. The long paper earned her grade. The page is what kept the work alive after she left, and both were graded.
The final synthesis has to be readable as a whole by someone who has not seen your earlier submissions. That means the problem, the evidence, the design, the implementation status, the results such as they are, the limitations and the recommendations, assembled in an order that carries a reader forward and edited so the seams between stages disappear. Copying six previous papers into one file and adding a conclusion is the most common way this stage goes wrong, because the redundancy is visible on the first page and the argument never accumulates.
The dissemination artifact is a different genre with different rules. Executives read for decision, not for method: the gap, the recommendation, the resource, the risk of doing nothing, the ask. Frontline staff read for what changes on their shift. Governance bodies read for accountability, ownership and measurement. If your section asks for a presentation, build it to the audience it names rather than compressing the paper into slides, which is a translation task rather than a formatting one.
The practicum boundary closes the course as it opened it. Your 144 hours, your activity log, your site documentation and your mentor's evaluation are your own verified record, never drafted, reconstructed or estimated with help, and nothing in a final paper should describe clinical work in a way that differs from what those records show. Report status honestly: designed, approved, tested at small scale, or fully implemented, whichever is true. Everything that reaches the page stays de-identified, aggregate and free of any detail that would let a reader place a patient or a colleague.
The NR-670 Week 8 method, step by step
Six moves that assemble a session of work into one document and one artifact.
-
Write the one-sentence result first
What the practicum produced and what it means, in a single sentence with a number in it. Everything you assemble afterward either serves that sentence or comes out, which is the fastest editing rule available at this stage.
-
Rebuild rather than paste
Open your earlier papers beside a blank document and write the synthesis fresh, pulling in the specific data, citations and definitions you need. Pasting preserves every transition written for a different context and produces the seams graders notice immediately.
-
Report status in exact language
Designed, approved, piloted over a stated number of cases, adopted into policy, or proposed for a named forum. Use the same verb consistently for the same component throughout the paper and the artifact.
-
Give the results their display and read it honestly
Show the counts over time or the before and after with denominators, then say what the display supports. A flat process measure and a flat outcome mean something different from a moving process measure and a flat outcome, and naming which you have is the analysis.
-
Write limitations as a reader would find them
Sample size, short window, single site, collector bias, concurrent changes. Anticipating the objection is stronger than surviving it, and a limitations section that names the three real threats scores better than one listing generic caveats.
-
Build the handoff, not just a conclusion
Named owner, where the standard lives, the audit that continues, the forum that reviews it, and the next decision required with its timing. This is the difference between finishing a course and finishing a piece of leadership work.
A layout and word budget for the final synthesis
Our frame for a capstone synthesis paper, sized for roughly 2,000 to 2,600 words plus tables and any dissemination artifact. It is our own outline rather than anything the university issues, and your section's rubric outranks it wherever the two disagree. Scale proportionally if your assigned length differs.
| Section | What belongs in it | Word target |
|---|---|---|
| Executive opening | The gap, the change, the status and the result in a paragraph a decision-maker could read alone. | 150 to 190 |
| Problem and setting | The measured gap with its base and window, and only as much microsystem detail as the argument needs. | 320 to 400 |
| Evidence base | The synthesis compressed to the claims that justified this design, with citations retained and summaries cut. | 380 to 460 |
| Design and implementation | What was built, what was approved, what was tested and at what scale, with the framework named once. | 420 to 520 |
| Results and limitations | Measures with denominators, the display, an honest reading, and the three threats that most affect interpretation. | 420 to 520 |
| Recommendations and handoff | What should happen next, who owns it, what continues to be audited, and the decision being requested. | 310 to 390 |
Evidence craft for a capstone synthesis
Every number in the paper reconciles with every other one. Read the whole document once looking only at figures. A baseline of 19 of 30 in one section and 19 of 32 in another is the kind of inconsistency that makes a grader question the parts they cannot check.
Keep causal language matched to the design all the way to the last page. Conclusions are where controlled verbs sneak in. If the design was a single-unit before and after, the recommendation section still says associated with and followed, not reduced, no matter how much you believe the change worked.
Retain citations when you compress the synthesis. Shortening a literature section frequently strips the support from claims that still appear. Cut the description of studies, keep the attribution, and re-check that the reference list still matches the text exactly after the edit.
Translate rather than shrink for the dissemination artifact. An executive summary is not the paper in smaller font. Lead with the decision requested, support it with three figures, and put method in a single line, because the audience's question is what should we do rather than how did you find out.
Proof the mechanical layer last and deliberately. Title page, headings, running elements, reference formatting, table numbering and captions. In a capstone these rows are worth real points, they are entirely within your control, and they are the ones most often lost to fatigue in the final hours of an eight-week session.
Five mistakes that cost points in this week's territory
- Assembly by copy and paste. Repeated paragraphs and mismatched transitions announce that the document was collected rather than written.
- Status inflation. Describing a proposed change as implemented contradicts your own earlier stages and is the most serious error available here.
- Results without denominators. A final paper that reports percentages alone leaves the reader unable to weigh the one thing the whole project was for.
- Generic limitations. Further study is needed is not a limitation; a two-week window with 34 observations collected by the project's designer is.
- A conclusion with no owner. Recommendations addressed to nobody in particular end the practicum and end the change with it.
Before you submit
- The opening paragraph works alone as a summary for a decision-maker
- Every figure in the paper reconciles with every other appearance of it
- Implementation status is stated in exact, consistent verbs
- Results appear with denominators and a named display
- Limitations are specific to this project's design and window
- The handoff names an owner, a location, a continuing audit and a next decision
- Reference list, headings, tables and captions have all been proofed after the final edit
Assembling the NR-670 final synthesis?
Send the rubric and your earlier submissions out of Canvas. A premium original draft comes back in 24 to 48 hours rebuilt as one argument rather than pasted, with status stated exactly and the handoff written in, and revisions run until the grade lands.