The least discussed doctoral skill is managing upward. Your supervisory team advises the project; you run it — and the candidates who internalise that early get more supervision from the same supervisors than the candidates who wait to be managed. None of this is about difficult supervisors (though the method helps there too); it is about the ordinary mechanics of getting sustained expert attention from busy people for three to four years. Here is the procedure.
Step 1: Learn what the team is for — role by role
UK doctorates are normally supervised by a team rather than a single academic: typically a primary supervisor carrying day-to-day responsibility and one or more co-supervisors adding method expertise, subject coverage or examination experience. The division of labour is real and worth mapping in your first month: who reads drafts, who owns the methods questions, who signs the progress paperwork, who knows the examiners’ world. Sector expectations back this up — the UK Council for Graduate Education’s Good Supervisory Practice Framework, written by Professor Stan Taylor, sets out ten criteria of good practice covering everything from supervisory relationships with candidates and with co-supervisors through supporting the research project, encouraging writing and giving appropriate feedback, keeping the research on track, to supporting completion, examination and dissemination. Read it once: it tells you what you are entitled to expect, in the sector’s own words, and its existence — along with the UKCGE’s recognition programme built on it — is evidence that supervision is a professional practice with standards, not a personality lottery.
Expected output of this step: one page stating each supervisor’s role as you understand it, checked with your primary supervisor in an early meeting. Ambiguity here is the root of half of all later trouble.
Step 2: Install meeting discipline — yours, not theirs
The single highest-return habit: you own the meeting machinery. Book a recurring slot for the term rather than negotiating each meeting from scratch. Send a short agenda the day before — three items: what you did, what you are stuck on, what you need decided. Bring the specific thing you want looked at rather than a status narrative. And within a day, send a five-line summary: decisions made, actions (yours and theirs), date of next meeting. That summary note is quietly load-bearing: it converts conversation into commitments, becomes your progress-review evidence, and — because most institutions expect records of formal supervisions — it is usually you doing well what the regulations require anyway.
Step 3: Ask for feedback like a professional
“Any thoughts on my chapter?” produces late, vague feedback because it is an unbounded request to a person with forty bounded hours. The form that gets answered: what the document is, what stage it is at, the two or three questions you want answered about it, and when you need it — with a realistic window agreed rather than imposed. Send less, more often: a supervisor who receives a tight fifteen pages with two questions reads it this week; the one who receives ninety pages “whenever you get a chance” reads it at Christmas. Stage your requests too — argument-level feedback on early drafts, line-level only near the end — and say which you are asking for, so nobody wastes a pass correcting commas in a chapter you are about to restructure. The drafting rhythm that feeds this — steady chapters rather than year-three avalanches — is exactly what the notes-to-chapter workflow is for.
Step 4: Use the team’s plurality instead of suffering it
Two supervisors will eventually disagree — about your method, your structure, your timeline. This is a feature: you are watching expert disagreement about your project, which is a preview of your examiners. The management rules: never relay messages between supervisors (get contested issues into a joint meeting where the disagreement can resolve itself in the room); when it does not resolve, remember the decision is yours to make and defend — write down the options, the advice, and your reasoned choice, which is precisely the intellectual independence your examination assesses; and keep both supervisors informed at the level they want, which you established in Step 1. A team you actively route questions to, by expertise, is worth two of a team you treat as interchangeable readers.
Step 5: Treat progress reviews as your instrument, not theirs
Annual progress reviews and the upgrade or confirmation review feel like inspections; used properly they are your once-a-year lever. The written submission is your chance to state the project’s trajectory in your own terms; the independent panel is your chance to hear how the work reads to someone outside the supervisory bubble; and the formal record is your chance to log, neutrally, anything the supervision needs more of — earlier feedback, a methods specialist, a co-supervisor with time. Reviews are where structural fixes happen cheaply, because the machinery for change is already in the room.
Step 6: Know the escalation ladder before you need it
Most supervision problems are fixed by Steps 2–4: unclear expectations, slow feedback, drifting meetings. For the remainder — sustained unavailability, conduct problems, irretrievable breakdown — every institution runs a formal route, normally starting with a postgraduate tutor, director of PGR or graduate school, and including supervisor changes, which happen far more often than candidates believe and are administratively routine rather than scandalous. Three rules for the rare bad case: escalate patterns, not incidents, which is another job your meeting summaries quietly do; escalate early rather than heroically late — the sunk-cost year you spend enduring is a year of thesis; and use the informal conversation with the PGR director first, which resolves most cases without paperwork. Your code of practice names the route; read it in year one, when you do not need it.
The part you control completely
Every step above works better when there is work on the table: supervision is a reaction to material, and the candidates who feed the machine — a chapter draft, an analysis, a written question — get compounding returns from it. Keeping that material flowing is the one lever entirely in your hands. Tesify keeps the thesis moving between meetings — structured chapters, steady drafting, bibliography handled automatically, 100% written by you — so that every supervision starts from new pages rather than old apologies.
Frequently asked questions
How often should I meet my PhD supervisor?
Institutional codes commonly set minimum frequencies, but the working norm in most fields is a regular slot every two to four weeks, denser during writing-up and fieldwork transitions. The reliable answer is a recurring commitment rather than an ad hoc average.
What is the difference between my primary and second supervisor?
The primary carries day-to-day responsibility for supervision and progression; co-supervisors add defined expertise — methods, subject area, examination experience. The exact split varies by team, which is why Step 1 is to write it down and confirm it.
My supervisor takes months to return drafts. What can I do?
Change the request before escalating the person: smaller documents, explicit questions, agreed return dates, and a polite nudge at the deadline. If the pattern survives that, raise it at your progress review or with the PGR director — with your dated summaries as the record.
My supervisors give contradictory advice. Who do I follow?
Neither, automatically. Get the disagreement into a joint meeting; if it persists, decide yourself and record your reasoning. Navigating expert disagreement is not an obstacle to the doctorate — it is one of its assessed skills.
Can I change my PhD supervisor?
Yes — every UK institution has a procedure, usually via the graduate school or PGR director, and it is used routinely for expertise fit, availability and relationship breakdown alike. It is a normal administrative act, not a nuclear option.
Should supervision meetings be documented?
Yes, and ideally by you: a five-line summary of decisions and actions after each meeting. It aligns expectations immediately, satisfies institutional record-keeping expectations, and is your evidence base if anything ever needs escalating.
What does the Good Supervisory Practice Framework actually give me?
A sector-endorsed statement, in ten criteria, of what good supervision involves — from relationships and project support through feedback, progress monitoring, examination and dissemination. It is written for supervisors, which is exactly why reading it as a candidate calibrates your expectations.
How much should my supervisor shape my thesis?
Advice, critique and direction-setting: yes, abundantly. Writing it: no — the thesis must be your work, and supervisory input operates within your institution’s authorship and integrity norms. If you ever feel a supervisor is steering toward their project rather than yours, that is a Step 4 conversation.
Is it my job to chase my supervisors?
Functionally, yes — the asymmetry of stakes makes it so: the thesis matters more to you than to anyone else in the building. The method in this guide is designed to make the chasing invisible: agendas, summaries and bounded requests chase without nagging.
What if my supervisor leaves the university?
Institutions are obliged to maintain supervision and will reconstitute your team; continuing co-supervision from the departed academic is often arranged. Get the new arrangement in writing early, and use the disruption as a legitimate reason to revisit Step 1’s role map.