The closing stage of a concluding graduate experience does three separate jobs and students routinely treat it as one. It assembles a document whose parts were written six to sixteen weeks apart into something that reads as though one person wrote it in one sitting. It produces a terminal reflection that analyzes the experience against professional competencies rather than narrating it. And it sets out how the work leaves the building: who receives it, in what form, and on what timetable. Your section may print this as NR 652 or NR652; 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-652 Week 8 asks for
Picture the reader nobody writes for. Eight months from now, a newly hired clinical services coordinator at a skilled nursing facility opens a shared drive folder and finds your final report. She was not in the room for the presentation, she has never met you, and she is trying to work out why a step in the transfer routine exists and whether it is still doing anything. What she needs is a document that names the problem, states what was done and what happened, identifies who owns the step now, and says what the measure was and where to find it. Whether she finds that in ten seconds or gives up is decided this week, by how the final artifact is assembled.
The first job, then, is coherence. Work written across a two-course sequence accumulates seams: terminology that drifted, a project name that changed, an aim stated three different ways, tense that switches between the proposal's future and the report's past, tables formatted by three different versions of you. None of those are content errors and all of them are visible. A coherence pass is genuine work and it takes longer than students budget, particularly the terminology audit, which frequently turns up four names for the same intervention.
The second job is the terminal reflection, and it is the part most often written badly. A closing reflection in a graduate capstone is not a diary of the semester and it is not gratitude. It is an assessment of your own performance against the competencies the program is built on, argued with evidence drawn from the project. Naming a competency, describing a specific moment in the work where it was demanded, saying honestly how you performed and what you would do differently, is analysis. Saying that the experience was challenging and rewarding and that you grew as a leader is a paragraph that could have been written before the project started.
The third job is dissemination planning, which is where a capstone either lands or evaporates. The presentation reached the people in the room. The report sits in a folder. A dissemination plan states who else should know, in what form the work reaches them, who sends it, and by when. Deliverables at this stage commonly include the assembled final report or portfolio, the reflection, and often a dissemination or handover statement. Where a discussion board runs alongside, post final copy; contributions do not reopen after submission in Canvas.
Boundary setting: the closeout record is the student's alone
The end of a practicum sequence is exactly where the boundary matters most, because deadlines cluster and the temptation to have paperwork handled is highest. It does not move. Total clinical or practicum hours, hour logs, activity and encounter documentation, attendance verification, site agreements, preceptor and mentor evaluations, faculty site evaluations and any final competency attestation are produced, entered and signed by you and by the people who supervised you. They are never drafted, reconstructed, estimated or reconciled with outside help, and no writing support of any kind touches them. If your hours are short, that is a conversation with your faculty and your site, held early, and there is no written solution to it.
What can be taught is the assembly and the reflective craft that sits on top of a real practicum. How to run a coherence pass on a long document. How to build a competency-to-evidence map so a reflection argues rather than asserts. How to write a self-assessment that is candid about a weakness without reading as either apology or performance. How to structure a dissemination plan around recipients and dates. How to make a final artifact legible to a stranger. Those skills apply equally well to a project that went smoothly and to one that did not.
The de-identification discipline holds to the last file. Final portfolios travel further than any other document you produce in the sequence: they get uploaded, archived, sometimes shared with future cohorts, and occasionally attached to a job application. Check that no resident, family member, employee or preceptor is identifiable anywhere in the assembled document, including in appendix material, screenshots of forms, meeting references and file names. Write roles, describe the site by type and scale, and confirm before submission that nothing carrying a name has been pasted in from a working file.
The NR-652 Week 8 method, step by step
Six moves for closing a concluding graduate experience properly.
-
Run a terminology and naming audit across the whole document
Search for every name the intervention was given across the sequence and standardize on one. Do the same for the measure, the population and the setting descriptor. This is a mechanical pass with a disproportionate effect on how the assembled document reads.
-
Fix tense and voice at the seams
Proposal-stage text describes what will happen; report-stage text describes what did. Where the two are stitched together, the tense usually breaks mid-section. Read the joins specifically rather than reading the whole document for the fifth time.
-
Build a competency-to-evidence map before writing the reflection
A two-column list: each competency your program names, and the specific moment in the project that demonstrates or fails to demonstrate it. The map is a working document, not a submission, and it converts the reflection from recollection into argument.
-
Write the reflection with one genuine shortfall in it
Choose a real one, describe the situation, say what you did, say what a stronger performance would have looked like, and name what you will do differently in practice. A reflection in which everything went well demonstrates nothing about your capacity to evaluate your own work.
-
Write the dissemination plan as a table of recipients and dates
Who receives the work, in what form, who sends it, by when. Internal committees, the facility's leadership, a system or corporate quality group, a professional organization, a conference abstract deadline, a manuscript submission. Each row is a commitment, so only include rows you intend to keep.
-
Do the mechanical submission pass last and against the actual checklist
File format, file naming, title page, page numbering, heading levels, table titles, appendix labels, reference list against in-text citations both directions, and every submission portal your section requires. Mechanical losses at the end of a sequence are the most avoidable points in the program.
A layout and word budget for the closing submission
Our frame for the final assembled artifact and its reflection, sized for a reflection of roughly 1,200 to 1,600 words alongside an assembled report. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever the two disagree.
| Component | What belongs in it | Word target |
|---|---|---|
| Executive summary | Problem, change, result with denominators, current owner and ongoing measure, on one page for the stranger who inherits it. | 300 to 400 |
| Assembled body | Proposal and report sections merged into one tense, one terminology and one numbering scheme. | Carried forward |
| Reflection: competency evidence | Three or four competencies, each with a specific project moment attached as evidence. | 450 to 600 |
| Reflection: the shortfall | One genuine weakness, the situation that exposed it, and what a stronger performance looks like. | 250 to 350 |
| Reflection: forward practice | What changes in your practice as a result, stated concretely enough that someone could check it. | 200 to 280 |
| Dissemination plan | Recipients, format, sender and date, as a table rather than as prose intentions. | 200 to 300 |
| Handover statement | Role owner, the routine the change now lives inside, the ongoing measure, the review cadence. | 150 to 220 |
Evidence craft for closing and reflective writing
Anchor every competency claim to a dated moment in the project. A reflection that says you developed collaboration skills asserts. A reflection that says a scheduling conflict between therapy and nursing threatened delivery in the third week, describes what you proposed and how it was received, and evaluates the outcome, demonstrates. Graders score the second and cannot score the first.
Cite in the reflection, even though it is about you. Professional competency frameworks, leadership standards and role documents are published and dated, and quoting the language you are measuring yourself against turns self-assessment into a comparison with an external benchmark. This is the single most reliable way to lift a closing reflection out of the personal register.
Keep numbers consistent to the last page. Assembled documents frequently contain two versions of the same figure because an early draft was never updated after the final data pull. Search the document for each key number and confirm every instance matches, including in the abstract, the executive summary and any table title.
Write the dissemination plan in the passive-free form. Findings will be shared with leadership commits nobody. The director of nursing receives the two-page summary from me by the end of the month, and the corporate quality council receives it at its next quarterly meeting, names an actor, an object and a date, which is what makes it a plan.
Let the executive summary carry the whole project. Assume it is the only page most people will ever read, and write it so that a reader who reads nothing else knows the problem, the change, the result with its denominators, the current owner and where the ongoing measure lives.
Five mistakes that cost points in this week's territory
- A reflection made of gratitude. Thanking the site and describing the experience as rewarding leaves the analysis row empty on a rubric that exists to score analysis.
- Visible seams. Four names for one intervention and two tenses in one section tell a reader the document was assembled rather than written.
- Numbers that disagree with themselves. A figure in the summary that no longer matches the results section undermines every other number in the report.
- Dissemination as intention. A paragraph of things that will be shared, with no recipient, sender or date, is not a plan and is easy for a grader to mark as such.
- Leaving the mechanical pass undone. Missing appendix labels, unpaired citations and wrong file naming are pure avoidable loss in the last week of a program.
Before you submit
- One name is used for the intervention, the measure and the population throughout
- Tense is consistent across every section stitched from earlier work
- Each key number is identical in every place it appears, including the summary
- The reflection attaches each competency claim to a specific moment in the project
- One genuine shortfall is examined rather than mentioned
- The dissemination plan names a recipient, a sender and a date for every row
- Nothing anywhere in the assembled file identifies a resident, family member, employee or preceptor
- Every reference appears in the text and every in-text citation appears in the list
Closing out the sequence this week?
Send the rubric out of Canvas with your assembled draft and your program's competency list. A premium original draft of the reflection, the executive summary and the dissemination plan comes back in 24 to 48 hours, with the coherence pass done across the whole document, and revisions run until the grade lands. Hours, logs, evaluations and every signed practicum record remain entirely your own.