The DNP project proposal is the document that gets a project approved — by a committee, an institutional review process, or both — before any implementation work begins. It's more detailed than a general capstone proposal because it has to convince a doctoral-level committee that the project is grounded in evidence, theoretically sound, and feasible to execute. This guide goes section by section through what a strong DNP project proposal includes, at DNP depth.
How a DNP Proposal Differs From a General Capstone Proposal
Our nursing capstone proposal help guide covers the general shape of a capstone proposal: problem statement, PICOT question, brief literature review, proposed methodology, and timeline. A DNP project proposal covers the same ground but at greater depth and with additional expectations specific to doctoral-level practice projects:
- A more developed significance section connecting the local problem to broader healthcare priorities (national quality measures, organizational strategic goals, cost implications)
- A theoretical or conceptual framework section that isn't just named but actively applied to explain how the proposed change process will work
- A preliminary literature review substantial enough to demonstrate the evidence base — often several pages, not a paragraph
- A more detailed project plan including stakeholder engagement, resource requirements, and a realistic implementation timeline
- Often, an early discussion of IRB/ethics considerations, since DNP projects involving staff or patient data typically require some form of institutional review (see IRB approval for nursing students)
The proposal is, in effect, a smaller-scale version of the full project's first three chapters — written persuasively enough that a committee approves moving forward with implementation.
DNP Project Proposal Sections at a Glance
| Section | Depth Expected | Key Question It Answers |
|---|---|---|
| Problem statement | 1–2 paragraphs, specific and local | What clinical gap exists, where, and why now? |
| Significance | 1–2 pages, connects local to broader context | Why does this matter beyond one unit or department? |
| PICOT question | One precise, well-formed statement | What, specifically, will this project investigate? |
| Theoretical/conceptual framework | 1–3 pages, applied not just named | What model explains how the proposed change will work? |
| Preliminary literature review | 3–8 pages depending on program | What evidence supports this intervention for this population? |
| Project plan / methodology overview | 2–5 pages | How, concretely, will this be implemented and measured? |
| Timeline and feasibility | 1 page, often a table or Gantt-style chart | Can this realistically happen within the program's constraints? |
| IRB/ethics considerations | 1 page or more depending on program | What approvals or protections are needed before starting? |
The Problem Statement and Significance: Local Gap, Broader Context
The problem statement should be specific and local — a particular gap, on a particular unit or in a particular population, evidenced by something concrete (a quality metric, an incident rate, a gap identified in a needs assessment). "Falls are a problem in healthcare" isn't a problem statement a DNP committee will accept; "Unit 4B's fall rate has exceeded the hospital's benchmark for three consecutive quarters, with X falls per 1,000 patient days compared to a benchmark of Y" is.
The significance section then does the work of connecting that local, specific problem to something larger — a national quality indicator (e.g., a measure tracked by CMS or The Joint Commission), the organization's strategic priorities, financial implications (cost of falls, length-of-stay impact), or a recognized practice gap described in the literature. This is where a DNP proposal earns its "doctoral" framing: it's not just "this is a problem here," but "this local problem is an instance of a broader, evidence-recognized issue, and addressing it here has implications beyond this unit."
The PICOT Question: The Hinge of the Whole Proposal
Everything else in the proposal either supports the PICOT question (significance, literature review, framework) or operationalizes it (project plan, timeline). Our PICOT project help guide and PICOT format guide cover how to construct this question; in a DNP proposal specifically, the question needs to be realistic given the resources, access, and timeframe a doctoral student actually has — not the ideal study a fully-resourced research team might run.
Theoretical Framework: Applied, Not Just Cited
A common weak point in DNP proposals is a theoretical framework section that names a model — the Iowa Model, PDSA, Lewin's Change Theory, the Diffusion of Innovations model — defines it in a paragraph, and then never refers to it again. A strong framework section instead uses the model's own structure to organize the proposal's logic.
For example, if the proposal uses the Iowa Model, the proposal might explicitly walk through the model's stages as applied to this project: how the "trigger" was identified (the local problem), how the evidence was assessed (the literature review), and how the planned implementation maps onto the model's "pilot the change" stage. If it uses PDSA, the project plan section might be explicitly organized around Plan-Do-Study-Act phases. The framework should feel load-bearing — if you removed it, the proposal's logic should visibly need it back.
The Preliminary Literature Review: Evidence for This Specific Intervention
Unlike a brief capstone proposal's literature paragraph, a DNP proposal's preliminary literature review needs to substantively demonstrate that the proposed intervention has an evidence base for the proposed population and setting. This typically means synthesizing multiple studies (not just citing them individually), discussing the level of evidence available, and being honest about gaps — a DNP committee is often more reassured by a proposal that says "evidence is strong for population X but more limited for population Y, which this project will help address" than one that overstates certainty.
This preliminary review will likely be expanded into the full Chapter 2 literature review later (see DNP literature review help), so building it thoroughly at the proposal stage saves substantial rework.
Building the Project Plan and Timeline Sections
- Describe the intervention in concrete, replicable detail — what exactly will be done, by whom, and how often
- Identify stakeholders (unit leadership, staff who will implement the change, any departments affected) and how they'll be engaged
- List the resources needed — staff time, materials, training, any technology or data system access
- Lay out data collection points: what's measured, how often, and using what tool or method
- Build a realistic timeline mapped to your program's actual academic calendar — including time for IRB approval, which often takes longer than students expect
- Address feasibility directly — acknowledge constraints (staffing, access, timeframe) and how the plan accounts for them
- Note IRB/ethics steps explicitly, even if the determination is "exempt" — committees want to see this has been considered, not assumed
Common Mistakes to Avoid
- A problem statement that's too general to be specific to your setting, population, or timeframe
- A significance section that doesn't connect the local problem to any broader quality measure, strategic priority, or recognized practice gap
- Naming a theoretical framework without using its structure anywhere else in the proposal
- A preliminary literature review that lists studies individually instead of synthesizing them toward a conclusion
- A PICOT question that's aspirational rather than realistic given the student's actual access and timeframe
- A project plan too vague to be implementable ("staff will receive education") without specifics on format, frequency, or who delivers it
- A timeline that doesn't account for IRB review time, which can take weeks to months depending on the institution
- Treating the proposal as disconnected from the eventual full project, requiring substantial rework later
Ready to Start?
Send your clinical problem area, program proposal template, and any preliminary sources you've gathered — we'll help build a proposal your committee can approve.
Get nursing writing helpExplore nursing servicesRelated Guides
DNP Project Proposal Guide FAQ
It goes deeper in several areas — significance tied to broader quality measures, an actively applied theoretical framework, a more substantial preliminary literature review, and a more detailed project plan with stakeholder and resource considerations.
It varies by program, but commonly 3–8 pages — substantial enough to demonstrate the evidence base, since much of it will be expanded into the full Chapter 2 later.
It helps to have one in mind early, since the framework should shape the project plan section — but if you're unsure which fits, we can help match one to your proposed intervention.
Significant changes usually need committee approval, but minor refinements are common — we can help revise the proposal and flag what else needs to stay consistent.
Most DNP proposals address this in some form, even if the eventual determination is "exempt" — committees want to see it's been considered. See IRB approval for nursing students.
Yes — this is a common starting point. Send your topic area, program template, and any constraints, and we can help develop the proposal from there.
The proposal essentially becomes the foundation for Chapters 1-3 of the final manuscript — see DNP capstone writing guide for how the full document builds on it.
Send the feedback along with the current draft — revisions are made to address each point while keeping the PICOT question, framework, and plan consistent throughout.