Once a project is live, the written work shifts from planning to observation, and the observation that matters most is fidelity: whether the change is actually being delivered as specified, where it is not, and why. The early implementation stage of a capstone typically asks for a structured process account rather than a story about the launch. Written well, it lets you interpret your results later; written loosely, it leaves every disappointing number with two explanations. Your section may print this as NR 652 or NR652; 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-652 Week 2 asks for
In a memory care neighborhood where a new pre-transfer checklist went live on a Monday, the first audit shows it completed on nine of eleven weekday transfers and on none of the four that happened over a weekend. That is not a failure of the checklist and it is not a failure of the weekend staff. It is a design fact: the role assigned to complete it does not work weekends, and nobody noticed because the workflow was written by people who were in the building on Tuesdays. Fidelity monitoring exists to surface exactly that kind of fact within days rather than at the end, and the written stage that reports it is where a capstone either becomes analytic or becomes anecdotal.
The core distinction to hold is between adherence and adaptation. Adherence is whether the specified components happened. Adaptation is a deliberate local modification, which may be entirely appropriate and must be recorded as a modification rather than absorbed silently. Drift is the third category and the dangerous one: components quietly falling away while everyone believes the intervention is running. A process account that separates these three gives your later results a meaning that no amount of statistical care can substitute for.
The stage also asks you to write about people at work without writing about people. Staff will have opinions about the change, some of them sharp, and those opinions are legitimate implementation data. The craft is to report them as patterns tied to roles and shifts rather than as complaints attributed to individuals, and to analyze what each one reveals about the design. A comment that the step takes too long at 7 a.m. is a workflow finding. Written as evening staff are not cooperating, the same information becomes unusable and unprofessional.
Expect this stage's deliverable to combine a short quantitative fidelity summary with a narrative account of implementation to date and the adjustments made. If your section runs a discussion alongside, post final copy and keep individuals out of it; contributions do not reopen after submission in Canvas, and in a live project your posted words describe a workplace you will still be in next month.
Boundary setting: what a process account may and may not contain
The line in this stage is unusually easy to draw and unusually easy to blur under deadline. Your practicum hours, hour logs, activity or encounter documentation, site attendance records and every preceptor, mentor, sponsor or faculty evaluation are your own record. They are never drafted, reconstructed or estimated by anyone else. A process account is a scholarly document about the project; it is not the practicum record and it can never substitute for it.
Equally, a process account reports what happened. It does not manufacture what happened. Audit counts must come from real audits you conducted or that were conducted at your site under your plan, and a count you did not actually collect is fabricated data no matter how plausible it looks. If an audit was missed, say it was missed and say why. Missing an audit is an ordinary implementation event with a legitimate paragraph attached; inventing one is misconduct.
Everything you write stays de-identified. Fidelity work sits close to individual staff performance, which makes it doubly sensitive: no resident, patient or family member should be identifiable, and no employee should be identifiable as the person who did not complete a step. Report by role, shift and count, suppress or aggregate any cell that would point at one person, and never carry identifiable audit material out of site systems.
The NR-652 Week 2 method, step by step
Six moves for writing an implementation account that earns its place in the final report.
-
Audit against the component list, not against an impression
Take the components you specified in the proposal and check each one separately. Was it triggered, was it completed, did the artifact exist, did it reach the receiver. Component-level auditing is what lets you say later that two parts of a three-part intervention were delivered.
-
Report fidelity as counts with denominators and cuts
Completed on a stated number of a stated number of eligible events, then broken by the dimension most likely to matter: shift, day of week, unit, role. The cut is where the finding lives. An overall percentage almost always hides the pattern that tells you what to fix.
-
Classify every deviation as adaptation or drift
For each departure from the plan, say whether it was a decision someone made for a reason or an erosion nobody chose. Record adaptations with who authorized them and why, and treat drift as a barrier requiring a response rather than as a fact about staff attitude.
-
Diagnose each barrier at the level of design
Ask what about the workflow, the timing, the location of materials, the role assignment or the record system made the miss likely. Barriers stated as design problems generate fixes. Barriers stated as motivation problems generate another in-service that will not work.
-
Write each adjustment as a decision with a date and an owner
What was changed, on what date, by whose authority, and what you expect it to do to the next audit. A capstone whose adjustments are recorded this way produces a results section that can explain its own trajectory rather than presenting one flat number.
-
Close the loop on the previous adjustment before making a new one
Check whether the last change moved the fidelity count before layering another on top. Three simultaneous adjustments make the eventual result uninterpretable, and the discipline of one change at a time is itself a scored piece of improvement reasoning.
A layout and word budget for a fidelity and process report
Our frame for an early implementation report inside a capstone practicum, sized for roughly 1,200 to 1,500 words plus the audit table. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever they disagree.
| Section | What belongs in it | Word target |
|---|---|---|
| Implementation status | Go-live date, what is running, on which units and shifts, as of a stated date. | 130 to 170 |
| Fidelity method | What was audited, by whom, how often, against which component definitions, and the sampling rule. | 160 to 200 |
| Fidelity results | Counts and denominators by component, cut by shift, day or unit, with the pattern named. | 250 to 320 |
| Adaptations | Deliberate local modifications, each with its reason and the person who authorized it. | 150 to 200 |
| Barriers and diagnosis | Each barrier stated as a design problem, with the mechanism that makes the miss likely. | 220 to 280 |
| Adjustments made | Change, date, owner, and the expected effect on the next audit. | 170 to 220 |
| Implications for measurement | What the current fidelity level means for how the outcome data can be interpreted. | 120 to 160 |
Evidence craft for implementation reporting
Report the denominator before the percentage. Nine of eleven weekday transfers tells a reader what they need. Eighty-two percent, in a project where the weekly volume is single digits, invites a conclusion the numbers cannot carry.
Name the audit method precisely. Whether you reviewed every eligible event or a sample, who abstracted, whether the abstractor knew the project's purpose, and how disagreements were resolved. Fidelity data collected by the project lead alone is usable and should be labeled as such.
Anchor the barrier language in implementation literature. Concepts such as competing demands, workflow fit, relative advantage and the role of local champions are published constructs, and using them with attribution is what makes your account scholarship rather than a status update.
Separate what staff said from what you observed. Both are evidence, and they frequently disagree. A step reported as quick and observed as slow is a finding worth a paragraph, and blending the two into one confident sentence throws away the most interesting thing you learned this week.
Timestamp everything and keep the tense straight. An implementation account is a record of a moving object. Every count carries the period it covers, every adjustment carries its date, and completed actions stay in the past tense while planned ones stay clearly in the future.
Five mistakes that cost points in this week's territory
- A launch narrative instead of a fidelity report. A chronological account of the week is not an assessment of whether the intervention was delivered.
- One overall fidelity number. Without a cut by shift, unit or component, the number cannot tell you or the reader what to fix.
- Deviations described as attitude. Staff resistance as an explanation ends the analysis; a design diagnosis continues it.
- Unlogged adaptations. A modification absorbed silently means your final report describes an intervention that did not run.
- Several simultaneous changes. Three adjustments in one week make the next audit uninterpretable and waste the data you already collected.
Before you submit
- Fidelity is reported component by component, not as a single impression
- Every count carries its denominator and its observation period
- Results are cut by at least one dimension likely to explain variation
- Each deviation is classified as adaptation or drift, with authorization recorded for adaptations
- Barriers are stated as design problems with a mechanism attached
- Each adjustment carries a date, an owner and an expected effect
- No individual staff member, resident or family member is identifiable
Writing the implementation report this week?
Send the rubric out of Canvas with your audit counts and your notes from the unit. A premium original draft comes back in 24 to 48 hours, with fidelity reported component by component and barriers diagnosed as design rather than attitude, and revisions run until the grade lands. Your hours, logs and evaluations remain your own record.