A proposal is not an essay about a topic. It is a case that a specific, answerable question is worth answering, that you have a defensible way to answer it, and that you can do so with the time and access you actually have.
Committees reject proposals for a small number of recurring reasons. Nearly all of them are avoidable.
The question must be falsifiable
"Exploring the impact of social media on youth" cannot be answered, only discussed. A committee reading it cannot picture the finding, so it cannot judge whether the study is worth approving.
A good question implies its own answer’s shape. "Does daily use of image-based platforms predict body-image dissatisfaction among undergraduate women in Lahore, controlling for baseline self-esteem?" — a reader immediately knows what data would settle it, and what a null result would look like.
If you cannot describe the result that would prove you wrong, the question is not ready.
The literature section justifies the question, nothing else
Proposal literature reviews sprawl because they try to demonstrate reading. Their actual job is narrower: establish that the question has not been answered, and that there is theoretical reason to expect a particular answer.
Three to five pages, ending at the gap. Everything that does not build toward the gap belongs in the eventual thesis chapter, not here.
Methods must be justified, not merely stated
"A questionnaire will be distributed to 200 respondents" states a method. It does not justify one. Why a survey rather than interviews? Why 200 — what does that give you in power terms? How are they sampled, and what does the sampling frame exclude?
Every methodological choice should be followed by the reason it was chosen over the obvious alternative. That single habit distinguishes proposals that pass from proposals that come back with a page of questions.
Feasibility is assessed, and honesty helps you
Committees have watched students propose forty interviews with senior officials and complete eleven. They are reading for realism.
State your access explicitly: which institution, which gatekeeper, whether permission is already secured. Include the ethics timeline as a real dependency. Where a risk exists, name it and give the fallback. A proposal that says "if access to Group A is refused, the design remains viable with Group B" reads as competence, not doubt.
The timeline must contain the parts that actually take time
Most student timelines allocate months to data collection and weeks to analysis and writing. Real projects run the other way.
Include ethics approval, instrument piloting, transcription, supervisor turnaround, and revision rounds. A timeline showing three months for writing is more credible than one showing three weeks, because everyone reading it has written a thesis.
Write the abstract last, and make it exact
The abstract is what circulates, and often the only part every committee member reads closely. It needs the question, the design, the sample, and the intended contribution — in that order, in about two hundred words, with no throat-clearing.
If the abstract is vague, the committee arrives at the proposal already unsure what you are proposing, and nothing later in the document fully recovers.
We do this work every week — for MPhil and PhD candidates, faculty, and whole departments.
Start a conversation
