The closing stage of NR-670A assembles a session of separate submissions into one document that argues a single result and hands the work to somebody who will still be there next quarter. The writing task is compression and honesty rather than addition: rebuild the earlier stages into a continuous argument, report what actually happened in exact language, and name an owner for what comes next. Your section may print this as NR 670A or NR670A; 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 final paper has to prove and hand over
A nurse leader closing a community program practicum discovered her problem in her own arithmetic rather than in her project. Her week-three baseline had counted episodes, and her week-six measurement had counted encounters, and the two numbers had never been compared because they had lived in separate documents. Reconciling them took an evening and cost her one claim she had expected to make. It also produced the most credible paragraph in her paper, because she wrote the reconciliation down: what each figure counted, why they differed, and which one the conclusion rests on. Assembly is where a capstone either becomes coherent or reveals that it never was.
A final synthesis is not the earlier stages stapled together, and graders identify pasted work immediately because the seams show in the tense, the register and the repetition. Each earlier stage was written for its own scoring rows and carries scaffolding the final paper does not need. What the closing document needs is one argument moving from a gap to a result, with the evidence base compressed, the design summarized, the findings displayed and read honestly, and the limitations placed where a reader would encounter them rather than buried at the end.
Exact status language carries more weight here than anywhere else in the session. Designed, proposed, approved, piloted on one unit for a stated period, adopted as standard and sustained beyond the practicum are six different claims, and only the true one belongs in your paper. Students inflate at this stage out of anxiety that an unimplemented project reads as failure. It does not. A capstone is assessed on the quality of the leadership reasoning, not on whether an organization moved inside eight weeks, and an inflated claim that unravels under a single question costs far more than the modest true one would have.
The practicum boundary applies to the last page as firmly as the first. Your 144 hours, the hour log, activity counts, site paperwork and the mentor evaluation remain your own record of work you personally performed, never drafted, reconstructed or estimated with any help. Nothing in the closing paper describes activity that did not occur, and no result is reported that you did not obtain. What the written layer supports is assembly and argument: how to rebuild rather than paste, how to display and read a small result honestly, how to write limitations a reader will trust, and how to construct a handoff. Everything drawn from real practice is de-identified before it appears, reported in aggregate, with no names, no dates and no traceable detail. Where you reuse your own earlier submissions, check your program's policy on self-reuse and follow whatever your section requires.
The NR-670A Week 8 method, step by step
Six moves that assemble eight weeks of separate work into one argued document.
-
Write the result in one sentence and put it first
What existed at the start, what you built, what happened, and what should happen next, compressed into a single line before any section is drafted. If that sentence will not form, the paper is not ready to be assembled and the missing piece is usually a reconciliation you have been avoiding.
-
Reconcile your numbers across every stage before writing prose
Put the baseline count and the evaluation count side by side and confirm they measure the same unit over comparable bases. Where they differ, say so in the paper and state which one the conclusion rests on. This is the single highest-value hour in the closing stage and the one students most often skip.
-
Rebuild each section rather than pasting it
Rewrite the problem, the evidence and the design from your own earlier work in continuous prose sized for the final document. Pasted sections carry the tense and framing of the week they were written in, and the discontinuity is visible to a grader within two paragraphs.
-
Report status in the exact language of what happened
Choose deliberately between designed, proposed, approved, piloted, adopted and sustained, and use the same term consistently throughout. Where an approval is pending, write pending and name the decision-maker by role. Precision here is an integrity matter before it is a scoring one.
-
Give the findings their display and then read them out loud
Present the measures with their denominators in the display you chose in advance, then write the reading in prose: what moved, what did not, and what a flat result means given the window. A table left to speak for itself forfeits the interpretation row entirely.
-
Build a handoff, not a conclusion
Name who owns the work now by role, where the artifacts live, what audit continues at what interval, and what decision the organization has to make next. A capstone that ends with a summary ends. One that ends with a handoff has produced something the setting can still use in six months.
A layout and word budget for the final synthesis
Our tutors' frame for a closing paper of roughly 2,000 to 2,800 words. 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 |
|---|---|---|
| Result stated first | The gap, what was built, what happened and what is recommended, compressed into an opening a busy reader could stop after. | 140 to 190 |
| Problem and setting, compressed | The microsystem and the measured gap rebuilt in continuous prose, with the baseline count and its window. | 320 to 400 |
| Evidence base, compressed | What the literature supported, how strong it was, and the conditions the intervention needed, in a fraction of the original length. | 300 to 380 |
| What was designed and what occurred | The intervention, the pilot if there was one, and the exact status language for each element. | 380 to 470 |
| Findings, display and honest reading | Measures with their bases, the chosen display, the interpretation in prose, and the reconciliation of any figures that differ. | 420 to 520 |
| Limitations, recommendations and handoff | The threats that most affect interpretation, what follows from the result, and the owner, location, audit interval and next decision. | 420 to 520 |
Evidence craft for a capstone synthesis
Compress the evidence base without losing its weight. The final paper needs the direction the literature pointed, how strong the body of evidence was, and the conditions attached, in perhaps a third of the space the earlier synthesis used. What survives compression is the appraisal, not the individual study descriptions.
Put limitations where a reader meets them naturally. Sample size belongs beside the count it constrains, and the short window belongs beside the outcome measure it prevented from moving. A limitations section quarantined at the end reads as a formality; limitations placed in context read as a writer who understands their own evidence.
Keep causal language proportionate to the last line. Everything in the closing paper has been building toward a result, and that is precisely when writers overreach. A single-site before and after comparison supports association and sequence, never causation, however strongly the numbers point.
Write recommendations that follow from what you found. Each one should be traceable to a specific finding, sized to the authority that would have to act, and addressed to a named role. A recommendation nobody in particular could execute is a wish, and the handoff paragraph is where capstones are most often thin.
Name your audience explicitly if a dissemination piece is required. A practice council, a service line director and a unit staff meeting need different documents: different length, different opening, different level of methodological detail. Saying in the paper who the piece is written for demonstrates the communication judgment the row is assessing.
Five mistakes that cost points in this week's territory
- Sections pasted from earlier weeks. The seams show in tense and register long before a grader reaches the content.
- Status language inflated past the truth. Writing adopted when the accurate word is proposed is the fastest way to lose a reader who was persuaded.
- Numbers that do not reconcile across stages. A baseline and a result counting different things makes the entire conclusion unusable.
- A display with no reading. A chart presented without interpretive prose forfeits the row that asks what the result means.
- A conclusion instead of a handoff. With no owner, no location and no continuing audit, the work ends when the session does.
Before you submit
- The result appears in the first paragraph, not the last
- Baseline and evaluation figures reconcile, or the difference is explained in the paper
- Every section is rebuilt in continuous prose rather than pasted
- One status term is chosen accurately and used consistently throughout
- Measures appear with their denominators and are read in prose
- Limitations sit beside the claims they constrain
- Causal language matches what a single-site design can support
- An owner, a storage location, an audit interval and a pending decision all appear in the handoff
Assembling the NR-670A 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 continuous argument with the result stated first, and revisions run until the grade lands.