Before a DNP project can propose a solution, it has to prove there is a problem worth solving at this specific site. This guide covers how to establish the current state of practice, describe a credible, evidence-based desired state, and state the gap between them clearly enough to justify the project that follows.
Quick answer. A needs assessment establishes the current state of practice at your site, the desired state described by current evidence or guidelines, and the specific gap between them. That gap is what justifies the entire project; a project addressing a gap nobody can demonstrate exists is difficult to defend to a committee.
Early in a DNP project, before a solution is proposed, the project has to answer a more basic question: is there a real, demonstrable problem here, and how big is it. That is the job of a needs assessment and gap analysis. Done well, it gives a reader three clear pieces of information: what is currently happening in practice at the site, what current evidence or standards say should be happening, and how far apart those two things are.
This section matters more than students sometimes expect, because it is the foundation the rest of the project sits on. A PICOT question, an intervention, and an evaluation plan are all, in effect, answers to the gap identified here. If the gap is vague, poorly evidenced, or assumed rather than demonstrated, everything built on top of it inherits that weakness, which is why committees often scrutinize this section closely even though it can feel, to students, like a formality on the way to the "real" project.
A common early draft states something like "patient education on discharge could be improved," without specifying what is currently happening, what a better version would look like, or how the writer knows either of those things. That framing describes a general area of interest, not a needs assessment. A needs assessment answers, specifically, what is happening now, what should be happening based on a cited source, and what the difference is.
The current state describes what is actually happening in practice at your site right now, and it needs to be grounded in some form of real information rather than a general impression. Several sources are commonly used, alone or in combination, depending on what is accessible and appropriate at your site.
Whichever sources you use, any real, identifiable site data must follow your site's and your program's data-access, privacy, and, where applicable, IRB or ethics-review requirements. Where full data access is not available at the proposal stage, it is appropriate to describe what is planned and cite general or published evidence of the problem's prevalence in similar settings, while being transparent about what has and has not yet been directly observed at your specific site.
The desired state describes what evidence-based practice recommends, and it needs a cited source behind it, not an assumed standard of "best practice." A desired state with no citation reads as the writer's opinion of what should happen, which does not carry the same weight as a stated recommendation from a current clinical practice guideline, professional organization, or accreditation or regulatory body.
State the desired practice specifically enough that a reader could recognize it if they saw it in place, rather than in general terms like "improved communication," which cannot be compared cleanly against a current state.
The gap is the specific, stated difference between the current state and the desired state, and it is the sentence or short section that everything else in the project is built to address. A strong gap statement names both sides of the comparison and, where possible, gives some indication of scope or significance, such as how often the current practice falls short or how many patients or staff are affected.
| Vague | Specific |
|---|---|
| Discharge education could be improved. | Chart review indicates that teach-back is documented in a minority of discharge encounters for patients newly prescribed insulin, though current guidelines recommend teach-back for all such patients before discharge. |
| Handoff communication is sometimes incomplete. | Staff-reported handoff omissions most often involve pending tasks and pending results, while the unit's own handoff policy requires both to be stated verbally at every shift change. |
| Fall prevention practices vary. | Current fall-risk reassessment is not consistently repeated after a change in patient condition, though the adopted fall-risk protocol requires reassessment following any status change. |
Each specific version names a current practice, a desired practice drawn from a policy or guideline, and a clear point of comparison. That specificity is what turns a general concern into a defensible, project-justifying gap.
Share your topic, setting, and any available site information with your brief, and a specialist can outline, draft, or edit this section for you. The price is shown before you pay, and every delivered paper includes 14 days of free revisions.
The table below is invented to show the pattern for a hypothetical unit-level problem. It contains no real site or data.
| Element | Illustrative entry |
|---|---|
| Current state | Informal staff interviews and a brief chart review suggest that post-fall huddles are held inconsistently after inpatient falls on the unit. |
| Desired state | The hospital's own fall-prevention policy, aligned with published fall-prevention guidelines, calls for a structured post-fall huddle after every inpatient fall. |
| Gap | Post-fall huddles are not consistently occurring, despite an existing policy requiring them after every fall, suggesting an implementation gap rather than a knowledge gap. |
| Implication for the project | The project can focus on implementation supports, such as a huddle prompt or checklist, rather than staff education on huddle content alone. |
Notice that the gap here is framed as an implementation gap, not a knowledge gap, which meaningfully changes what kind of intervention makes sense, an insight the gap analysis itself surfaced.
A needs assessment built on a single source of information is more vulnerable to challenge than one that draws on two or three independent sources pointing in the same direction. Triangulation, using more than one method or source to confirm a finding, is a standard way to strengthen the credibility of a current-state claim, and it does not require a large or complex study to apply.
| Primary source | Confirming source | What agreement between them shows |
|---|---|---|
| Chart audit indicating inconsistent documentation of a required step | Staff interviews describing the same step as frequently skipped under time pressure | The gap is a real, recognized practice pattern, not an artifact of how records happen to be kept |
| Staff survey reporting low confidence in a procedure | Direct observation showing hesitation or workaround behavior during the same procedure | A perceived gap in confidence corresponds to an observable gap in practice |
| Existing policy requiring a specific action | Incident or quality data suggesting the action is not reliably occurring | The written standard and the lived practice have genuinely diverged |
Where full triangulation is not feasible within the constraints of a proposal-stage project, being transparent about relying on a single source, and naming that as a limitation to address as the project moves forward, is more defensible than presenting a single-source finding as though it were fully confirmed.
Occasionally, different sources point in different directions, for instance, a chart audit suggesting a practice is followed consistently while staff describe frequent workarounds. Rather than picking whichever source supports the project you already wanted to propose, name the discrepancy directly and reason through it. A documented practice may be followed only when observed, or staff perception may lag behind a recent process change; either explanation is worth stating rather than quietly ignored.
Beyond gathering the right evidence, how the needs assessment section is written affects whether a committee reads it as rigorous or as a collection of loosely connected observations. A few conventions consistently help.
| Weak | Stronger |
|---|---|
| Patient falls are a problem on many units and something should be done about them. | Post-fall huddles, required by the unit's own fall-prevention policy, are inconsistently held, based on staff interviews and a review of recent fall documentation. |
| Nurses could benefit from better training on the new equipment. | Observation of equipment use during three shifts found inconsistent adherence to the manufacturer's documented safety checklist, despite mandatory annual training on that checklist. |
Students sometimes conflate the needs assessment with the literature review, since both draw on published evidence, but the two sections do different jobs and a committee expects to see that difference reflected in how each is written.
| Aspect | Needs assessment / gap analysis | Literature review |
|---|---|---|
| Primary purpose | Establish that a specific, local gap exists and matters | Establish what is broadly known about the topic and the intervention |
| Focus of evidence used | Guidelines and standards that define the desired state, plus local/site data for the current state | Studies evaluating interventions, outcomes, and prior approaches to the problem |
| Typical length | Shorter, tightly focused on establishing current state, desired state, and gap | Longer, synthesizing a broader body of evidence by theme |
| Where it points | Directly toward the PICOT question and intervention chosen | Toward the theoretical or evidence basis for why that intervention should work |
Some programs combine these into a single section, and others keep them fully separate; either way, the needs assessment's job is to establish that a specific gap exists here, while the literature review's job is to establish what evidence says about closing gaps like it in general. Keeping that distinction in mind while drafting helps prevent the needs assessment from drifting into a second, redundant literature review.
A clearly stated gap does more than justify the project; it also sets up the next two pieces of project planning. The gap is what your PICOT question is built to address, and it is often what a logic model's inputs and activities are designed around. See our DNP PICOT question development guide and our logic model for a DNP project guide for how each builds directly on the gap established here.
Illustrative example, not a real client. This short story is invented to show the pattern, and it contains no real people, sites, or data.
The problem. A DNP student drafted a needs assessment stating that "wound care documentation needs improvement," with no supporting detail.
The tension. Her committee asked how she knew documentation needed improvement, and against what standard, questions her draft could not yet answer.
The turn. She arranged a small, properly authorized chart review against the unit's own wound-care documentation policy, and found a specific, recurring gap in how often wound measurements were documented at required intervals.
The proof. Her revised section named the current practice, cited the existing policy as the desired state, and stated the gap in specific terms her committee could evaluate.
The payoff. Because the gap was concrete, her proposed intervention, a documentation prompt built into the existing wound-care flowsheet, followed logically from it, and her committee's remaining questions moved to implementation detail rather than whether the problem was real.
Describe what data access is planned and cite published evidence of the problem's prevalence in comparable settings in the meantime, being transparent about what is confirmed versus anticipated. Follow your program's expectations for what a proposal-stage needs assessment must include.
Specific enough that a reader could recognize the desired practice if they observed it, and specific enough to compare directly against the current state you described. A general aspiration is not the same as a stated practice standard.
Yes, some projects do identify a genuine knowledge gap, where staff or patients lack information rather than failing to apply known information. Be clear about which kind of gap you are describing, since it changes what kind of intervention is appropriate.
It depends on your institution, your data sources, and whether the activity is considered quality improvement or research under your program's definitions. Ask your program early, and see our IRB application and research ethics guide.
Length depends on your program's template, but the section should be long enough to establish the current state, desired state, and gap with real supporting detail, not so long that it drifts into content that belongs in the literature review.
A needs assessment and gap analysis is not a formality to move past quickly; it is the evidence that your project addresses a real, demonstrable problem at your site rather than an assumed one. Ground the current state in real information, ground the desired state in a cited source, and state the gap specifically enough to carry the weight of everything you propose to do about it.
Want this section outlined or drafted for your project? Get my instant quote. The price is shown before you pay, every delivered paper includes 14 days of free revisions, and refund terms are on the money-back guarantee page. Please use any model paper in line with your institution's academic-integrity policy.