Scheduling a Research Project
The subject requires a timetable and teaches nothing about producing one. This page assembles a method from what it does say — scattered across four weeks — plus what its single worked chart demonstrates, with the seam between source and synthesis marked at every step.
What the subject actually requires, and where it says it
There is more scheduling instruction in the supplied material than a first reading suggests; the problem is that no week collects it. Read separately, each item looks like a passing remark. Read together, they are close to a specification.
THE SOURCE'S OWN SCHEDULING INSTRUCTIONS, COLLECTED
| What it says | Where it sits | What it leaves undefined |
|---|---|---|
| A proposed timeline for the research is required | The proposal's additional-information section | Form, granularity, units, detail |
| A timetable or project plan is a methodology component | A third proposal structure the same week supplies | Its relation to the timeline above |
| Create a timetable to avoid last-minute panics | The final week's do-and-don't checklist | How |
| Do not leave it to the last minute; do not overestimate the time you have | Same checklist | Any method for estimating what you have |
| Get ethical approval first; do not collect without it | The ethics week, and the same checklist | How long approval takes |
| Allow plenty of time for transcription; do not underestimate it | Same checklist, twice | Any figure at all |
| Start writing drafts early and show them to your supervisor | Same checklist | How early, how many |
| Take as much time as is needed for editing and polishing | The writing-up week | Any figure at all |
The checklist rows are paraphrased; the source reproduces that checklist from a methods text under a publisher's copyright line.
What follows is assembled rather than transcribed. Each section marks what comes from the source, what comes from the one worked chart in the dataset, and what is this library's synthesis. The chart is at a worked thesis schedule; its faults, instructive in their own right, at what goes wrong in a thesis schedule.
Gates first, because you do not control them
This library's synthesis, built on two things the source supplies: a documented thesis procedure in which work is submitted, reviewed and either approved or sent back at named points, and a worked chart on which ethical approval is a task with its own dates rather than an assumption. Neither is presented as a scheduling method. Together they support one.
A gate is any point at which somebody other than you has to say yes before the next thing can start. Supervisor sign-off on a topic. A proposal accepted. Ethics clearance from a university committee, and separately from a host organisation if the study sits inside a workplace. Access negotiated with whoever holds the data. Each is a queue you sit in, and each can send you back.
Build the plan in this order
List the gates and the deadline
Every point where approval is required, plus the submission date — usually the only date genuinely fixed for you. Nothing else goes on the page yet.
Put each gate's queue time next to it
Not your work — their turnaround, asked for directly. The material tells you to check the timelines that apply with each organisation, and that is all it says about how long any of this takes.
Assign every task to the gate it must clear
Design work before the proposal gate. Instrument development and access negotiation before the ethics gate. Collection after it. A task belonging to no gate is either genuinely unconstrained or has a dependency you have not found.
Estimate durations, in working days, with no dates yet
The step most plans skip, and skipping it makes a plan unfalsifiable.
Lay the durations against a real calendar
Set the working week. Mark the periods you are unavailable — leave, other commitments, shutdowns, times your participants do not exist. Let the tool compute the finish dates.
Insert float in front of every gate, then check what is left
If the plan now finishes after the deadline, you have learned the most valuable thing a schedule ever tells anyone, while there is still time to reduce scope.
Durations before dates
This library's synthesis, demonstrated negatively by the worked chart. There, durations and dates were both entered by hand and do not agree: a task marked ten days spans twenty-five, another marked forty-five spans a hundred and twenty-two. Summary lines finish before the tasks beneath them, and nothing recalculates.
The fix is an ordering discipline, not a tool feature. Estimate how much work each task contains, in working days, while you are still thinking about the work. Then lay those durations against a calendar and let the dates fall out. Dates entered first quietly rewrite the durations to fit, and you will not notice, because the chart will look right.
When you cannot estimate a duration
Float in front of every approval
This library's synthesis. The source contains no concept of float, buffer, contingency or reserve. What it contains is a set of statements that make float necessary, and one case showing what happens without it.
The statements: you cannot proceed without approval; check the timelines that apply with each organisation; workplace-hosted research needs clearance from the host as well as the university; do not expect everything to go to plan. The case: an application that went back to the committee five times for amendments and took more than five months. That case is one study — insider research on a dependent group, the hardest category there is — presented as an illustration. It is not a planning figure, an average or a norm.
The dependency that ends projects
Two structural consequences. Everything downstream of collection — analysis, coding, results, discussion, conclusions, the entire second half of a research project — sits behind a milestone whose date somebody else sets. And work done in the wrong order is not merely late, it is void: a collection task that starts a fortnight early has not saved a fortnight, it has produced data that cannot appear in the findings.
This is why the worked chart's treatment of approval is worth copying even though its durations are not. Ethical Approval appears there as a line with a start, a finish and a place in the sequence, ahead of collection — the difference between a plan with a visible constraint and one with a hidden one. The process is at seeking ethics clearance, and what committees send applications back for at ethics application failures.
A minimum task set, with its provenance marked
A task list for a research schedule, with the origin of each line shown. Nothing here is a duration — durations are yours. The provenance column exists so you can tell an instruction from a demonstration.
TASKS, AND WHERE EACH COMES FROM
| Task | Provenance |
|---|---|
| Topic refinement and feasibility check | Source — a question the proposal must answer |
| Literature search, kept updated throughout | Source — the checklist asks for both halves |
| Literature review | Source; the worked chart's longest task, 51 days |
| Synthesis across the bodies of literature | Worked chart — a separate 45-day task |
| Defining the gap | Source; also a separate task on the chart |
| Research questions, aims or hypothesis | Source |
| Research design and method selection | Source |
| Writing the proposal, and its approval gate | Source. Absent from the chart, which begins after it |
| Negotiating access | Source — in the checklist both ways round |
| Pilot study | Source names it among the design components and teaches it nowhere |
| Ethics application, and the gate behind it | Source; a discrete task on the chart |
| Data collection | Source; a task on the chart |
| Transcription | Source — flagged twice as underestimated, never quantified |
| Analysis, deliberately overlapping collection | Source — start as you collect; do not wait for everything |
| Coding | Source, in the qualitative material; a task on the chart |
| Results, discussion, conclusions | Source — all three are in the report structures |
| Recommendations | Source, as a closing step. Absent from the chart |
| First draft complete | Source milestone — called a major one |
| Re-writing and editing | Source, unquantified. Absent from the chart |
| Polishing to final draft | Source, unquantified |
| Abstract, written last | Source; correctly placed near the chart's end |
| Contents, references, appendices, acknowledgements, cover | Worked chart — each its own line |
| Submission | Both |
"Source" means the supplied teaching material asks for it somewhere. "Worked chart" means one student's plan treated it as a separate task and the teaching material does not. No row carries a duration: the material supplies none, and the chart's belong to one study.
What the worked chart teaches by leaving things out
Three rows above are marked absent from the worked chart, and the pattern is worth more than the rows. The plan has no task for the proposal, none for re-writing and editing, and none for recommendations.
What tends to get scheduled
- Work with a visible artefact at the end — a chapter, a data set, a chart
- Work you have a name for because the material named it
- Work that happens once and finishes
What tends to be left off
- Work that improves what already exists — editing, re-writing, revision
- Work whose output is somebody else's decision — approvals, sign-offs
- Work that repeats with no obvious end, such as keeping a search current
- Work the material named once and never taught, such as the pilot study
The right-hand column is where research schedules fail, and it fails the same way in delivery plans. The reason is not carelessness: these activities have no clean deliverable to hang a bar on, so there is nothing obvious to draw. Schedule them anyway, with a named line and an honest duration, and accept that the line will look vaguer than the others. A vague line on the chart beats an invisible one underneath it. An earlier student attempt shows the same omission pattern at writing a thesis plan.
Before you circulate it
The finished-schedule checklist
- Every approval is a line on the chart, with that body's own stated turnaround beside it
- Every task is assigned to the gate it must clear
- Durations were estimated before any date was entered, and the tool computed the dates
- The working calendar is set, and weekend starts are deliberate and stated or absent
- Float sits in front of each gate, sized for one rejection, not pooled at the end
- The ethics-to-collection dependency is a drawn link, not implied by adjacency
- Collection and analysis overlap on purpose, and the chart says so
- Transcription, editing and re-writing all have lines, and none is the smallest task on the plan
- Recommendations exist if an organisation rather than an examiner is the audience
- The plan's total is shorter than the time you have, and you can say by how much
What to carry forward
- The subject's scheduling advice is scattered across four weeks and supplies no method. This page is assembled, and each part is marked source, demonstration or synthesis.
- Gates first. Approvals are queues you sit in, not tasks you perform, and everything else belongs to the gate it must clear.
- Durations before dates, in working days, with the calendar set afterwards. Dates entered first silently rewrite durations to fit.
- Float belongs in front of each gate, sized for one rejection. Float pooled at the end warns you about nothing.
- Ethics approval to data collection is the one hard dependency the material states without hedging: data collected before clearance cannot be used at all.
Frequently asked questions
Does the supplied material teach how to build a research schedule?
No. It requires a proposed timeline in the proposal, asks for a timetable or project plan as a methodology component, and tells you to build a timetable to avoid last-minute panics. It never teaches a technique, names a tool, defines a dependency or supplies a worked plan of its own. The only worked schedule in the dataset is a student's.
Why should gates come before tasks?
Because a gate's timing is not yours. A committee's turnaround, a supervisor's availability and an organisation's access decision are queues you sit in, and they set the shape of everything around them. Once the gates and the deadline are placed, each task can be assigned to the gate it must clear, and any task that belongs to no gate either is genuinely unconstrained or has a dependency you have not found.
How much float should I put in front of an ethics approval?
The source gives no figure and no concept of float at all. This library's position is to size it for at least one rejection — one round of amendment plus one further queue time — and to place it in front of the gate rather than pooling it at the end. The material's one quantified case, five rounds over more than five months, describes the hardest category of application and is an illustration, not a planning number.
What is the single most important dependency on a research schedule?
Ethics approval to data collection. The material states without hedging that you cannot proceed without approval, and that data gathered before clearance cannot be used in your findings. That makes early collection worse than useless: the work is void, not merely early, and everything downstream of collection sits behind a date somebody else sets.
Should the schedule show analysis overlapping collection?
Yes, if that is your intention — and the material's own final checklist asks for exactly that, telling you to start analysing as soon as you collect and not to assume you must collect everything first. The important thing is to annotate the overlap so nobody reading the chart has to guess whether it was deliberate.
How long should I allow for transcription and editing?
The supplied material names both as risks and quantifies neither. It tells you to allow plenty of time for transcription and separately not to underestimate it, and it tells you to take as much time as is needed for editing. Estimate both from your own past work, put the basis of the estimate on the plan, and treat any figure you find elsewhere as somebody else's study.
References and source attribution
- The supplied teaching source: weekly study notes, slide decks and assessment activities for a master's-level research methods subject in project management. Author, institution and year not stated in the supplied files.
- An anonymised student thesis schedule supplied with the teaching material: a commercial scheduling application's project file and its printed Gantt chart, twenty-five lines. Used as observed practice, not as a model answer.
- A methods text's student-researcher checklist of do's and don'ts, reproduced by the teaching source from a publisher's website with a copyright line dated 2012, and paraphrased throughout this page.
- O'Leary, Z. 2017, The Essential Guide to Doing Your Research Project, 3rd ed., Sage Publications, London.
- Naoum, S. G. 2013, Dissertation Research & Writing for Construction Students, 3rd ed., Routledge.
Suggested questions for Ask KEVOS
- How do I build a schedule for a master's research project?
- What tasks belong on a research project plan?
- How do I schedule around an ethics committee's turnaround?
- Why should durations be estimated before dates?
- What does a research schedule usually leave out?