The evaluation plan is how you answer the question every faculty reviewer is asking: "How will you know if this worked?" A vague answer — "outcomes will be monitored" — earns minimal credit. A specific answer — naming the exact metric, the measurement tool, the baseline comparison, the data source, the collection timeline, and the success threshold — demonstrates that you have designed a credible, implementable evaluation. This guide breaks down every component your evaluation plan needs.
Three types of evaluation in a nursing capstone
Most capstone rubrics ask for an evaluation plan, but they don't always specify what type of evaluation. Understanding the three types prevents you from confusing them — or omitting the ones your rubric actually requires.
| Type | What it measures | Question answered | When used |
|---|---|---|---|
| Process evaluation | Whether the intervention was implemented as designed — fidelity, reach, and dose | "Was the protocol actually followed? Did the right people receive the intervention at the right frequency?" | Always — tells you whether poor outcomes are due to a failed intervention or a failed implementation |
| Outcome evaluation | Whether the targeted clinical or nursing outcome changed as expected | "Did fall rates decrease? Did compliance rates increase? Did patient satisfaction scores improve?" | Always — the primary measure of whether the project achieved its PICOT outcome |
| Impact evaluation | Broader system effects beyond the immediate outcome — organizational, financial, or population-level impact | "Did the cost of falls decrease? Did the practice spread to other units? Did nurse confidence improve?" | Optional at BSN level; expected at MSN/DNP level to demonstrate system-level thinking |
A complete evaluation plan includes at least process and outcome evaluation. Impact evaluation strengthens an MSN or DNP capstone but is not always required at the BSN level.
The logic model: connecting inputs to outcomes
A logic model is a visual framework that maps the logical chain from what you invest (inputs) through what you do (activities) to what results (outputs and outcomes). Some programs require a logic model as an appendix; others just expect the evaluation plan to reflect logical model thinking without a formal diagram.
Inputs
- RN staff time (7.5 hrs education)
- STRATIFY tool (free)
- EHR flowsheet update
- Printed pocket cards
- Charge nurse time (auditing)
Activities
- Staff education session
- EHR template setup
- Protocol launch
- Daily STRATIFY assessments
- Weekly compliance audits
Outputs
- % nurses trained
- STRATIFY completion rate
- Individualized care plans created
- Compliance audit scores
Short-term outcomes
- ↑ STRATIFY completion rate ≥ 90%
- ↑ Nurse knowledge scores post-education
- ↑ High-risk patients flagged
Long-term outcomes
- ↓ Fall rate per 1,000 pt-days
- ↓ Fall-related injuries
- ↓ Fall-related costs
- Protocol integrated into P&P
SMART outcomes: what the rubric means
When a rubric says your outcome measures must be "SMART," it means each outcome must be:
- Specific: names exactly what will change (not "improve patient safety" but "reduce fall rate")
- Measurable: expressed as a number or percentage that can be verified from a data source
- Achievable: realistic given the intervention and the timeframe (a 50% reduction in falls in 6 weeks is not credible; a 20–25% reduction over 12 weeks is supported by evidence)
- Relevant: directly tied to your PICOT outcome — the outcome you measure must be the outcome your PICOT question asked about
- Time-bound: includes a specific timeframe for measurement ("at 12 weeks post-implementation")
SMART outcome examples — strong vs. weak
| Weak (not SMART) | Strong (SMART) |
|---|---|
| "Falls will decrease" | "Fall rate on the 36-bed medical-surgical unit will decrease by ≥20% (from the 3.8 falls/1,000 patient-days baseline to ≤3.0 falls/1,000 patient-days) at 12 weeks post-implementation, as measured by the unit's Safety Event Tracking system" |
| "Nurses will use the assessment tool" | "STRATIFY assessment completion rate will reach ≥90% for all patients aged 65+ within 4 weeks of protocol launch, as measured by monthly chart audit of nursing admission assessment EHR flowsheet" |
| "Patient safety will improve" | "Fall-related injury rate will decrease by ≥15% at 12 weeks post-implementation compared to the 12-week pre-implementation baseline, as measured by incident report classification in the facility's adverse event tracking system" |
| "Staff knowledge will increase" | "Mean nurse knowledge test score will increase from pre-education baseline to ≥80% correct on the 10-item STRATIFY scoring knowledge assessment, administered before and immediately after the education session" |
The evaluation timeline
Your evaluation plan must specify when each measurement occurs. A clear timeline prevents the common mistake of planning to measure outcomes too early (before the intervention has had time to work) or too late (after the pilot has ended and data are no longer available).
| Timepoint | What to measure | Data source |
|---|---|---|
| Pre-implementation (Weeks 1–4) | Baseline fall rate; baseline STRATIFY completion rate (if tool was used previously); baseline nurse knowledge score (pre-education) | EHR audit; Safety Event Tracking log; pre-education knowledge quiz |
| Implementation launch (Week 5) | % staff trained; education session attendance; EHR template operational | Attendance record; IT confirmation of EHR update |
| Early implementation (Weeks 5–8) | STRATIFY completion rate (process measure); early barrier identification | Weekly compliance audit; informal staff feedback |
| Full implementation (Weeks 9–16) | STRATIFY completion rate; fall rate; fall-related injury rate | Biweekly compliance audit; Safety Event Tracking log |
| Post-implementation (Week 17+) | 12-week post-implementation fall rate compared to 12-week baseline; nurse knowledge retention; staff satisfaction with protocol | EHR audit; knowledge post-test (optional); brief staff survey |
Don't measure outcomes before the intervention has had time to work
A common mistake is designing an evaluation that measures fall rates at 4 weeks post-launch. Falls are relatively low-frequency events — a 36-bed unit averages 1–2 falls per month. At 4 weeks, you may have too few data points to detect a meaningful difference from baseline. Plan your primary outcome measurement at 8–12 weeks minimum. Process measures (compliance rates, training completion) can be measured earlier because they reflect protocol adherence rather than infrequent clinical events.
Need your evaluation plan written?
Our writers build complete evaluation plans — SMART outcomes, process and outcome measures, logic model connections, evaluation timeline — aligned to your rubric.
Start your capstone Data collection guideRelated guides
Frequently asked questions
Check your specific rubric. Some programs explicitly require a logic model table or diagram (usually as an appendix); others accept a prose description that demonstrates logic model thinking without a formal graphic. If the rubric says "logic model," produce a table or diagram — do not substitute prose. If the rubric says "evaluation plan" without specifying a logic model, a well-structured prose evaluation plan with SMART outcomes, a data source for each measure, and an evaluation timeline is sufficient. Adding a simple logic model table as an optional appendix is never penalized and often appreciated.
Acknowledge the statistical limitation directly and frame your primary process measure as the leading indicator. Write something like: "Given the low incidence of fall events on this 32-bed unit (mean 1.4 falls/month at baseline), the 12-week pilot window will yield approximately 17 expected fall events under baseline conditions — insufficient for robust statistical comparison. Therefore, the primary process measure (STRATIFY completion rate, target ≥90%) will serve as the leading indicator of protocol fidelity during the pilot. The fall rate (falls/1,000 patient-days) will be tracked as the primary outcome measure with the acknowledgment that a longer post-implementation observation window (6–12 months) would be required to detect a statistically significant change." This demonstrates that you understand the measurement challenge and have designed an evaluation plan that is both honest and clinically meaningful.