The sustainability plan argues that the change will persist. The handoff document is what actually makes that possible: a short, practical package written for the person who inherits the work, not for a committee. In our teaching order this stage of the 192-hour block produces it. What the change is, how it runs on an ordinary shift, where every artifact lives, what breaks and what to do about it, and who to contact by role. Written well, it is the most re-read page your project ever produces. Your section may print this as NR 709B or NR709B; 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-709B Week 7 asks for
Eight months after a neuroscience intensive care unit adopts a structured neurological reassessment prompt, the charge nurse who inherits it is looking for the audit tool and cannot find it. It exists, on a drive belonging to a graduate who has moved to another organization, in a folder named with a version number. That is how good projects die, and it is entirely preventable by two pages written in week seven rather than in the last hour of the session.
The audience is the difference here. Every other document in this block is written for faculty and for a scholarly reader. This one is written for a working nurse leader with fifteen minutes, who needs to operate something they did not design. That changes the prose completely: short sections, concrete nouns, no literature, no methodology, no defence of the design. If a sentence would only make sense to somebody who read your discussion, it does not belong in the handoff.
The boundary, which applies to this document as much as to any other. Practicum hours, the hour log, encounter counts, preceptor or mentor evaluations, site paperwork and any signature attached to them are your own record of your own work and are never drafted, reconstructed or estimated with help of any kind. Only the written layer is supportable: how a handoff package is organized, how an operating instruction is phrased, how a decision record is summarized. Anything drawn from real cases or site data appears de-identified, at the moment it is written.
There is also a scholarly reason to write it, beyond courtesy to a successor. Implementation literature treats the transfer of ownership as a distinct phase with its own failure modes, and a document that handles that phase deliberately is evidence of systems thinking rather than project management. Your final scholarly document can point to the handoff package as the mechanism by which the change stopped depending on a single person, which is a stronger claim than any assurance you could write in a paragraph. It also gives your sustainability plan something concrete to rest on: an owner, a structure and a review date are promises until the artifacts, instructions and reasoning behind them exist somewhere the owner can reach.
Expect this to appear either as an appendix to your final scholarly document or as a separate deliverable, depending on your section. Either way it usually needs a real conversation with the receiving owner, which is why it lands here with a week still available to correct whatever that conversation reveals.
The NR-709B Week 7 method, step by step
Six moves for writing a package somebody can actually operate.
-
Open with what the change is, in four sentences
What happens, to which patients, at what point in the pathway, and why it exists. A reader who stops after this paragraph should still be able to describe the change correctly to somebody else.
-
Write the operating instructions as a shift would meet them
Who does what, when, and where it is documented. Use the language of the unit rather than the language of your manuscript, and name the screen or form where the action actually occurs.
-
Inventory every artifact and its permanent location
Protocol, education materials, audit tool, data queries, slide sets, contact list. Each with where it lives now, in a location the organization controls rather than one you control.
-
Record the decisions that are not self-evident
Why a population was excluded, why a threshold is where it is, why one workflow was rejected. Successors relitigate exactly the decisions nobody wrote down, and usually badly.
-
List the known failure points and their fixes
The three things that went wrong during implementation, what caused each, and what resolved it. This is the section that saves the next person a month and it comes straight from your working record.
-
Give roles, not names, and a first review date
Contacts by role survive turnover; contacts by name do not. Close with the next scheduled review and what the reviewer should look at.
A layout and word budget for the handoff package
Our frame for a handoff document, sized for roughly 800 to 1,000 words so it stays readable. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever the two disagree.
| Part | What the receiving owner needs from it | Word target |
|---|---|---|
| The change in brief | What happens, for whom, at what point, and the reason, with no methodology. | 90 to 120 |
| How it runs | Roles, timing and documentation location, written as a shift encounters them. | 180 to 220 |
| Artifact register | Every document and query, its permanent location, and who controls access. | 120 to 160 |
| Decision record | The design choices that would otherwise be reopened, each with its one-line reason. | 150 to 190 |
| Failure points | What broke, why, and what fixed it, drawn from your contemporaneous account. | 150 to 190 |
| Contacts and next review | Roles rather than names, the review date, and the two figures the reviewer should pull. | 90 to 120 |
Evidence craft for operational writing at doctoral level
Write for the reader in front of you. Scholarly register is correct in your manuscript and wrong here. Short sentences, active verbs, second person where it helps, and no citation unless the reader needs to find a source to do their job. Being able to switch register deliberately is itself a doctoral competency.
Keep every figure consistent with the scholarly document. If the handoff quotes a baseline, it must be the same baseline, with the same denominator and window, as the one in your discussion. Numbers drifting between documents is the single most damaging inconsistency an examiner can find, and it is entirely avoidable if all documents draw from one frozen figures file.
Store artifacts where the organization can reach them. A handoff pointing at personal storage or an expiring student account has not transferred anything. Name a shared organizational location, and if placing files there requires permission, write who granted it and when.
De-identify the whole package. Audit tools and worked examples often carry sample entries that came from real charts. Replace them with constructed illustrations before the document is shared, and say in the package that the examples are illustrative.
Date the package and give it a version. A handoff document without a date becomes ambiguous the first time anything about the process changes, and a successor cannot tell whether they are reading current instructions or a historical record. One line at the top carrying the date, a version number and the role that maintains it costs nothing and preserves the document's usefulness for years.
Do not sign anything on anyone's behalf. Acceptance of the handoff is the receiving owner's act, recorded by them. Your document states what was transferred and when it was discussed, and it stops there.
Five mistakes that cost points in this week's territory
- A handoff written in manuscript voice. Methodology and citations tell a working nurse leader nothing they can act on.
- Files left in personal storage. A register pointing at a drive you own is a register of things about to disappear.
- Contacts by name. Names change within a year on most acute units; roles survive.
- No decision record. Undocumented reasoning gets reversed by the first person who finds the choice inconvenient.
- Numbers that disagree with the main document. Two versions of your own baseline is a credibility problem, not a typographical one.
Before you submit
- The change is described completely in the first paragraph without methodology
- Operating instructions name roles, timing and the exact documentation location
- Every artifact has a permanent organizational location and an access owner
- Design decisions and known failure points are recorded with reasons
- All figures match the scholarly document exactly
- No hour, log, evaluation or signature is drafted, and nothing is signed for anyone else
Writing the NR-709B handoff package?
Send the rubric and your project materials out of Canvas. A premium original draft comes back in 24 to 48 hours written in operating register, with the artifact register and decision record built out, and revisions run until the grade lands.