How to Write a DNP Prospectus: Alignment First

A DNP prospectus is not rejected because the topic is unimportant or because the student lacks knowledge. It is rejected because the ten points do not align. The problem statement describes one thing, the PICOT question measures another, the design cannot actually answer that question, and the data analysis plan would work for a study that the project was never designed to be. A committee that traces that chain from Point 1 to Point 10 and finds it broken will return the prospectus for revision, sometimes more than once, because alignment cannot be corrected by rewording; the underlying logic has to change.

This guide works through the prospectus and the ten-point framework with alignment as the organizing principle. It covers what each point requires, what the chain between them must look like, and the misalignment patterns that account for most returns. If you are still working out whether your project belongs at the MSN or DNP level, our article on MSN vs DNP project differences covers the execution-level distinction in detail.

Once you have confirmed you are working at the doctoral level, our DNP project support is built around both the AACN criteria and your program's specific framework.

Quick Answer:

A DNP prospectus is a concise pre-proposal document that outlines the concept, framework, and design of the planned project before a full proposal is written. In programs that use the ten strategic points, each point covers a discrete element of the project design. The central evaluation criterion is alignment: the problem must flow to the purpose, to the PICOT-D question, to the sample, to the methodology and design, to the data collection, and to the analysis plan, without a break in the chain. The purpose statement, which integrates all of this into a single sentence, is written last. The ten-point framework originated at Grand Canyon University and is used primarily in GCU-based DNP programs under the Direct Practice Improvement (DPI) project model; other programs use different frameworks, so your program handbook is always the definitive source.

What a Prospectus Is and Is Not

The prospectus is a pre-proposal document. It is shorter and less formal than a full proposal, and it exists to establish shared understanding between the student and the project team before the formal proposal process begins. A proposal is action-oriented and seeks approval to proceed; a final project report documents what happened and evaluates outcomes. The prospectus sits before both of them, as a conceptual sketch that answers the question: Is this project worth proposing?

Most programs use the prospectus as a gatekeeping document. A well-developed prospectus that passes team review proceeds to the formal proposal stage. A prospectus that reveals a misaligned design, an impossible data source, or a scope that constitutes research rather than quality improvement is returned before the student invests weeks in a full proposal. The prospectus is therefore not just a formality; it is the single most efficient point in the process to catch problems and fix them. Our guide to choosing a DNP capstone topic covers the topic-feasibility screen that should happen before the prospectus is begun.

The Ten Strategic Points: Origins and Purpose

The ten strategic points framework originated at Grand Canyon University and is documented in doctoral program course materials. It has been adapted for the DNP as the Direct Practice Improvement (DPI) project model, and it is now used across GCU-based DNP programs as the structure for the prospectus, the proposal, and the final project. Other programs use different frameworks, so the ten-point structure is not universal; some programs use a five-chapter format, some use SQUIRE 2.0 as the organizing framework, and some have proprietary alignment tools. Whatever framework your program requires, the underlying logic is the same: every element must align with every other element, and that chain must be traceable from the practice problem all the way to the data analysis.

The ten points in the GCU/DPI framework are, in order: the broad topic area; the literature review, including background, the gap, theoretical foundations, a thematic review, and a summary; the problem statement; the sample and location; the clinical question in PICOT-D format; the definition of variables; the methodology and design; the purpose statement; the data collection approach; and the data analysis approach. Each point builds on the ones before it, and each constrains the ones that follow.

Table 1: The Ten Strategic Points — What Each Requires and What Misalignment Looks Like

The Chain That Must Hold

Alignment is not a conceptual ideal; it is a structural requirement that committees check systematically. The chain runs as follows. The problem statement names a specific, measurable practice gap at a specific site. The purpose statement synthesizes that problem into a single sentence that also names the methodology, design, and sample, and it must state the purpose precisely enough that a reader can trace it directly back to the problem and forward to the PICOT-D question. The PICOT-D question scopes the intervention, comparison, outcome, time frame, and, critically, the data source, which is the D. The sample and location must match the site where that data lives. The methodology and design must be appropriate for answering the PICOT-D question. The data collection approach must collect the data the design needs. The data analysis approach must analyze the data in a way that answers the question.

A break anywhere in that chain is a misalignment. The most common break is between the problem statement and the outcome measure: the problem is about one thing, and the PICOT-D question measures another. The second most common is between the design and the analysis: the student labels the design as a pre-post quality improvement study but describes an analysis plan involving inferential hypothesis testing that would only make sense if the project were a research study. Understanding what distinguishes QI data from research data, and when each type of analysis is appropriate, is covered in our guide to QI versus research versus EBP.

The PICOT-D Question: What the D Changes

Programs that use the ten-point framework use PICOT-D rather than standard PICOT for the clinical question. Standard PICOT covers Population, Intervention, Comparison, Outcome, and Time. The D, which stands for Data, adds the identification of the data measures and the digital or electronic data source where those measures already live, including the source format and extract format.

