Five Strategies To Improve Your Grant Success Rates

01 Begin with the funding call, not the project description

Researchers often begin by describing the work they want to conduct and then try to fit that description into a funding opportunity. This can produce a scientifically credible application that still sits awkwardly within the purpose of the call.

Before drafting, identify the programme’s stated objectives, assessment criteria, eligible activities and expected outcomes. Pay attention to how terms such as excellence, impact, feasibility or innovation are defined by that particular funder. Their meaning is not identical across every scheme.

A useful preparation exercise is to construct a simple table with three columns: the assessment criterion, the evidence the reviewer will need and the section of the proposal in which that evidence will appear. This exposes omissions before substantial writing begins.

• Confirm that the project falls clearly within the funder’s remit.
• Identify every scored criterion and any threshold requirements.
• Map each criterion to specific evidence in the application.
• Check that the budget and project duration are appropriate for the scheme.

02 Define one central scientific proposition

Reviewers should be able to identify the proposal’s central argument after reading the summary and aims. If the application appears to pursue several loosely connected questions, it becomes difficult to judge what the project is principally intended to establish.

The central proposition should connect four elements: the unresolved problem, the relevant gap in current knowledge, the proposed contribution and the reason the work should be undertaken now. The individual aims can address different aspects of the problem, but they should collectively advance the same scientific argument.

This does not require reducing a complex project to a slogan. It requires deciding which claim the evidence, methods and work plan are organised to support. Secondary questions that do not materially strengthen that claim may be better removed or reserved for subsequent work.

03 Make the relationship between aims, methods and outcomes explicit

A proposal should not require the reviewer to reconstruct its logic. Each aim needs a defined question, an appropriate method, an interpretable outcome and a clear relationship to the overall objective.

The work packages should be connected without creating unnecessary fragility. If the entire project depends on one early experiment producing a particular result, reviewers may reasonably question whether the later work can proceed if that result is not obtained.

For each aim, explain:

• the question or hypothesis being examined;
• why the selected approach is suitable;
• what evidence will be generated;
• how different possible outcomes will be interpreted; and
• what alternative route is available if the initial approach proves unsuitable.

These connections are often easier to evaluate when they are supported by a restrained figure or workflow. A useful diagram clarifies the experimental logic; it should not merely repeat the written work plan.

04 Demonstrate feasibility without concealing uncertainty

Ambitious research is not necessarily unfeasible research. The distinction depends on whether the proposal shows that the team understands the technical risks and has the expertise, resources and alternatives required to manage them.

Preliminary observations can support feasibility, but they should not be presented as though they have already answered the proposed question. Their role is to establish that the system can be studied, that the principal methods are workable or that the underlying premise is sufficiently credible to justify further investigation.

Feasibility is also conveyed through less prominent sections of the application. A realistic timetable, justified sample sizes, access to facilities, clearly allocated responsibilities and a budget that corresponds to the work plan all contribute to the reviewer’s assessment.

Discuss important risks directly. A carefully considered limitation accompanied by a credible mitigation strategy is generally more reassuring than an application in which no uncertainty is acknowledged.

05 Revise for evaluation, not only for readability

Editing a grant proposal is not limited to improving its language. The final review should test whether the application provides the evidence needed to support a favourable judgement under each assessment criterion.

Ask at least one colleague who was not involved in preparing the proposal to read it under realistic conditions. Rather than asking whether the text “sounds good,” ask them to identify the central question, summarise the approach, describe the expected contribution and list the most important risks.

If their account differs substantially from what you intended, the problem is usually structural rather than stylistic. Further polishing will not resolve it until the scientific argument has been made clearer.

The final check should also compare the summary, aims, work packages, impact statement, timeline and budget. Small inconsistencies between these sections can undermine confidence because they suggest that the project has changed during drafting without the full application being updated.