The final stage of a 192-hour block closes two things at once: the term's written record, and the state of the project as it passes to the next phase. The handoff document is the piece that carries real weight - where the implementation stands, what the evidence so far supports, what remains unresolved, and what the site needs in order to keep the change running without you. Written properly it becomes the spine of your next block and a genuine asset to the practice. Your section may print this as NR 705B or NR705B; 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-705B Week 8 asks for
The honest question at the end of a block like this is whether the screening step survives the day you stop attending the huddle. In most family practices the answer is decided by three things: whether the step is embedded in a template rather than in a person's memory, whether someone other than the student owns it, and whether anyone will still be looking at the number in three months. A closing document that reports what was accomplished and says nothing about those three has answered the smaller question and skipped the one a doctoral committee cares about.
Interim results, at this point, need careful handling. You almost certainly have counts covering a partial operating period, and they may look encouraging or discouraging. Both need the same treatment: report them with bases and periods, label them interim, and refuse to draw a conclusion an evaluation stage has not yet earned. The discipline of writing screening completed at 118 of 187 eligible visits across the operating period to date, with the pattern still unstable and no comparison against baseline yet performed, is what separates a doctoral writer from an enthusiastic one.
The forward-looking half is where sustainability reasoning lives. Sustainability is not a paragraph of hope; it is a set of structural facts. Is the step in the electronic record build or on a piece of paper you restock? Does a named role own it in a job description or does it belong to whoever remembers? Is there a report someone receives without asking for it? Does the practice's own leadership have a reason to keep it that survives your departure? Write those as findings about the site, honestly, including where the answer is no.
Where the boundary sits. The end of a block is when the practicum record gets finalized, and this is exactly where the line must be clearest. Your 192 clinical hours, the log recording them, encounter and activity counts, mentor and preceptor evaluations, site agreements and any signature the university verifies are yours alone. They are never drafted, assembled, reconstructed, back-filled or estimated with anyone's help, and no legitimate service touches them at any point in the term, least of all in the closing week. What written support covers is the scholarly layer: the handoff document, the interim results narrative, the sustainability analysis, the reflection. De-identify every clinical detail that appears in your writing. The clinical hours cannot be shortcut and clearer writing about work you genuinely did is the whole offer.
The NR-705B Week 8 method, step by step
Six moves for closing an implementation block on paper.
-
State the project's status in one paragraph a stranger could act on
What is running, in which visit types, under which protocol version, with what measurement in place. Someone picking this up cold should know the operating state before they know the history.
-
Report interim numbers with their bases and refuse the conclusion
Counts, denominators, the exact operating window, and a plain statement that the evaluation stage has not yet occurred. Any comparative claim made here will be quoted back at you later.
-
Assemble the version and change record into one table
Protocol versions with effective dates and what each changed. This is the document your evaluation stage will depend on most, and reconstructing it later is far harder than assembling it now.
-
Answer the four sustainability questions in writing
Embedded or manual, owned by a role or by a person, monitored automatically or on request, and supported by a local reason that outlives you. Answer each with what is true, not with what you intend.
-
Write the ownership transfer as a named request
Which role takes the step, what they inherit, what they need to receive - the reference sheet, the report, the escalation path. A transfer described in general terms does not happen.
-
List the open items with owners and consequences
Baseline extract not yet pulled, template field still queued, one provider's visits still excluded. For each, who owns it and what it costs the evaluation if it stays open. This is your first task list for the next block.
A layout and word budget for a stage-closing handoff document
Our frame for a closing document written to serve both the course and the project, sized for roughly 1,500 to 1,900 words plus tables. It is our own outline rather than anything the university issues, and your chair's direction and your week's rubric outrank it wherever they disagree.
| Section | What belongs in it | Word target |
|---|---|---|
| Operating status | What is running now, in which visit types, under which protocol version, and what measurement is in place. | 160 to 200 |
| What the block accomplished | The implementation milestones actually reached, written as facts with dates rather than as achievements. | 220 to 270 |
| Interim indicators | Counts with denominators and the operating window, explicitly labelled as pre-evaluation and uninterpreted. | Table plus 180 |
| Version and change record | Every protocol version with its effective date and what it altered, plus any period that ran under mixed conditions. | Table plus 120 |
| Sustainability assessment | Embedding, ownership, monitoring and local rationale, each answered with the current reality including the negatives. | 300 to 370 |
| Ownership transfer | The role taking the step, what they receive, and what remains dependent on you until the next block. | 200 to 250 |
| Open items for the next stage | Each unresolved item with an owner, a target, and the specific cost to the evaluation if it remains open. | 220 to 270 |
Evidence craft for a closing document
Label everything pre-evaluation. The single most damaging sentence a student can write at this stage is one that reads as a result. Say that the evaluation has not been conducted, that the figures are operational counts, and that any comparison awaits the next stage. That sentence costs nothing now and protects the credibility of your findings later.
Write sustainability as observed structure, not intention. The step is built into the visit template and appears without staff action is a structural fact. The practice intends to continue is a hope. Committees have read a great many projects that ended with the second sentence and did not continue.
Cite sustainability literature once, correctly. There are published frameworks for assessing whether an improvement will persist, and using one gives your assessment categories a reader can recognize. Apply it to your site rather than describing it, and name the source with its year.
Keep the accomplishment section factual. A protocol was written, staff in three roles were prepared, the step ran across a stated number of eligible visits over a stated window. Dates and counts. Adjectives like successful and robust invite a reader to check whether they are earned.
De-identify to the end. The closing document tends to be the one shared most widely, sometimes with the practice itself. Aggregate everything, remove any detail that could identify a family, and use roles rather than names throughout, including for people you want to credit.
Five mistakes that cost points in this week's territory
- Declaring success on interim numbers. A partial operating window with no baseline comparison supports no conclusion, and claiming one at this stage is the error most likely to follow you into a defense.
- Sustainability written as optimism. A paragraph about the team's commitment is not an assessment. Embedding, ownership, monitoring and local rationale are.
- No version record. If the closing document cannot say which protocol ran in which weeks, the next stage inherits an interpretive problem it may not be able to solve.
- Open items with no owner. An unresolved item listed without a role attached is a note to yourself, and it will still be open at the start of the next block.
- Treating the closing document as a course submission only. The site can use this. Written for both audiences it is a genuine contribution; written for a grader alone it is discarded the day it is marked.
Before you submit
- The operating status paragraph would orient someone who knows nothing about the project
- Every number appears with a denominator and the exact operating window
- All figures are explicitly labelled pre-evaluation and uninterpreted
- The protocol version record is complete with effective dates
- Sustainability is assessed on structure, including where the answer is unfavourable
- Ownership transfer names a role and lists what that role receives
- Every open item carries an owner and a stated cost if it stays open
- Nothing in the document identifies a family, a staff member or a specific encounter
Closing NR-705B this week?
Send the rubric, your protocol versions and your own aggregate counts out of Canvas. A premium original draft comes back in 24 to 48 hours with interim figures written with their bases and sustainability assessed structurally, revised free until it lands. Practicum hours, logs and evaluations remain entirely and only yours.