The final stage of a 192-hour block produces two things at once: a synthesis that tells a doctoral reader what the block established and what it did not, and a handover that lets the site keep running the change without you. Both are written documents, both are graded, and the second is the one students forget until the last weekend. Write the synthesis so the next block can start from it rather than reconstruct it. Your section may print this as NR 707B or NR707B; 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-707B Week 8 asks for
Two weeks after a doctoral student finishes on a medical-surgical unit, the audit report stops being run. Not because anyone decided to stop, but because the person who ran it every Monday morning has gone and nobody was ever told it was theirs. This is the most predictable ending in improvement work, and it is prevented by a document rather than by enthusiasm. Whatever else this stage produces, it should produce a page that says who now owns each recurring task, how often, and how they would know it had lapsed.
The boundary that governs this manual, restated at the close because it matters most when time is short. Practicum hours, the hour log, encounter counts, site paperwork, and any evaluation completed by a preceptor or mentor are your own record of work you personally performed. In the final week, when a total has to be reconciled and a signature obtained, the temptation to have someone help you tidy the record is at its highest and the answer is still no. Nobody drafts, reconstructs, estimates, or phrases those documents. The written and scholarly layer, which is where support belongs, is the synthesis, the handover, the limitations, and the argument about what the block established. Every clinical detail on those pages is de-identified.
A closing synthesis at doctoral level does three things. It states what happened, with numbers and their qualifications. It says what the block can and cannot support as a conclusion, explicitly, in its own paragraph rather than by implication. And it positions the work for what comes next: the remaining stages of your project, the site's decision about continuation, and any dissemination still to be arranged. A summary that only performs the first of the three reads as a report to a manager rather than as doctoral scholarship.
Expect the deliverable to be a final written report or synthesis, often with a reflection component, sometimes with a presentation, and usually a closing discussion post. If reflection is included, hold it to the analytic register the rest of the session used: what you would specify differently, what your readiness assessment missed, which decision you would take earlier. Reflection at doctoral level is an examination of judgment, not a description of feelings about a hard eight weeks.
The NR-707B Week 8 method, step by step
Six analytic moves for closing a block so the work survives it.
-
1. Reconcile every number against its source one final time
Pull each figure back to the report or the verification sheet it came from and confirm the definition never drifted. A single inconsistency between your week four counts and your week eight table undermines an otherwise sound document.
-
2. State the conclusion the evidence actually supports
Write it in one sentence with its qualifications inside the sentence, then check that nothing elsewhere in the document claims more. This is the sentence your reader will test everything else against.
-
3. Enumerate limitations by class, not as a list of apologies
Design, measurement, duration, setting, and attribution are five distinct classes. Say what each one prevents you from concluding, in one sentence each. Specific limitations demonstrate command; generic ones demonstrate a template.
-
4. Assign every recurring task to a role, in writing
Audit, data pull, training of new staff, exception escalation, and the review that decides continuation. Each needs an owner by role, a frequency, and a failure signal that tells someone it has lapsed.
-
5. Write the block's residue for the next stage
What is unfinished, what is still running, what data will exist by a future date, and what decision is pending. A block that ends with a clean statement of its residue saves the next stage two weeks of orientation.
-
6. Reflect on judgment, not on effort
Name the decision you would take earlier, the assumption that proved wrong, and the evidence that should have changed your mind sooner than it did. That is the reflection a doctoral reader scores.
A layout for a closing synthesis and handover
Our frame for a final block document, sized for roughly 1,500 to 1,900 words plus a handover table. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever the two disagree.
| Section | What belongs in it | Word target |
|---|---|---|
| What the block did | Scope delivered against scope planned, live weeks achieved, and the components actually launched. | 180 to 220 |
| Results, reconciled | Outcome, process, and balancing measures with counts, denominators, periods, and definitions restated. | 280 to 340 |
| The supportable conclusion | One sentence carrying its own qualifications, expanded into a short paragraph of reasoning. | 170 to 210 |
| Limitations by class | Design, measurement, duration, setting, and attribution, each with what it prevents you concluding. | 260 to 320 |
| Handover | Each recurring task with an owner by role, a frequency, and the signal that would show it lapsed. | 220 to 270 |
| Residue and next stage | What remains open, what data will exist later, and which decision sits with whom. | 190 to 240 |
Evidence craft for a closing doctoral document
Restate definitions where results appear. A reader arriving at your results table should not have to page back to week three to know what the numerator counted. One clause of restatement per measure costs almost nothing and removes the most common source of misreading.
Match the strength of the verb to the strength of the design. Improved, was associated with, and coincided with are three different claims. A single-site pre and post evaluation with a short window supports the third comfortably, the second cautiously, and the first almost never. Doctoral faculty read verbs closely at this stage.
Name the rival explanations you cannot exclude. Seasonal variation, a concurrent initiative, staffing changes, and the attention the project itself created are all live alternatives in improvement work. Listing them is not weakness; omitting them is the weakness, because a reader who thinks of one you did not mention starts doubting the whole document.
Keep the translation frame to the last sentence. The work moved existing evidence into practice at one site and evaluated what happened there. It did not generate new knowledge, it is not a thesis, and it does not establish what would occur elsewhere. Where a determination about human subjects oversight applies at your organization, describe the process you followed rather than characterizing its outcome.
Check every citation and every number twice in the final pass. Late-session documents accumulate errors from copying: a figure updated in one table and not another, a source cited in text and missing from the list. Both are cheap to fix on Friday and expensive on Sunday, and both are entirely visible to a grader.
Five mistakes that cost points in this week's territory
- A conclusion stronger than the design. The single most reliable way to lose points in a closing doctoral document is a verb the evidence does not carry.
- Template limitations. Small sample size and short duration appear in every weak report and say nothing specific about yours.
- No handover. A project with no named owners is a project that ends when you do, and the document should not pretend otherwise.
- Numbers that disagree across your own documents. Consistency with your week four and week six writing is checked, and inconsistency is read as carelessness with data.
- Reflection about effort. How demanding the block was is not a doctoral finding. Which judgment you would revise is.
Before you submit
- Every figure has been reconciled to its source and matches your earlier documents
- The conclusion sentence carries its qualifications inside itself
- Limitations are organized by class, each stating what it prevents you concluding
- Every recurring task has an owner by role, a frequency, and a lapse signal
- The residue for the next stage is stated with dates and pending decisions
- Nothing in the document drafts, reconstructs, or reconciles hours, logs, or evaluations
Closing the NR-707B block?
Send the rubric and your accumulated documents out of Canvas. A premium original synthesis comes back in 24 to 48 hours with numbers reconciled, limitations written by class, and a handover somebody could actually execute, and revisions run until the grade lands.