How to Write a Grant Proposal: Funder Fit, Aims, Approach, Budget and Resubmission

Reviewers typically read several proposals under time pressure and score each against the funder's criteria. They look for a clear problem, a credible plan and a capable team, and they note anything that makes them doubt feasibility. A proposal that requires detective work to understand loses points even when the underlying idea is excellent.

Before writing, find the call's assessment criteria and scoring scheme and paste them at the top of your working document. Every section you write should visibly answer one or more of these criteria, ideally using the funder's own terms as headings or signposts. If the funder publishes reviewer guidance, read that too; it tells you what reviewers are told to look for.

Funder fit is the most common reason good proposals fail before review. Each funder and each scheme has a mission, eligible applicants, eligible costs, typical award sizes and priority themes. A basic-science project will not fit a scheme that funds implementation in communities, however strong it is.

Search funder databases available through your institution's research office, read the call text in full, and look at previously funded projects, which many funders list publicly. Check eligibility early: career stage, host institution, country, collaborators, and whether you need an institutional endorsement or an internal selection round. Many schemes also require a letter of intent, pre-proposal or outline stage, which is short but decides whether you are invited to submit a full proposal.

If the call allows it, contact the program officer with a short summary of your idea. Program officers cannot write your proposal but can often tell you whether it fits, which saves weeks of work on a mismatched application.

• Does the funder's mission or call explicitly include your topic or approach?
• Are you and your institution eligible, including any career-stage rules?
• Does the typical award size and duration match what the project needs?
• Are your major costs, such as staff, equipment or overheads, eligible?
• Is there an outline or letter-of-intent stage, and what is the internal deadline at your institution?

Many funders ask for a one-page aims or objectives section, and even where they do not, drafting one first disciplines the whole proposal. It usually opens with the problem and its importance, identifies the specific gap or barrier your project addresses, states the overall goal and, where relevant, a central hypothesis, then lists two to four aims, each with a short description of approach and expected outcome, and closes with the expected impact.

Aims should be related but not dependent on each other in a way that makes the whole project fail if one aim does not work. They should also be achievable within the time and budget. Reviewers are wary of proposals with too many aims or aims phrased as vague activities such as "to explore" or "to investigate" without a measurable outcome.

A useful test is to show the aims page to a colleague outside your immediate field. If they cannot explain back what you will do and why it matters, reviewers on a mixed panel may struggle too.

Significance explains why the problem matters and what will change if you succeed. Be concrete: who is affected, what the current limitation is, and how your results will be used by researchers, practitioners, policymakers or communities. Cite the key literature that establishes the gap, but do not turn this section into a full literature review.

Innovation explains what is new: a concept, a method, a population, a data source, a combination of disciplines. Innovation for its own sake does not score well; tie it to why the new element is needed to solve the problem. Some funders, especially in Europe, frame this as the project's excellence and ambition in relation to the state of the art.

The approach section is where most scoring decisions are made, because it determines whether reviewers believe the project can succeed. For each aim, describe the design, participants or materials, data collection, analysis plan, and how the results will answer the aim. Justify key choices, such as sample size through a power calculation or a qualitative sampling rationale, and address rigor and reproducibility where the funder asks for it.

Anticipate problems. A brief section on potential pitfalls and alternative strategies for each aim shows reviewers you have thought realistically about risk. Preliminary data, pilot results or previous publications can demonstrate feasibility, and many funders value them strongly even when they are not required.

Present the work plan visually. A Gantt chart or timeline with work packages, milestones and deliverables helps reviewers see that the plan fits the time and staff available. Large collaborative proposals, such as those for Horizon Europe, typically require detailed work packages, a risk table and a management structure.

The outline below is invented to show the logic of a strong aims page for a three-year project on reducing hospital readmissions among older adults. It is not a template to copy; funders and fields differ.

Notice that each aim has a distinct approach and a distinct deliverable, and that aim 3 uses the outputs of aims 1 and 2 without failing entirely if either produces unexpected results. The closing paragraph links the expected outcomes directly to the problem stated at the start.

