Over 180 specialty-organized project ideas spanning BSN capstones, MSN scholarly projects, and DNP doctoral projects — with clear notes on how expectations shift as you move up the academic ladder.
DissertationHorse has spent years in the trenches of dissertation-level work — problem statements, methodology chapters, defense prep, the whole arc of doctoral research across business, education, psychology, and the applied sciences. Nursing is genuinely new ground for us as a named specialty, and we want to say that plainly rather than pretend otherwise. What isn't new is the underlying skill: scoping a project so it's feasible, defensible, and actually answers a question that matters. That skill transfers directly to nursing capstones and DNP projects, and it's why we're expanding into this space now — not because we've quietly been doing nursing work all along, but because the core competency (turning a vague clinical interest into a structured, evidence-backed project) is exactly what we already do for dissertation writers every day. This guide exists to prove that out: 180-plus concrete project ideas across every major specialty, organized by degree level, with the DNP tier treated with the same rigor we'd bring to a PhD dissertation chapter.
A project idea that sounds interesting in a brainstorming session can still be impossible to execute in the time and access you actually have. Before you commit to any idea from the bank below — or one of your own — run it through the same feasibility checks we'd apply to a dissertation topic.
Can you actually reach the population your idea depends on? A project comparing outcomes across three hospital units only works if you have a placement, a preceptor relationship, or an approved data-sharing agreement with those units. Many strong ideas die not because they're poorly conceived but because the student never confirms access before proposing them. Before you commit, ask your preceptor or unit manager directly whether the data or population you need is realistically reachable in your timeframe — not just theoretically available somewhere in the health system.
"Improve patient satisfaction" is not measurable until you attach it to an instrument — a validated survey, a chart-audit metric, a readmission rate, a documented time-to-intervention. Every idea in the sections below is written so it implies a metric, but you'll still need to name the specific instrument or data source you'll use (HCAHPS scores, a validated fall-risk scale, EHR-pulled readmission counts) before a committee will sign off.
BSN and MSN capstones typically run one or two semesters. That rules out anything requiring a long baseline period, a slow-accruing sample, or multi-site IRB coordination. DNP projects have more runway — often two to four semesters of implementation and evaluation — but "more time" is not "unlimited time," and DNP committees are just as unforgiving about projects that quietly balloon in scope.
A good capstone or DNP idea is rarely a novel discovery — it's the translation of already-validated evidence into a specific practice setting. If you can't find at least a handful of recent, credible sources supporting the intervention or approach you want to test, the idea needs to be reframed around something the evidence base actually supports.
Any project touching patient data, staff behavior, or a clinical workflow change needs a green light — usually from a facility's nursing research council, sometimes from a full IRB, and always from your program's project chair. Projects framed as quality improvement (rather than generalizable research) often qualify for an expedited or exempt review, which is one reason so many capstone ideas below are framed as QI initiatives rather than research studies.
Every one of these checks tightens at the doctoral level. A BSN capstone can sometimes get away with a small convenience sample and a short pre/post survey. A DNP project committee will expect a named theoretical or practice-change framework (Iowa Model, Kotter's change model, PDSA cycles), a formal implementation plan with defined phases, a rigorous evaluation design — often mixed-methods — and enough data to support generalizable claims about sustainability. If you're weighing whether your idea is "BSN-sized" or "DNP-sized," the honest test is whether it needs that level of structural scaffolding to be defensible. If it does, you're already thinking at the doctoral level.
Quick gut check: if you can't name (1) the population, (2) the outcome measure, (3) the timeline, and (4) the approval pathway in one sentence each, the idea isn't proposal-ready yet — no matter how good it sounds in the abstract.
Every idea below is written specifically enough to be a starting point for a PICOT question or DNP problem statement — not a generic topic area. Adjust population, setting, and scope to match your own clinical placement and program level.
General medical-surgical units see the widest range of acuity and turnover, which makes them fertile ground for workflow and safety-focused projects. Because these units admit almost every diagnosis category, they also generate the largest volume of readily available chart data, which makes feasibility checks easier than in more specialized settings. Most of the ideas below can be piloted on a single unit within one semester, which is part of why med-surg is such a common starting point for first-time capstone students.
Critical care projects tend to center on sedation practice, delirium, and the reliability of high-stakes protocols. Because ICU patients are monitored so continuously, these units generate rich physiologic and process data, which supports stronger quantitative evaluation designs than lower-acuity settings typically allow. The tradeoff is smaller sample sizes and more variable patient trajectories, so plan your evaluation window generously and expect more variability in your outcome measures than a med-surg project would show.
ED projects usually revolve around triage accuracy, throughput, and recognition of time-sensitive conditions. The unpredictable volume and acuity mix in emergency settings makes randomized comparisons difficult, so most workable ideas here lean on before-and-after process metrics — door-to-provider time, time-to-antibiotic, time-to-CT — rather than controlled trials. If your placement is in an ED, confirm early whether your facility's registration and triage systems can actually pull the timestamp data your idea depends on.
Pediatric projects combine clinical safety with family-centered communication and developmentally appropriate care. Weight-based dosing, nonverbal pain assessment, and caregiver health literacy all add layers of complexity that adult-focused projects don't have to account for, so build extra review time into your timeline for pharmacy and child-life stakeholder input. Family-centered outcome measures — caregiver-reported understanding, satisfaction, or confidence — are often as important as the clinical metric itself in this population.
These ideas focus on postpartum safety, breastfeeding support, and early recognition of obstetric emergencies. Maternal-newborn projects often need to track two patients at once — mother and infant — which doubles your data-collection burden but also opens up richer outcome comparisons if your timeline allows it. Postpartum hemorrhage and hypertensive-disorder recognition remain two of the most consequential safety gaps in this specialty, which is why several ideas below target early-warning and risk-assessment tools specifically.
Behavioral health projects tend to focus on de-escalation, screening, and safe transitions of care. Documentation in this specialty is often more sensitive and more heavily regulated than in general medical settings, so confirm your data-access plan with your facility's privacy officer before proposing anything involving chart review. Many of the strongest ideas here pair a process metric (screening completion, restraint use) with a patient-reported measure, since behavioral health outcomes rarely tell the full story through chart data alone.
Long-term-care ideas frequently address falls, polypharmacy, and dignity-centered end-of-life practice. Residents in these settings often have longer lengths of stay than acute-care patients, which actually works in your favor — you can track an outcome over months rather than days, giving you a more stable evaluation window. Facility staffing and documentation systems vary widely between skilled nursing settings, so confirm what data your specific facility can realistically export before finalizing your idea.
Community-facing ideas emphasize access, prevention, and closing gaps for underserved populations. These projects often depend on partnerships with a clinic, school district, shelter, or community organization outside your usual clinical placement, so lock in that partnership formally before you propose the idea to your committee. Outcome measures here tend to be softer and slower-moving than acute-care metrics — screening or enrollment rates rather than mortality or readmission — so set expectations accordingly with your chair.
Perioperative projects target the handoffs, checklists, and thermoregulation practices that drive surgical outcomes. Surgical services move quickly and involve multiple departments — pre-op, OR, PACU — so a project that only looks at one segment of that chain often misses where the actual breakdown happens. Checklist-compliance and infection-rate data are usually well tracked in surgical settings already, which makes this specialty a relatively data-friendly place to start a first capstone.
Oncology ideas balance symptom management with the psychosocial dimensions of a cancer diagnosis. Because treatment courses run for months, oncology projects can track an outcome across an entire regimen rather than a single admission, which supports more meaningful before-and-after comparisons than acute-care settings usually allow. Distress and quality-of-life measures are just as legitimate an outcome here as a clinical metric, so don't feel pressured to make every idea purely physiological.
Informatics projects address how documentation tools and decision-support systems change frontline practice. These ideas are attractive because EHR systems already generate detailed usage and outcome logs, but that same data richness means you'll need IT and analytics support early to actually extract what you need. A strong informatics project always pairs a system-level metric (alert-override rate, documentation time) with a frontline nurse's actual experience of the tool, since adoption failures are usually a workflow problem, not a technology problem.
Workforce-focused ideas look at onboarding, retention, and how leadership structures affect frontline nurses. These projects sit a little apart from clinical-outcome ideas because your primary data source is often staff surveys, turnover reports, and engagement scores rather than patient charts, so plan your evaluation instrument (validated where possible) well before your implementation phase begins. Leadership and workforce projects also tend to require sign-off from HR or nursing administration in addition to your unit manager, so build that extra approval step into your timeline.
These ideas apply formal QI methodology (PDSA, Six Sigma, root-cause analysis) to a specific safety problem. Because QI projects are explicitly about improving an existing process rather than generating new knowledge, they're usually the fastest category to clear for expedited or exempt review — which makes this a good fallback specialty if your first-choice idea in another category is stuck in a slow approval queue. Pair every idea here with a named methodology (a PDSA cycle, a fishbone diagram, a control chart) rather than an informal "before and after" comparison, since committees expect the formal QI structure to be visible in your proposal.
Telehealth ideas examine access, engagement, and outcomes for care delivered outside the traditional bedside. This is one of the newer specialty areas in nursing scholarship, so the evidence base is thinner than in more established specialties — expect to lean more heavily on recent, sometimes preliminary, studies when justifying your intervention. Access and equity are recurring themes here, since telehealth adoption often varies sharply by patient age, income, and broadband access, and a strong project acknowledges that variation rather than treating the technology as universally accessible.
DNP projects are where this list intersects most directly with what DissertationHorse already does best. A doctoral project needs the same structural backbone as a dissertation chapter sequence — a defensible problem statement, an explicit theoretical or practice-change framework, a rigorous implementation and evaluation plan, and a discussion that honestly weighs sustainability and limitations. The ideas below are written with that scope in mind; several could anchor an entire DNP project on their own, and each implies the kind of multi-phase design a doctoral committee expects.
The same clinical problem can support a BSN capstone, an MSN scholarly project, or a DNP project — the difference is depth of framework, rigor of evaluation, and the claims you're allowed to make at the end. Understanding this distinction is where our dissertation background actually adds the most value, because these are the same structural questions we help doctoral candidates answer every day in other fields.
At the BSN level, a capstone is usually a synthesis project: you identify a practice problem on your unit, review a focused set of evidence, and propose (sometimes pilot) a change. The bar is competent application of evidence to practice — you are not expected to generate new knowledge, and a small convenience sample or a short pre/post comparison is generally acceptable. The project statement is closer to a single clear sentence: "this unit has problem X; the evidence supports intervention Y; here's a proposed or piloted implementation."
At the MSN level, especially in clinical nurse leader, education, or informatics tracks, the scholarly project usually needs a named framework (even if lightweight — a change-management model or a QI framework like PDSA) and a slightly more developed evaluation plan, often spanning a full semester of data collection rather than a snapshot. You're still not expected to produce generalizable findings, but the project needs enough structure that another nurse leader could replicate it in a similar setting.
At the DNP level, the project needs to function almost like a compressed dissertation, and this is where the parallel to our core work becomes explicit. A DNP project committee expects, at minimum:
If you're unsure which tier your idea belongs in, ask whether it needs all five of those elements to be defensible. If it does, you're proposing DNP-level work, even if your program calls it something else. If a lighter, single-cycle version of the same idea would satisfy your committee, you may be over-scoping for an MSN or BSN capstone — which is its own common mistake, covered below.
Picking an idea from the bank above is the easy part. Converting it into a proposal your committee will approve takes several more concrete steps, and this is where our dissertation-proposal experience is most directly transferable — a DNP project proposal and a dissertation proposal share almost the same skeleton.
Start by writing a one-paragraph problem statement using the same "this population has this problem, evidenced by this data, and this intervention is supported by this evidence" structure we recommend for dissertation topics — see our guide to scoping a researchable topic for the underlying method, which transfers directly to a DNP problem statement. Next, pull together a focused evidence review — not a full systematic review, but 15-25 recent, credible sources that justify your chosen intervention; our literature review guide walks through how to search and organize sources efficiently even when your final product is shorter than a dissertation chapter.
From there, name your framework explicitly and sketch your implementation phases against a realistic calendar — most committees want to see this as a simple table (phase, activity, timeframe, measure). Identify your outcome measures and where the data will come from before you submit anything for approval; vague measures are the single most common reason proposals bounce back for revision. Finally, confirm your approval pathway early — talk to your unit's nursing research council or your program's IRB liaison about whether your project needs full review, expedited review, or qualifies as exempt quality improvement, since this determines your realistic start date more than almost anything else in the proposal.
It's worth building your proposal document in the order your committee will actually read it, not the order you thought of the pieces. Lead with the problem statement so the reader immediately understands the stakes, follow with just enough evidence review to justify the intervention (not an exhaustive survey of the field), then the framework, then the implementation and evaluation plan. Resist the urge to pad the evidence-review section to look more thorough — a tight, well-chosen set of sources that clearly supports your intervention reads as more credible to a committee than a bloated review padded with tangentially related studies. If your program requires a formal defense of the proposal before you begin implementation, treat that defense exactly like a dissertation proposal defense: anticipate the three or four hardest questions a skeptical committee member would ask about feasibility, measurement, or approval, and have a direct answer ready for each one rather than hoping the topic doesn't come up.
From picking the right idea to a full proposal — problem statement, framework, methodology, and evaluation plan.
A DNP project is practice-focused rather than knowledge-generating: it applies existing evidence to solve a specific organizational or clinical problem and is evaluated on implementation and outcomes, while a PhD dissertation is expected to produce new, generalizable knowledge through original research. Structurally they look similar — problem statement, framework, methodology, findings, discussion — but a DNP project's methodology chapter usually centers on program evaluation or quality-improvement design rather than a traditional research design, and its findings are scoped to "did this work here" rather than "what does this tell us broadly."
Yes, and it's a common, sensible path. A BSN capstone identifying a practice gap and proposing an intervention can become the seed of a much more developed DNP project years later, once you add a formal framework, a longer implementation window, and a rigorous evaluation design. Just be honest with your DNP committee about the earlier work and be prepared to substantially deepen the scope rather than resubmitting the same document.
Often not a full IRB review — many QI projects qualify for exempt or expedited review because they're implementing already-established evidence rather than testing something new. But "often not full review" isn't "never any review," and the determination is made by your facility's research office or IRB, not by you. Submit early, because these determinations can take weeks.
Specific enough to name a population, a setting, and an intervention in one or two sentences. You don't need a finished proposal, but "I want to look at fall prevention" is too broad; "I want to evaluate whether hourly rounding reduces falls on our 32-bed medical-surgical unit" is a workable starting point for a first conversation.
This is common enough that it's worth having a backup idea ready before you submit for approval. Often a nearby alternative — a different unit, a slightly different outcome measure, or a QI framing instead of a research framing — will clear approval faster than your original idea. Don't treat a denied access request as a dead end; treat it as a scoping signal.
A BSN or MSN capstone typically needs a focused review of 10-20 recent, credible sources directly supporting your intervention. A DNP project usually needs a broader review — often 25-40 sources — because you're also justifying your framework choice and situating the problem in a wider body of evidence, closer in scope (though not full systematic-review depth) to a dissertation literature review chapter.
Yes — what we bring is the structural and methodological expertise that underlies any capstone or doctoral project: scoping a defensible problem, choosing and justifying a framework, designing a rigorous evaluation plan, and writing findings and discussion sections that hold up under committee questioning. That expertise doesn't depend on nursing-specific history; it depends on understanding how doctoral and capstone-level work is structured, which is exactly what we've built this site around.
Most DNP committees expect at least one full implementation cycle with a measurable pre/post window — commonly 8 to 16 weeks of active implementation, sometimes evaluated again at 6 or 12 months for sustainability. Shorter windows struggle to show a credible effect; much longer windows risk running past your program's timeline, so this is a key feasibility check before you finalize your idea.
For capstones and DNP projects, lean toward the well-supported side rather than the original side. Unlike a PhD dissertation, where originality is the whole point, a capstone or DNP project is judged on how well you translate existing, credible evidence into your specific setting. An idea with a strong evidence base behind it is easier to justify, easier to get approved, and easier to defend — save the more exploratory, less-established ideas for a future research doctorate if that's a path you want to pursue later.
Audience and purpose. A dissertation chapter is written to contribute to a scholarly conversation and withstand a doctoral committee's scrutiny of your original contribution to knowledge. A capstone or DNP project document is written to demonstrate that you can apply existing evidence competently to a real practice problem and evaluate the result honestly. The writing itself is often more concise and more oriented toward practical recommendations, even though the underlying structure — problem, evidence, method, findings, discussion — looks remarkably similar on the page.