,

How to Turn Supervisor Feedback Into an Action Plan

Editorially reviewed and edited by Brett Stadelmann.

Supervisor feedback becomes useful when it stops being a page of comments and becomes a sequence of decisions. The goal is not to obey every note mechanically. It is to understand the underlying concern, decide what change will address it, and revise in an order that avoids doing the same work twice.

If feedback tends to arrive during meetings, pair this system with the PhD supervisor meeting agenda so that unclear comments become questions before you leave the conversation.

Do not start at comment one

A document may contain 70 comments, but they are not 70 equally independent tasks. One structural change can resolve ten local comments. If you begin fixing punctuation while the chapter argument is still changing, you create avoidable rework.

First read all the feedback without editing.

The Australian National University guidance on feedback distinguishes higher-order concerns—such as argument, organisation and whether key questions are addressed—from lower-order concerns such as style, grammar and punctuation. That distinction is extremely useful for revision planning.

Step 1: Translate comments into underlying problems

A supervisor’s comment is often a signal, not the final edit.

Comment Possible underlying issue Action
“So what?” The significance of the finding is not explicit. Add the implication and connect it to the research question.
“Evidence?” A claim is unsupported or too strong. Add evidence, qualify the claim or remove it.
“I’m lost here.” The logical sequence is unclear. Map the paragraph or section argument before rewriting sentences.
“Why this method?” The methodological rationale is missing. Explain the link between question, method and trade-off.
“Too descriptive.” Sources or results are reported without analysis. Add comparison, interpretation or evaluation.
“Move?” The information may interrupt the current argument. Decide where the reader actually needs it.

Step 2: Triage feedback by level

Use four buckets:

  1. Argument: research question, contribution, chapter purpose, logic.
  2. Structure: order of sections, missing transitions, repeated material.
  3. Evidence: literature, data, analysis, methodological justification.
  4. Surface: wording, grammar, formatting, references.

Revise in that order unless a deadline or explicit supervisor request gives you a reason not to.

Four distinct groups of comment slips represent argument, structure, evidence and surface edits.
Triage feedback by level so argument and structure are resolved before sentence polishing, unless the deadline or brief requires a different order.

Step 3: Separate clear actions from questions

Some feedback tells you exactly what to do. Other feedback requires a decision or clarification.

Create two lists:

Action now: tasks you understand and can complete.

Clarify: comments where you do not understand the concern, where two comments conflict, or where the suggested change would alter the research claim substantially.

Do not spend half a day guessing what “needs more” meant. Ask.

A copyable feedback action table

Location Feedback Underlying issue Action Priority Status
2.3 “Why is this important?” Significance unclear Add 2–3 sentences linking pattern to RQ2 High To do
3.1 “This seems out of order” Structure Move framework before case description; check transitions High To do
4.4 “Citation?” Unsupported background claim Find source or qualify statement Medium To do
Throughout Long sentences Readability Sentence-level edit after structural revision Low Later

Step 4: Find the comments that share one cause

Look for clusters.

If several comments say:

  • “why?”
  • “link?”
  • “how does this answer the question?”
  • “what does this mean?”

the problem may not be four sentences. It may be that the section lacks a clear argument.

Fix the cause first, then revisit the individual comments.

Step 5: Sequence revisions to avoid rework

A useful order is:

  1. research question or central claim;
  2. chapter purpose;
  3. section structure;
  4. missing evidence or analysis;
  5. paragraph logic;
  6. sentence clarity;
  7. references, formatting and proofreading.

If a chapter needs substantial restructuring, duplicate the file or use version control before moving large sections. The exact tool matters less than being able to recover a previous state.

A draft is reorganized in large sections while a saved copy remains separate.
Preserve an earlier version before restructuring, and settle the chapter’s argument and order before proofreading.

Step 6: Make each action specific enough to start

“Fix Chapter 4” is not an action.

Better:

  • rewrite the opening paragraph to state the chapter claim;
  • move Section 4.3 before 4.2;
  • compare the two conflicting studies in paragraph 12;
  • add a limitations paragraph on participant selection;
  • replace the causal wording in three highlighted claims.

This is particularly important when revision triggers procrastination. The guide to dissertation anxiety and procrastination uses the same principle: define the smallest meaningful next action.

Step 7: Decide when not to make a suggested change

Supervisor feedback is expert input, not an instruction to remove your judgement from the thesis.

You may reasonably choose a different solution when:

  • the suggested edit would create a factual problem;
  • it conflicts with another requirement;
  • the comment identifies a real issue but the proposed fix does not solve it;
  • two supervisors recommend incompatible changes;
  • you have evidence supporting the existing choice.

Do not silently ignore significant feedback. Record your reasoning and discuss it when the decision matters.

How to handle conflicting supervisor feedback

Do not attempt to satisfy contradictory instructions simultaneously.

Write the conflict in neutral terms:

“Comment A suggests moving the theoretical framework earlier so it guides the analysis. Comment B suggests reducing the framework and keeping the chapter empirical. My proposed solution is to keep a shorter framework section before the analysis and move extended theory to Chapter 2. Does that resolve the concern?”

You have turned disagreement into a decision supervisors can respond to.

Step 8: Keep a revision log for major changes

A simple log helps when feedback arrives over months:

Date:
Chapter/version:
Feedback source:
Major issue:
Decision:
Change made:
Anything still unresolved:
Question for next meeting:

You do not need to log every comma. Record changes you may need to explain later.

Step 9: Review the document after the comments disappear

Once individual comments are resolved, read the revised section cleanly. Local fixes can create repetition, broken transitions or inconsistent terminology.

Ask:

  • Does the section now make one clear argument?
  • Did I accidentally repeat the same explanation?
  • Did moving a paragraph break a later reference?
  • Are claims still proportionate to the evidence?
  • Does the conclusion match the revised analysis?

A 30-minute feedback reset

If you receive a heavily commented draft and do not know where to begin:

  1. Read all comments without editing.
  2. Write the three largest concerns on paper.
  3. Mark each as argument, structure, evidence or surface.
  4. Create one concrete action for each high-level concern.
  5. List comments that need clarification.
  6. Choose one 25-minute revision task.

Then stop planning and do that task.

Use the next supervisor meeting to close the loop

Bring a short summary:

  • what you changed;
  • what you deliberately did not change;
  • where you are uncertain;
  • the next decision you need from your supervisor.

The supervisor meeting agenda template includes an action record so feedback does not disappear into another round of vague notes.

If revision is competing with fieldwork, teaching and other deadlines, the PhD time-management guide can help turn the action table into a realistic week rather than an impossible list.