Ahmed Mohamed Hussain

Supervisory meetings are where most of a PhD actually happens: direction gets set, feedback gets given, disagreements get worked out. Most students treat them casually, show up, talk, leave, and rely on memory for what was said. That works fine until it doesn't.

The habits that protect you in a difficult situation are the same habits that make a good relationship run more smoothly. Build them from your first meeting, not after something has already gone wrong.

Here's a framework for running these meetings in a way that protects you and actually moves your work forward.

Document everything

This is the most important practice, and the one most students skip until they need it.

Keep a record of every substantive interaction with your supervisor: meetings, emails, feedback on drafts, decisions about authorship or direction. Where possible, record meetings, or at minimum take detailed notes during the meeting and send a short follow-up email afterward summarizing what was discussed and agreed. A follow-up email doesn't need to be long. A few lines confirming what was decided, what the next steps are, and by when, is enough to create a written record that both sides can refer back to.

Before you record anything, check the recording and data protection laws that apply where you are. Rules on consent (whether you need the other person's permission, whether one-party consent is sufficient, whether the recording can be used later) vary significantly by country and sometimes by institution policy. Some universities also have their own rules about recording meetings on campus or with staff. Look this up for your specific situation before you record, and don't assume the rules from one country apply somewhere else.

As one example, Sweden permits one-party consent recording: if you're a participant in a conversation, it's legal to record it without the other person's knowledge or agreement. SULF, the Swedish union for university teachers and researchers, explicitly recommends this as a way to document oral harassment or difficult conversations, alongside keeping a dated log of incidents and saving relevant emails.

This is a good illustration of why it's worth checking your own country's rules directly rather than assuming: the answer can be more permissive than people expect, but it's specific to that jurisdiction and shouldn't be assumed to hold elsewhere.

If recording isn't an option, or you'd rather not, written notes and follow-up emails serve the same purpose. What matters is that there's a contemporaneous record, something created close to the time of the conversation, rather than a reconstruction from memory months later. Memory is unreliable, and unreliable in ways that tend to favor whoever has more power in the relationship.

A good record serves you in two different scenarios. If a dispute goes through the university's own channels (mediation, an ombudsperson, a formal complaint), a clear record of what was actually said and agreed is often the single most useful thing you can bring to that process. And if the internal process fails to resolve things fairly, the same record is what allows the situation to be described accurately to anyone outside the university who ends up needing to understand it.

This isn't about assuming bad faith. It's about the same reason people keep receipts, save contracts, and write things down after important conversations in any professional relationship: agreements are easier to honor, and disagreements are easier to resolve, when there's a clear record of what was actually said.

Come with an agenda, even a short one

A meeting with no structure tends to drift into whatever the supervisor wants to talk about, which isn't necessarily what you need. Before each meeting, write down two or three things you want to cover: a specific question, a decision you need, a piece of feedback you're waiting on. Share it in advance if the relationship allows for that. This keeps the meeting focused and makes it much easier to notice, at the end, whether your actual questions got answered.

Leave with clear, written next steps

Every meeting should end with both people knowing what happens next: who's doing what, and by when. If that's not stated explicitly, ask for it directly: “So to confirm, I'll send you the revised section by Friday, and you'll get back to me by the following week?” Then put it in the follow-up email.

Ambiguity about next steps is one of the most common sources of frustration in supervisor relationships, and it's almost entirely avoidable.

Separate feedback on the work from feedback on you

Good supervision feedback is specific and about the work: this argument needs more support, this section is unclear, this result needs a stronger baseline. Watch for feedback that shifts from the work to broad statements about your ability, character, or effort, especially if it's vague and hard to act on. Specific, actionable feedback is a sign of a functional meeting. Vague, personal criticism usually isn't.

Keep a running log outside of email

Emails get buried, and threads get long. Keep a separate, simple log (even just a dated list) of major meetings, decisions, and any notable incidents. Include dates, what was discussed, and what was decided. This takes a few minutes after each meeting and becomes invaluable if a dispute ever needs to be reconstructed months or years later.

Know the escalation path before you need it

Ask early on, not in a moment of crisis, how the department handles disagreements between students and supervisors. Is there an ombudsperson, a mediator, a formal process? Who is the backup contact if your supervisor becomes unavailable or a conflict arises that the two of you can't resolve directly?

Knowing this in advance means you're not scrambling to figure out the process for the first time while already in the middle of a difficult situation.

The bottom line

The practices that protect you in a difficult case are the same practices that make a good relationship run more smoothly: clear expectations, written confirmation of decisions, and a habit of checking that both sides understood the meeting the same way. Build these habits from your first meeting, not after something has already gone wrong.