How to Plan a Final Year Research Timeline

# How to Plan a Final Year Research Timeline

Start From the Submission Date, Not From Today

Put the deadline at the top of the page and count backwards from it. Every later decision depends on how many weeks remain, and that number is smaller than most students assume.

Write down two dates. The hard date is the one your department will not move: the day the bound copy or final file must be submitted. The soft date is the last day you could submit and still be safe — usually a week or two earlier. Plan against the soft date. The gap between soft and hard is your only remaining room if something goes wrong.

Count in working weeks, not calendar weeks. A calendar week containing two days of teaching, a group assignment and a funeral is not a full working week. Be honest about how many hours you can give the dissertation in a normal week, then divide your remaining work by that number. If the result is larger than the weeks available, you have found the problem early. That is the point.

Subtract the weeks you already know are lost. At Makerere University, Kyambogo University, Gulu University and most other Ugandan institutions, the academic year runs on a semester system, and the final semester usually includes an examination period before submission. Teaching blocks, examination weeks, public holidays, family obligations and travel are in the calendar now. Removing them at the start produces a realistic figure. Removing them in the final month produces panic.

Check your own faculty's calendar rather than relying on a general description. Semester dates, examination periods and submission deadlines differ between institutions and sometimes between faculties within the same institution. The dates that apply to you are the ones printed in your handbook or announced by your department.

One general point is worth keeping in mind: planned timelines commonly diverge from actual ones [S2]. That is not a reason to skip planning. It is a reason to build slack into the plan rather than assuming it will hold exactly.

List What Must Be Finished, Not What You Hope to Do

A timeline built from named deliverables is easier to defend than one built from vague phases. "Literature review" is a phase. "Literature review chapter drafted, 4,000 words, with reference list" is a deliverable you can tick off or fail to tick off.

Start by listing the minimum set of things that must exist for the study to be submitted. For most final-year projects this includes a proposal, an approved topic, a literature review chapter, a methodology chapter, data, an analysis, a findings chapter, a discussion, a conclusion, a reference list, and the front matter. Your department may require more or fewer items, so check your own handbook rather than assuming this list is complete.

Then separate writing tasks from waiting tasks. Writing tasks move when you work on them. Waiting tasks move only when someone else acts: a supervisor reading a draft, a department approving a topic, an office granting permission, a respondent agreeing to a date. Waiting tasks are where timelines quietly die, because students schedule them as if they took the same time as writing.

Mark which tasks depend on other people. A task that depends on your supervisor cannot start until your supervisor has the document. A task that depends on a gatekeeper cannot start until access is granted. In Uganda, gatekeepers often include district or sub-county local government offices, non-governmental organisations, schools, health facilities, and in some cases the Uganda National Council for Science and Technology (UNCST) or a named institutional review board. Draw these dependencies on your list. They determine the order of everything else.

Estimate Each Task, Then Add a Buffer You Can Name

Estimates for academic work are usually optimistic. The fix is not to estimate better — most people cannot — but to attach a specific, reasoned buffer to each task instead of one vague cushion at the end.

For each task, write two numbers: the time you think it will take, and the reason it might take longer. "Literature review: three weeks, plus one week because two key sources are only available through interlibrary loan." That is a named buffer. It tells you what the extra week is for and when you can drop it if the risk does not materialise.

A single buffer at the end of the project hides the real risk. If the fieldwork runs late and the analysis runs late and the supervisor is slow, one cushion at the end absorbs all three at once and then disappears. Buffers attached to individual tasks fail one at a time, which is survivable.

Attach the largest buffers to tasks you do not control. Your own writing speed is at least partly within your influence. A supervisor's reading time, a gatekeeper's permission, a vehicle breaking down on a murram road and a respondent cancelling are not. Those tasks deserve the most generous estimates.

Do not treat any duration in this article as a typical value. No study of student dissertation task durations is supplied here, so any numbers you see are planning assumptions, not findings. Set your own, based on your own previous work, and label them as assumptions in your plan.

Build the Supervision Cycle Into the Calendar

Supervisors are not on your schedule. Planning as if they are is the most common cause of a collapsed timeline. A chapter that sits unread for two weeks is not a delay you can work around at the end; it is a delay that has already happened.

Assume a longer turnaround than you would like, then plan for longer still. The specific figures you choose are your planning assumptions, not facts about supervision in Uganda or anywhere else. What matters is that you choose a number larger than your optimistic guess and build the calendar around it.

