How to Read Vague Dissertation Feedback from Your Advisor

The chapter came back. The comments are in the margin, some of them one word long, and you have read them four times without knowing what to type.

Here is the whole of my advice, in two lines:

Every comment is a request for a specific edit.

Your job is to work out which edit before you touch the draft.

Most dissertation feedback names the fault and leaves out the fix. That is not because your advisor (or supervisor, in the UK) is being cruel. It is because they read forty pages in an hour and wrote what they noticed, not what you should do about it. Translating one into the other is a skill, it can be taught in an afternoon, and this post is the afternoon.

About 17% of a sample of 804 students we worked with between 2024 and 2026 described feedback that named a fault without saying how to fix it. One student told me: “I keep getting feedback that this needs a bit more work, this needs a bit more direction, but I’m not getting any.”

So let’s get you some direction.

Read the mood before the words

Advisors write comments in a handful of moods, and the mood tells you what kind of edit is wanted before the words do.

An instruction is an instruction. “Cut this.” “Move this to chapter three.” Do it.

A tentative comment is a question about your reasoning, not an order. “I wonder whether this belongs here” usually wants one sentence explaining why it does, or a quiet move if you cannot write that sentence. It does not want a deletion and an apology.

A question is not automatically a rejection. “Why two models?” almost always means “defend this choice”, not “use one”. Before you change anything, decide whether the comment says this is wrong or tell me why you did this. They need opposite responses.

Text inside quotation marks is nearly always a proposed replacement. Paste it in.

A highlight with no note is a flag, not a verdict. It means “look at this again”. Read the highlighted sentence aloud. Nine times out of ten you will hear the problem. The tenth time, ask, in one line.

And the amount of ink is not the severity. Fifty word-level comments on a chapter can be an afternoon’s work. One comment on your research question can be a month. Count them, then sort them. Twenty scattered remarks are usually three concerns wearing different hats, and your first job is to find the three.

The twelve torturous comments

These are some of the most common vague comments we’ve seen over the course of helping 10,000+ students, translated into plain, actionable language. For each: what it usually means, what to do about it, and a check you can run yourself before you send it back.

A worked example: “more detail”

This one comes up most weeks. A results chapter comes back with “more detail” written beside a sentence like: “Participants reported challenges with leadership support.”

The student reads it as “write more” and drafts two extra paragraphs of background. But the comment was asking for precision, not volume. Which participants? How many? What kind of challenge?

The fix is one sentence: “Five of the eleven leaders described the same challenge: approval decisions that took weeks and arrived without reasons.”

Same length. All the detail. Then she goes back through the chapter and finds the same fix waiting in a dozen places, which is the real lesson: one comment, properly decoded, usually unlocks a whole class of edits rather than one.

The two-readings email

Sometimes the mood and the list still leave two live readings. Do not pick one in the dark.

Write out both, Option A and Option B, and send a short email: “Reading your comment on 2.3, I could take it two ways: A) drop the second model and defend the first, or B) keep both and justify why two are needed. I plan to do A unless you tell me otherwise.”

That works because you have handed a busy person the cheapest possible decision. Most advisors will answer a yes-or-no question inside a day when a paragraph would sit in their inbox for a month. If the reply is vague, you may politely take that as permission to proceed with A. One email per round, with the questions batched, never a drip of six.

If the difficulty is not the comment but the asking, this post on asking your advisor for help covers the phrasing. And if what you are dealing with is the relationship itself rather than a comment, that is a different post, and a different problem.

Count, sort, shrink

A returned chapter feels like a wall. It is a list, badly formatted. Here is how I turn it into a plan with a client, usually in the first half of a session.

1. Count the comments. Then remove the compliments and anything that carries no request. The number that remains is smaller than the number you felt.
2. Sort what is left into three tiers: word-level, paragraph-level, argument-level. Do the argument-level ones first. Fixing structure changes which of the small comments still apply, and some of them vanish.
3. Shrink the pile to three or four numbered jobs. If your advisor wrote a summary paragraph, that paragraph is the map; work from it before the margins.
4. For each comment, choose one of three responses: change it, modify it, or argue it. Concede wording every time. Argue only where you have a real methodological reason, and cite the reason.
5. Do exactly what was asked, and nothing extra. Anything you add beyond the request must be flawless, because it opens a fresh round of comments on new material.
6. Keep a response table as you go: the comment, where it was, what you did. When you resubmit, attach it with a one-page note of what changed. Indiana University of Pennsylvania’s writing center recommends the same table, in three columns, before any revising starts, and I have never seen a better habit for stopping the next round being about the old draft.

