The closing stage of a 128-hour practicum block asks you to report where the project actually stands and to reason about what would keep the change alive after your attention leaves. Milestone reporting means stating what was completed, what was not, and why, in language a committee can verify rather than in a summary that implies more progress than exists. Sustainment reasoning means asking who owns the change when the project ends, what would make it survive a staffing shift, and what would cause it to quietly lapse. Both are doctoral competencies and both reward accuracy over optimism. Your section may print this as NR 705A or NR705A; 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-705A Week 8 asks for
Ask any experienced nurse leader in long-term care what happens to a well-designed process eighteen months after the person who built it moves on, and you will get the same answer with different details. It survives if it was absorbed into something that already had to happen, and it lapses if it depended on the attention of a particular individual. A structured pre-transfer check built into the existing shift routine and printed on the form that already travels with the resident is likely to still be running. The same check maintained through a weekly reminder from a project lead is almost certainly gone. Nothing about the clinical merit differed. The difference was structural absorption.
Sustainment reasoning is that analysis written out. It belongs in this closing stage even though the change may not yet be implemented, because sustainment is a design property rather than an afterthought: the decisions that determine whether something lasts are made while it is being specified. A doctoral reader looks for whether you know that, and for whether your design has been shaped by it. Ownership after the project, integration into existing documents and routines, the measurement that continues without you, and the conditions that would break it are the four elements that carry the section.
The other half of this stage is honest reporting. Deliverables here typically include a project status or milestone summary describing where the work stands at the end of the block, along with whatever closing documentation your program requires, and often a reflection tied to doctoral competencies. Where a discussion accompanies it, treat it as final copy, since posts do not reopen once submitted in Canvas.
Accuracy in a status report matters more than most students expect. A committee reads these documents against what you wrote in week one, and the fastest way to damage credibility is a summary that describes preparation as implementation or that omits a milestone quietly. The stronger move, invariably, is to state what did not happen, say why in one factual sentence, and say what it does to the sequence ahead. A student who reports an unmet milestone with a revised plan attached reads as someone managing a project. A student whose report contains only completions reads as someone whose report cannot be relied on.
The placement boundary, stated plainly
At the close of the block the boundary holds exactly as it did at the start. Your 128 practicum hours, the hour log, activity and encounter records, mentor and preceptor evaluations, site agreements, final attestations and every verified signature are your own record. They are never drafted, reconstructed, estimated, back-filled or completed with help from anyone, and a closing summary is not an occasion to reconstruct hours from memory with assistance. Nobody may perform, document or reconstruct clinical activity on your behalf. What is teachable is the written layer: how to structure a milestone report so a committee can verify it, how to write about an unmet objective without either defensiveness or evasion, how to build a sustainment analysis, and how to write a reflection that analyzes rather than narrates. Any real resident, transfer or site document appearing in your writing must be fully de-identified.
The NR-705A Week 8 method, step by step
Six moves for closing a practicum block in writing.
-
Reduce the rubric rows to verbs and check what closing documentation is required
Programs differ in what a block close consists of, and some require a specific summary format alongside the course submission. Establish the full list before you start writing any of it.
-
List the milestones you set in week one and mark each honestly
Complete, partial or not started, with one factual sentence of explanation for anything short of complete. Marking against your own stated plan is what makes the report verifiable rather than impressionistic.
-
Report the state of each project artifact
Problem statement, evidence synthesis, framework mapping, process analysis, measurement plan, review documentation. Say what exists, in what draft state, and what remains. Artifacts are more checkable than activities.
-
Write the sustainment analysis around structural absorption
Ask what existing routine, form or report the change lives inside, who owns it after you, and what measurement continues without your involvement. A change with no host routine and no owner has no sustainment argument.
-
Name the two conditions most likely to end the change
Usually a departure, a competing initiative, a system change or a staffing shift. Say what each would do and what could be built now to blunt it. Specific threats read as analysis; a general note about the importance of buy-in does not.
-
Write the handoff to the next stage as a sequenced plan
What the next block begins with, in order, with the dependencies that must clear first. This is the paragraph a committee uses to judge whether you understand your own timeline.
A layout and word budget for a block close and sustainment section
Our frame for a closing status and sustainment submission, sized for roughly 1,400 to 1,700 words. It is our own outline rather than anything the university issues, and your chair's guidance and your week's rubric outrank it wherever they disagree.
| Section | What belongs in it | Word target |
|---|---|---|
| Position statement | Where the project stands at the close of the block, in two or three sentences, without inflation. | 110 to 150 |
| Milestones against plan | Each objective set at the start marked complete, partial or not started, with one factual sentence for each shortfall. | 260 to 320 |
| Artifact status | Each written product with its draft state and what remains to finish it. | 200 to 250 |
| Sustainment analysis | Host routine, post-project ownership, continuing measurement, and what makes the change structurally absorbable. | 300 to 360 |
| Threats to durability | The two conditions most likely to end the change, with what could be built now to blunt each. | 210 to 260 |
| Handoff and sequence | What the next stage starts with, in order, and the dependencies that must clear before each step. | 200 to 250 |
Evidence craft for closing documentation
Report status against your own stated plan, in its own terms. Quote the objective as you wrote it in week one, then mark it. A status report that describes progress in fresh language a committee cannot align to the original plan is not really a status report.
Give a delay a cause and a consequence, not an apology. An approval that took five weeks rather than two is a fact with a schedule effect. Write both, revise the sequence accordingly, and leave the tone flat. Doctoral readers respond to management, not to contrition.
Cite sustainment thinking rather than asserting it. Published work on sustainability and de-implementation exists and gives your analysis an external frame. Attributing a sustainability model, with its year, lifts the section above intuition about what tends to stick.
Keep reflection analytic and attached to evidence. Where a reflective component is required, connect each claim about your development to something concrete you produced or decided during the block. A reflection that could have been written before the term began demonstrates nothing at doctoral level.
Five mistakes that cost points in this week's territory
- Preparation described as implementation. Language implying a change is running when it is specified is the credibility error a committee is most likely to catch, since your earlier documents are on file.
- Milestones quietly dropped. An objective set in week one and absent in week eight reads worse than one reported as not started with a reason attached.
- Sustainment as a paragraph about buy-in. Durability comes from ownership, host routines and continuing measurement, not from enthusiasm.
- No named owner after the project. A change whose continuation depends on the student is a change with an end date built into it.
- Reflection as gratitude. Thanking the experience and promising to apply the learning appears in a large share of closing submissions and demonstrates nothing.
Before you submit
- Every week-one objective is marked and unmet ones carry a factual reason
- Each written artifact has a stated draft state
- The sustainment section names a host routine and an owner after the project
- Continuing measurement is specified without your involvement
- Two specific threats to durability are named with mitigations
- Nothing in the document implies more implementation than has occurred
Closing out NR-705A this week?
Send the rubric and your block documentation out of Canvas. A premium original draft comes back in 24 to 48 hours with milestones reported against plan, sustainment argued structurally, and a handoff a committee can follow. Revisions run until the grade lands, and your hours, logs, evaluations and signatures stay entirely yours.