Book supervision slots before you need them. If your department uses a sign-up sheet, a booking system or a fixed weekly hour, take the slot early in the term, even if you have little to show. A standing appointment gives you a deadline that is not the final submission date, and deadlines that arrive sooner are more useful.

Send material ahead of the meeting so the time is not wasted. A short covering note with three specific questions — "Is this research question narrow enough?", "Is this sampling approach defensible?", "Which of these two chapters should I write first?" — turns a general conversation into decisions. A meeting with no prepared questions often ends with advice you already had.

Keep working while a chapter sits with your supervisor. The instinct is to wait, because the chapter might come back needing changes. Waiting is the wrong move. Start the next chapter, start collecting data, or draft the methods section. If the returned chapter needs rework, you will rework it with the rest of the project still moving.

Plan the Fieldwork Week as If It Will Run Late

Fieldwork almost never finishes on time. Treat the overrun as expected rather than as a failure. This is the central discipline of the whole timeline.

Define what "finished" means before you travel. Not "I have collected data" but "I have completed twelve interviews, each recorded and backed up, with consent forms signed." A defined finish line lets you judge, on the ground, whether you are done or whether you need another day. Without one, fieldwork expands to fill whatever time you have.

Schedule the week so a second week is possible. Leave the week after fieldwork empty of anything that cannot move. If the fieldwork finishes on time, you have gained a week for analysis. If it runs late, you have somewhere to put the overrun without breaking the rest of the plan.

Have a reduced-scope version ready. If access fails, if transport fails, if permissions do not arrive, what is the smallest version of this study that still answers your research question? Write that version down before you travel, while you are calm. Deciding it in the field, under pressure, usually produces either a rushed compromise or an abandoned trip.

If access, transport or permissions fail outright, tell your supervisor immediately and bring options rather than a problem. "The district office has not granted permission and I have three alternatives" is a message that gets a fast reply. "I could not do the fieldwork" is not.

Put the Analysis and Writing Blocks in the Right Order

Analysis and writing overlap more than students expect. Sequencing them badly creates a bottleneck in the final month.

Analyse as data arrives, not after it is all in. If you are conducting interviews, transcribe and code the first few while the rest are still being arranged. If you are running a survey, check the first batch of responses for problems before you collect the rest. Early analysis tells you whether your instrument is working while you can still change it.

Write the methods and literature chapters early. Neither depends on your findings. The methods chapter describes what you did and why, which you already know. The literature review describes what is already known, which does not change when your data arrives. Writing these first means that when the findings are ready, the only chapters left are the ones that genuinely need the data.

Leave the discussion until the findings are stable. The discussion interprets your results against the literature, and it is wasted effort if the results are still moving. Draft it once the analysis has settled, and expect to revise it after your supervisor reads it.

Add the Tasks Students Forget

Formatting, referencing, similarity checks, printing, binding and departmental sign-off consume real days and are routinely left out of the plan. They are not optional, and they are not instant.

Formatting and the reference list take longer than most students expect, especially if you have been citing inconsistently throughout. Set aside a block for making every in-text citation and every reference entry match the required style, and check your department's formatting rules rather than guessing.

Similarity checks and departmental clearance are procedural steps that depend on your institution. Check your own department's requirements for what is required, when it must be done and how long it takes. Do not assume a particular product or a particular deadline applies to you; confirm it.

Printing, binding and submission logistics take time, particularly if you are submitting in a city where print shops are busy at the end of term. In Kampala, the print and binding shops near the main university campuses are typically busiest in the final weeks of the semester, and a job that takes an hour in the middle of term can take a day or more at the end. Find out now what the submission format is — hard copy, electronic, or both — and what the binding specification is, if any. Costs vary by shop, by binding type and by the number of copies your department requires; the specific figure is not fixed, so ask your department and get a quote before you commit.

Supervisor sign-off and any departmental clearance are waiting tasks. They depend on other people, and they cannot be compressed by working harder. Put them in the calendar with a buffer, and start them earlier than feels necessary.

Write the Plan as a One-Page Calendar You Can Actually See

A plan buried in a notebook does not get used. A single visible page does.

Build a simple week-by-week table. Down the left, list the weeks remaining, counting backwards from the soft submission date. In a second column, write what must be finished by the end of each week. Keep it to one page; if it does not fit, you have listed tasks rather than milestones.

Mark milestones, not just tasks. A milestone is a state of the world: "proposal approved", "fieldwork complete", "first full draft to supervisor", "final file submitted". Tasks are the things you do to reach them. A page of milestones is readable at a glance, which is what you need when you are deciding what to do on a Tuesday evening.

