NR-667 Week 5 typically converts the synthesis into consequences: one concrete change the evidence funds, planned to the level where a clinic could actually run it. That means owners with roles, a timeline, real costs, the barrier most likely to appear, and the number that will decide whether it worked. Your section may print this as NR 667 or NR667; 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.
Planning a change on paper does not require anyone's clinic to adopt it, and your practicum's actual operations, along with its hours and its paperwork, remain wholly in your program's lane. The written plan is the graded artifact, and it is the artifact a desk can help polish.
What NR-667 Week 5 asks for
Expect the territory to move through translation science at working scale: selecting the single change your synthesis supports most strongly, mapping the people whose behavior the change touches, sequencing it into steps with dates, pricing it in staff time and materials, anticipating resistance concretely rather than generically, and specifying measurement tight enough that success and failure are distinguishable afterward. The intellectual center is a chain: evidence to change to measure, with no link asserted that the previous link cannot hold.
Deliverable shapes at this point usually include the implementation section of the capstone document, a standalone change proposal, or a project plan with timeline and measures attached. If your section runs a discussion this week, it often asks which barrier would most threaten your project and how you would answer it, a question that rewards students who have imagined a specific Tuesday morning rather than an abstract rollout.
Your week's rubric will likely fund specificity: named roles rather than "staff," dollar and hour figures rather than "minimal cost," and a measure with a numerator, a denominator and a collection method rather than a hope.
The NR-667 Week 5 method, step by step
Six moves from a supported position to a runnable plan.
-
Choose the one change the evidence actually funds
Not the three changes you can imagine, the one your synthesis supports at its strongest point. Write it in a single sentence with the population and setting from your gap statement carried forward unchanged.
-
Cast the plan in roles
Who initiates, who performs, who checks, who is informed, each as a role title that exists at a real clinic. A plan whose actor is "the team" has no actor, and faculty read that absence as unbuilt thinking.
-
Sequence with dates a session could hold
Break the change into steps small enough to schedule: preparation, training touch, go-live, check-in, measurement pull. Attach each to a week, because a timeline without dates is a wish list in columns.
-
Cost it in hours and dollars, honestly
Staff minutes per patient or per shift, materials, any licensing, and the opportunity cost of the time. Small honest numbers build more credibility than round optimistic ones, and cost is where reviewers test whether the plan met reality.
-
Pick the barrier that will actually happen
Not a list of every conceivable obstacle: the one or two your setting would really produce, workflow interruption, a skeptical role, a competing priority, each with a countermove that costs something you have already budgeted.
-
Define the measure and the decision rule, then format
The numerator, the denominator, the collection method, the baseline, and the number at which the change is kept, adjusted or dropped. Then the mechanics: current APA, the timeline formatted to your section's template, headings in your rubric's wording.
An implementation plan, section by section
Targets assume roughly 1,250 words for a capstone implementation section. Rescale to your prompt, keeping the barrier and measurement blocks from being squeezed by the narrative ones.
| Section | What belongs there | Word target |
|---|---|---|
| The change, in one sentence | What will be done differently, for whom, where, carried forward from the synthesis | 60 to 90 |
| Owners by role | Each step's actor as a role title, with the initiating and checking roles distinguished | 160 to 200 |
| Timeline with dates | The sequenced steps mapped to weeks, including training and the measurement pulls | 200 to 250 |
| Resources and cost | Hours, materials and dollars, itemized, with the source of each estimate | 180 to 230 |
| Barriers and countermoves | The one or two likeliest obstacles, each with a budgeted, specific response | 220 to 270 |
| Measure and decision rule | Numerator, denominator, method, baseline, and the thresholds that decide keep, adjust or stop | 200 to 250 |
The decision rule is the section students most often omit and the one that most changes how the whole plan reads: a plan that can fail, visibly and by prearranged criteria, is a plan someone thought about.
Costing and measuring with sources attached
Cost figures need provenance like any other evidence. Time estimates can come from observed workflow described as observation, published time-and-motion data cited with year and setting, or vendor pricing named as such; what they cannot come from is thin air rounded to a friendly number. When an estimate is genuinely uncertain, give a range and say which end you budgeted.
Measurement definitions borrow the discipline of the appraisal weeks: an operational numerator and denominator, a stated collection window, and a named collection method someone in the plan actually owns. If a validated instrument exists for your outcome, name it and its validated population; if you are counting events from records, say who counts them and how often, and keep the count de-identified and aggregate.
Where implementation literature informs your approach, cite it at its real strength: much of it is descriptive or quasi-experimental, which supports "has been associated with adoption" rather than "will ensure success." The plan's credibility comes from the fit between its claims and its citations, exactly as the capstone's earlier sections did.
Five mistakes that cost points in an implementation week
- "Educate staff" standing where a plan should be. Education is one step, not a strategy, and a plan that ends there has not engaged behavior change at all.
- A costless change. Every change costs at least attention and minutes, and a budget of zero tells reviewers the workflow was never walked.
- Generic barriers. "Resistance to change" with no named role, moment or countermove is a stock phrase where the week's hardest thinking belongs.
- A measure without a collection method. Naming the metric but not who pulls it, from where, on what schedule, leaves the plan unmeasurable in practice.
- Success undefined. Without thresholds and a decision rule, no result can ever count against the change, which means the measurement section was ornamental.
Before you submit
- The change is one sentence and traces to the synthesis's strongest claim
- Every step has a role-titled owner
- The timeline carries dates a single session could hold
- Costs are itemized with the source of each estimate
- Each barrier has a specific, budgeted countermove
- The measure has numerator, denominator, method, baseline and decision rule
Plan section flat while boards prep eats the week?
Send the synthesis and the rubric. A costed, role-cast implementation plan with its decision rule written returns inside 24 to 48 hours, revised free until it lands.