Dissertation Proposal Help — Getting Your Proposal Approved

A dissertation proposal that gets rejected isn't a failure — it's a signal that something in your research design, framing, or argument needs clarification. Most doctoral students receive at least one revision request on their proposal. The challenge is interpreting what "revise and resubmit" actually means, translating vague committee feedback into concrete changes, and knowing whether your revision genuinely fixes the problem or just shuffles the same content around. This guide breaks down the most common proposal rejection reasons and shows you exactly how to address each one.

The five most common proposal rejection reasons

1. Research question is too broad or unfocused

What this means: Your PICOT or research question encompasses too many variables, populations, or contexts. The committee can't tell what you're actually studying. Fix: Narrow the scope. Specify the population (not "students" but "first-year engineering students at [university]"). Narrow the intervention (not "teaching innovation" but "flipped classroom in Organic Chemistry"). Make the outcome specific (not "improvement in learning" but "exam scores and course completion rates"). The tighter your question, the more feasible your project.

2. Methodology is unclear or methodologically weak

What this means: Your design doesn't match your research question. Or it's underpowered (sample too small), lacks a comparison group when one is necessary, or doesn't control for confounds. Fix: Defend why this design is appropriate. If you proposed a qualitative study but the question demands quantitative data, that's a mismatch. If you're comparing two groups but didn't explain how you'll account for selection bias, add that explanation. Work with a methodology consultant if this feedback is complex.

3. Lack of evidence base or weak theoretical grounding

What this means: Your literature review doesn't justify why this project is needed, or it's too brief. Or you've chosen a theoretical framework without explaining why it fits. Fix: Expand the literature section. Show the evidence gap (what does research support vs. what remains unknown?). If the evidence is limited in your area, say so and explain why your project fills that gap. Connect your framework explicitly to your research question and methodology.

4. Feasibility concerns (timeline, access, resources)

What this means: The committee doubts you can actually complete this project. Maybe you need access to a site you don't have, or the timeline is unrealistic, or you need IRB approval for a sensitive population and haven't accounted for the approval time. Fix: Be specific about access and partnerships. If you need access to a clinic, hospital, or school, get a letter of support from the gatekeeper and include it. Break down your timeline realistically (literature 3 months, data collection 6 months, analysis 4 months, writing 3 months). Acknowledge constraints honestly.

5. Ethical or IRB concerns unclear

What this means: Your proposal doesn't adequately address how you'll protect human subjects, maintain confidentiality, or manage risk. Or it's not clear whether you need IRB approval. Fix: Explicitly describe: how you'll recruit (informed consent), how you'll store data (de-identification, secure storage), who can access it, what you'll do with it after the study, how you'll handle sensitive disclosures. If your study involves vulnerable populations (minors, incarcerated people, etc.), explain additional safeguards. When in doubt, consult your IRB office before resubmitting.

How to interpret vague committee feedback

Sometimes committee feedback is specific: "Your sample size is underpowered — you need n=200, not n=50." Other times it's vague: "The methodology section needs work" or "I'm not convinced this is feasible." When feedback is vague, here's how to decode it:

Vague feedback	What it probably means	How to respond
"Needs more work"	Not clear what the problem is, or multiple problems exist	Ask for specifics: "Can you point me to the sentence that's unclear?" or "Which aspect—scope, design, or timeline?"
"Not convinced"	The evidence or logic doesn't add up. Gaps or jumps in reasoning.	Provide more detail. If the committee isn't convinced your design is appropriate, add a paragraph explaining why. If they're not convinced about feasibility, add evidence (site letters, timeline breakdown).
"Unclear writing"	The section is disorganized or uses jargon without defining it	Rewrite for clarity. Use topic sentences. Break long paragraphs into shorter ones. Define all terms on first use. Have a non-expert read it and flag confusing parts.
"Major revisions needed"	The scope, design, or framing needs substantial rework, not minor edits	Be prepared to rebuild sections, not just rewrite them. Consider asking your advisor which sections to prioritize if multiple issues exist.

When to ask for clarification vs. when to revise

Ask for clarification if: The feedback contradicts itself (different committee members want different things), uses vague language ("tighten this up"), or seems to reject your entire approach without explanation. It's reasonable to ask: "I want to ensure I address your concern. Can you clarify what you mean by [X]?"
Revise without asking if: The feedback is specific and actionable, addresses a clear gap in the proposal (missing detail, weak evidence, unclear methodology), or you can confidently interpret what's needed. Don't use "I need clarification" as a delay tactic — if you genuinely understand what's needed, address it.

Proposal revision timeline

Most programs allow 2–4 weeks for revision. If revision requires substantial rework (methodology redesign, new literature searching, site access letters), you may need more time. Ask your advisor for a realistic deadline.

Pro tip: If your proposal received "major revisions," consider hiring a developmental editor for one revision round. They can help you translate feedback into concrete changes and ensure your revision actually addresses the concerns rather than just reorganizing existing content.

Got proposal feedback you can't interpret?

Tell us what your committee said and we'll help you understand what changes are actually needed.

Get proposal help Methodology concerns?

Related guides

Frequently asked questions

How many revision rounds is normal?

Most proposals require 1–2 revision rounds. First submission → feedback → revision → approval is typical. If you're on revision 3 or 4, the issue is likely something fundamental (scope, design fit, feasibility) rather than clarification. Talk to your advisor at that point — they can help you understand what the committee ultimately wants.

What if my committee disagrees with each other?

This happens. Different committee members have different standards. Your advisor (chair) is the tiebreaker. They guide you on which feedback to prioritize and which requests may conflict. Address the chair's concerns first, then tackle other committee members' concerns if they don't directly conflict.

Can I resubmit the same proposal without changes?

Not if your committee said "revise and resubmit." Resubmitting without addressing feedback will likely be rejected again. They expect to see changes. If you don't understand what changes are needed, ask for clarification before resubmitting.