SATURDAY, 7 NOVEMBER 2026A GLOBAL PERSPECTIVE ON LEARNING

Education. Science. Ideas.
The future starts with understanding.

Study Guides / GUIDE

Plan a dissertation through dependencies, not chapter titles

Build a schedule that accounts for access, analysis, feedback and revision.

Crop unrecognizable male student in casual clothes writing in workbook while doing homework in park
Illustrative photograph · Budgeron Bach / Pexels

List the decisions that unlock the work

A chapter list is not yet a work plan. Identify the decisions and permissions that must precede research, analysis and writing. These may include an approved question, access to material, an ethics process or agreement about the method. Requirements vary by project, so confirm them with your supervisor. Do not treat a preferred submission date as evidence that every earlier activity can be compressed without affecting the quality or legitimacy of the work.

Estimate the task in visible pieces

Break a broad activity such as literature review into searching, selecting, reading, comparing and drafting. Estimate the work using your actual pace where possible. Keep uncertainty visible instead of assigning a precise date to every unknown. A first estimate is a hypothesis to review, not a promise about your future performance. The plan should help you notice a problem early enough to discuss it, rather than simply documenting that you have fallen behind.

Schedule feedback as a dependency

Ask about the supervisor’s process and expected arrangements for drafts. Leave time to act on comments before the next dependent task. Do not assume immediate review or unlimited rounds of revision. Distinguish an agreed feedback arrangement from your personal preferred date. If the project changes substantially, discuss the impact on the plan rather than quietly absorbing the change and discovering later that the remaining schedule is no longer realistic.

Keep a fallback for an uncertain resource

A project that depends on one unconfirmed dataset or interview route needs an early discussion about alternatives. Define the point at which you will review the dependency and who can authorise a change. A fallback should still address an appropriate question and meet the course requirements. It is not permission to switch methods, participants or sources without approval. Protect the project’s coherence rather than keeping the original title while changing everything underneath it.

Review progress through outputs

Use checkpoints such as a defensible question, a source comparison or a draft analysis rather than only hours spent. Ask what the output permits you to do next. If a task took longer than expected, examine the reason: unclear scope, missing access, insufficient preparation or an unrealistic estimate. Each may need a different response. Avoid solving every delay by deleting the revision stage, because revision is part of the intellectual work rather than decoration after it.

Construct a dependency sketch

Choose the next major output and list what must be true before it can be completed. Mark the items under your control and those requiring another decision or resource. Add a review date for the most uncertain dependency and a question for your supervisor. Compare this sketch with the official submission rules and your current commitments. The result should be a plan you can explain, revise and discuss. It is not an argument for an extension; any request to change an official deadline must use the institution’s designated procedure.

Reporting, explanation or opinion as labelled above. AALBORG Journal is affiliated with Aalborg Academy. This article is not an independent institutional ranking or a peer-reviewed research paper.

Read next

Search the Journal