The seventh stage of NR-702C is the measurement plan, and it is graded as a design rather than as a list. A complete plan carries an outcome measure tied to the aim, one or two process measures that show whether the intervention is actually being delivered, and at least one balancing measure that watches for the harm a successful change can cause somewhere else. Each measure needs an operational definition, a source, a collection method, a frequency, an owner and an analysis approach. At 256 hours the term can support building and testing the collection route rather than merely describing it. Practicum hours, hour logs, site documentation and mentor evaluations are your own record and are never drafted, reconstructed or estimated with help. Your section may print this as NR 702C or NR702C; 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-702C Week 7 asks for
A surgical step-down unit reduces indwelling catheter days by adding a daily necessity check to the multidisciplinary round. Catheter days fall. Six weeks later, the unit's incontinence-associated skin injuries have risen and nobody connected the two, because the project measured only what it was trying to improve. That is the argument for balancing measures in one paragraph, and it is the part of a measurement plan students skip most often.
The three-measure structure is doctoral practice. The outcome measure answers whether the thing you promised in the aim changed. The process measures answer whether the intervention was delivered at all, which is the first question to ask when an outcome does not move. The balancing measure answers whether you improved one thing by degrading another. A plan missing the middle category cannot distinguish an ineffective intervention from an undelivered one, and that distinction is the whole value of the evaluation.
Definitions carry the weight. For each measure: what counts in the numerator, what population forms the denominator, which patients are excluded, what event starts and stops any clock, which system or form the data comes from, how often it is collected, who collects it, and how it will be displayed and interpreted. Vague definitions produce numbers nobody can defend, and a committee will test one definition to see whether the rest hold.
Analysis in a quality improvement project is not a trial analysis. Run charts and control charts, with rules for distinguishing signal from ordinary variation, are the standard tools because they show behavior over time rather than a single before-and-after comparison. A pre and post difference at one site cannot rule out everything else that changed in the same period, and writing as though it can is the most common overreach in this section.
What this manual does not touch
Practicum hours, the hour log, encounter records, site forms, signatures and any evaluation completed about you are yours alone, and no part of that layer is drafted, reconstructed or estimated with assistance. What a manual teaches is the written design: definitions, collection routes, analysis approach and the honest limits paragraph that closes the section.
Measurement writing lives at aggregate level by nature, and that is also what keeps it compliant. Report counts, rates, denominators and periods. Never carry patient identifiers, dates of service or any detail that could reconstruct an individual case into a draft, and say in the plan that the data handled is de-identified and held inside your organization's approved systems.
The NR-702C Week 7 method, step by step
Six moves for a measurement plan a committee can approve.
-
Start from the aim and derive the outcome measure directly
If the aim and the outcome measure are not the same quantity in the same units, one of them is wrong. Check the wording literally rather than approximately.
-
Add process measures at the point of delivery
Was the check performed, was the prompt completed, was the step taken. Process measures are usually easier to collect and faster to move, and they are what tell you whether an unchanged outcome means the intervention failed or never happened.
-
Choose the balancing measure by asking what could get worse
Time added to a workflow, a delay elsewhere in the pathway, a burden shifted to another role, or a clinical risk created by removing something. Name one that is plausible and collectable rather than one that is easy.
-
Write a full definition for every measure in the same format
Numerator, denominator, inclusions, exclusions, clock, source, frequency, owner. Consistent formatting is not cosmetic; it is what lets a reviewer check six measures without losing track.
-
Specify the collection route and test it once
Which report, which query, which manual audit, and who runs it when you are not there. A route nobody can execute without you is a route that stops when the project does, and sustainability is a scored idea in doctoral work.
-
State the analysis and the interpretation rules before you have data
Which chart, how many baseline points, what pattern you would treat as a genuine shift rather than noise. Deciding the rules in advance is what makes the eventual conclusion credible.
A layout and word budget for a measurement and evaluation plan
Our frame for this section of a first-stage plan, sized for roughly 1,700 to 2,100 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 |
|---|---|---|
| Measurement logic | Why these measures follow from the aim and the intervention's mechanism, written as a chain rather than as a list. | 200 to 250 |
| Outcome measure | Full definition, source, frequency, owner, and how it maps word for word onto the aim. | 230 to 280 |
| Process measures | One or two, defined at the point of delivery, with the reason each is the right proxy for fidelity. | 260 to 320 |
| Balancing measure | The plausible harm, its definition, and the threshold at which you would pause or modify the intervention. | 220 to 270 |
| Collection and data handling | Route, tool, frequency, responsible role, storage, de-identification, and what happens when you are unavailable. | 240 to 290 |
| Analysis plan | Chart type, baseline points, the rules that distinguish a shift from variation, and how results will be displayed to stakeholders. | 260 to 320 |
| Limits of the evaluation | What this design cannot establish, written plainly, including the confounders a single-site evaluation cannot exclude. | 170 to 210 |
Evidence craft for measurement sections
Borrow definitions from published sources where they exist. If a national body defines a measure, adopt the definition and cite it. Comparability is worth more than a bespoke definition, and it removes an argument you would otherwise have to win.
Say who is blind to what, or say that nobody is. In improvement work, the person collecting data is often the person delivering the change. That is normal and it is a bias worth naming, especially where a measure depends on judgment rather than a system timestamp.
Report every rate with its counts. Thirty-four of 261 in the baseline period against 19 of 248 afterwards tells a reader far more than two percentages, and small denominators are the most common reason an apparent improvement is not one.
Keep statistical claims proportionate to the design. A run chart shows a pattern over time. Significance testing on a single-site before-and-after comparison invites a question about independence and confounding that the design cannot answer.
Write the limits section yourself. Every single-site evaluation shares the same weaknesses: concurrent changes, seasonality, the attention created by the project, and documentation behavior shifting alongside practice. Naming them precisely is credibility; leaving them for a reviewer is a scoring event.
Five mistakes that cost points in this week's territory
- No balancing measure. The clearest single signal that a plan has been written to prove success rather than to evaluate a change.
- An outcome measure that does not match the aim. If the aim promises one quantity and the plan measures a neighbor, the evaluation cannot answer the question you asked.
- Measures defined in adjectives. Timely, appropriate and adequate are not definitions until a numerator, a denominator and a clock are attached.
- A collection route that only you can run. Sustainability fails at exactly this point, and a committee will ask about it.
- Analysis language borrowed from research. Power, hypotheses and control groups signal a design you are not conducting and cannot support.
Before you submit
- The outcome measure matches the aim in quantity and in units
- At least one process measure sits at the point of delivery
- A plausible balancing measure appears with a threshold for action
- Every measure carries numerator, denominator, source, frequency and owner
- The collection route names a role who can run it without you
- The analysis approach and interpretation rules are set in advance
- Limitations name the confounders a single-site design cannot exclude
Designing the NR-702C measurement plan?
Send the rubric and your aim section out of Canvas. A premium original draft comes back in 24 to 48 hours with the three measure families defined in one consistent format, the analysis rules set in advance and the limits written honestly, and revisions run until the grade lands. Hours, logs and evaluations stay entirely yours.