The D component was developed because standard PICOT does not capture the data-availability question, which is decisive for a DNP practice improvement project. A project that plans to measure A1C reduction must not only specify A1C as the outcome; it must identify that A1C is recorded in the practice management system, that it is extractable as a numerical value, and that it can be pulled for the relevant patient cohort within the project timeline. A student who discovers mid-project that the planned outcome is not captured in a retrievable form has a data-access problem that the PICOT-D requirement would have surfaced at the prospectus stage. This concept was first published by Elias, Polancich, Jones, and Convoy in the Journal of Nursing Education in 2015, who argued that standard PICOT "falls short" for DNP scholarly projects that need to compare current real-world practice against the evidence base.

Our guide to how to write a PICOT question covers the standard PICOT framework; the D extension applies the same scoping logic to identifying the data source before the project begins.

For students who need help appraising the evidence base before constructing the PICOT-D question, our EBP and PICOT support is designed for that earlier stage of the work.

The Purpose Statement: Written Last, Not First

The purpose statement is Point 8 in the ten-point sequence, which surprises many students who expect to write it at the beginning. It belongs at Point 8 because it is a synthesis document: it integrates the problem, the methodology, the design, the sample, and the location into a single sentence that can stand alone as a complete description of the project. You cannot write that synthesis accurately until the other seven points are clear.

The purpose statement follows a consistent structure: "The purpose of this [methodology] [design] project is to [project aim] in [population] at [location]." Every element named in that sentence must be defined in the surrounding points. If the purpose statement names a pre-post quality improvement design, Point 7 must describe a pre-post design. If it names a facility's medical unit as the location, Point 4 must name that unit as the sample location. If those correspondences break down, the purpose statement is internally inconsistent and will be flagged in review.

The discipline of writing the purpose statement last is the same discipline our MSN vs DNP article describes at the level of project design. Every element serves the central purpose, and the central purpose must be traceable to every element.

The Literature Review and the Theoretical Framework

Point 2 in the framework requires more than a summary of research. It has four parts: the background that contextualizes the practice problem, the identification of the practice gap, the theoretical or conceptual framework that grounds the project, and a thematic review of the evidence organized around the themes that support the intervention.

The theoretical framework is where students most often write something decorative rather than functional. Naming a nursing theory in the literature review and then never referencing it again in the design or the evaluation plan is a sign that the framework is not doing any conceptual work. A functional framework shapes the design: if you choose Dorothea Orem's self-care model, that choice should determine how you define the outcome, how you structure the patient education component, and how you evaluate whether the intervention worked. Our guide to applying a nursing theory to a DNP capstone goes through that integration in detail, and the /nursing/nursing-theory-concept-analysis service covers the full theoretical grounding work.

Our nursing theory and concept analysis support is available for students who need help selecting and operationalizing the framework before the prospectus is submitted, since committee reviewers are more likely to pass a prospectus where the theoretical grounding is substantive than one where the framework appears as a list item with no functional connection to the design.

Methodology, Design, and What QI Allows

Point 7 is the point where the QI-versus-research distinction becomes concrete, and it is the source of one of the most common misalignments. A DNP practice improvement project is a quality improvement initiative, not a research study. That means the design should be described in QI terms: a pre-post design measuring a process or outcome metric before and after an intervention, evaluated using run charts, statistical process control charts, or descriptive statistics appropriate for the data and the timeline.

Students who have completed graduate research methods courses sometimes describe their QI design using research language: null hypothesis, control group, Type I error, and power analysis. That language signals a research design, not a QI design, and a committee that reads it will ask whether the project needs IRB review rather than QI determination. The AACN 2015 white paper is explicit that clinical significance guides DNP projects the way statistical significance guides research, and reporting standards for QI work follow SQUIRE 2.0 rather than CONSORT or STROBE.

For the analysis plan at Point 10, this means: if the design is a pre-post QI study, the analysis plan should describe run chart analysis, descriptive statistics comparing baseline and post-intervention measures, and compliance or process-measure tracking, not t-tests intended to test whether a pre-specified null hypothesis should be rejected. SQUIRE 2.0 at its Results item (item 13) specifies exactly what a QI results section must report, and aligning the analysis plan in the prospectus to those requirements is a design decision, not a writing task.

The EBP framework governing the implementation sequence should also be named in Point 7, since the committee will trace it from the literature review through the design. Our guide to the Iowa Model, Johns Hopkins, and JBI frameworks covers how to choose and defend that selection.

Table 2: Three Common Misalignment Cases and Their Corrections

Common Reasons Prospectuses Are Returned

