DNP 955 Topic 2: DPI project timeline
The tasks you control are the easy part. What decides whether this timeline survives is the queue at the IRB and the availability of people who do not report to you.
Editorial process
Last reviewed · August 15, 2026
A timeline is a dependency map, not a wish list
Timelines for doctoral projects fail in a consistent way, and it is not because the writing took longer than expected. It is because of dependencies on other people: committee review turnaround, site permission, IRB submission windows and revision cycles, data access approval, and the availability of whoever has to actually deliver the intervention. Those have queue times you do not control and cannot compress by working harder. So build the timeline around them. Find the real numbers — how often your IRB meets, how many submissions come back with modifications, how long your chair takes on a full draft. The timeline also covers two phases with different risk profiles. The proposal phase is dominated by review and approval, where delay comes from other people. The project phase is dominated by recruitment and data collection, where delay comes from the world: slow enrolment, a site that reorganises, a season that changes the case mix.
Then work backwards from the fixed points. Programme milestones and course end dates are immovable; your writing schedule is not. Identify the critical path — the chain of dependencies where any slip moves the end date — and note that IRB approval sits on it for almost every project, which is why it should be submitted earlier than feels necessary. Build in explicit slack rather than hoping, since a plan with no float is a plan that fails on its first delay, and there is always a first delay. Two things are worth marking specifically: the tasks that can run in parallel with waiting, so a review period is not dead time, and the decision points where a delay should trigger a change of scope rather than a longer timeline. A timeline that identifies in advance what you would cut is far more useful than one that assumes nothing will go wrong.
Likely learning objectives
Inferred from the brief — check these against your own rubric.
- 01Build a schedule around external dependencies rather than own tasks.
- 02Identify the critical path through a project.
- 03Use observed turnaround times rather than optimistic estimates.
- 04Plan slack and scope-reduction triggers in advance.
Read the full question
Review every instruction before using the planning guidance that follows.
Turn the brief into deliverables
- 01A timeline covering both the proposal and the project.
- 02External dependencies with realistic queue times.
- 03The critical path identified.
- 04Explicit slack and parallel activity.
- 05Decision points where scope would be reduced.
Fixed dates first, then work backwards
Fixed points
Establish the immovable programme milestones and end dates.
External dependencies
List approvals and other people's tasks with their real turnaround.
The critical path
Identify the chain where any slip moves the end date.
Slack and parallel work
Build in float and identify what can proceed during waits.
Scope triggers
Define the delays that would change the project rather than the date.
How long each approval actually takes
Recommended databases
- Your IRB's meeting calendar
- Your programme's milestone schedule
- Your chair's stated turnaround
- The DPI Project Timeline resource
Search sequence
- 1.Find your IRB's submission deadlines and meeting dates for the whole period.
- 2.Ask what proportion of submissions in your category are approved first time.
- 3.Confirm your site's own permission process and who signs it.
- 4.Ask your chair how long a full draft review typically takes.
Reference shortlist
These are authoritative starting points, not a ready-made bibliography. A qualified reviewer must confirm that each source fits the assignment and supports the claim beside which it is cited.
Nothing here is cleared for citation until you have read it.
- 01
Research Ethics
StatPearls, NCBI Bookshelf · 2023
On the research ethics review process, which is the dependency most often underestimated in these timelines.
- 02
Informed Consent
StatPearls, NCBI Bookshelf · 2023
Covers consent requirements, which determine how much IRB scrutiny a submission attracts and therefore how long it takes.
- 03
Implementation strategies for large scale quality improvement initiatives in primary care settings: a qualitative assessment
BMC Primary Care · 2023
An implementation study documenting where projects actually lost time, which is rarely where the plan assumed.
- 04
Quality Improvement Methods (LEAN, PDSA, SIX SIGMA)
StatPearls, NCBI Bookshelf · 2024
On improvement methods and their cycle times, useful for estimating the implementation phase realistically.
Review before submission
Common mistakes
- Scheduling only the tasks you control.
- Assuming IRB approval on first submission.
- Building a plan with no float anywhere in it.
- Treating review periods as dead time.
Submission checklist
- Are external queue times based on actual figures?
- Is the critical path marked?
- Is there slack, and is it where the risk is?
- Have you said what you would cut if a delay hits?
Use this guide to plan and review your own work. Follow your institution's rules and read our academic-integrity policy.
Written by
Aaron Bishop
MA, Education
assignment interpretation and research-methods coaching across disciplines
Aaron leads the EssayCrackers editorial desk. He works on how assignment briefs are read — what a rubric is actually asking for, and where students most often answer a different question than the one set.
Reviewed by
Dr. Nathan Cole
PhD, Rhetoric & Composition
Argumentation and thesis development
Nathan teaches first-year composition and directs a university writing center. He reviews EssayCrackers guides for argumentative soundness and citation accuracy.