PhD Proposal: Use Supervisor Feedback Well

PhD Proposal: Use Supervisor Feedback Well

Revise a PhD proposal by identifying the research problem behind each supervisor comment, then changing the design you can defend. Do not accept every suggestion mechanically or interpret detailed feedback as an admission offer. A better draft still belongs to you.

Our recommendation is to treat feedback as information about the project before treating it as a verdict about yourself. “Too broad,” “not sufficiently original” and “reads like consultancy” describe different problems. Replacing a few adjectives will not repair all three.

If you are still deciding which document is required, start with the PhD proposal guide. Here, the task is responding after a prospective supervisor has read an actual draft. It is separate from writing an initial inquiry or chasing an unanswered email.

What feedback establishes—and what it leaves open

LSE Statistics' 2022 doctoral open-day guidance explicitly discusses seeking proposal feedback from potential supervisors. It presents that as something applicants may do, with some supervisors willing to respond. It is guidance about developing a proposal, not a current promise that every faculty member will read one.

Cambridge's central proposal guidance likewise suggests discussing the proposal with a supervisor and makes the course's instructions controlling. Neither source makes the amount of feedback an admissions probability.

A reader can find an idea interesting while doubting its scale, evidence or match. They can also suggest a viable project that you do not want to undertake. The next draft should help both sides evaluate the actual fit.

Translate comments into decisions

Make a change log before revising sentences. Record the comment in your own words, the issue it raises and the response you propose.

This table is an editorial decision aid. It is not a demand that you satisfy every possible criticism in one draft. Some comments reveal alternatives that cannot sensibly coexist.

Prioritize changes that affect the question, contribution and feasibility. Correcting reference style may be necessary, but it does not resolve a proposal whose central question remains undefined. Conversely, do not redesign a sound project because one sentence was unclear.

Case A: an industry plan needs a research question

Constructed GradPilot case; not a real applicant or supervisor. An engineer proposes building a dashboard to improve maintenance scheduling. A prospective supervisor says the plan describes a useful deliverable but does not explain what would be learned beyond producing it.

The applicant initially wants to add “novel” before dashboard and promise more data. Our recommendation is to return to the uncertainty. Which scheduling assumption would the project examine? Under what conditions might the current approach fail? What evidence could distinguish explanations?

A revised project description might say:

The original plan focused on delivering a scheduling tool. I have narrowed the proposed research to how incomplete failure records affect the comparison of maintenance policies. The tool would support that investigation rather than constitute the contribution by itself. I would compare policies under documented missing-data conditions and examine which conclusions remain stable across those conditions.

The passage changes the project's purpose. It does not establish that the approach is novel; the literature and methods still need to support that claim. Nor does it promise better scheduling before any investigation.

The applicant's reply can briefly explain the change and identify what remains uncertain. For example: “I have revised the question around the reliability of policy comparisons, rather than the delivery of a dashboard. The main remaining issue is whether the proposed records support that comparison.”

This is an account of a decision, not a request for the supervisor to finish the intellectual work. The data-access feasibility guide covers the unresolved resource issue.

Case B: a suggestion creates a different project

Second constructed case. An applicant wants to study how migrant workers interpret workplace communication. A prospective supervisor suggests using a large public corpus of corporate statements instead, because it is easier to access and matches the supervisor's methods.

The suggestion may produce a worthwhile project, but it changes whose perspective the evidence captures. Our recommendation is to identify that change explicitly. Do not retain claims about workers' interpretations when the revised evidence consists of organizations' public language.

The applicant might respond:

The corpus would make a study of organizational framing more feasible. It would not answer my original question about workers' interpretations. I could revise the project around institutional framing, but I would like to clarify whether that is the intended direction before developing the new design.

There are two legitimate outcomes. The applicant may discover that the revised question is compelling and fits their goals. Or they may decide that the original research interest matters enough to seek another supervisory match. Accepting every change to preserve a possible offer can conceal an important mismatch.

A disagreement should concern the question and evidence, not the supervisor's motives. Explain the consequence of the proposed change and ask a focused question. You can be open to learning without claiming enthusiasm for a project you would not want to pursue.

Keep a version record that shows intellectual ownership

Save the original draft, the feedback and the revised version. In a private note, identify what you changed and why. If several readers propose conflicting approaches, you should be able to explain which one you chose.

This does not mean placing a lengthy revision memo inside the application. It helps ensure that the final proposal remains coherent and that you can discuss it independently. A document assembled from every reader's preferred method can become less feasible with each revision.

When an application asks about assistance, acknowledge it according to the actual instructions. Do not claim the proposal was developed entirely without input if that is untrue. A supervisor's willingness to comment does not override the institution's authorship or assistance rules.

If the revision requires a technique you have never used, distinguish learning the approach from claiming present expertise. The methods-without-prior-experience guide addresses that boundary.

Send a focused revised draft

Use the format the reader requested. Briefly state the main design changes, attach or link the version through the agreed channel and identify one or two unresolved questions if further feedback has been invited.

Avoid asking the supervisor to approve every sentence. Ask about matters where their expertise can change the project: whether the revised scope fits the degree, whether an alternative comparison is meaningful, or whether the proposed resource is actually available.

Do not assume an invitation to revise means unlimited rounds. If a deadline is approaching, state the date factually and ask whether a further read is possible. Silence does not confirm approval, and an informal approval does not replace the application process.

Does strong criticism mean I should abandon the application?

Not by itself. Examine whether the criticism identifies a repair you understand and can make. A concern about the fundamental fit or available supervision may have different implications from a request to narrow the question. No phrase reliably predicts selection.

Must I make every requested change?

You should understand and respond to the important concerns. If a suggestion conflicts with your research aim or another requirement, explain the tradeoff and seek clarification. Do not conceal disagreement inside a proposal you cannot defend.

Can I change the topic after admission instead?

Do not use that as an assumed escape route. Cambridge says a proposed topic change may need Degree Committee consideration, including feasibility and resources. Other institutions have their own processes. Apply with a project you can honestly support now.

Check the revised argument

Read only the question, methods, evidence and anticipated contribution. Do they describe the same project? Then compare the draft with the comments and mark which concerns have been resolved, which remain open and which reflect a genuine choice between directions.

The standalone PhD research-proposal rubric, available through PhD writing review, can help examine that written coherence. It does not interpret a supervisor's intentions or predict admission. For the surrounding application, use the PhD essays hub and supervisor-contact guide.

Primary guidance checked September 14, 2026. Cases and revision tools are original GradPilot illustrations.