The final stage of a project practicum usually asks you to produce two things: a proposal narrative that reads as one continuous document written by one person, and a reflection that analyzes what 192 hours of practicum work taught you rather than recounting it. Both are scholarly products for a practice audience. The integration pass is unglamorous, it is where the closing grade tends to live, and in a three-credit block there is enough time to do it properly. Your section may print this as NR 702B or NR702B; 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-702B Week 8 asks for
What does a committee actually read for in a proposal narrative? Coherence, mostly. They will check that the problem you named in the opening is the problem your measures address, that the intervention you specified is the one your synthesis supports, and that the evaluation could detect the change you claim to expect. Documents written a week at a time drift at exactly these joints. A hospice outpatient service project that opened as a symptom documentation problem and ended with measures about family contact has drifted, and the fix is not more words but a decision about which project it is, applied consistently from the first page to the last.
The reflection has a different demand and a shape clinicians usually have to be taught. A record of what happened during your hours, however detailed, is a log rendered in paragraphs. An analytic reflection selects two or three specific moments, examines what each revealed, and states what changed in your reasoning as a result. In a 192-hour term there will be more candidate moments than you can use, which is an advantage: choose the ones that changed something. The conversation where a data analyst explained that the field you needed was optional and therefore unreliable is worth more than a week of routine observation.
The third demand is forward-facing. A first project practicum sits inside a sequence, and its closing writing should hand a defined position to whatever comes next: what is settled, what is provisional, what is blocked and on whom, and what the next block of hours must accomplish. Students who write a closing summary produce a document nobody opens again. Students who write a handover produce the working spine of the next term.
The boundary that governs every page in this manual. Practicum hours, hour logs, encounter counts, site documentation, preceptor evaluations and signatures are the student's own record and are never drafted, reconstructed or estimated with help from anyone. This applies with particular force to reflective writing, which must describe experiences you genuinely had. Support can shape and sharpen your own analysis; it can never supply the work behind it. De-identify every patient, colleague and site detail, describe roles rather than individuals, and keep the setting anonymous by type and size.
The NR-702B Week 8 method, step by step
Seven moves for assembling the proposal and writing a reflection that analyzes.
-
Build a one-page decisions sheet first
Population, intervention as specified, outcome definition, benchmark, framework, evaluation design, all in their final wording. Then edit every section to match it. This single pass removes most of what a reader would otherwise flag.
-
Read the whole document only for coherence
Ignore sentences. Ask whether each section answers a question raised by the one before it and whether any argument appears twice. Repetition usually means two sections are competing for the same job.
-
Check the chain from problem to measure
The problem names a gap, the synthesis supports an intervention that addresses that gap, the specification delivers it, and the evaluation measures it. Walk the chain link by link and fix whichever link does not hold.
-
Write the introduction and the abstract-style summary last
Both are written after the document exists, because only then do you know what it says. A summary drafted in week one will promise something the finished proposal does not deliver.
-
Add transitions where sections were written weeks apart
Two or three sentences at each junction, saying why what follows follows. This is the cheapest quality gain available in the whole assembly pass and it is what makes a set of assignments read as a document.
-
Select reflection moments by consequence
Take only moments that changed how you think or what you did. Anything you cannot attach a consequence to is an anecdote, and anecdotes are what make reflections read as chronology.
-
Write each moment as situation, insight, change
Three sentences of what happened, then what it revealed, then what you did differently. That structure produces analytic reflection without any reflective vocabulary, and it is what a doctoral reader is scoring.
A layout and word budget for the closing deliverables
Our frame for a combined proposal narrative and reflection, sized for roughly 1,600 to 2,000 words across both pieces in a three-credit block. It is our own outline rather than anything the university publishes, and your week's rubric outranks it wherever they disagree.
| Section | What belongs in it | Word target |
|---|---|---|
| Summary written last | Problem, evidence, intervention, evaluation and expected contribution, in one tight paragraph. | 150 to 190 |
| Problem and gap, condensed | The measured shortfall with its numbers intact, compressed without losing the denominators. | 170 to 210 |
| Evidence in brief | The synthesis conclusion and the two or three claims that drove the intervention choice. | 200 to 250 |
| The plan as specified | Workflow, framework stages, timeline phase and fidelity threshold in their final wording. | 230 to 280 |
| Evaluation and sustainability | The measure set and the mechanism that holds the change once the project ends. | 200 to 250 |
| Reflective episodes | Two or three episodes from your own hours, each carrying a consequence you can name. | 350 to 430 |
| Competency and handover | Development argued against a named professional standard, then settled, provisional, blocked and next. | 250 to 300 |
Evidence craft for closing and reflective writing
Reflective writing still carries citations. Doctoral reflection normally argues development against published competencies or professional standards rather than against personal impression. Name the standard and its year, and connect a specific piece of your own work to a specific expectation, which turns self-report into an evidenced claim.
Reconcile terminology across the whole document. Search for each key term and read every instance. Where the outcome is documented completion within a defined window, it says that in the summary, the plan, the evaluation and the reflection. Readers notice this before they notice anything else.
Write sustainability as an artifact and an owner. The template, standing order, agenda item or report that carries the change, plus the role responsible once you leave. Enthusiasm, commitment and buy-in are not mechanisms and cannot be evaluated.
Protect confidentiality hardest in the reflection. The moments that taught you something are specific, which is exactly what makes them identifying. Strip names, dates and role combinations that would single out a colleague in a small service, and include patient detail only to the degree your analysis actually needs it.
Use the tense that matches reality. A first practicum course plans; it does not usually implement or evaluate. Do not describe anticipated results as though they occurred, because the sequence's later documents will contradict it and the discrepancy is the kind a committee remembers.
Five mistakes that cost points in this week's territory
- A proposal that contradicts itself across sections. An outcome defined one way in the baseline and another in the evaluation is the most visible integration failure there is.
- Reflection as a week-by-week account. Chronology demonstrates attendance rather than judgment, and judgment is the thing being assessed.
- A recycled introduction. Written before the plan existed, it promises a project the document no longer describes.
- Sustainability with no owner named. Embedded into practice specifies no artifact and no person, so nothing about the claim can be checked.
- Results language in a planning document. Describing expected findings as though they had been obtained creates a discrepancy that later coursework will expose.
Before you submit
- Every key term matches the decisions sheet in every section
- The chain from problem to measure holds link by link
- The summary and introduction were written after everything else
- Transitions exist at each junction between sections written weeks apart
- The reflection uses two or three moments, each with a stated consequence
- Development is argued against a named standard with a year
- Sustainability names an artifact and a responsible role
- Nothing in the document could identify a patient, a colleague or the service
Closing out NR-702B?
Send the rubric and every section you have written out of Canvas. A premium original draft comes back in 24 to 48 hours reading as one document, terminology reconciled throughout and a reflection built on analysis rather than chronology, and revisions run until the grade lands.