How to write a research proposal

When you apply for a PhD place or a research grant, the proposal is usually the part that decides the outcome. It shows whether you can frame a real question, design a way of answering it and explain why the answer is worth having. A strong proposal can carry an average academic record, and a weak one can sink a strong candidate.

What reviewers are checking

Reviewers do not expect a finished plan that will never change. Projects often change once the work starts, and the people reading your proposal know that. They want to see three things:

1. that the question matters
2. that it can be answered with the time and resources available
3. that you are capable of doing the work

Everything in the proposal should support at least one of those. When you revise, go through it paragraph by paragraph and ask which of the three each one serves. A paragraph that serves none of them can usually go.

The usual sections

Formats differ by field and by funder, so follow whatever brief you are given, including any word or page limit. Most proposals, though, contain the same basic parts, and each one does a particular job for the reviewer.

• Title and research question or aim. Clear and specific. The title should tell a reviewer the topic, and often the setting, in one line.
• Background. What is already known and where the gap or problem lies, written to show you know the field without listing everything in it. Organise it around the gap, not as a summary of one paper after another.
• Significance. Why the question is worth answering, for the field and, where relevant, beyond it. Keep the claims in proportion to the project.
• Approach and methods. What data you will collect or use, how you will analyse it, and why these methods suit this question. Enough detail to show the work is feasible.
• Timeline. A realistic plan for the period available, often by year or by phase.
• Key references. A focused list of the work your proposal builds on.

The research question

The question is the most important element. A precise, answerable question makes every other section easier to write and easier to judge, and vague, sprawling questions are the most common weakness reviewers see. If yours is too broad, narrow it until it could be addressed within a PhD or the life of the grant. Reviewers would sooner fund a small, sharp question done well than a grand one that could never be finished.

Narrowing usually means fixing some of these: a place, a population, a period, a variable, a method. Here is an illustrative example of the same interest at two stages.

The first version is a topic, not a question. Nobody could answer it in three or four years, and a reviewer cannot tell what you would do on your first day. The second names a group, a place, a period and a relationship to measure, so the methods section almost writes itself: you can see what data would be needed and how it might be compared.

A sharper question is not a less important one. It is one where the reader can see what a finished answer would look like.

Background without the reading list

The background section is where many applicants try to show how much they have read, and it becomes a list: one author found this, another found that. Reviewers learn little from this. Organise the section around an argument instead: what is established, where the evidence disagrees or runs out, and how your question sits in that gap. Cite the sources that build that argument and leave out the rest.

Feasibility

Ambition is welcome, but reviewers are wary of projects that cannot be completed. Match the scope to the time and resources, choose methods you are able to use, and be frank about the likely difficulties and how you would deal with them. A proposal that acknowledges its own risks comes across as more credible.

Things a reviewer will look for:

• access to the data, participants, archives or field sites you need, and whether you have it already
• the skills the methods require, and how you would learn any you do not yet have
• ethical approval, if the work involves people, and time allowed for getting it
• equipment, travel or software costs, if the funding is meant to cover them
• a timeline that leaves time for writing up, which always takes longer than planned

Fitting it to the reader

For a PhD, write the proposal with a particular supervisor or group in mind whose expertise matches the work. For a grant, align it with what the funder says it supports. A proposal that makes clear why this group or this funder is the right home for the project is much stronger than one that could have been sent anywhere.

In practice that might mean referring to the group’s methods or recent work, or using the funder’s own priorities as the frame for your significance section. It is often worth contacting a potential supervisor before you finalise the proposal; our guide to emailing a potential PhD supervisor covers how. Some supervisors will comment on a draft, which is the best feedback you can get.

Drafting and revising

Reviewers read a lot of proposals, often quickly, so a clear structure, plain language and a logical order help. Write an early draft, ask someone in your field to comment on it, and cut anything vague or padded before you submit.

A useful test: give the first page to someone outside your field and ask them to tell you, in one sentence, what you will find out. If they cannot, the question is not yet clear enough. Then check the practical details: the word limit, the reference style, the file format and the names of the people and group you mention.

If you are applying for funding alongside the place, our guides to finding a funded PhD and the PhD funding checklist cover the next steps.