A research proposal is a short document with an outsized job. It decides whether you get to do the project you want, whether you get the supervisor you want, and in some cases whether you get funded at all.
Most rejected proposals are not rejected because the idea was bad. They are rejected because the question was too broad, or because the writer never made clear what they would actually do on a Tuesday morning. This guide covers how to write a research proposal that survives that scrutiny.
What your supervisor is really assessing
Behind whatever the form asks for, three questions are being answered:
- Is this worth doing? Does it address something that is genuinely unresolved?
- Can it be done? With your time, your access, your skills, and your budget.
- Can you do it? Do you understand the field well enough to be trusted with it?
Feasibility is the one students underestimate. An ambitious proposal that clearly cannot be completed in the time available is worse than a modest one that can. Supervisors have watched projects collapse in month four, and they are trying to prevent it.
How long should it be?
Undergraduate proposals are usually 1,000 to 2,000 words. Masters proposals tend to run 1,500 to 3,000. PhD applications commonly ask for 2,000 to 5,000, and funded studentships sometimes more.
Check the specification and stick to it. Going over is read as an inability to follow a brief, which is a bad first impression for someone asking to be supervised.
The sections, and what each one has to do
Title
Specific, not clever. It should tell a reader the topic, the population and ideally the approach.
“Social media and mental health” tells nobody anything. “The relationship between night-time smartphone use and reported sleep quality among first-year UK undergraduates” tells them everything, and it took the same amount of effort.
Background and context
A few paragraphs establishing what is already known and where the unresolved edge is. This is a compressed literature review, and the compression is the skill.
Do not summarise everything ever written. Cite the small number of studies that directly set up your question, and move quickly to the gap.
The problem statement and your question
This is the heart of the document. Everything before it exists to justify it; everything after explains how you will answer it.
Good research questions are narrow enough to answer and open enough to be interesting. “Does social media affect students?” fails both tests. “How do final-year students describe the effect of coursework deadlines on their sleep routines?” passes.
One main question is usually enough, with two or three sub-questions beneath it. Five main questions signals that you have not decided what your project is about yet.
Aims and objectives
These get confused constantly, so: the aim is what you want to achieve overall. The objectives are the concrete steps that get you there.
Objectives should start with verbs you can actually complete and tick off — identify, measure, compare, evaluate. Avoid “understand” and “explore” as objectives, because you can never prove you have finished them.
Proposed methodology
Enough detail that a reader believes you have thought it through. Name your approach, your participants, roughly how many, how you will reach them, what instrument you will use, and how you will analyse what you collect.
Two sentences that often rescue a shaky proposal: say how you will get access to your participants, and say what you will do if recruitment is slower than hoped. Nothing reassures a supervisor faster than evidence you have imagined the project going wrong.
Ethical considerations
Even at proposal stage, show you have thought about consent, anonymity, data storage and withdrawal. If your project involves anyone under eighteen, anyone vulnerable, or any sensitive subject, say so plainly and explain your safeguards. Flagging it early speeds up approval; hiding it delays everything.
Timeline
A simple table of phases against months. Reading, ethics approval, instrument design, data collection, analysis, writing, revision.
Build in slack. Ethics approval routinely takes longer than students expect, and a timeline with no margin tells your supervisor you have never done this before.
References
Formatted in whatever style your department requires, and consistent throughout. A proposal with sloppy references suggests a dissertation with sloppy references.
The mistakes that sink proposals
A question that is too big. By far the most common. If your question could be a book, it is not a dissertation. Narrow by population, by location, by timeframe, or by outcome — narrow by all four if you have to.
No gap. If your background section does not end with something unresolved, your proposal has not made its case. “Nobody has studied this in a UK context” is a legitimate gap. “Nobody has studied this at all” is usually a sign you have not searched properly.
Methods that do not match the question. A question asking how people experience something cannot be answered with a multiple-choice survey. This mismatch is spotted instantly.
Assuming access you do not have. Proposing interviews with hospital consultants, or survey access to a company’s staff, without having asked anyone. Secure access first, or propose something you can actually reach.
Writing it as a finished argument. A proposal describes work you have not done. If you already know what you will find, either you are guessing or the project is not worth doing.
A test that catches most problems
Describe your project out loud in two sentences, to someone outside your subject. First sentence: what you are going to find out. Second: how you are going to find it out.
If you cannot do it without saying “well, it depends” or trailing off, the proposal is not ready — and the problem is almost always the question, not the writing.
Before you send it
Read it once asking only whether the methodology could actually answer the question. Read it again asking whether the timeline is honest. Then check every claim in the background section has a citation attached.
Send it to your supervisor with a specific question rather than “any feedback welcome”. Something like “is the scope realistic for the time available?” gets you a far more useful reply.
Getting help with it
Proposals are short, which makes them deceptively hard — there is nowhere to hide a vague idea in 1,500 words. If yours keeps coming back with comments about scope, the fix is nearly always narrowing the question rather than rewriting the prose.
We work on proposals as part of our thesis writing help and dissertation writing help, and we also handle research papers across most subject areas. Once your proposal is approved, the next thing you will write is usually the methodology — there is a separate guide to that chapter which picks up where this one stops.