Beyond misalignment, several other patterns account for most returns. Scope inflation is the most common: the problem statement describes a unit-level gap, but the design proposes a facility-wide or multi-site implementation that cannot realistically be completed in the project timeline. Inaccessible data is a close second: the PICOT-D outcome is named without confirming that the data source exists and is extractable, and the committee asks for documentation of data access before approving. The absence of an organizational sponsor is a third: a prospectus that does not name a clinical champion with actual authority over the change area lacks the site-access infrastructure the project depends on.

The fourth pattern describes a research project as a QI project without checking the boundary. A study that uses a control group, collects de-identified data with the intent to publish generalizable findings, or requires participant consent beyond what organizational QI review would require is likely research, not QI. Our guide to the QI versus research distinction covers where that line sits and how your institution draws it. Getting that classification wrong at the prospectus stage is costly; it can force a full redesign of the methodology.

Understanding what constitutes a genuine practice gap before any of these issues arise is the first step to preventing them. Our guide to identifying the DNP practice gap covers the diagnostic work that should precede the prospectus.

Before the Prospectus: What Should Already Be Settled

A prospectus works best when several things are already in place. The practice gap should be identified and measurable, meaning you have a baseline data point or a documented discrepancy between current practice and the evidence. The organizational sponsor should be named and engaged, not assumed. The data source should be confirmed accessible, meaning someone with data-access authority has confirmed that the planned outcome variable is captured in the EHR or quality dashboard and can be extracted for your patient population and time period.

The EBP framework should be selected and matched to the project type. Our guide to question frameworks beyond PICOT covers when PICOT, PEO, PICO-SD, or PCC better fits the clinical question type, so the PICOT-D question captures the right construct. The IRB or QI determination should also be underway before the prospectus is submitted.

None of these is a writing task; they are design and infrastructure decisions that determine whether the prospectus can succeed. Our research proposals support helps students at both the MSN and DNP levels build this infrastructure and translate it into the written document their program requires.

If you are working at the master's level, our MSN capstone support covers the prospectus and proposal for MSN-level scholarly projects.

Our capstone projects hub gives an overview of what support is available at each degree level and what to expect at each stage of the process.

Frequently Asked Questions

What is the difference between a DNP prospectus, a proposal, and the final project?

The prospectus is a brief pre-proposal document that outlines the concept and design before any formal approval is sought, primarily to establish alignment and feasibility. The proposal is more detailed and action-oriented; it seeks formal approval from the project team and sometimes the institution before implementation begins. The final project report documents implementation, results, evaluation, and sustainability, and is the document typically submitted for program completion and deposited in a repository.

Is the ten-point framework required for all DNP programs?

No. The ten strategic points framework originated at Grand Canyon University and is used primarily in GCU-based DNP programs under the DPI project model. Other programs use different frameworks, including five-chapter formats similar to a dissertation, SQUIRE 2.0 as an organizing structure, or institution-specific alignment templates. The underlying principle, alignment across all elements, applies everywhere, but the specific format is always program-determined. Check your program handbook.

What is PICOT-D, and why does it differ from standard PICOT?

Standard PICOT covers Population, Intervention, Comparison, Outcome, and Time. The D adds Data: the identification of the specific electronic data sources, measures, source format, and extract format available at the practice site. The D was developed because DNP practice improvement projects depend on pre-existing institutional data, and a project whose outcome cannot be extracted from available data systems has a fatal feasibility problem. PICOT-D was first described by Elias and colleagues in 2015 in the Journal of Nursing Education.

Why is the purpose statement written last among the ten points?

Because the purpose statement integrates all preceding points into a single sentence that names the methodology, design, sample, and location, it cannot accurately synthesize what has not yet been decided. Students who write the purpose statement first and then build the other points around it usually produce misaligned documents, because the purpose statement implies a project that the subsequent points do not support; writing it last forces the synthesis to reflect actual decisions rather than aspirations.

What does alignment mean in a prospectus review?

Alignment means that every element is logically consistent with every other element: the problem statement produces the practice gap, the practice gap produces the PICOT-D question, the question is answerable by the design, the design uses the data source identified in the D component, the sample is located where that data lives, and the analysis plan produces information that answers the question. A committee traces this chain explicitly, and a break at any point is sufficient cause to return the document.

Trace the Chain Before You Submit

The ten strategic points are not ten separate things to write; they are a single chain that must hold from end to end. Before submitting the prospectus, trace it yourself: read the problem statement, then ask whether the purpose statement answers the same problem. Read the PICOT-D question, then ask whether the design can answer it, whether the data source can capture the outcome, and whether the analysis plan produces an answer to the question rather than a significance test for its own sake. If you can trace the chain without a break, the prospectus is ready for team review. If you find a break, fix the logic before you fix the wording.

If you would like a specialist to trace your chain before you submit, share your draft prospectus, and you will have an itemized quote within 2 to 4 business hours, no obligation.