A Weekly Review System for PhD Students

Why the PhD week has no natural shape

Most work environments have built-in weekly structure — stand-ups, sprint reviews, deliverables, check-ins. A PhD has almost none of that. Your formal milestones are measured in months or years: confirmation of candidacy, chapter submission, the final defence. In between, you largely manage yourself.

That is intentional. Independent scholarship requires learning to direct your own work without constant external structure. But it creates a real problem: without weekly checkpoints, it is easy to confuse activity with progress. You can stay genuinely busy — reading, note-taking, planning, meeting — for months without your thesis materially advancing. And because the feedback loop is so long, you may not notice until your supervisor asks where you are and the answer is harder to give than you expected.

A weekly review does not add bureaucracy to your PhD. It adds one honest question each week: am I moving, or am I spinning?

What a weekly review actually does

The purpose of a weekly review is not to feel organised. It is to generate a weekly data point on your actual progress — separate from your felt sense of progress, which in a PhD is often unreliable.

Done consistently, a weekly review gives you something more valuable than a snapshot: a record. After four weeks you can see patterns. Which chapters are stalled. Which days you actually write. Where your blockers tend to cluster. Whether your estimate of how long things take is accurate.

That record also changes how you relate to slow weeks. A week where nothing moved is discouraging in isolation. Seen as one data point in a longer series, it becomes information — something to understand rather than something to feel bad about.

What to cover each week

Keep this to twenty or thirty minutes. A weekly review that takes three hours will not survive contact with a busy semester. The goal is a consistent, lightweight practice — not a comprehensive audit.

Chapter status check

Where does each chapter stand right now? A simple set of states works well: not started, active drafting, revising, with supervisor, complete. Update each chapter honestly. The value is not in the labels themselves but in noticing when a chapter has been in the same state for three weeks in a row.

What actually moved

Not what you did this week — what changed. A section drafted. A source properly integrated. A structural problem solved. A chapter sent for review. If you cannot name something specific that moved, that is information worth sitting with rather than skipping past.

This distinction matters because reading, planning, and note-taking all feel like work — and they are. But they are not the same as moving a chapter forward. The weekly review is one of the few moments where you draw that line explicitly.

Your current blocker

Name the one thing slowing you most right now. Vague blockers are not useful: "I need to write more" tells you nothing. Specific blockers are actionable: "I cannot write section 3.2 until I read Smith and Jones 2019" or "I do not know how to frame the transition between chapters two and three."

Naming the blocker specifically often makes it smaller. It also sometimes reveals that the thing you have been avoiding is a thirty-minute task you have been treating like an unsolvable problem.

Next week's one thing

Not a list. One thing. The specific outcome that would make next Friday feel like a good week. This constraint is deliberate — a long task list for a PhD week usually means most of it does not happen, which makes the review feel like failure rather than information. One clear target is harder to ignore and easier to hold yourself to.

Supervisor meeting preparation

When is your next supervisor meeting? What will you send beforehand? What do you want feedback on specifically? If you do not know the answers, that is worth resolving now rather than the night before the meeting.

The difference between busy and moving

Reading is not the same as integrating. Planning is not the same as drafting. Annotating is not the same as writing. None of this is obvious in the moment — the PhD creates conditions where all of these activities feel equally valid, because at different points they are.

The problem emerges over time. A student who spent three weeks "working on chapter four" but cannot point to anything in the chapter that changed has been busy, not moving. That distinction is invisible without a record. With one, it becomes visible after two weeks — early enough to adjust, not late enough to panic.

This is not about judging how you spend your time. It is about having accurate information about where your thesis stands, so you can make better decisions about where to put your attention next.

Using your weekly review to prepare for supervisor meetings

Most doctoral students arrive at supervisor meetings having done work but not having thought carefully about what they want from the meeting. The result is a general check-in that covers a lot of ground without going deep on anything.

A weekly review changes this. When you know exactly where each chapter stands, what moved last week, and what is blocking you, a supervisor meeting becomes a focused conversation. You arrive knowing what you need — which makes the feedback you receive more specific and more useful.

It also means you can send work to your supervisor with a clear frame: here is what I am trying to do in this chapter, here is what I am uncertain about, here is the specific feedback that would help me most. That kind of directed submission produces better feedback than sending a draft and waiting to see what comes back.

For more on preparing a chapter before it goes to your supervisor, see what to check before sending a chapter to your supervisor.

Making it a system

A weekly review works because it is consistent, not because any individual session is particularly insightful. A few things that help it survive:

• Same time each week. Friday afternoon before you close down, or Sunday evening before the week begins. The timing matters less than the consistency — it should not require a decision each week.
• Keep it short. Twenty to thirty minutes. A review that expands into a half-day audit becomes something you avoid. The constraint is a feature.
• Write it down. The record matters as much as the review itself. A log of weekly chapter states, blockers, and one-things is a surprisingly useful document six months in — both as a record of progress and as a reality check on how long things actually take.
• Do it even when the week was bad. Especially when the week was bad. A review after a difficult week is more informative than one after a productive one.

Research Think's project dashboard is designed around this kind of weekly visibility — chapter status, scoring history, and progress over time — so the review has somewhere to land and something to compare against week to week. If you want to see how to structure a thesis project to support this kind of tracking, see how to set up a thesis project in Research Think.

And if the issue is not tracking progress but understanding whether your writing quality is improving alongside it, the guide to why word count is not enough covers what to measure instead.