Data collection is the mechanism by which your evaluation plan becomes real. You can have a well-designed PICOT question, strong evidence, and a solid implementation plan — but if your data collection section does not specify exactly what you will measure, how you will measure it, who will collect it, and when, your evaluation plan is incomplete. Faculty reviewing capstones know the difference between a student who has thought through data collection and one who has written vague statements about "monitoring outcomes."
The purpose of data collection in a capstone EBP project
In a BSN or MSN EBP capstone, you are not conducting primary research — you are proposing (and in some programs piloting) a practice change and describing how you would evaluate whether it worked. Data collection serves two purposes: (1) establishing a baseline to show the magnitude of the current problem, and (2) measuring the outcome after the intervention to determine whether improvement occurred. Both are necessary for a credible evaluation plan.
Data collection methods by project type
| Method | Best for | Data produced | Key considerations |
|---|---|---|---|
| Chart / EHR audit | Fall rates, HAI rates, medication error rates, readmission rates, documentation compliance | Retrospective numerical counts; rates per 1,000 patient-days | Requires EHR access approval; specify the audit period, the data fields extracted, and who conducts the audit |
| Direct observation / audit tool | Hand hygiene compliance, catheter care bundle adherence, SBAR use during handoff, fall risk assessment completion | Real-time compliance rate (# observed compliant / total observed × 100) | Specify the observation window (shift, days of week), who observes, and the audit tool or checklist used |
| Survey / questionnaire | Nurse knowledge, attitudes, confidence, satisfaction; patient experience; staff perception of safety culture | Likert-scale scores, knowledge test scores, pre/post comparison | Use a validated instrument when available (e.g., AHRQ Safety Culture Survey, CBI, NSSE); specify administration method (paper vs. electronic), timing, and anonymity |
| Existing quality dashboard data | Units with NDNQI, Press Ganey, or CMS quality metrics already tracked | Monthly or quarterly outcome rates already collected by the institution | No additional data collection burden; specify the exact metric and the data pull period; acknowledge that the data are aggregate and not patient-identifiable |
| Patient outcome tracking | Blood glucose control (HbA1c), blood pressure, weight, readmission, length of stay | Clinical values extracted from the EHR | Requires IRB/QI determination — if outcome data are patient-identified, data use agreement may be required |
Chart audits: the most common BSN capstone data source
A chart audit (also called a record review or EHR audit) is a systematic examination of patient records to determine whether a specific event occurred, a protocol was followed, or an outcome was achieved. It is the most practical data collection method for BSN capstone projects because it uses existing data without requiring patients to do anything.
How to describe a chart audit in your evaluation plan
A complete chart audit description answers six questions:
- What records will be reviewed? — "All patient discharge records from the 36-bed medical-surgical unit"
- What time period? — "A 12-week pre-implementation baseline period (Month 1–3) and a 12-week post-implementation period (Month 7–9, allowing 4 weeks for full protocol integration)"
- What data will be extracted? — "Fall events (documented in the unit's Safety Event Tracking system), fall-related injuries (documented in the incident report), and STRATIFY assessment completion rates (extracted from the nursing assessment EHR flowsheet)"
- Who will conduct the audit? — "The unit's quality improvement coordinator will extract aggregate fall data; the student investigator will audit 20 randomly selected charts per month for STRATIFY completion documentation"
- What tool will be used to record findings? — "A standardized data extraction form with fields for patient MRN (de-identified for QI purposes), admission date, fall event (Y/N), STRATIFY completion (Y/N), STRATIFY score"
- How will the data be stored and protected? — "De-identified data will be stored in a password-protected spreadsheet accessible only to the student investigator and unit quality coordinator"
Surveys: what "validated instrument" means and why it matters
When your capstone uses a survey to measure nurse knowledge, confidence, or attitudes, use a validated instrument whenever possible. A validated instrument is one that has been tested for reliability (it measures consistently across administrations) and validity (it measures what it claims to measure) in prior peer-reviewed research. Using a validated instrument strengthens your evaluation plan because the measurement tool itself has established credibility.
- Nurse knowledge assessment: if no validated instrument exists for your specific topic, you can develop a brief knowledge quiz based directly on your educational content — but acknowledge in your evaluation plan that the instrument has not been independently validated
- Safety culture: AHRQ Hospital Survey on Patient Safety Culture (HSOPS) — free, widely used, benchmarkable
- Pain assessment: NRS, VAS, FLACC, CPOT — all validated; choose based on patient population
- Nurse burnout: Maslach Burnout Inventory (MBI) — validated but requires licensing; abbreviated alternatives (Mini-Z, OLBI) are freely available
- Patient satisfaction: HCAHPS — institutionally administered; use existing scores rather than conducting your own survey
What counts as "pilot data" in a capstone?
Some programs ask students to collect pilot data as part of the capstone — a small-scale test of the intervention before proposing full implementation. Pilot data in this context means:
- Baseline data collected before the intervention (e.g., 4 weeks of fall rates prior to implementing a new protocol)
- A small initial implementation with a subset of staff or patients (e.g., one shift, one care team) with preliminary outcome data
- Pre/post knowledge test scores from a single educational session
- Compliance audit data from the first two weeks of protocol implementation
Pilot data does not need to be statistically conclusive — its purpose is to demonstrate that the measurement approach is feasible and that the intervention shows early signals of the expected effect. Present pilot data descriptively (percentages, means, counts) and acknowledge that the small sample limits inference.
Do not collect identifiable patient data without proper authorization
Even for a QI project, if you are extracting data that includes patient names, MRNs, or other identifying information from the EHR, you need explicit authorization from the facility — typically through the quality department, a data use agreement, or an IRB QI determination letter. De-identified aggregate data (total falls this month, overall compliance rate) generally do not require this. Always clarify the data access policy with your clinical site before beginning data collection. Submitting a capstone that describes collecting identifiable patient data without authorization documentation is an academic integrity and HIPAA compliance risk.
Need your evaluation plan and data collection section written?
Our writers build complete, specific evaluation plans — data collection methods, instruments, timelines, and protection procedures — all aligned to your rubric.
Start your capstone Evaluation plan guideRelated guides
Frequently asked questions
Most BSN capstone projects are proposals, not full implementations. You write the data collection section in the future tense, describing exactly what data you would collect if the project were implemented: what records would be audited, what survey would be administered, what compliance rate would be tracked, and when. Use specific, operational language — not "data would be collected" but "the unit's safety event tracking log would be audited by the quality coordinator for all fall events occurring in the 36-bed medical-surgical unit during a 12-week baseline period." The grader is evaluating whether you have designed a credible data collection plan, not whether you have actually executed it. Specificity and feasibility are what earn points.
For a QI capstone proposal, you do not need to calculate a formal sample size the way a researcher would. You need a data collection window long enough to capture a meaningful number of events or observations — typically 8–16 weeks. For low-incidence outcomes (CLABSI, falls), a 12-week window on a busy unit typically captures 10–30 events, which is sufficient for descriptive comparison. For compliance audits (hand hygiene, catheter care), plan for at least 25–30 observations per audit period to calculate a reliable compliance rate. For surveys, plan for 70–80% of eligible staff to respond — if your unit has 20 nurses, aim for 14–16 survey completions. These are practical targets for a QI project, not statistical power thresholds. Acknowledge in your evaluation plan that the sample is convenience-based and limits generalizability.