Stage five of NR-669 answers the question every stakeholder audience eventually asks: what happens when you leave. The written work is a sustainability plan naming who owns the process afterwards, what will be monitored and how often, what has been built into structure rather than left to attention, and what would trigger a response if performance slipped. A project without a named owner ends when the student does. Your section may print this as NR 669 or NR669; 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-669 Week 5 asks for
A medication reconciliation step for children on asthma controllers survived four months because one nurse cared about it and checked the list every clinic morning. That is a fragile achievement. If the same check has been added to the rooming template in the record, appears on a monthly report someone already reviews, and belongs to a named role rather than a named person, it survives a resignation. The difference between those two states is what a sustainability plan is written to establish, and it is judged on structural detail rather than on enthusiasm.
Sustainability writing has four components. Ownership: which role, not which individual, holds the process after you leave, and who they report to about it. Monitoring: what measure continues, from what source, at what interval, appearing on whose desk. Structure: what has been embedded in templates, order sets, schedules, orientation material or job descriptions so the change does not depend on memory. And response: what threshold would trigger action, and what that action would be.
The honest version of this document also says what is not sustainable. If the change currently depends on a manual daily check that nobody has agreed to continue, saying so is not a failure of the project; it is the most useful sentence in the plan, because it tells the organization exactly where to invest. Where a section runs a discussion at this stage, it usually asks what would decay first without you. Post it as final copy, since Canvas responses do not reopen.
Where the boundary sits in a handoff stage. The 168 clinical hours, the immersion, every conversation at the organization and each relationship there belong to you alone and cannot be delegated or reconstructed. Hour logs, encounter counts, census entries, site paperwork, signatures and any evaluation completed about you are your own record, never drafted, reconstructed or estimated with help. The written layer is what a manual can support: how to write an ownership statement, how to design a monitoring plan on paper, how to describe structural embedding so a reader can judge it. Any observation from the site enters your writing de-identified and in role terms.
The NR-669 Week 5 method, step by step
Six moves for a handoff that outlives the project.
-
Assign ownership to a role, then confirm it with that role
Write the position, not the person, because people move. Then check that whoever holds it has actually agreed, and say in the plan whether the agreement is confirmed or proposed. An unconfirmed owner written as settled is the most common fiction in these documents.
-
Reduce the monitoring measure to something maintainable
The measure that survives is the one that costs almost nothing. If your project measure required hand review, propose the simplest automated proxy that would still detect decay, and say plainly what the proxy would miss.
-
Set an interval and a destination for the report
Monthly, quarterly, and onto which existing meeting agenda. Data that arrives somewhere nobody reviews is not monitoring. Attaching it to a meeting that already happens is far more durable than proposing a new one.
-
List what has been embedded in structure
Template fields, prompts, standing orders, schedule changes, orientation content, written procedure. Each item with its current status: built, requested, or not started. This list is the honest measure of how much of the change no longer needs anybody to remember it.
-
Define the threshold and the response
State the level at which performance would count as decay, and what happens then, by whom. If documented completion falls below a stated proportion for two consecutive months, the owner raises it at a named meeting. A threshold with no response attached is a number nobody acts on.
-
Write down what is still fragile
Name the parts that depend on a single person, an unbuilt record field or goodwill. This paragraph earns more credit than any optimistic summary, and it is what a director in the room actually wants from you.
A layout and word budget for a sustainability plan
Our frame for a handoff document, sized for roughly 1,200 to 1,500 words. It is our own outline rather than anything the university issues, and your scoring guide outranks it wherever they disagree.
| Section | What belongs in it | Word target |
|---|---|---|
| Current state at handoff | What is running now, at what level of performance, and how much of it depends on the project itself. | 180 to 220 |
| Ownership | The role that holds the process, who it reports to, and whether the assignment is confirmed or proposed. | 160 to 200 |
| Ongoing measure | The maintainable measure, its source, its interval, who produces it and what it would miss. | 230 to 280 |
| Structural embedding | Templates, prompts, procedures and orientation content, each with a built, requested or not started status. | 250 to 300 |
| Threshold and response | The performance level that counts as decay, the response, the role responsible and the forum where it is raised. | 170 to 210 |
| Remaining fragility | Everything still dependent on one person, one unbuilt field or continued goodwill, stated plainly. | 180 to 220 |
Evidence craft for sustainability writing
Ground the plan in a published sustainability framework. Models describing what makes improvement stick exist and are citable, and using one gives your plan categories a reviewer recognizes rather than a list you invented. Name it with its year at first use and apply its terms consistently.
Report the decay you have already observed. If performance dipped during a week when the trained staff member was away, that is direct evidence about dependence, and it belongs in this document with its counts. Local evidence about fragility is more persuasive than any general claim about sustainability.
Write commitments only where they exist. There is a real difference between the practice manager has agreed to review the monthly report and the plan proposes that the practice manager review the monthly report. Blurring the two produces a document that will embarrass you in the room when someone says they never agreed to that.
Cost the ongoing work in minutes. A monitoring step that takes ten minutes a month gets done; one that takes two hours does not, whatever anyone agreed. Estimating the time honestly, and saying who absorbs it, is the practical detail that makes a sustainability plan credible to operational readers.
Keep every reference to people role-based. Name positions rather than individuals throughout, both because staff change and because this document may circulate at the organization. Role-based writing is also what makes the plan portable to another site.
Five mistakes that cost points in this week's territory
- An owner who has not agreed. Assigning a role in writing without confirmation produces a plan that dissolves the moment it is read aloud.
- Monitoring that costs more than the change. A continuing measure requiring manual chart review will be abandoned within two months regardless of intent.
- No threshold. A plan to keep watching, without a level that triggers action, means nothing will happen when performance slips.
- Structure claimed but not built. Listing template changes as complete when they are still requested is the kind of error someone in the room can check on their phone.
- Fragility unmentioned. A plan that reads as fully secure is not believable in any real clinic, and its optimism costs credibility everywhere else.
Before you submit
- Ownership is assigned to a role and marked confirmed or proposed
- The ongoing measure is maintainable and its blind spots are stated
- The monitoring report has an interval and a named existing forum
- Every structural item carries a built, requested or not started status
- A decay threshold is stated with the response and the responsible role
- Remaining fragility is named rather than smoothed over
Writing the NR-669 handoff?
Send the scoring guide and your project status out of Canvas. A premium original draft comes back in 24 to 48 hours with ownership written to roles, a monitoring plan sized to what anyone will actually maintain, and fragility named honestly, and revisions run until the grade lands. Your hours, your site and your logs stay entirely yours.