• Opening: the problem, its scale and consequences, stated in two or three sentences with key citations.
• Gap: existing discharge interventions rarely address medication complexity in patients with cognitive impairment.
• Goal and hypothesis: to test whether pharmacist-led discharge support reduces 30-day readmissions in this group.
• Aim 1: characterize medication-related readmission pathways using linked health records (quantitative, retrospective).
• Aim 2: co-design the intervention with patients, carers and pharmacists (qualitative, participatory).
• Aim 3: test feasibility and preliminary effect in a pilot randomized trial across two hospitals.
• Impact: evidence to inform a full-scale trial and discharge guidelines for older adults with cognitive impairment.

Reviewer comments on unsuccessful proposals tend to repeat the same themes across funders and disciplines. Checking your draft against this list before internal review can prevent many of them.

• The aims are too ambitious for the time and budget, or depend on each other so that one failure sinks the project.
• The methods lack detail on sampling, measures, analysis or how aims will be answered.
• No pitfalls or alternatives are described, suggesting the team has not considered risk.
• Significance is asserted rather than demonstrated with evidence of the problem.
• The team lacks a key expertise, such as statistics or a clinical partner, with no collaborator named.
• The budget does not match the work plan, or costs are unexplained.
• The proposal ignores a specific call requirement, such as patient involvement, equality considerations or a data management plan.
• Dense, jargon-heavy writing makes the proposal hard to follow for a mixed panel.

Criteria differ, but most can be mapped onto the same core questions. The table gives a general picture; always read the current call document, because criteria and weightings change.

The US National Institutes of Health, for instance, introduced a simplified review framework for most research project grant applications with due dates from 25 January 2025. It organizes review around whether the research should be conducted and whether it can be conducted, with scored factors for the importance of the research and for its rigor and feasibility, and an assessment of whether expertise and resources are sufficient.

The budget translates the work plan into costs, and reviewers check that the two match. Every staff member, trip, piece of equipment and consumable should be traceable to an activity in the approach section. Unexplained round numbers or a large travel line without a stated purpose invite questions.

Work closely with your institution's research finance office. They know the funder's rules on overheads or indirect costs, salary rates, inflation, equipment thresholds and cost categories, and many funders require institutional approval of the budget before submission. Common categories include personnel, equipment, consumables, travel, participant costs, publication and open access fees, subcontracts and indirect costs.

The justification should be specific and brief: what the cost is, how it was calculated and why it is necessary. For example, rather than "Travel: conference", write "Travel for one researcher to present results at a major international conference in the final year, estimated from typical registration, economy airfare and accommodation for four nights."

Many funders ask how results will reach users beyond academic publication. Describe named audiences, specific channels and realistic activities, such as practitioner workshops, policy briefs, open datasets or software releases, and how you will know whether they worked. Development and social-impact funders frequently require a logical framework or theory of change that links activities to outputs, outcomes and long-term impact with measurable indicators.

Do not neglect the supporting sections. Data management plans, ethics statements, letters of support, biosketches or CVs in the required format, equal opportunity or gender equality plans, and institutional letters often carry mandatory requirements. A missing or incorrectly formatted document can make an application ineligible without any scientific review.

Write in plain, active language, use headings that mirror the criteria, and make key sentences easy to find, for example by bolding the one-sentence statement of each aim. Figures that summarize the concept, design or timeline are often more effective than extra text.

Build in time for internal review. Ask at least one colleague familiar with the funder, and one outside your field, to read the full proposal and score it against the criteria. Many institutions run internal peer review or mock panels for large schemes. Then allow several days for institutional sign-off and for problems with the funder's submission portal, which are common close to deadlines. An independent grant proposal review can serve the same purpose where internal support is limited.

Most successful researchers have had proposals declined, and many funded projects were resubmissions. If you receive reviewer comments and scores, treat them as the best guide to what the next panel will look for. Separate comments about fundamental weaknesses, such as feasibility or significance, from those about clarity, which are often easier to fix.

Check the funder's resubmission rules. Some schemes allow a formal resubmission with an introduction responding to previous reviews, some limit the number of resubmissions, and others treat every application as new. Where an introduction is allowed, summarize the main criticisms and the specific changes you made, in a courteous, non-defensive tone similar to a response to journal reviewers. Where it is not, still address the criticisms within the proposal, because some reviewers may have seen the earlier version.

Sometimes the right response is a different funder or scheme rather than a revised proposal. If reviewers praised the science but questioned fit, look again at funder alignment.