03 · What You Need to Know
How to Estimate Whether the Whole Research Project Fits
Start with the real deadline
Before constructing a timeline, determine what your deadline actually means.
Is it the date the final thesis must be submitted? The date a manuscript must reach your supervisor? The date of an oral defense? A graduation clearance deadline? The end of funding? The last date on which participants can be followed? These are not interchangeable.
A thesis submitted on June 30 may need to be complete weeks earlier if your supervisor requires time to review it. A defense may require submission to examiners before the defense date. Institutional procedures may impose formatting, clearance, or administrative deadlines after academic work is finished.
Identify every fixed external date first. Your usable research period ends earlier than the final calendar date whenever review or administrative processes must occur before that date.
List every major stage from question to final submission
A realistic timeline includes the whole project rather than only data collection.
Depending on the study, major stages may include refining the research question, literature review, protocol development, instrument development or adaptation, ethics or institutional review, site permission, data-access applications, pilot testing, recruitment, data collection, follow-up, transcription, data cleaning, coding, analysis, interpretation, writing, supervisor review, revision, formatting, and final submission.
Not every study requires every stage. An analysis of an immediately accessible public dataset may avoid recruitment entirely. A qualitative interview study may require transcription and iterative analysis. Laboratory work may require specimen preparation and equipment scheduling. Archival research may depend on travel and archive access.
The principle is to identify the work your particular study actually requires. University research-planning guidance commonly recommends constructing a detailed timeline or milestones that reflect the methodology and logistical steps needed to complete the project rather than treating the timeline as an isolated administrative requirement.
Break vague phases into tasks you can estimate
"Do the analysis" is difficult to estimate because it hides too much work.
A quantitative analysis phase might include importing files, checking coding, cleaning data, constructing variables, documenting exclusions, examining missingness, conducting descriptive analysis, checking relevant assumptions, running the planned models, sensitivity analyses, producing tables and figures, interpreting results, and revising the analysis after methodological review.
Likewise, "write thesis" may contain several chapters or sections, supervisor feedback, rewriting, reference checking, figure preparation, formatting, and final proofreading.
Break large phases down until you can make a meaningful estimate of their duration. The objective is not to schedule every fifteen minutes of your doctorate. It is to expose work that disappears inside optimistic labels.
Estimate duration from evidence whenever possible
Time estimates are stronger when they come from something more concrete than intuition.
For recruitment, use historical rates from the site, comparable studies, pilot information, or a recruitment funnel. For interviews, estimate the number of sessions and the time required for scheduling, conducting, processing, and analyzing them. For laboratory work, use equipment throughput and procedural duration. For restricted data, investigate the provider's application and provisioning process.
Your own previous experience can also inform estimates. If coding one interview has consistently taken several hours, planning to code twenty interviews in a weekend is not an efficiency strategy.
Where direct evidence is unavailable, make the assumption explicit and plan conservatively around its uncertainty.
Separate effort from elapsed time
Some research tasks require many hours of your work. Others require relatively little effort but consume substantial calendar time.
An ethics application might require several days of preparation but then spend weeks under review. A data request may take an afternoon to submit but months to approve. Laboratory specimens may require waiting periods during which other work can proceed. A supervisor may need a week to return comments on a chapter that took you two weeks to write.
Effort
The amount of researcher or team working time required to complete a task.
Elapsed time
The calendar time from the beginning of a task until the study can move beyond the dependency it creates.
Both matter. A task requiring only two hours of your effort can still determine the project timeline if you then wait six weeks for someone else's decision.
Map dependencies before adding up durations
Research is not always a simple sequence in which one task finishes before the next begins.
Some tasks cannot begin until another is complete. Participant recruitment may require the applicable ethics and site approvals. Analysis cannot begin in its final form until the necessary data exist. A longitudinal endpoint cannot be analyzed before participants reach the required follow-up period.
Other activities can overlap. Literature review and writing can continue during an approval period. Early interviews may be transcribed while later participants are still being recruited. Data-management code can sometimes be prepared before the final dataset arrives. Methods sections can often be drafted before results exist.
Draw these relationships explicitly. A timeline becomes substantially more realistic once you distinguish tasks that must be sequential from those that can genuinely run in parallel.
Find the chain of tasks that controls the completion date
Suppose your ethics review takes six weeks, recruitment takes twelve weeks, and analysis takes four weeks. Adding those numbers alone may still misrepresent the project if some writing can occur during recruitment or if site permission must follow ethics approval rather than occur simultaneously.
The important issue is the chain of dependent activities that determines the earliest date on which the project can finish.
Project-management terminology often calls this the critical path. You do not need sophisticated project-management software to use the underlying idea. Ask which tasks have to happen in sequence and which delay would push the final completion date later.
Protocol finalized The ethics application cannot be completed until the protocol and study materials are sufficiently developed.
Required approvals obtained Recruitment cannot begin until the approvals applicable to the study are in place.
Required sample recruited The final participant cannot complete the study before being enrolled.
Final follow-up completed The complete dataset cannot be finalized until required participant follow-up is finished.
Dataset prepared Final analysis depends on a sufficiently complete and checked analytical dataset.
Analysis completed The final results and discussion depend on the completed analysis.
Writing and revision completed Submission requires enough time after the results exist to interpret, write, receive feedback, and revise.
If one of these stages moves later, everything dependent on it may move as well.
Work backward from the deadline
Working backward is particularly useful for time-limited research. Monash University, for example, recommends starting from the end date and working backward when developing a proposed research timeline.
Begin with the date on which the final version must genuinely be ready. Reserve the time needed for final review, revision, formatting, and submission. Before that, reserve the period needed for complete writing and interpretation. Before that comes analysis and data preparation. Continue backward until you reach the present.
This approach protects later stages from a common planning failure: allowing data collection to expand until it consumes nearly the entire project period.
If working backward shows that recruitment would have needed to begin two months ago, the timeline has told you something important. Do not solve the problem by deleting the analysis and revision time.
Protect time for analysis
Researchers can underestimate analysis because the data appear to be the hard part. Once collection finishes, surely the statistics or coding will follow quickly.
Analysis often involves considerably more than running a command or reading transcripts. Data may require cleaning, coding, merging, transcription, validation, transformation, or management of missing information. The researcher may need to learn unfamiliar techniques, consult a statistician or methodologist, rerun analyses, check robustness, or resolve unexpected patterns.
If the analysis method is technically demanding, ask whether you have the skills required to conduct the study or whether additional learning and specialist consultation need to appear explicitly in the schedule.
Do not schedule advanced analysis as though your first attempt will automatically become the final one.
Protect time for writing before the data are complete
Writing should not necessarily begin after analysis ends.
Parts of the introduction, literature review, conceptual framework, and methods can often be developed while other research activities are underway. Maintaining methodological records and documenting analytical decisions as you work can also reduce the burden later.
University of Texas School of Public Health guidance on project planning explicitly encourages researchers to maintain a timetable and write as the project progresses rather than leaving all writing until the research phase has ended.
That does not mean finalizing conclusions before seeing the evidence. It means treating writing as an ongoing research activity rather than a final clerical step.
Reserve time for feedback and revision
A first complete draft is rarely the final submission.
Your supervisor, committee, coauthors, statistician, or other reviewers may identify unclear arguments, analytical problems, missing literature, inconsistencies, or presentation issues. You then need time to respond.
Revision can involve more than editing sentences. A reviewer may ask for an additional analysis, clearer justification of a methodological decision, restructuring of a chapter, or reconsideration of an interpretation.
If your timeline places completion of the first full draft immediately before the final deadline, it assumes that no meaningful revision will be necessary. That is a bold empirical hypothesis for a research project.
External dependencies deserve special attention
Some activities are largely under your control. Others are not.
External dependencies may include ethics review, institutional permissions, data-provider approval, recruitment through partner organizations, participant availability, laboratory access, equipment repair, transcription services, software procurement, collaborator input, or supervisor feedback.
Identify each dependency and ask what happens if it takes longer than expected.
Studies dependent on restricted data deserve particular attention because unconfirmed data access can become a single point of failure when no equivalent source exists.
For recruitment studies, estimate the final participant date
Do not schedule a participant-based study solely by writing "Recruitment: September to November."
Estimate the recruitment rate and determine when the required final participant is likely to enroll. If follow-up is required, add the full follow-up period for that participant.
NIMH recruitment policy illustrates this logic in clinical research by requiring realistic recruitment milestones and emphasizing that recruitment timing should allow for necessary start-up while ending with sufficient project time remaining for follow-up and analysis.
For a detailed recruitment estimate, first determine how much time recruitment and data collection realistically require.
Include learning time when the study requires unfamiliar methods
If your study requires software, analysis, laboratory techniques, qualitative methods, programming, or data-management procedures you have not yet mastered, the learning curve belongs in the timeline.
This does not mean you need expert-level mastery before starting. Researchers learn throughout projects. The mistake is scheduling an unfamiliar technique as though competence will appear exactly when the data arrive.
Training, practice datasets, pilot analyses, consultations, or supervised practice can sometimes occur while other stages are underway. Plan them deliberately.
Include administrative and logistical work
Research schedules often omit tasks because they do not look intellectually interesting.
Booking rooms, scheduling interviews, sending reminders, arranging travel, purchasing materials, preparing participant payments, managing consent records, naming files, backing up data, organizing references, obtaining signatures, coordinating collaborators, and formatting final documents all consume time.
Individually, these tasks may be small. Collectively, they can occupy a substantial portion of the working week.
A timeline that assumes every available hour can be spent on analysis or writing will usually overestimate your effective research capacity.
Estimate your actual available research time
A twelve-month project does not necessarily provide twelve months of full-time research.
You may also be teaching, taking courses, working clinically, holding another job, caring for family, attending required activities, or completing other academic responsibilities. Holidays, examinations, conferences, and institutional closures can further reduce available time.
Estimate how much focused research time you can realistically devote during an ordinary week or month. Then consider whether the tasks assigned to that period fit within that capacity.
This is particularly important for student projects. Calendar duration and researcher availability are not the same resource.
Add contingency where uncertainty actually exists
A realistic schedule should not assume that every uncertain event resolves at its fastest plausible speed.
Contingency should be targeted. A task entirely under your control and familiar to you may require relatively little buffer. A task dependent on participant recruitment, institutional review, external data extraction, equipment, field conditions, or another organization deserves more protection.
There is no universal percentage of extra time that makes every research timeline safe. The amount should reflect the uncertainty and consequences of delay associated with the particular task.
Do not simply add 20% to the end of the project and call the schedule realistic. Place flexibility where the risk actually occurs.
Use milestones that tell you whether the study is still on track
A timeline should help you manage the project after it begins.
Instead of only listing broad phases, identify meaningful milestones: ethics application submitted, site access confirmed, first participant enrolled, 25% recruitment reached, data collection complete, dataset locked, preliminary analysis complete, full draft submitted for review, revisions complete.
For recruitment-intensive clinical research, NIMH similarly emphasizes establishing realistic recruitment milestones from the outset and monitoring progress during the project.
Milestones reveal slippage while there is still time to respond. If a three-month recruitment period requires 50 participants per month and only 20 have enrolled after the first month, the timeline should trigger reassessment rather than silent optimism.
Build decision points for high-risk dependencies
Some delays require more than monitoring. They require a decision.
Suppose your project depends on restricted data that may take several months to approve. Determine the latest date at which those data can arrive while still leaving sufficient time for preparation, analysis, writing, and revision. If access has not been secured by that date, switch to the planned alternative.
The same logic can apply to recruitment sites, equipment, specialist support, or other critical resources.
A decision point prevents one uncertain component from consuming so much time that both the preferred project and the fallback become impossible.
Test the timeline against a plausible delay
Once the schedule looks complete, stress-test it.
What happens if ethics review takes three weeks longer? What if recruitment runs at 70% of the expected rate? What if one site withdraws? What if the data provider delivers the dataset a month late? What if your first analysis reveals a data problem requiring re-cleaning?
You do not need to model every catastrophe. Ask whether a modest and plausible disruption causes the entire project to miss its deadline.
If it does, the timeline may be technically possible but too fragile to call comfortably feasible.
Watch Out
A research timeline is not realistic merely because every task fits when nothing goes wrong. If one ordinary delay causes data collection, analysis, writing, and revision to collide at the end of the project, the schedule has little resilience and the study may need simplification or an earlier start.
A Gantt chart can expose problems that a list of dates hides
A simple Gantt-style timeline can be useful because it displays tasks across calendar time and makes overlaps and dependencies visible.
You do not need specialized software. A spreadsheet can show tasks in rows and weeks or months in columns. Mark when each task begins and ends, which activities overlap, and important milestones or decision points.
The visual representation often reveals problems immediately: writing has been given two weeks, three external approvals are assumed to happen simultaneously, recruitment continues into the analysis period, or a six-month follow-up somehow finishes four months after the study begins.
The chart does not make the study feasible. It makes your assumptions harder to hide from yourself.
If the timeline does not fit, change the study rather than the estimate
This is the most important principle.
If careful planning shows that the project requires fourteen months and you have eight, rewriting "14 months" as "8 months" does not make the study feasible.
You may need to narrow the population, reduce the number of research questions, remove a nonessential method, use an accessible dataset, shorten a follow-up period only if the revised question remains valid, recruit through additional appropriate sites, simplify an unnecessarily complex analysis, or choose another design.
The appropriate modification depends on what gives the study its scientific value. The objective is not simply to make the project shorter. It is to preserve the central research contribution while reducing demands that are not essential to it.