Past the midpoint, a capstone stops being about whether the idea is right and starts being about whether it would survive contact with a real unit. The implementation section is where you write the sequence: who approves, who trains, who resists, what happens in week one, what happens when the champion is on nights, and what specifically would cause the whole thing to quietly stop. It is scored on plausibility, and plausibility comes from naming roles, sequences and obstacles rather than intentions. Your section may print this as NR 575 or NR575; 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. Clinical hours, logs, site documents and preceptor evaluations remain your own record and are never drafted, reconstructed or estimated with help.
What an implementation section has to make believable
Go looking for the tools a unit adopted two years ago and the audit is instructive. Some are laminated at every station and genuinely in use. Some exist as a form in a binder that nobody has opened since the education day. The difference is almost never the quality of the tool. It is whether somebody owned the rollout, whether the workflow made using it easier than not using it, and whether anyone checked in the second month. Your implementation section is an argument that your product would land in the first category, and the evidence for that argument is structural detail.
Four things have to be visible. A sequence with a beginning, phases and a point at which the change is considered adopted rather than piloted. Named roles at each phase: who authorizes, who trains, who reinforces at the bedside, who reports upward. A realistic account of resistance, meaning the specific reasons a competent, busy clinician would decline to use this rather than a general note about change fatigue. And a set of resources, including the least glamorous ones, which are usually time and printing and access to an education slot that is already fully booked.
A named change framework earns its place here if you actually use it. Frameworks for planned change and for translating evidence into practice give you a vocabulary a grader recognizes and a structure that prevents the section from becoming a list of good intentions. Using one means walking your product through its stages, not naming it in the opening paragraph and then writing whatever you were going to write anyway. Graders in capstone courses spot the ornamental version immediately.
The boundary is worth restating because this is the stage where students drift across it. Writing a plan is academic work. Approaching managers, seeking site approvals, arranging education time or introducing anything into a live workflow is site business governed by your program and the organization, and it is yours to conduct. Nobody helping with your writing contacts a site, a preceptor or faculty, completes any placement document, or logs an hour. Where real conversations informed your plan, describe the substance without identifying the people or the facility.
Deliverables at this stage are usually a written implementation section for the capstone, occasionally with a stakeholder analysis or a timeline appendix. Any accompanying post should be written as final copy; posts do not reopen after submission in Canvas.
The NR-575 Week 5 method, step by step
Six moves that make a rollout plan read as executable.
-
Map the decision path before the training plan
Who has to say yes, in what order, and what each of them needs to see in order to say it. A unit council, a nursing director, an informatics group and a practice committee all want different evidence, and naming that is the first sign of a plan written by somebody who has watched one happen.
-
Anchor the sequence in a named change framework
Choose one framework, cite it, and walk your product through its stages explicitly. The value is not the citation; it is that the framework forces you to plan the parts everybody skips, usually reinforcement and sustainment.
-
Write the first shift in concrete detail
What is physically present on the unit on day one, who introduces it, at which huddle, what the handover script says, and where a confused clinician goes with a question at three in the morning. This paragraph carries more marks per word than any other in the section.
-
Name resistance with reasons, not attitudes
Not staff may be resistant to change. Instead: the tool adds a step to an assessment that is already the busiest twenty minutes of a shift, and the people most affected are the ones with the least discretion over their time. Then say what you would do about that specific objection.
-
Budget the resources including the invisible ones
Education hours and who covers the floor during them, printing or build time, informatics work, the champion's time, and the follow-up rounds in months two and three. Plans that cost nothing are plans that were never costed.
-
Write the sustainment clause
What keeps this alive when the person who cared about it rotates off. Ownership assigned to a role rather than a person, a place in an existing audit cycle, and a stated point at which continuation is reviewed.
A layout and word budget for the implementation section
Our frame for a capstone implementation section, sized for roughly 1,100 to 1,400 words. 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 |
|---|---|---|
| Framework and why this one | The change model named and dated, with one sentence on why it fits a unit-level clinical change rather than an organizational one. | 130 to 170 |
| Approval path | The groups and roles whose agreement is required, in sequence, and what each needs to see. | 170 to 210 |
| Phased rollout | Preparation, launch, reinforcement and adoption, each with a duration and a stated exit condition. | 250 to 320 |
| Day one in detail | What is present, who says what at which huddle, and where questions go on off-shifts. | 160 to 200 |
| Barriers and responses | Three specific objections a competent clinician would raise, each with a concrete response rather than reassurance. | 220 to 280 |
| Resources and sustainment | Time, materials, build work, champion capacity, and who owns the tool by role after the project ends. | 180 to 230 |
Evidence craft for an implementation argument
Cite implementation research, not only clinical research. There is a literature on why evidence-based changes fail in practice settings, on audit and feedback, on champions and on the decay of adoption over time. A section leaning on it is arguing from evidence about behaviour, which is what this part of the capstone is actually about.
Date and attribute the change framework in the sentence. Name the model, its originators and the edition or year you are working from, then use its own stage vocabulary consistently. Switching between two frameworks' terminology halfway through is a common and easily fixed error that reads as borrowed structure.
Describe your setting concretely without identifying it. Unit type, approximate bed count as a range, staffing model, shift pattern and documentation system class all matter to the plan and none of them require naming a facility. This is the balance graders reward: specific enough to be plausible, anonymous enough to be appropriate.
Attach a number to each resource claim. Two education sessions of twenty minutes each across three weeks, covering roughly forty staff, is a costed plan. Staff education will be provided is not. The precision is what converts a proposal into something a reader can imagine approving.
Keep any real stakeholder conversation de-identified and labelled. If a manager or preceptor told you what would actually be required, that insight is valuable and belongs in the reasoning, described without role titles specific enough to identify a person, without the site, and without being dressed up as citable evidence.
Five mistakes that cost points at this stage
- A timeline with no exit conditions. Weeks one to two, education. Weeks three to six, implementation. Nothing in that says how you would know a phase had succeeded.
- Resistance treated as a personality problem. Naming staff attitudes instead of workflow costs is the tell of a plan written from outside the unit.
- An ornamental framework. Cited in the first paragraph, absent from the structure, contradicted by the phases that follow.
- Nobody owns anything. Passive constructions throughout, so no role is accountable for approval, training, reinforcement or review.
- No sustainment. A plan that ends at go-live is a plan for a pilot, and the row asking about sustainability has nothing to score.
Before you submit
- One change framework is named, dated and used as the section's actual structure
- Every phase has a duration and a condition for moving on
- Each action is attached to a role rather than to no one
- Three specific barriers appear with concrete responses
- Resources carry numbers, including time and who covers it
- Ownership after the project ends is assigned to a role
- The setting is described concretely but no facility or person is identifiable
Writing the NR-575 implementation section?
Send the rubric and your product draft out of Canvas. A premium original draft comes back in 24 to 48 hours with a phased plan, named roles, costed resources and barriers written as real objections, and revisions run until the grade lands.