How to Write a Research Proposal

A research proposal has one job — to convince the reader that your question is worth answering and that you have a credible plan to answer it.

A research proposal is a plan you write before the research, to persuade a supervisor or committee that the project is worthwhile, original, and feasible. It’s a pitch as much as a document: a strong one shows you know the field, have a sharp question, and have thought through exactly how you’ll investigate it. Most proposals share the same core sections, whatever the discipline.

Start with a focused research question

Everything follows from the question, so make it specific and answerable. “Social media and mental health” is a topic, not a question. “How does daily time spent on image-based social media relate to body-image dissatisfaction among first-year university students?” is a question — bounded, measurable, and clearly the thing the study will answer. A working title and one or two clear objectives should flow directly from it.

Make the case: rationale and significance

Explain why the question matters and why now. What gap in current knowledge does it fill? Who benefits from the answer — a field, a profession, a policy debate? This is where you justify the project’s existence; a reader who finishes this section unconvinced that the study is needed won’t approve it, however sound the method. Be concrete about the contribution rather than claiming your topic is simply “important.”

Situate it in the literature

Show that you know the relevant existing work and where your study fits within it. Summarize the key findings and debates, and identify the gap your research addresses — proper research builds on what’s been done rather than reinventing it. Organize this around themes or arguments rather than listing one source after another, and cite as you go; this section proves you’ve done the groundwork and aren’t duplicating a study that already exists.

Set out the methodology

Describe how you’ll actually answer the question, in enough detail to show it’s workable. Will the approach be qualitative, quantitative, or mixed? Who or what will you study, and how will you sample? How will you collect and analyze the data? Justify each choice by linking it back to the question — the method has to fit the problem, not the other way around. Note any ethical approval you’ll need and how you’ll protect participants, since committees look for this closely.

Anticipate outcomes and limitations

You can’t know the results in advance — if you did, there’d be no point running the study. But you can discuss the outcomes you expect and why, and what different results would mean. You can also name the limitations honestly: constraints of time, sample, or scope. Acknowledging these up front signals rigor, not weakness, and shows you’ve thought past the ideal version of the project to the real one.

Add a realistic timeline and resources

Close with a schedule that breaks the project into phases — literature review, ethics approval, data collection, analysis, writing — with rough dates, and note any resources you’ll need (software, equipment, access to participants). A credible timeline reassures the reader that the project can actually be completed in the time available, which is often the quiet difference between a proposal that’s approved and one that’s sent back for a rethink.

Make the problem statement do real work

A proposal is judged first on whether the question is worth answering. The problem statement should establish three things quickly: what is currently known, what is missing, and why the gap matters. Reviewers form a view here, and a proposal that opens with general background rather than a specific gap has spent its most valuable paragraph on scene-setting.

Be concrete about the gap. “Little research exists” is rarely true and easy to dismiss; “existing studies have examined this in acute settings, but community settings differ in staffing ratios and continuity of care” identifies exactly where the boundary of knowledge sits.

Write questions your method can answer

Research questions and methods are chosen together. A question asking how a group experiences something implies qualitative work; one asking whether an intervention changes an outcome implies a design with comparison. A proposal whose questions and methods do not match is the fastest way to lose a reviewer’s confidence.

Keep the number small. One main question with two or three sub-questions is usually right for a student proposal; a list of eight signals that the scope has not been decided.

Justify the method rather than describing it

Describing what you will do is necessary; explaining why it is the right choice is what earns marks. For each major decision — design, sampling, instrument, analysis — give the reason and, where relevant, the alternative you rejected. “Semi-structured interviews were chosen over a survey because the study aims to surface reasoning that fixed-response items would foreclose” shows judgement.

Specify enough that a reader can picture the study happening: how many participants, recruited how, from where, over what period, and analysed with what approach.

Address ethics concretely

Ethics sections that promise confidentiality in general terms are weak. Name the actual risks your study creates and the specific measures that address them: how consent is obtained and from whom, how data is stored and for how long, what happens if a participant discloses something distressing, and how withdrawal works after data collection.

Where approval is required, say which committee and note the timeline — reviewers assessing feasibility want to see that you have accounted for it.

Show the project is achievable

Feasibility is assessed even when the brief does not name it. A timeline broken into phases, with realistic durations for recruitment and approval, demonstrates that you have thought about execution. So does an honest account of what you will do if recruitment is slower than hoped.

• Access — do you have, or can you obtain, permission to reach participants?
• Skills — do you have the analytical techniques the design requires?
• Time — does the schedule survive approval delays?
• Resources — equipment, software, transcription, incentives.

State the contribution and its limits

Close by saying what will be known at the end that is not known now, and for whom that matters. Then state the limits plainly. A proposal that acknowledges what its design cannot establish is more credible than one that implies it will settle a question the method cannot reach.