A client put it this way: “I feel like it’s right there, and then she moves the target on me.” The response table is how you pin the target. Every round starts from the last one, in writing, and nobody has to remember.

Where students often go wrong

Most of the damage from vague feedback happens in the reading, not the rewriting. The same few misreadings come up again and again, and each one costs a week of work in the wrong direction.

• “Go deeper” read as “write more”. Depth is analysis. Length is length.
• A question read as an order to delete. Most questions want a reason, not a removal.
• A wording comment read as a methodology failure. “Be consistent” is a search-and-replace, not a crisis.
• The volume of markup read as the whole chapter being wrong. Partly positive feedback is still partly positive, and the word “major” describes the size of one job, not the quality of the whole.
• Fixing only where the comment sits. “Too descriptive” and “be consistent” apply to the whole document.
• Accepting the tracked changes and calling it done. The word-level edits are the cheap ones. The substantive comments are still there, unanswered.
• Reading silence as approval, or as disaster. It is usually a queue, and the wait is workable.

None of these is a failure of intelligence. They are what a tired person does with an under-explained comment at eleven at night, and I have watched very capable students make every one of them. The cure is the same each time: decode before you edit, write the decoding down, and send it back so the next round starts from it rather than from a guess.

Still have questions?

Does this comment mean add, cut or rewrite?

Start with the mood, because it tells you most of the time. An instruction (“cut”, “move”, “expand”) names the edit. A tentative comment more often wants a sentence of justification than a change, and a question is more often asking for a reason. Advisors differ, though, and some phrase every instruction as a question, so if two readings are still live after that, the two-readings email is safer than guessing.

Does a comment apply only where it was written, or throughout?

Word-level comments apply where they sit. Comments about a property of the writing, such as “be consistent”, “too descriptive” or “unclear”, are meant for the whole document more often than not, because an advisor rarely marks the same fault twice. Treat those as a prompt to search the entire draft, and if you are unsure whether one was meant globally, that is a fair question to ask.

How do I know whether a comment is major or minor?

The three tiers are a reasonable first sort. Word-level comments tend to be minor. Paragraph-level ones, such as flow, synthesis and depth, sit in the middle. Argument-level ones, such as the research question, scope and alignment, are the major ones, because they change what comes after them. The tiers are a guide rather than a law: a single wording comment on a research question can be major, and your advisor’s summary paragraph, if there is one, is the better signal of what they weigh most.

How much should I write in response to each point?

In the draft, as little as removes the cause. Many comments are answered by one precise sentence rather than a new paragraph, and the worked example above is the common shape, though a comment on scope or method can genuinely need a page. In the response note, one row per comment is enough in most cases: what it said, where it was, what you did. Where you argued rather than changed, add the reason and a citation. You are writing a change log, not a defense.

How do I check that my revision actually addressed the comment?

Every entry in the decoder ends with a cross-check, and running the one that matches the comment is a good start: delete the reporting sentences for “too descriptive”, search for the variant for “be consistent”, read the last sentence of the paragraph for “so what?”. None of these is a guarantee, because only your advisor can say whether the concern is settled. Resubmitting with the one-page note helps there too, since the next round then judges the new draft rather than your memory of the old one.

What if two comments, or two committee members, contradict each other?

It is rarely worth arbitrating yourself. The cleanest move is to put both instructions side by side in one short email to your chair and ask which one stands, since the person who signs off on the final document is the one to follow. Committee dynamics vary, though: if your chair defers to a specialist on method, that view may carry the point. Whichever way it goes, keep the answer in writing, because a reversed instruction is far cheaper to deal with when the earlier one is in an email.

Can’t find your answer here? Ask a Grad Coach directly – the initial chat is free.

Speak with a friendly coach →