The closing stage of the first concluding experience is assembly, and assembly is a skill of its own. Seven stages of separately written components have to become one document with one voice, one aim sentence repeated identically wherever it appears, a reference list that reconciles with the text, and an opening summary that an administrator with twelve minutes could act on. Alongside it usually sits a reflection, and the reflection is graded on analysis rather than on narration of what you did. Your section may print this as NR 651 or NR651; 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-651 Week 8 asks for
Here is the scene that should govern the assembly week. A regional director of clinical services for a group of long-term care buildings sits down with your proposal between two meetings. She will read the first page carefully, scan the headings, stop at the resource table and the timeline, and decide in about twelve minutes whether this is something her buildings could carry. She will not read the synthesis. She will notice if the aim on page two differs from the aim in the evaluation section, and she will lose confidence entirely if the cost estimate contradicts the staffing assumption three pages later. Everything the assembly stage asks of you follows from imagining that reader.
Internal consistency is the graded property that most students underestimate. A proposal written over seven weeks accumulates drift: an aim that was 24 hours in one stage and one business day in another, a population that shifted from all transfers to unplanned transfers, an objective that was cut but still appears in the evaluation table, a component described one way in the workflow and another in the appendix. None of these are hard to fix and all of them are visible to a careful grader, because a scoring guide for a capstone proposal is largely a consistency check dressed as content rows.
The reflection is a different kind of writing and is scored on a different axis. A weak reflection recounts the sequence of the term: I met with my sponsor, I searched the literature, I built a timeline. A strong reflection selects two or three moments where your thinking changed, analyzes what caused the change, and connects it to graduate-level competencies and to how you will practice differently. The unit of a good reflective paragraph is an insight with evidence, not an event in chronological order.
This stage also functions as a handoff. Whatever survives into the second course does so through this document, so anything ambiguous now becomes an obstacle later. Write the proposal so that a version of you eight weeks from now, holding data and a sponsor's impatience, can find the definition, the approval and the measure specification without reconstructing them.
Boundary setting: the reflection analyzes work you actually did
A reflection is the most personal document in the course and therefore the one where the boundary matters most. It reflects on your practicum: hours you were present for, conversations you had, resistance you met, judgments you made. Those hours, the log that records them, activity or attendance documentation and any preceptor, mentor or sponsor evaluation are your own record, produced by you, and are never drafted, reconstructed or estimated with outside help. A reflection about a practicum someone else described for you is not a reflection; it is a fabrication with a graded rubric attached.
What can properly be taught is structure and register: how to move from narration to analysis, how to select the two or three moments worth writing about out of eight weeks of them, how to connect an experience to a competency without sounding like you are reciting one, and how to close on a forward commitment that is specific. Those are craft skills, and applying them to your own real experience is entirely legitimate.
De-identification still applies, and reflections are where it most often slips, because the moment that changed your thinking usually involved a specific person. Write the role and the substance, not the name and the scene. Never include resident or patient detail that could identify someone to a reader who works at the site, and think carefully before writing anything about a named colleague that you would not say to them.
The NR-651 Week 8 method, step by step
Six moves for turning seven stages of drafts into one document plus a reflection worth reading.
-
Rebuild the document in the rubric's order, not the order you wrote it
Open a clean file, put the scoring rows in as headings, and move content in under them. Anything with no home is either an appendix or a cut. This one move fixes most structure deductions, because the grader's path through your document now matches their scoring guide.
-
Run a consistency pass on the four things that drift
The aim sentence, the population definition, the objective list and every number. Search the document for each and make the wording identical wherever it appears. Where two versions exist, decide which is right rather than splitting the difference, and correct all instances at once.
-
Write the executive summary last and to a hostile clock
Problem, evidence in one sentence, aim with its number, what will be done, what it costs, how it will be judged. Roughly a page. Written last, it is a summary; written first, it is a guess that the rest of the document then has to live up to.
-
Reconcile citations and references in both directions
Every in-text citation appears in the list and every entry in the list appears in the text. Then spot-check three references against the actual articles for year, authorship and the claim you attached to them. Drift here is common after seven weeks of drafting and it is the easiest deduction a grader can justify.
-
Build the appendix set with purpose and cross-reference it
Draft artifacts, the measure specification table, the timeline, the search record. Each appendix should be referred to at least once in the narrative at the point where a reader would want it, and each should carry a label and a title of its own.
-
Draft the reflection around turning points, then cut the chronology
Write the two or three moments where your understanding changed, what you believed before, what changed it, and what you now do differently. Delete every sentence whose only content is that something happened in a particular week. What remains is analysis.
A layout and word budget for the assembled proposal and reflection
Our frame for the closing deliverables of the first concluding experience. The proposal length is driven by your rubric and by what your earlier stages produced; the reflection frame below is sized for roughly 800 to 1,100 words. This is our own outline rather than anything the university issues, and your week's rubric outranks it wherever they disagree.
| Element | What belongs in it | Word target |
|---|---|---|
| Executive summary | Problem, evidence, aim with its number, planned action, resources and how success will be judged. | 250 to 350 |
| Assembled proposal body | The seven stages edited into one voice under the rubric's headings, with drift removed. | Per rubric |
| Approval and sponsorship status | What has been agreed, by whom, in what form, and what approval remains outstanding. | 120 to 160 |
| Reflection: opening claim | The one thing you understand differently now, stated before any account of the term. | 70 to 100 |
| Reflection: turning points | Two or three moments, each with the belief before, the cause of change, and the consequence for the project. | 380 to 520 |
| Reflection: competency connection | How the experience maps to graduate practice expectations, named from a published source with a year. | 170 to 230 |
| Reflection: forward commitment | What you will carry into the second course, specific enough that someone could check it. | 90 to 130 |
Evidence craft for assembly and reflective writing
Give the reader the same number everywhere. If the intervention takes an estimated seven minutes per transfer, that figure appears identically in the workflow, the resource table and the risk section. Contradictory figures do more damage to credibility than an unfavourable figure ever does.
Cite in the reflection too. Reflective writing at graduate level still connects to published competency statements, professional standards or implementation literature. One or two well-placed sources convert personal narrative into scholarly reflection, and their absence is a common deduction.
State approval status honestly. If your sponsor has agreed verbally but no committee has reviewed the proposal, say exactly that. Overstating organizational commitment creates a problem in the second course that is far worse than the small deduction honesty might cost now.
Keep appendices labeled and referenced. An unreferenced appendix is invisible, and an appendix stack with no titles reads as material you did not know where to put. Point to each one from the sentence in the narrative where a reader would reach for it.
Write the reflection in the past tense about what happened and the present about what you now believe. That tense discipline is what keeps a reflection from sliding back into chronology, and it makes the analytic sentences audibly different from the narrative ones.
Five mistakes that cost points in this week's territory
- Stapling the stages together. Seven documents with seven introductions is not a proposal; transitions and a single voice are part of what is scored.
- An aim that has quietly changed. Different wording in different sections is read as carelessness even when the intent was constant.
- A reflection that narrates the term. Chronology is the default and it scores at the bottom of the reflective row every time.
- Reference drift. Sources cited in early stages that never made the final list, or list entries that appear nowhere in the text.
- Overstated approval. Writing that the organization has approved a project that one manager has verbally supported creates an unrecoverable problem later.
Before you submit
- The document is ordered to the rubric's own headings
- The aim sentence is identical everywhere it appears
- Every number in the document agrees with every other instance of it
- Citations and references reconcile in both directions
- Each appendix is labeled, titled and referenced from the narrative
- The reflection is built on turning points rather than chronology
- Approval and sponsorship status is stated exactly as it stands
Assembling the proposal this week?
Send the rubric out of Canvas with your stage drafts. A premium original edit or draft comes back in 24 to 48 hours, ordered to the scoring rows with the drift removed and an executive summary written for a reader with twelve minutes, and revisions run until the grade lands. Your practicum hours, logs and evaluations remain your own record throughout.