Reading a worked example of a well-constructed MSN capstone helps more than almost any abstract guide. These ten examples show you what a strong project looks like across the four most common MSN tracks — how the PICOT connects to the framework, how the intervention is scoped for a 1–2 semester timeline, and what the evaluation plan measures. Use them as structural models, not content to copy.
How to use these examples
Each example includes: Clinical problem (the gap in practice), PICOT question (the formal research/project question), Theoretical framework (with the key linkage explained), Intervention summary (what the project does), and Evaluation plan outline (outcome measure, instrument, and timeline). The depth shown here represents the level of specificity expected in a strong MSN capstone — not a rough draft.
FNP Track Examples FNP
Example 1: Uncontrolled Type 2 Diabetes in a Community Health Center
Clinical problemAt a federally qualified health center (FQHC) serving a predominantly Latino population, 42% of patients with T2DM have HbA1c above 8%, compared to the national FQHC benchmark of 28%. Chart review indicates fewer than 20% have ever been referred to a certified diabetes educator or structured DSMES program.
PICOT questionIn adult patients aged 30–65 with T2DM and HbA1c ≥8% seen at [FQHC name] (P), does FNP-initiated referral to a CDC-recognized DSMES program with a structured follow-up protocol at 4 and 12 weeks (I), compared to standard pharmacotherapy management and brief counseling at office visits (C), reduce HbA1c by ≥0.5% (O) at 3 months (T)?
Theoretical frameworkSocial Cognitive Theory (Bandura, 1986). The DSMES program builds diabetes self-management self-efficacy through mastery experiences (skill practice), vicarious learning (peer group sessions), and verbal persuasion (FNP encouragement). The FNP follow-up protocol reinforces outcome expectations and monitors behavioral progress. Self-efficacy is the mediating variable between DSMES attendance and HbA1c improvement.
Intervention summaryFNP reviews HbA1c at every visit. Patients with HbA1c ≥8% receive a warm referral (FNP-initiated call to DSMES coordinator during the visit), culturally adapted education materials in Spanish and English, and scheduled FNP follow-up at 4 and 12 weeks. FNP documents referral and follow-up in a structured EHR flowsheet. A medical assistant makes reminder calls at 48 hours before each DSMES session.
Evaluation plan outlinePrimary outcome: HbA1c reduction from baseline at 3 months (EMR lab data). Secondary: DSMES attendance rate (≥4 of 6 sessions); Diabetes Empowerment Scale — Short Form (DES-SF) at baseline and 12 weeks. Analysis: Paired t-test for HbA1c change; chi-square for attendance rate. IRB classification: QI exemption (de-identified aggregate EMR data). Timeline: Baseline audit → protocol implementation → 12-week outcome measurement = 16 weeks total.
Example 2: PHQ-9 Universal Depression Screening in Primary Care
Clinical problemA 10-provider primary care clinic conducts PHQ-9 screening opportunistically — only when depression is a presenting complaint. Review of 6-month encounter data shows 14% of adult patients received PHQ-9 screening versus the USPSTF-recommended universal screening for all adults ≥18.
PICOT questionIn adult patients aged 18–75 presenting for any primary care visit at [clinic name] (P), does FNP-initiated universal PHQ-9 screening at every visit with a structured positive-screen protocol (score ≥10 → FNP assessment within 2 weeks; score ≥15 → same-day referral to behavioral health) (I), compared to current opportunistic screening (C), increase the depression identification rate and time-to-treatment initiation (O) over 8 weeks (T)?
Theoretical frameworkHealth Belief Model (Rosenstock, 1974). Perceived susceptibility and severity are addressed through FNP framing of PHQ-9 results. Perceived barriers (stigma, time, cost) are addressed through same-day behavioral health referral within the clinic. Cues to action are operationalized through the systematic screening protocol — every visit becomes a trigger rather than patient-initiated disclosure.
Intervention summaryMA administers PHQ-9 on tablet at rooming for all adult patients. EHR generates automatic FNP alert for score ≥10. FNP reviews score before entering the room and follows structured response protocol: score 5–9 (mild) → patient education + rescreen at next visit; score 10–14 (moderate) → assessment and follow-up within 2 weeks; score ≥15 (severe) → same-day warm handoff to behavioral health clinician.
Evaluation plan outlinePrimary outcome: PHQ-9 completion rate (% of adult encounters with PHQ-9 score documented) at 8 weeks vs. baseline 6-month rate. Secondary: Time from positive screen (≥10) to documented assessment or referral; treatment initiation rate at 30 days. Data source: EHR report of PHQ-9 completion and follow-up documentation. Analysis: Pre/post percentage comparison; descriptive statistics for time-to-treatment. Timeline: 2-week training → 8-week implementation → outcome measurement = 12 weeks.
Nursing Education Track Examples MSN-Ed
Example 3: High-Fidelity Simulation for Obstetric Emergency Management
Clinical problemBSN students in the obstetric nursing course report low confidence in managing obstetric emergencies (shoulder dystocia, postpartum hemorrhage). Faculty post-clinical evaluations note that students observe emergencies in clinical but rarely have opportunity to participate in active management due to the high-acuity, fast-paced environment.
PICOT questionIn BSN students enrolled in the Women's Health Nursing course (P), does a structured 2-hour high-fidelity simulation scenario for postpartum hemorrhage management with structured debriefing (I), compared to the current clinical observation-only approach (C), improve simulation performance checklist scores (O) at end of the course (T)?
Theoretical frameworkNLN Jeffries Simulation Theory (2005, revised 2016). The simulation is designed around five core design characteristics: objectives (clearly stated PPH management steps), fidelity (high-fidelity manikin with bleeding simulation), complexity (progressive scenario: stable → hemorrhage → critical), cues (structured escalation prompts from faculty facilitator), and debriefing (15-minute structured debrief using the PEARLS framework). Student support and problem-solving are the theory's facilitating conditions.
Intervention summaryTwo-hour simulation session in groups of 4 during the obstetric clinical week. Session includes: 15-minute pre-brief (objectives, orientation to manikin), 40-minute scenario (stable patient → PPH → team response), 15-minute debriefing using PEARLS framework. Faculty complete the Simulation Performance Checklist (SPC) in real time. Students complete the Simulation Design Scale (SDS) and Debriefing Assessment for Simulation in Healthcare (DASH) post-session.
Evaluation plan outlinePrimary outcome: Simulation Performance Checklist (SPC) score — faculty-rated, 18-item checklist aligned to AWHONN PPH management standards. Secondary: SDS satisfaction score; DASH debriefing quality score; pre/post student confidence survey (Likert, 5-item). Analysis: Descriptive statistics for SPC scores; paired t-test for pre/post confidence. Comparison: SPC scores vs. prior cohort's clinical evaluation scores (historical control). Timeline: Scenario development (4 weeks) → pilot with one cohort → end-of-course evaluation = 10 weeks.
Example 4: Flipped Classroom for Pharmacology Pass Rates
Clinical problemFirst-year BSN pharmacology course has a 22% failure rate on the unit 3 exam (cardiovascular and renal pharmacology). Faculty surveys indicate students find traditional lecture for these high-volume content areas difficult to process before application in ATI practice questions. The course uses 3-hour lecture blocks twice weekly.
PICOT questionIn first-year BSN students enrolled in the Pharmacology II course (P), does a flipped classroom model for Units 3–4 (pre-recorded 30-minute lecture video + 90-minute in-class case application session) (I), compared to the traditional 3-hour lecture format (C), improve Unit 3 and 4 exam scores (O) over 8 weeks (T)?
Theoretical frameworkConstructivism (Vygotsky, 1978). Students construct pharmacology knowledge by first processing content at their own pace (video lecture), then working within the Zone of Proximal Development during in-class case analysis — solving problems just beyond their independent capability with peer and faculty scaffolding. The instructor's role shifts from information transmitter to scaffold — guiding case discussions rather than delivering content.
Intervention summaryPre-class: 30-minute recorded lecture video (cardiovascular drugs: MOA, indications, nursing considerations) posted in LMS by Monday. Students complete 10-question pre-class quiz before attending (accountability structure). In-class: Two 45-minute case study rotations in groups of 4–5. Faculty circulate, prompt reasoning, and debrief cases. Students complete ATI pharmacology practice questions post-session as homework.
Evaluation plan outlinePrimary outcome: Unit 3 and Unit 4 exam scores vs. prior cohort (same instructor, same exam). Secondary: Pre/post student perception of learning survey (5-item Likert); ATI pharmacology sub-score at end of course. Analysis: Independent t-test for exam score comparison; paired t-test for perception survey. Limitation: Cohort comparison design; unmeasured confounders between cohorts. Timeline: Video recording + case development (3 weeks) → 8-week course delivery → end-of-course analysis = 12 weeks.
Nursing Leadership Track Examples Leadership
Example 5: Nurse Residency Program and 1-Year Retention on Med-Surg
Clinical problemA 350-bed community hospital reports 34% 1-year RN turnover on three medical-surgical units — above the NSI national benchmark of 18.4%. Exit interviews identify "lack of support in first year" and "feeling unprepared" as the top two drivers. The current orientation is 6 weeks, unstructured, with inconsistent preceptor assignment.
PICOT questionIn newly licensed RNs hired to medical-surgical units at [hospital name] (P), does a structured 12-month nurse residency program (monthly cohort sessions, dedicated preceptor for 12 weeks, clinical competency progression checkpoints at 3, 6, and 12 months) (I), compared to the current 6-week unstructured orientation (C), improve 1-year retention rates and Casey-Fink Graduate Nurse Experience Survey scores (O) at 6 and 12 months (T)?
Theoretical frameworkBenner's Novice-to-Expert Model (1984). The residency program is structured around Benner's five stages of clinical competency development: novice (weeks 1–4: skills lab, simulation, orientation), advanced beginner (months 2–3: supervised patient assignment with preceptor present), competent (months 4–6: independent assignment with resource nurse support), proficient (months 7–9: charge nurse shadowing, complex patient assignments), expert development support (months 10–12: specialty certification introduction, leadership project). Monthly cohort sessions address professional role transition at each stage.
Intervention summary12-month structured residency: dedicated preceptor pair (trained through 8-hour preceptor education program) for first 12 clinical weeks; monthly 2-hour cohort educational sessions (clinical reasoning, communication, self-care); clinical competency checklist at 3, 6, and 12 months; 1:1 manager check-in at 1, 3, and 6 months. Casey-Fink survey administered at 3, 6, and 12 months.
Evaluation plan outlinePrimary outcome: 1-year retention rate (HR data: % of cohort still employed at 12 months). Secondary: Casey-Fink GNES scores at 3, 6, 12 months (validated, 4 subscales); preceptor satisfaction survey at 12 weeks. Analysis: Retention rate comparison to prior 3-year historical average; repeated-measures ANOVA for Casey-Fink scores across timepoints. IRB: QI exemption; Casey-Fink survey = program evaluation data. Timeline: Program development (8 weeks) → cohort 1 enrollment → 12-month outcome = 14 months total; interim data at 6 months.
Example 6: Safety Huddle Implementation and Shift Adverse Events
Clinical problemA 36-bed telemetry unit has no structured shift-change communication beyond a brief verbal report. Incident reports over 12 months show 68% of reported adverse events occurred within the first 2 hours of a shift — a pattern consistent with communication failures at handoff. The unit has no formal mechanism for identifying high-risk patients before shift start.
PICOT questionIn RNs and CNAs on a 36-bed telemetry unit (P), does a nurse manager–led 10-minute safety huddle at shift change (structured agenda: high-risk patients → pending procedures → equipment concerns → staffing issues) (I), compared to no formal pre-shift communication (C), reduce the percentage of adverse events occurring in the first 2 hours of a shift (O) over 8 weeks (T)?
Theoretical frameworkHigh Reliability Organization (HRO) Theory (Weick & Sutcliffe, 2007). The safety huddle operationalizes the HRO principle of "sensitivity to operations" — creating a structured mechanism for the team to detect weak signals of risk before they escalate. The structured agenda for high-risk patients addresses "preoccupation with failure." The nurse manager facilitation of the huddle models "deference to expertise" — frontline staff identify safety concerns that leadership acts on.
Intervention summary10-minute standing huddle at the nurses' station at the start of day, evening, and night shifts. Agenda card posted at the station: (1) high-risk patients (falls, restraints, post-procedure, new admissions); (2) pending procedures or transfers; (3) equipment or supply issues; (4) staffing concerns. Charge nurse facilitates; nurse manager attends day huddle. Huddle occurrence documented on a unit log. Anonymous post-huddle survey distributed at 4 weeks.
Evaluation plan outlinePrimary outcome: Percentage of unit incident reports occurring in hours 1–2 of a shift, pre/post (unit incident log; 8-week baseline vs. 8-week post-implementation). Secondary: Huddle attendance rate (huddle log); staff perception of communication safety (AHRQ SOPS communication openness subscale, pre/post). Analysis: Chi-square for adverse event timing distribution; paired t-test for SOPS scores. Timeline: Staff training on huddle structure (2 weeks) → 8-week implementation → 4-week outcome measurement = 14 weeks.
Nursing Informatics Track Examples Informatics
Example 7: BCMA Compliance Improvement on a Medical-Surgical Unit
Clinical problemA 28-bed medical-surgical unit has a bar-code medication administration (BCMA) scan compliance rate of 82%, below the institution's 95% target and ISMP safety benchmark. Nurse leaders identify two primary bypass patterns: scanning at the Pyxis dispense cabinet rather than at bedside, and manual override for medications labeled "scan not available." Near-miss medication events attributable to scan bypass averaged 3.2 per month over the past 6 months.
PICOT questionIn RNs administering medications on a 28-bed medical-surgical unit with current BCMA compliance of 82% (P), does a targeted re-education intervention (root-cause analysis of bypass patterns, nurse-specific compliance dashboard, and workflow adjustment for scan-not-available medications) plus peer champion support (I), compared to no additional intervention beyond existing compliance monitoring (C), increase BCMA scan compliance to ≥95% (O) at 8 weeks (T)?
Theoretical frameworkTechnology Acceptance Model (Davis, 1989). The low compliance rate reflects barriers to perceived ease of use (workarounds for scanner malfunction, time pressure) and, for some nurses, low perceived usefulness (belief that bedside scanning does not meaningfully reduce errors). The intervention addresses both dimensions: peer champions demonstrate efficient bedside scanning workflow (ease of use); near-miss data shared at huddles makes the safety value concrete (perceived usefulness). Behavioral intention to scan is expected to increase when both barriers are addressed.
Intervention summaryPhase 1 (weeks 1–2): Root-cause analysis of bypass patterns using EHR override reason codes. Identify top 3 bypass reasons and design targeted solutions (additional mobile scanners; pharmacy label correction for scan-not-available medications; badge reader repair request protocol). Phase 2 (weeks 3–4): 15-minute unit education sessions at shift change; individual nurse compliance dashboard accessible in EHR (shows each RN their personal scan rate vs. unit average). Phase 3 (weeks 5–8): Two trained peer champion nurses available on each shift for scanner issues; weekly compliance data reviewed at safety huddle.
Evaluation plan outlinePrimary outcome: BCMA scan compliance rate (% of medication administrations with bedside scan) at 8 weeks vs. baseline (EHR pharmacy compliance report). Secondary: Override rate by reason code (identify if specific bypass patterns persist); near-miss medication events per month (incident reporting system). Analysis: Run chart for compliance rate over 8 weeks; pre/post comparison with control chart for statistical process control. Timeline: Root-cause analysis (2 weeks) → education + dashboard rollout (2 weeks) → peer champion implementation (4 weeks) → outcome measurement = 10 weeks.
Example 8: Patient Portal Activation for Elderly Patients at Discharge
Clinical problemAdults aged ≥65 discharged from a community hospital have a MyChart patient portal activation rate of 19%, compared to 67% for adults aged 18–64. Discharge nurses report they do not have time to complete portal enrollment during discharge, and patients over 65 report not knowing the portal exists or how to use it. CMS quality data links portal non-use to higher 30-day readmission rates in this age group at this facility.
PICOT questionIn adults aged ≥65 being discharged from medical-surgical units at [hospital name] who do not have an activated patient portal account (P), does a nurse navigator–guided bedside portal activation session (15 minutes, tablet-based walkthrough of MyChart features relevant to discharge: test results, medication list, follow-up scheduling) on the day of discharge (I), compared to standard printed portal invitation handout (C), increase 30-day portal activation rates (O) at 30 days post-discharge (T)?
Theoretical frameworkTechnology Acceptance Model (Davis, 1989) adapted for elderly users. Perceived usefulness is addressed by demonstrating MyChart features directly relevant to post-discharge needs (viewing discharge summary, scheduling follow-up, messaging the provider). Perceived ease of use is addressed through guided tablet walkthrough and printed "how-to" reference card for home use. Prior research demonstrates that perceived usefulness is the stronger predictor of portal adoption in adults ≥65; the intervention prioritizes making the portal immediately relevant rather than just technically accessible.
Intervention summaryTrained nurse navigator (2 per shift) conducts 15-minute bedside session on morning of anticipated discharge. Session: activate account, demonstrate how to view discharge instructions and medication list, schedule follow-up appointment, send a message to PCP. Patient receives a laminated "MyChart Quick Start" card. Navigator documents session in EHR. Patients without smartphones or tablets are offered a follow-up phone-based activation call within 3 days by the care transitions team.
Evaluation plan outlinePrimary outcome: 30-day portal activation rate (% of intervention patients with at least one MyChart login within 30 days post-discharge; EHR analytics data). Secondary: Number of portal messages sent within 30 days (engagement proxy); 30-day readmission rate (administrative data; underpowered for this endpoint in a pilot). Analysis: Chi-square comparison of activation rates: intervention group vs. historical control (prior 3-month discharge cohort aged ≥65). Timeline: Navigator training (1 week) → 8-week enrollment → 30-day follow-up data pull = 14 weeks total.
Example 9: Sepsis Early Warning Alert — Evaluation and Optimization
Clinical problemA hospital's Epic-based sepsis early warning alert fires 40 times per day across medical-surgical units. Provider override rate is 74%. Chart review of a 90-day sample shows 18% of alerts represent true early sepsis (alert positive predictive value = 18%), and 8% of true sepsis patients did not trigger an alert (alert sensitivity gap). Nurses report "alarm fatigue" as the reason for delayed responses to alerts that are eventually confirmed as sepsis.
PICOT questionIn RNs and hospitalists managing adult inpatients on medical-surgical units (P), does a CDS alert rationalization intervention (addition of lactate and procalcitonin to alert criteria; removal of isolated tachycardia as sole trigger; addition of tiered alert severity based on composite score) (I), compared to the current alert configuration (C), improve alert positive predictive value and reduce the override rate (O) at 8 weeks post-implementation (T)?
Theoretical frameworkSociotechnical Systems Theory (Sittig & Singh, 2010). The alert fatigue problem is not a clinical knowledge deficit (nurses know what sepsis is) — it is a sociotechnical failure: a technical system (alert algorithm) that does not match the clinical workflow and cognitive patterns of its users. The rationalization intervention redesigns the technical system to better fit the clinical social system by increasing specificity (reducing false positives), tiering severity (supporting clinical judgment), and aligning alert criteria with current diagnostic evidence. The intervention addresses the technical, content, and human-computer interface dimensions of the Sittig-Singh model simultaneously.
Intervention summaryPhase 1 (weeks 1–3): Multi-disciplinary workgroup (nursing informatics specialist, hospitalist champion, pharmacist, infection control) reviews 90-day alert data. Identifies criteria modifications: add lactate ≥2.0 mmol/L as a required trigger; add procalcitonin >0.5 ng/mL as supportive criterion; remove isolated tachycardia HR >100 as a standalone alert. Implement tiered alert: yellow (2 SIRS criteria + lactate) → nursing assessment; red (3 SIRS + lactate or procalcitonin) → immediate physician notification. Phase 2 (weeks 4–6): IT build and testing in sandbox environment. Phase 3 (weeks 7–8): Go-live with monitoring dashboard. Staff education: 10-minute at-shift in-service on new alert tiers.
Evaluation plan outlinePrimary outcome: Alert positive predictive value at 8 weeks post-implementation vs. 90-day baseline (chart review of 50 randomly selected alerts per period). Secondary: Override rate (EHR analytics); time from alert to treatment initiation (order timestamp vs. alert timestamp). Analysis: Chi-square for override rate pre/post; descriptive statistics for PPV and sensitivity; run chart for weekly alert volume. Timeline: Workgroup formation → build → go-live → 8-week evaluation = 16 weeks.
Example 10: Nursing Informatics Competency Training and EHR Efficiency
Clinical problemA needs assessment at a 200-bed community hospital finds that 58% of RNs score below the "proficient" threshold on the Nursing Informatics Competency Questionnaire (NICQ), and the help desk receives an average of 4.3 EHR-related calls per nurse per month. Nurses report spending an average of 32% of their shift on documentation — above the NDNQI benchmark of 25%.
PICOT questionIn inpatient RNs at [hospital name] with NICQ scores below the "proficient" threshold (P), does a structured 4-hour informatics competency education program (EHR navigation efficiency, documentation shortcuts, clinical decision support interpretation, patient portal support) delivered in unit-based cohorts (I), compared to self-directed EHR learning via the vendor LMS (C), improve NICQ scores and reduce EHR-related help desk calls per nurse FTE (O) at 60 days (T)?
Theoretical frameworkStaggers and Bagley Smith Nursing Informatics Model (2002). The four levels of nursing informatics competency (beginning nurse → experienced nurse → informatics specialist → informatics innovator) frame the education program design. The target population (beginning to experienced nurses below the proficient threshold) requires foundational competencies in data entry accuracy, basic EHR navigation, and information retrieval — not advanced analytics or system design. The program is explicitly calibrated to the first two competency levels, which is where the documentation time and help desk call data indicate the gap lies.
Intervention summary4-hour unit-based training delivered in groups of 8–10 during protected education time (charge nurse coverage arranged with nurse manager). Content: (1) EHR navigation efficiency — top 10 shortcuts, quick-order sets, dot-phrase documentation templates (90 min); (2) Clinical decision support — how to read alerts, when to override, how to document override rationale (60 min); (3) Patient portal — how to enroll patients, answer patient messages, view proxy requests (30 min); (4) Practice station — hands-on scenario-based exercises using training environment (60 min). Post-training: 30-day "tip of the week" email from nursing informatics team.
Evaluation plan outlinePrimary outcome: NICQ total score at 60 days vs. baseline (validated, 30-item, 5-point Likert). Secondary: EHR-related help desk calls per nurse FTE at 60 days (IT service desk data); self-reported documentation time per shift at 60 days (5-item post-training survey). Analysis: Paired t-test for NICQ score change; descriptive comparison of help desk call rates. IRB: QI exemption (de-identified program evaluation data). Timeline: Training development (3 weeks) → cohort delivery over 4 weeks → 60-day follow-up = 11 weeks.
What these examples have in common
Across all ten examples, the strongest structural features are:
- A quantified problem statement — every example opens with specific numbers (a rate, a benchmark gap, an incident frequency) that establish the problem concretely before naming the PICOT
- A PICOT with a defined comparison — the C element specifies what current practice actually is, not just "standard care"
- Framework application at the intervention level — each framework is connected to a specific component of the intervention, not described in the abstract
- A named outcome measure — every evaluation plan names the specific instrument, data source, and measurement timing
- A realistic timeline — none of these projects require 18 months; all fit within a 10–16 week implementation window
Need your MSN capstone written?
Our MSN-level writers build full capstone papers around your track, framework, and program rubric. Send us your topic and requirements to get started.
Start your MSN capstone Browse more topic ideasRelated guides
Frequently asked questions
You can use the structure — the PICOT format, the framework application model, the evaluation plan layout — as a template for your own project. The content itself (the specific setting, population, intervention, and data) must be your own work. Your program's academic integrity policy prohibits submitting any previously written work as your own, and these examples are publicly accessible. Use them to understand what a strong capstone looks like, then apply that understanding to your own clinical problem and setting.
Yes. The PICOT, framework, and literature review sections are identical in structure between an EBP proposal and an implementation project. The difference is in Chapter 4 and 5: an EBP proposal describes the intervention design and evaluation plan as a proposal (what you WOULD do), not a report of what you did. The level of specificity expected is the same — you must describe the intervention in enough operational detail that it could be implemented, and the evaluation plan must name specific outcome measures even if no data was collected.
Test your PICOT against three criteria: (1) Is the population specific enough that you could define inclusion and exclusion criteria? (2) Is the intervention described precisely enough that another clinician could replicate it? (3) Is the outcome measurable with a named instrument, rate, or score — not a vague descriptor like "improved outcomes"? If all three are yes, your PICOT is at MSN level. If any are no, revise that element before submitting your proposal to your committee.