The evaluation section is the row most capstones lose, and they lose it the same way: several hundred words about the importance of evaluation and one vague sentence about monitoring outcomes. What earns the band is arithmetic. Name the measure, define it operationally down to what counts and what does not, say where the data physically lives, say who pulls it and how often, state the baseline and the threshold that would count as improvement, and name what else could produce the same change. 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 and preceptor evaluations remain your own record and are never drafted, reconstructed or estimated with help.
What an evaluation plan has to make measurable
Sit in on a quality meeting where somebody presents a rate and watch the first three questions. Out of what? Since when? Who pulled it? A measure that cannot answer those on demand is not a measure, it is an impression, and every well-run audit dies at that table. Your evaluation section is written to survive the same interrogation from a grader who cannot see your unit and will judge entirely on whether the definitions hold.
Three families of measure belong in a capstone plan and each does a different job. Process measures say whether the thing was done: the proportion of eligible encounters where the tool was completed. Outcome measures say whether it mattered: time to reassessment, unplanned transfers, escalations that met criteria. Balancing measures say whether you broke something else while fixing this: documentation time, alert volume, delayed care elsewhere. A plan with only outcome measures cannot tell a failed intervention from an intervention nobody used, which is the single most useful thing an evaluation can distinguish.
Operational definition is where the marks concentrate. Time to reassessment is not a measure until you say what starts the clock, what stops it, which encounters are eligible, which are excluded and why, and what happens to the records where the field is blank. Two competent people applying your definition to the same twenty charts should produce the same number. If they would not, the definition is not finished, and a grader with a scoring guide will see the ambiguity before you do.
The boundary holds here too, and this stage is where it matters most in practice. Writing a plan for how data would be collected is coursework. Actually extracting patient data, auditing real records for a project, or collecting anything from staff requires your site's own approvals and your program's guidance, and those are yours to obtain and yours to conduct. Any illustrative figure that comes from your own precepted observation must be de-identified and labelled as your own local observation rather than presented as institutional data.
Deliverables at this stage are typically the written evaluation section of the capstone, sometimes with a measure table or a data collection instrument in an appendix. Where a discussion runs alongside, write it as final copy; posts do not reopen after submission in Canvas.
The NR-575 Week 6 method, step by step
Six moves that turn intended outcomes into a plan somebody could execute.
-
Write the measure sentence before anything else
The proportion of eligible transfers with a documented reassessment within the defined interval, drawn from the electronic record, reported monthly. If you cannot write that sentence, the problem is upstream in your product, not in this section.
-
Define numerator, denominator, exclusions and missing data
Say exactly what qualifies for each, then write the exclusions with reasons. Missing data needs its own rule, because in real audits blanks are the largest single category and how you count them changes the result more than the intervention does.
-
Choose at least one process and one balancing measure
The process measure tells you whether the tool was used. The balancing measure tells you what it cost. Together they let you interpret a null outcome result, which is otherwise uninterpretable.
-
Name the data source and the person who touches it
Which system, which report, which role runs it, at what interval, and what happens to the file afterwards. Data that would require a build request nobody has approved is a feasibility problem worth stating rather than assuming away.
-
State a baseline and a threshold in advance
What the measure reads now, or how you would establish it, and what value would count as meaningful improvement. Setting the bar before the data arrives is what separates evaluation from justification after the fact.
-
Write the rival explanation paragraph
Seasonal variation, a concurrent initiative, a staffing change, the attention the project itself created. Name the two most likely and say how you would tell them apart from a real effect.
A layout and word budget for the evaluation section
Our frame for the evaluation section of a capstone, sized for roughly 1,000 to 1,300 words with the measure table in an appendix. 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 |
|---|---|---|
| What success would look like | The change you are claiming the product would produce, stated as a direction and a magnitude before any method appears. | 90 to 120 |
| Primary outcome measure | Operational definition with numerator, denominator, eligibility, exclusions and the rule for missing data. | 250 to 300 |
| Process and balancing measures | At least one of each, defined to the same standard, with what each would tell you that the outcome cannot. | 210 to 260 |
| Data source and collection | System, report, role responsible, interval, storage and how identifiers are handled. | 170 to 210 |
| Baseline, threshold and window | Current value or how it would be established, the threshold for meaningful change, and how long you would look. | 170 to 210 |
| Rival explanations | The two most plausible alternative causes and how you would distinguish them from an effect of the product. | 160 to 200 |
Evidence craft for an evaluation plan
Borrow measures that already have definitions. Where a nationally reported or professionally endorsed measure exists for your outcome, use its published specification and cite it. Inheriting an established definition is both less work and more defensible than inventing one, and it lets your result be compared with something.
Report every proportion as a fraction with a window. Nine of twenty over one quarter, not forty-five percent. In an evaluation section the denominator is not decoration; it is the thing that tells a reader whether a change of two cases means anything at all in your volume.
Say plainly what your design can and cannot support. A before-and-after comparison on one unit is the most common capstone design and it cannot exclude concurrent change. Write that sentence yourself rather than leaving it for the grader, then say what you would do to strengthen inference: more baseline points, a comparison unit, a balancing measure that would move if the cause were something else.
Match the statistical claim to the volume you actually have. With small numbers, run charts and simple proportions communicate more honestly than significance testing, and saying so demonstrates judgment. Claiming statistical power you could not have is a marked error in graduate work.
Handle identifiers in the plan itself. State that collection would be aggregate, that any record-level extract would be de-identified, and where such data would be stored. Evaluation sections that describe pulling patient-level information with no word about protection lose credibility with graders who work in the same systems.
Five mistakes that cost points at this stage
- Satisfaction as the primary outcome. Staff liking a tool is a process signal at best. If your only measure is a survey, the plan cannot detect whether anything changed for patients.
- Definitions that two auditors would apply differently. Improved documentation and timely reassessment are phrases, not measures, until eligibility and timing rules are written.
- No baseline and no threshold. Without both, any result can be narrated as success, and a grader scoring rigour will read it exactly that way.
- Silence on missing data. Blanks are the largest category in most real audits and the rule for counting them changes the answer more than the intervention does.
- Rival explanations unmentioned. An evaluation that treats its own intervention as the only possible cause of change has not evaluated anything.
Before you submit
- The primary measure has a numerator, a denominator, eligibility rules and exclusions
- There is at least one process measure and one balancing measure
- The rule for missing or blank data is written down
- A data source and a responsible role are named for each measure
- Baseline, improvement threshold and observation window all appear
- Two rival explanations are named with a way to distinguish them
- Identifier handling and storage are addressed in one explicit sentence
Writing the NR-575 evaluation plan?
Send the rubric and your product and implementation drafts out of Canvas. A premium original draft comes back in 24 to 48 hours with operational definitions two auditors could apply identically and rival explanations handled, and revisions run until the grade lands.