Dissertation Progress Tracker: Chapters, Supervisor Feedback, and Deadlines

A dissertation progress tracker should tell you what each chapter needs next, which version your supervisor reviewed, and which decisions could delay submission. A chapter can have a complete draft and still need substantial revision. Track those states separately so the plan reflects the work left.

Use three records together. The chapter tracker shows the next deliverable. The feedback log ties each requested change to a version. The semester schedule reserves time for review, revisions, and final checks.

Copyable chapter tracker

Useful states are outline, drafting, sent for review, revising, ready for integration, and submitted. Use a separate blocker field if necessary. “Sent for review” means you sent a specific version and recorded when to check back. “Ready for integration” means the current revision meets the agreed checks and can join the full manuscript.

A work date tells you when to sit down and act. A deadline records when a deliverable is due. For instance, “revise methods sampling paragraph Tuesday” is the work date, while “send revised methods Friday” is the deadline. Put both in the plan if they serve different decisions.

Copyable supervisor feedback log

Feedback ID:
Received on:
Chapter and reviewed file/version:
Page, section, or comment reference:
Supervisor's request:
My interpretation or clarification question:
Planned change:
Acceptance check:
Status: Open / Clarify / Implemented / Confirmed
Revised version and location:
Follow-up date:

For large feedback rounds, separate the comments that change the argument from formatting or citation corrections. For example, resolving a question about the evidence supporting a claim can change multiple chapters. A formatting adjustment can often wait for a focused pass.

A worked semester plan

Mara is writing a fictional dissertation on how local libraries organize weekend events. Her department sets a December 18 submission deadline. Her supervisor has agreed to review selected chapters on a schedule. She builds backward from submission and leaves a week for final checks.

A sample feedback item makes the next step precise.

Feedback ID: F-12
Received: November 13
Reviewed: Findings v1, Figure 2
Request: Explain why some weekends are absent from the chart.
Planned change: Add the inclusion rule and a count of excluded weekends.
Acceptance check: Caption and methods use the same inclusion rule.
Status: Open
Follow-up: Check Findings v2 on November 18.

Mara can complete the caption edit before resolving whether the exclusions change her conclusion. If the answer changes the argument, she records a second item for the discussion chapter. Keeping the items separate shows which part of the feedback has actually been addressed.

Review the tracker once a week

1. Mark which files were sent and link the exact version.
2. Update the feedback log from the latest agreed review.
3. Pick the next deliverable for each active chapter.
4. Compare promised supervisor review dates with upcoming revision time.
5. Move low-priority edits out of the critical path when evidence or feedback needs more time.
6. Protect the submission buffer by agreeing which revisions must happen before the final checks.

Keep the authoritative manuscript and references in the tools your project uses. SelfManager.ai can hold dated writing tasks, supporting notes or documents, and the record you review at the end of the week. For example, add “Revise Figure 2 caption” to November 18 with the chapter version and feedback ID. The reference library remains the place for citation metadata and bibliography output. See SelfManager FAQ and how SelfManager works.

For a wider look at academic planning, see planner apps for PhD students and researchers.