Keep one copy where you will see it daily. A wall above your desk, the inside cover of the notebook you carry, or a pinned note on your phone. The point is not record-keeping; it is that the plan stays in front of you while there is still time to act on it.

When a Task Overruns: Triage Instead of Panic

When the plan breaks, the useful response is a short, ordered set of decisions rather than a general feeling of being behind.

First, decide what is essential and what is optional. The essential items are the ones without which the study cannot be submitted or cannot answer its research question. The optional items are the ones that would improve it. Write both lists down.

Second, cut scope before you cut quality. A smaller study done carefully is stronger than a larger study done badly. Reducing the number of interviews, narrowing the geographic area or dropping a secondary research question are scope cuts. Skipping transcription, guessing at analysis or padding the discussion are quality cuts. Take the first kind.

Third, tell your supervisor early, with options. A message that arrives three weeks before the deadline and offers two or three concrete ways forward is easy to respond to. A message that arrives three days before the deadline is not.

Fourth, rebuild the remaining weeks in one sitting. Take the time you actually have left, list what must still be finished, and rebuild the calendar from the submission date backwards. Do this once, properly, rather than adjusting the plan daily in your head.

Review the Plan Every Two Weeks

A timeline is a working document. A short, regular review catches slippage while it is still small.

Set a fixed fortnightly check. Look at what you planned to finish, what you actually finished, and what moved. The purpose is not to judge yourself; it is to find out early whether the plan still describes reality.

Track slippage, not just completion. If a task finished on time but only because you worked nights for a week, that is slippage in disguise, and it will show up later. Note it.

Adjust the plan, not the submission date. The submission date is fixed by your department. Everything else is negotiable. When the plan and reality disagree, change the plan.

A Worked Example: Twelve Weeks to Submission

The following is an illustration, not evidence of what typically happens. Its assumptions are stated so you can replace them with your own.

Starting assumptions. Twelve working weeks remain before the soft submission date. Fieldwork requires one week of travel and is expected to overrun by three to five days. The supervisor takes roughly two weeks to return a chapter. Two weeks are already lost to examinations.

The backwards calendar. Weeks 1–2: proposal finalised and submitted for approval; literature search begins. Weeks 3–5: literature review drafted; methods chapter drafted; instruments prepared. Week 6: fieldwork, with week 7 held empty as overrun space. Weeks 8–9: analysis, methods and literature revised, first draft of findings. Week 10: full draft to supervisor. Week 11: revisions, formatting, reference list, similarity check. Week 12: sign-off, printing, binding, submission.

What changed when the fieldwork ran late. Fieldwork took nine days instead of seven, using two days of the held week. Analysis started during the overrun, on the transcripts already collected, so the lost time did not become lost analysis. The full draft reached the supervisor two days late, which was absorbed by the buffer attached to the supervision task. The final week was unchanged.

The example works because the overrun had somewhere to go. A plan without a held week and without named buffers would have pushed the whole calendar into the submission date.

Where to Go Next

This timeline schedules tasks that other guides explain in detail. If you have not yet settled your topic, start with How to Write a Research Proposal: A Practical Guide for University Students in Uganda and How to Write a Research Problem Statement. For the chapters this timeline places, see How to Write a Literature Review Chapter, How to Choose a Research Design for a Student Project and How to Write a Research Proposal Methodology Section: Justify Every Choice. For the tasks in the final weeks, see APA 7 Reference List Rules Students Actually Need and How to Paraphrase Without Plagiarising: A Checklist.

A note on sources. The supplied sources for this piece are studies of timelines in other fields — life-history method [S1], strategy execution [S2], second-language learning [S3], coal phase-out targets [S4], a corporate planning cycle [S5], hypertension treatment history [S6], biodiversity policy [S7] and COVID-19 immunology [S8]. None of them is about student research planning, supervision, fieldwork or Uganda. Only one general point is cited above, on planned timelines diverging from actual ones [S2]. Every specific figure in this article — turnaround times, buffer lengths, the twelve-week example — is a planning assumption, not a finding, and should be treated as such.

Sources used

• [S2] Kobylko, Alexander A., 2023. "Planned and actual timeline of the strategy". doi:10.21638/spbu18.2023.205

No other supplied source is cited in this article. Sources S1, S3, S4, S5, S6, S7 and S8 are listed in the note above only to state that they were supplied and not used; they are not cited in the body text.

Related reading

• How to Choose a Sample Size for a Student Survey
• Design a Questionnaire You Can Actually Analyse
• How to Search Google Scholar and Library Databases