A workable system for PhD supervision: run several students as a cohort with a shared tracker, a fixed rhythm and a durable record, so no deadline slips.
A cohort can double in a semester, and the three students you had become six. Reading lists, chapter drafts, submission deadlines and supervision notes all feel urgent at once. The workable way to supervise several students is to run them as a cohort, with a shared tracker, a fixed rhythm and a durable record. With those in place, no student disappears and no deadline slips. The rest of this post sets out the system.
Thesis Studio is Lectimax's supervision module, and it supports that system by holding every student's plan, notes and deadlines in one place. That keeps the whole cohort visible. Thesis Studio keeps the record and the schedule, while deciding the feedback remains your side of the work.
What breaks when the cohort grows?
At two or three students, supervision runs in your head. At five or six it stops running there, and the first thing to slip is usually the quietest student rather than the loudest. A draft sits unread for two weeks, a deadline quietly passes, and a student you assumed was fine turns out to have been stuck for a month.
Effort is rarely the cause of this. The usual cause is that no single record holds everyone's position, so the supervision queue is rebuilt from memory at every meeting. Memory favours the students who message you. The fix is a record that updates as you go, so the queue never depends on what you happen to remember when a student walks in.
How do you run the students as a cohort?
A shared record only helps if it covers everyone, so keep one tracker for the whole group rather than a notebook page per student. Each row is a student. The columns are their working title and the phase of the thesis, plus the last feedback date, the next milestone and an agreed due date.
The cohort view then changes how you spend supervision time. Instead of opening each student cold and working out again where they are, you scan the board. You see who is due and who has gone quiet. You also see which milestone is approaching for the whole group. Students benefit too, because they can see that the plan is shared and fair.
Set a fixed rhythm and protect it
With the tracker showing the whole group, decide a meeting rhythm you can actually keep, fortnightly for most students and monthly for those deep in drafting, and book a slot per student. Protect the slot once it is set, because a cancellable one on one quietly becomes a deleted one.
The rhythm works as a contract with the cohort. When every student knows the slot is fixed, they bring work to it, because they know it will not vanish. When the rhythm is loose, students stop preparing and the meetings turn into status updates. Keep the rhythm short and protected, and let the agenda come from the tracker rather than from the hour.
Keep the written note as you go, not after
The meeting itself is where the record starts. Write the feedback note during the meeting, one line per action, so both of you leave with the same record. Assign a clear owner and a due date to every action, and state both before you end the call.
This written note makes supervision defensible and efficient. A one line record of what was agreed, by whom and by when turns a thirty minute chat into a traceable step. A student who later contests a direction can point at the record rather than at a memory of it. Capture it immediately, because the note written at the end of the day is the note that never gets written.
Catch the quiet student before they fall behind
Notes and a tracker also make it easier to see who has stopped contributing. In a cohort, the students who go quiet are usually the ones who need attention, and they are rarely the ones who ask for it. If a student misses a milestone or stops responding, treat that as a signal to reach out, because silence in a PhD is often stuckness rather than confidence.
The signal is the gap between the last agreed milestone and now. A student who does not raise a hand for three weeks is not necessarily fine, and may be stalled and avoiding the meeting out of embarrassment. Use a short, low stakes check in, and phrase it as a question about the work rather than a demand for progress. That usually surfaces the block. See the full account of AI thesis supervision management.
Make the record survive term to term
All of this only pays if the tracker keeps living after the semester ends. A paper tracker dies the moment a student leaves or a term closes. Keep the plan somewhere you can reopen and update, and let the record carry across the whole thesis and across changes in who is active.
This is the practical case for a supervision tool. Thesis Studio stores every student's plan, the notes and the deadlines together, and it surfaces who is due and who has gone quiet. Review the full Lectimax feature set.
FAQ
How many students is too many to supervise? The practical ceiling depends on the mix of thesis phases and your other load. The moment you can no longer hold every student's position in your head, you need a shared record. That usually arrives somewhere between four and six.
How often should I meet each student? Most cohorts work on a fortnightly rhythm, with monthly meetings for students deep in drafting. Protect the slot once it is set, because a cancellable meeting disappears.
How do I spot a student who is silently struggling? Watch the gap between the last agreed milestone and now. A student who goes quiet for three weeks usually needs a reach out rather than another invitation to a status meeting.
Does a supervision tool write my feedback for me? No. You decide the feedback, and the record of what was agreed and by when stays in the tool, so the cohort stays visible and nothing slips.
Where to go next
The supervision record also feeds into the wider way you run your teaching and marking. See what AI grading in higher education really is, or review Lectimax pricing.