Every change to a clinical workflow takes something from somewhere else, and the written work at this stage is the honest accounting of what. Balancing measures capture the cost: time, displaced tasks, staff load, patient experience, another step that quietly stopped happening. A project that reports only the measure it hoped to move has described half of what it did. Your section may print this as NR 705C or NR705C; 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-705C Week 6 asks for
A family practice adds ninety seconds to the rooming sequence and the reconciliation numbers rise nicely. Six weeks later the practice manager mentions that afternoon sessions are running fifteen minutes later than they were, and the lead medical assistant says the developmental screening handout - a different practice priority, nothing to do with your project - has stopped being given out on busy days because something had to go. Neither of those appears anywhere in an outcome measure. Both are effects of your project, and a doctoral account that omits them is not merely incomplete; it misrepresents the change.
Think in categories. Time and throughput effects show up in cycle time, session overrun and appointment lateness. Displacement effects show up as another task dropping. Workload effects concentrate on whichever role absorbed the new step, and in small practices that is usually one person. Patient and family experience effects appear in what people are asked to do in the waiting area or the exam room. Data burden effects are the ones students forget: staff spending time on recording that produces nothing for the visit itself.
A 256-hour term is long enough for these effects to surface and be examined, which is a real advantage. Effects on throughput and displacement do not appear in the first fortnight; they appear once the novelty has worn off and the practice has silently rebalanced. Being present in the building for that period, and having the measurement infrastructure already running, is what lets you write this section from evidence rather than from a conversation in a corridor.
Where the boundary sits. The practicum is yours in full. The 256 clinical hours, the log that records them, encounter and activity counts, evaluations by preceptors or site mentors, agreements and signatures are your own record and your own work, never drafted, reconstructed, back-filled or estimated with help from anyone, and no part of that is on offer here. Written support covers the written layer only: structuring a balancing-measure analysis, writing about unintended effects precisely, organizing reasoning so it holds. Keep project data aggregate in your writing, handled under your organization's rules, with no service dates and no detail that could identify a family or a colleague. The clinical hours cannot be shortcut and clearer written reasoning about work you genuinely did is the whole offer.
The NR-705C Week 6 method, step by step
Six moves for writing an honest account of what the change cost.
-
List every plausible cost category before you look at any data
Time, displacement, workload concentration, family experience, data burden. Writing the list first stops the section from becoming a defence of whatever the numbers happen to show.
-
Prefer a measure the site already collects
Cycle time, sessions ending late, a completion rate for a different step in the same sequence. A balancing measure that costs the practice nothing to produce is one that survives, and one you can extend backwards to a baseline.
-
Ask the role that absorbed the step, systematically
A short structured question set to the staff running the change, asked the same way at two points, beats an impression gathered in passing. Follow your program's requirements for anything collected from staff.
-
Look specifically for displacement
Name the tasks that share the same minute of the visit and check whether any of them moved or stopped. Displacement is the effect nobody volunteers, because the person who dropped a task rarely frames it as a consequence of your project.
-
Report movement in the balancing measure without minimizing it
If sessions are running later, say by how much, at which site, over which period. Then reason about whether the change is attributable, tolerable and reversible. Explaining away a real cost is the single most damaging move available in this section.
-
State what would make you stop or modify
A threshold, written in advance where possible: what degree of harm to the balancing measure would require the protocol to change. A project with a stopping rule reads as governed; one without reads as advocacy.
A layout and word budget for a balancing measure analysis
Our frame for the unintended-effects section, sized for roughly 1,500 to 1,900 words plus tables. It is our own outline rather than anything the university issues, and your chair's direction and your week's rubric outrank it wherever they disagree.
| Section | What belongs in it | Word target |
|---|---|---|
| Cost categories considered | The full list examined, including categories where nothing was found, with one line on how each was checked. | 200 to 250 |
| Balancing measures and their rules | Each measure with numerator, denominator, source and baseline, in the same format as your outcome measures. | Table plus 140 |
| Time and throughput findings | What the series shows, by site and period, with denominators and any confounding schedule events named. | 280 to 340 |
| Displacement findings | Tasks sharing the same workflow minute, whether any moved or stopped, and how that was established. | 250 to 300 |
| Staff workload and experience | What the role absorbing the step reported, gathered systematically, written in system terms without identifying anyone. | 250 to 300 |
| Attribution reasoning | Whether observed movement is plausibly caused by the change, with alternative explanations considered honestly. | 230 to 290 |
| Response and thresholds | What you changed or would change, and the threshold at which the project would be modified or paused. | 190 to 240 |
Evidence craft for unintended effects
Give balancing measures the same rigour as outcome measures. Numerator, denominator, source, baseline, period. A balancing measure written loosely is one that can be dismissed later, and it will be dismissed precisely when it is telling you something inconvenient.
Report negative findings in the same tone as positive ones. Afternoon sessions at the busier location ended a mean of eleven minutes later across the operating period than across the comparable baseline period. No hedging adverbs, no softening clause. The flat tone is what makes the section credible.
Separate attribution from observation. That the measure moved is observation. That your change caused it is an argument requiring you to consider staffing changes, seasonal volume, a new provider and anything else that shifted in the same window. Write both, in that order.
Cite the literature on the effect where it exists. Task displacement under time pressure and workload concentration on a single role are well described phenomena, and one citation frames your local finding as an instance of something known rather than as an anecdote.
Never make a colleague identifiable through a cost finding. In a small practice, describing the workload of the person who absorbed the step can name them by implication. Use the role, aggregate where possible, and be careful with any quoted phrasing.
Five mistakes that cost points in this week's territory
- A balancing measure chosen because it was unlikely to move. Selecting a measure your change could not plausibly affect satisfies the form and defeats the purpose, and experienced readers spot it immediately.
- Explaining away an unfavourable result. A cost minimized in the writing is a cost the site will experience anyway, and the credibility loss is worse than the finding.
- Ignoring displacement. The most common real harm from a workflow addition is that something else stopped, and it will never appear unless you go looking for it.
- Anecdotal staff feedback. A remark in a corridor is not evidence. Ask the same question the same way at two points and report it as what it is.
- No threshold for action. Without a stated point at which the project would change, the balancing measure is decoration rather than governance.
Before you submit
- Cost categories are listed, including those where nothing was found
- Each balancing measure has a full definition and a baseline
- Displacement was actively checked, not assumed absent
- Unfavourable findings are reported in plain, unhedged language
- Attribution reasoning considers at least two alternative explanations
- Staff feedback was gathered systematically, not anecdotally
- A threshold for modifying or pausing the project is stated
- No colleague is identifiable through a workload description
Writing the NR-705C balancing analysis?
Send the rubric, your measure set and your own aggregate series out of Canvas. A premium original draft comes back in 24 to 48 hours with cost categories covered systematically and attribution reasoning written honestly, revised free until it lands. Practicum hours, logs and evaluations remain entirely yours.