A good research idea alone rarely wins funding. Funders receive far more research proposals than they can support, so reviewers must choose between many worthwhile projects. The proposals that succeed are not always the most ambitious ones; they are the ones that make the reviewer's job easy. They state a clear problem, explain exactly what will be done, show that the plan is feasible within the budget and time available, and explain why the work matters beyond the research team itself.
This guide explains how to write a proposal that does all of that. It covers the components funders expect, how to build a credible budget and timeline, and the mistakes that most often lead to rejection. It builds on our guides on finding a research gap, writing a literature review, and writing a methodology section, because a strong proposal draws on all three skills: a gap worth filling, a literature base that proves it, and methods that can fill it.
Every funder publishes its own criteria, and you should read them before writing a single paragraph, but most reviewers weigh the same handful of questions. Is the problem important and clearly defined? Is the proposed work original, or does it repeat what is already known? Can this team actually deliver it, with the resources requested, in the time proposed? And will the results matter to anyone beyond the project itself — to other researchers, to practitioners, to policy, or to the public?
Fit matters as much as quality. A strong proposal sent to the wrong funder will fail, because reviewers judge it against that funder's priorities, not against research in general. Before you write, check the funder's themes, eligibility rules, typical award sizes, and previously funded projects. If your project does not fit the call, either reshape the project honestly to fit it or find a different funder. Reviewers can tell quickly when a proposal has been recycled without adaptation, and it damages your credibility.
Most funding proposals follow the same logical order, because it mirrors how a reviewer thinks: what is the problem, what will you do about it, how will you do it, what will it cost, and what will change as a result. Funder templates vary, so follow the headings your funder provides, but the components below appear in almost every proposal.
The title should name the topic and, where possible, the approach or population in plain words. Avoid clever wordplay that obscures the subject; reviewers often screen dozens of titles, and a clear title helps yours survive the first pass. The summary, usually one page or less, must stand alone: it states the problem, the aim, the methods in brief, and the expected outcome. Many reviewers read only the summary before deciding how carefully to read the rest, so write it last, after the full proposal is drafted, and make every sentence earn its place.
State the problem in concrete terms, with evidence that it exists and matters. Who is affected, how badly, and what happens if nothing is done? Then explain why now is the right time: a gap in the evidence, a new method, a policy window, or a problem that is getting worse. The rationale connects the problem to your project in one clear line of argument — if the reader cannot follow that line, the proposal will feel unfocused no matter how good the individual parts are.
Objectives state what the project will achieve, and research questions state what it will answer. Keep them few, specific, and measurable: three to five objectives are usually enough, and each one should map onto a method and an output later in the proposal. Vague objectives such as "to study the problem" or "to improve understanding" tell the reviewer nothing, because they cannot be tested. Strong objectives name the outcome, the population, and the standard of success — for example, to measure the prevalence of a condition in a defined group, or to test whether a specified intervention changes a specified outcome.
Show that you know the field and that your project fills a real gap in it, rather than repeating existing work. You do not need a full literature review, but you do need the key studies, the unresolved questions, and a clear statement of what is new about your approach. Reviewers in your field will know the literature, so cite accurately and do not overclaim: saying "no previous research exists" is risky unless you have searched thoroughly, because a reviewer who knows one counterexample will doubt the rest of the proposal.
The methods section is where most proposals are won or lost. Describe the design, the study population or sample, the data to be collected, and the analysis, in enough detail for a reviewer to judge feasibility and rigour. Name the sample size and how it was decided, the instruments or procedures, and the analytic approach. If the project has stages — a pilot, then a main study, for instance — explain the decision points between them. Reviewers look for risks here, so name the main risks yourself and say how you will handle them: a low response rate, a difficult recruitment setting, or a method that may need adjustment.
A budget is an argument, not just a list of costs. Every item should be justified in one line: why it is needed, and why the amount is reasonable. Funders commonly allow staff time, consumables, equipment, travel, and dissemination costs, but rules differ — some funders will not pay for certain items, and some cap particular categories. Check the rules first, cost honestly, and do not inflate or pad: reviewers notice padded budgets, and they also notice budgets so tight that the project could not realistically be delivered. If your institution adds overheads or requires matching funds, confirm those figures with your finance office before submitting, not after.
Present the timeline as phases with milestones and deliverables: ethics approval by a given month, data collection complete by another, analysis and writing by the end. A timeline shows the reviewer that the project is planned, not just imagined, and it lets them judge whether the schedule is realistic. Build in time for the slow parts — ethics approval, recruitment, and peer review of outputs all take longer than first-time applicants expect — and show what happens if a phase slips.
Show that the team covers the skills the project needs: the subject expertise, the methods, and the management. For each key person, give a short role description and the relevant experience, not a full CV — funders usually request CVs separately. If the project needs equipment, data access, or partnerships, state what is already secured and what is still to be arranged. A partnership described as "to be confirmed" without any evidence of discussion is a weakness; a letter of support from a partner organisation is much stronger.
Explain who will benefit from the work and how they will hear about it. Impact is not the same as publication: a paper in a journal reaches other researchers, but practitioners, policymakers, or communities may need briefings, workshops, guidelines, or training materials. Name the audiences, the channels, and the timing, and be realistic — claiming that a small study will transform national policy invites scepticism, while a credible plan to reach the practitioners who face the problem every day is persuasive.
State the ethical approvals the project needs and how they will be obtained, including consent procedures for human participants and welfare standards for animal work. Our guide on research ethics, consent, and animal welfare explains these requirements in detail. Also include a short risk register: the main things that could go wrong, how likely they are, and what you will do if they happen. Reviewers treat a proposal with no risks as naive, not as strong.
The most common reason is a mismatch between ambition and resources: a project that would need three years and a large team, proposed for a one-year small grant. The second is vagueness in the methods — reviewers cannot judge work they cannot see clearly, so a methods section that gestures at "surveys and analysis" without detail will score poorly. The third is a budget that does not match the plan: staff time for work the timeline does not include, or expensive equipment with no justification. The fourth is poor fit with the funder's call, which no amount of good writing can fix.
Presentation matters too. A proposal full of errors, inconsistent numbers, or sections that contradict each other signals that the project itself may be run carelessly. Read the whole proposal aloud before submitting, check that every number appears consistently in the text, budget, and timeline, and ask a colleague outside the project to read it for clarity. If they cannot explain back what you will do, why it matters, and what it will cost, a reviewer will struggle too. Finally, respect the funder's format exactly — page limits, font sizes, and required sections are not suggestions, and proposals that ignore them can be returned without review. Our guide on how to publish a research paper covers the later stage, when funded work becomes a manuscript, and our guide on writing a research abstract helps with the summary that opens both proposals and papers.
Rejection is a normal part of seeking funding, and the reviewer comments that come with it are the most valuable guidance you will receive. Read them once for the disappointment, then read them again slowly, separating criticisms you can fix from judgements you disagree with. Most comments fall into the first group: unclear objectives, methods that need detail, a budget that does not match the plan, or a timeline that looks unrealistic. Each of those can be addressed directly in a revision, and a short response document explaining what changed — and where — helps reviewers see that their advice was taken seriously.
Where you disagree with a reviewer, do not ignore the point or argue defensively. Explain your reasoning with evidence, and consider whether a compromise is possible: a design choice the reviewer questioned can often be defended more strongly with an added justification or a cited precedent. If the funder allows resubmission, use the revised proposal rather than sending the original elsewhere unchanged, because the same weaknesses will likely draw the same criticisms. Keep a record of each submission round, the comments received, and the changes made, so that the proposal improves with every attempt instead of merely circulating.
| Component | What it must show | Reviewer question |
|---|---|---|
| Title and summary | Topic, aim, methods, outcome in brief | Is this worth reading in full? |
| Problem and rationale | Evidence the problem matters, and why now | Why does this work need doing? |
| Objectives and questions | Few, specific, measurable aims | What exactly will be achieved? |
| Methods | Design, sample, data, analysis, risks | Can this team deliver credible results? |
| Budget and timeline | Justified costs, phased milestones | Is the plan realistic and affordable? |
| Impact and ethics | Beneficiaries, dissemination, approvals | Who benefits, and is the work safe? |
These authoritative external resources explain the standards and guidance mentioned in this article:
How long should a research proposal be?
It depends entirely on the funder. Some calls ask for two pages, others for twenty. Follow the funder's limit exactly, and treat it as a test of your ability to prioritise: if you cannot fit the argument in the allowed length, the argument is not yet clear enough.
Should I contact the funder before applying?
Yes, where the funder invites it. A short email or call to confirm that your project fits the call can save weeks of wasted writing. Prepare a one-paragraph summary before you contact them, so the conversation is useful.
What if I have no previous grants?
Funders do fund first-time applicants, but they need evidence you can deliver: relevant publications, a pilot study, a strong supervisor or collaborator, or institutional support. Name that evidence explicitly rather than hoping reviewers will find it.
Can I submit the same proposal to two funders?
Only if both funders allow it, and you must usually declare it. Submitting the same proposal to two funders without disclosure can breach their rules and damage your reputation, so check each funder's policy first.
What happens if my proposal is rejected?
Read the reviewer comments carefully, revise the proposal, and resubmit where the funder allows it. Many funded projects succeeded on a second or third attempt, and reviewer feedback is the most useful guidance you will get for the revision.
Do I need ethics approval before applying?
Usually not before submission, but most funders require approval before the funded work starts, and some ask for evidence that approval has been sought. State your ethics plan and timeline in the proposal so reviewers can see it is handled.