The proposal is the gate your committee uses to decide whether your study is worth pursuing. A weak problem statement or an unjustified methodology gets sent back — often more than once. Our specialists build proposals that pass committee review by being defensible from the first page.
| Section | Purpose | Common Failure Point |
|---|---|---|
| Problem statement | Establish the gap and why it matters | Describes a topic, not a problem |
| Research questions | State exactly what the study will answer | Too broad to be answerable |
| Theoretical/conceptual framework | Anchor the study in established theory | Framework doesn't connect to the questions |
| Methodology | Justify the design for these specific questions | Design chosen by convenience, not fit |
| Significance | Explain the contribution to the field | Overstates impact without evidence |
| Timeline | Show the study is feasible in the available time | Unrealistic or missing entirely |
Committees reject far more proposals for structural reasons than for topic choice. The most common pattern: a problem statement that describes an area of interest rather than an actual gap in the literature — "leadership styles affect employee retention" is a topic, not a problem. A defensible problem statement names what is unknown, who is affected, and what happens if it stays unanswered.
The framework is not a literature summary — it's the lens your entire study is interpreted through. A workable framework does three things: names the theory or model, explains why it fits your specific research questions (not just your general topic), and shows how it will be applied when you analyze your data later. If you can't explain how the framework will shape your discussion chapter, it isn't doing its job yet.
Test your problem statement with one question: "So what?" If a reader can ask "so what happens if this stays unanswered?" and you don't have a concrete answer, the problem statement needs more work before it reaches your committee.
Problem statement, research questions, framework, and methodology built to be defensible from the start.
Yes. Many clients come to us specifically because their problem statement keeps getting rejected. We can work on that section alone, or build out the full proposal once it's solid.
That alignment is the core of what we check first. We won't propose a quantitative design for a question that needs qualitative depth, or the reverse — mismatched designs are the single most common reason committees send proposals back.
This is a large share of our proposal work. Send us your committee's feedback alongside your draft, and we address the specific concerns raised rather than starting from scratch.