The problem
Supervisor feedback rarely arrives in a gentle form. It arrives as a document covered in tracked changes, a short email that says “see comments”, or a meeting where you nod along and forget half of what was said as soon as you leave the room.
It feels personal, even when it is not meant to be. You spent weeks on that chapter, and now someone is pointing out everything that is unclear, missing, or wrong. It is normal to feel defensive, embarrassed, or suddenly sure that you are not good enough for a PhD. Those feelings are common, and they are not evidence that you are failing.
The clear answer
Treat feedback as a work list, not as a verdict on you. Sort it, clarify what is unclear, answer it in writing, and track what you changed. That process protects your motivation, because it turns a vague bad feeling into a finite set of tasks you can finish one by one.
Do not reply the same day if you are upset. Read the feedback, sleep on it if you can, then come back to it with a pen and a plan.
Step 1: read it twice, in two different modes
First read: just read, without fixing anything. Notice where you feel defensive, and notice where you secretly agree. Both reactions are useful information.
Second read: read like an editor, not like the author. For each comment, write a short note in your own words. What is being asked? Is it about clarity, structure, evidence, methods, or writing style? If you cannot answer that question, mark the comment as “needs clarification” instead of guessing.
This second read usually shrinks the problem. A document that looked like “everything is wrong” often turns into ten clarity fixes, three structure fixes, and two questions you need to ask.
Step 2: sort every comment into four boxes
Put each comment into one of these boxes:
- Must fix: a factual error, a missing citation, a method that is described incorrectly, or a claim that is not supported.
- Clarify: a paragraph your supervisor did not understand, a term you did not define, or a jump in logic that needs a linking sentence.
- Consider: a suggestion about structure, emphasis, or scope that might improve the work, but is not clearly required.
- Discuss: a comment you disagree with, a comment that contradicts earlier advice, or a comment that would change the whole chapter if you followed it.
Do the must fix and clarify boxes first. They are usually the fastest wins, and they rebuild your confidence. Leave the discuss box for a meeting, not for a long email argument.
Step 3: ask good clarification questions
Vague feedback is hard to act on, and it is okay to say so, politely and specifically.
Instead of asking “What do you mean?”, try questions like:
- “In paragraph three, did you mean the method needs more detail, or that the method itself needs to change?”
- “If I move this section earlier, would that solve the structure issue you flagged, or would you prefer a different order?”
- “You noted this claim needs support. Would one more source be enough here, or do you want a fuller discussion of the evidence?”
Write the answers down during the meeting, and send a short summary afterwards. A summary protects you from misremembering, and it gives your supervisor a chance to correct you early, before you spend a week revising in the wrong direction.
Step 4: answer in writing, and keep a revision log
When you return the revised draft, include a short response note. For each major comment, say what you changed and where, or why you did not change it, with a reason linked to evidence or to scope.
A simple revision log works well. Copy this format for each comment:
Comment: in short form
What I did: changed, clarified, or kept, with a reason
Where to find it: page or section
Example: Comment: method is unclear. What I did: added two sentences on sample selection and a link to the full method in the previous chapter. Where to find it: page 4, methods section.
This does two things. It shows your supervisor that you took the feedback seriously, and it stops you from losing track of changes across multiple rounds. It also makes the next round faster, because your supervisor can check your changes instead of re-reading the whole chapter from scratch.
If you disagree with a comment, say so calmly and with evidence. For example: “I kept this section short because the full method is described in the previous chapter, and I added a cross reference to make that clear.” A reasoned disagreement, backed by a concrete change, is very different from ignoring feedback.
Step 5: protect your motivation while you revise
Revision is slow work, and it can feel like going backwards. A few habits help:
- Work in short, timed blocks, and stop at a clear point, not in the middle of a hard paragraph.
- Start each revision session with a comment you know how to fix, so you get an early win.
- Keep a separate note of what is already good in the draft. Supervisors comment on problems, not on everything that works, so your own note balances the picture.
- Do not compare your messy draft to a published paper. Published papers have been through many rounds of revision too. You are seeing the middle of the process, not the end.
If feedback leaves you feeling stuck for more than a few days, talk to someone you trust, a peer, a mentor, or a support service at your university. Needing support during a PhD is normal, and asking early is smarter than struggling alone for months.
Your next step
The PhD Toolkit, at $39, is COMING SOON only, and it will not be available to buy until it is actually built. When it is ready, it is planned to include starter templates for the kind of revision work in this post, including a simple feedback response log. For now, do not wait for it: use the four boxes above on your next round of feedback, and start with the must fix list.
To build a stronger draft before the next round of comments, read How to Write a Literature Review in 30 Days. To choose tools that can help you search and organise that draft, read Best AI Tools for Literature Review.
FAQ
Should I reply to supervisor feedback right away?
Not if you are upset. Read it, take a break if you need one, then come back and sort it into tasks. A calm, specific reply a day later is better than a defensive reply in the same hour.
What if two supervisors give contradictory feedback?
Note both comments, and raise the contradiction in a meeting, with the exact passages. Ask which direction to follow, and write down the agreed decision. Do not try to satisfy both directions at once by making the chapter vague.
What if I disagree with a comment?
You can disagree, but do it with a reason and, where possible, with a small change that addresses the underlying concern. Explain what you kept, why, and what you changed to make your reasoning clearer. Ignoring a comment without explanation usually brings it back in the next round.
How do I handle feedback that feels harsh?
Separate the tone from the task. If the tone was harsh, that is worth noting, and you can raise it later with a trusted mentor if needed. For the draft itself, focus on the actionable part: what needs to change, what needs clarifying, and what needs discussing. If feedback is repeatedly harsh or unclear, seek support early rather than absorbing it alone.
How many rounds of feedback are normal?
More than one, usually. A chapter often goes through several rounds, with each round focusing on a different level, from structure and argument first, to details and writing later. A second or third round does not mean you failed the first round. It means the work is being refined, which is what the process is for.