The closing stage of a first project practicum usually asks for two things at once: an assembled plan narrative that reads as one document rather than eight assignments stapled together, and a practicum reflection that analyzes what the hours taught you rather than recounting them. Both are scholarly products aimed at a practice audience. Neither is a summary. Your section may print this as NR 702A or NR702A; 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-702A Week 8 asks for
What does a plan look like when it has been assembled rather than merely collected? It reads in one voice, defines each term once, uses the same wording for the measure in every section, and moves forward without repeating itself. The most common closing-stage submission is the opposite: a problem statement written in week one beside a framework section written in week five, each perfectly reasonable, together contradicting one another about the population, the intervention or the outcome. A community health center project that began as a screening problem and ended as a referral problem needs to say which it is, in one place, and then be consistent everywhere else. Integration work is unglamorous and it is where the closing grade usually lives.
The second deliverable, the reflection, has a shape most clinicians have to be taught. A narrative of what happened during practicum hours is a log in prose. An analytic reflection takes two or three specific moments, examines what they revealed about the work, and states what changed in your reasoning as a result. The moments should be small and real: the conversation where a records analyst explained why the field you wanted did not exist, the clinic session where nobody had ninety spare seconds, the meeting where the sponsor asked a question your plan could not answer. Doctoral reflection is evidence of developing judgment, and judgment shows in specifics.
The third demand is forward-facing. A first practicum course sits in a sequence, and its closing writing should hand a defined position to the next course: what is settled, what is provisional, what has to be resolved before implementation, and what the next block of hours is for. Students who write a closing summary produce a document nobody uses again. Students who write a handover produce the working spine of the next term.
The boundary that governs every page in this manual. Clinical hours, hour logs, encounter counts, preceptor evaluations, site documentation and signatures are the student's own record and are never drafted, reconstructed or estimated with help. That applies with particular force to a reflection, which must describe experiences you genuinely had. Writing support can help you structure and sharpen an analysis of your own work; it can never supply the work or the hours 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-702A Week 8 method, step by step
Seven moves for assembling the plan and writing a reflection that analyzes.
-
Build a definitions sheet before you assemble anything
One page listing your population, intervention, outcome, benchmark and framework in their final wording. Then edit every section to match that sheet exactly. This single pass removes most of the internal contradictions a reader would otherwise find.
-
Read the document only for the thread
Ignore prose quality on this pass. Ask whether each section follows from the one before and whether anything appears twice. A plan that argues the same point in two places has usually lost track of what each section is for.
-
Write a new opening rather than reusing the first one
The introduction to an assembled document is written last, because only now do you know what the document says. It should state the gap, the change, the framework and the evaluation in a single paragraph a reader could quote back to you.
-
Add the seams that were never written
Transitions between sections that were composed weeks apart do not exist yet. Two or three sentences at each junction, saying why the next section follows, is often the difference between a stapled set and a document.
-
Choose two or three practicum moments for the reflection
Specific, small and genuinely yours, each revealing something you did not know when the term began. Discard anything you cannot say a consequence for, because a moment without a consequence is an anecdote.
-
Write each moment as situation, insight, change
What happened in three sentences, what it revealed about the setting or your reasoning, and what you did differently afterwards. That structure makes a reflection analytic without any need for reflective vocabulary.
-
Close with an honest handover to the next course
What is settled, what is still open, what depends on someone else, and what the next block of practicum hours has to accomplish. Write it as though a colleague were taking over the project, because in effect a future version of you is.
A layout and word budget for the closing deliverables
Our frame for a combined assembled plan and reflection, sized for roughly 1,400 to 1,800 words across the two pieces. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever they disagree. If the two are submitted separately, keep the proportions.
| Section | What belongs in it | Word target |
|---|---|---|
| New introduction | Gap, change, framework and evaluation in one paragraph, written after everything else is final. | 140 to 180 |
| Problem and baseline, condensed | The measured gap with its numbers, compressed from the earlier section without losing the denominators. | 180 to 220 |
| Plan in brief | The intervention, the framework stage sequence and the evaluation measures, in their final wording. | 240 to 300 |
| Feasibility and sustainability | What holds the change in place after the project ends and who owns it then. | 180 to 220 |
| Reflection: moments | Two or three specific practicum experiences written as situation, insight and change. | 320 to 400 |
| Reflection: competency movement | What developed in your practice this term, argued against a named professional standard rather than asserted. | 180 to 220 |
| Handover to the next course | Settled, provisional, blocked, and the specific work the next hour block must carry. | 160 to 200 |
Evidence craft for closing and reflective writing
A reflection still carries citations. Doctoral reflection is usually expected to argue development against published competencies or professional standards rather than against a personal sense of progress. Name the standard, name the year, and connect a specific piece of your work to a specific expectation, which converts self-report into an evidenced claim.
Fix terminology globally, not locally. If the outcome is documented completion within fourteen days, it says that in the introduction, the plan, the evaluation and the reflection. Searching your own document for each key term and reading every instance is a twenty-minute task that catches the errors readers notice first.
Sustainability is a person and a process, not a wish. Write who owns the change after you leave, what mechanism keeps it running when attention moves elsewhere, and what would have to be true a year from now for it to still be happening. Standing orders, embedded templates and existing meeting rhythms are sustainability; enthusiasm is not.
Keep confidentiality tight in reflective writing. Reflection is where identifying detail slips in, because the moments that taught you something were specific. Strip names, dates and role combinations that would identify a colleague in a small site, and describe patients only in the terms your analysis actually needs.
Do not claim outcomes you have not produced. A first practicum course plans; it does not usually implement or evaluate. Write in the tense that matches reality, and resist the pull to describe anticipated results as though they had occurred, because a committee reading the sequence later will notice the discrepancy immediately.
Five mistakes that cost points in this week's territory
- An assembled document that contradicts itself. A population defined one way in week one and another in week seven is the most visible integration failure and the easiest to fix.
- Reflection as chronology. An account of what happened week by week is a log rendered in paragraphs and demonstrates none of the judgment being assessed.
- An introduction recycled from the first submission. It was written before the plan existed and it almost always promises something the finished document does not deliver.
- Sustainability without an owner. Saying the change will be embedded in practice names no mechanism and no person, so nothing about it can be evaluated.
- Past tense for work not yet done. Describing planned implementation as though it occurred creates a discrepancy the next course's documents will expose.
Before you submit
- Every key term matches the definitions sheet in every section
- The introduction was written after the rest of the document was final
- Transitions exist at each junction between sections written weeks apart
- The reflection is built from two or three specific moments, each with a consequence
- Development is argued against a named professional standard with a year
- Sustainability names an owner and a mechanism
- Tense matches what has actually happened so far
- No patient, colleague or site is identifiable anywhere in the document
Closing out NR-702A?
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 with terminology reconciled throughout and a reflection built on analysis rather than chronology, and revisions run until the grade lands.