A strong grant application is not simply a good idea written persuasively. It is a response to a specific funding call, written for a defined review process, within strict eligibility, budget and formatting rules. The most common mistake is beginning with the narrative before confirming that the applicant, host institution and project actually fit the scheme.
This guide focuses on the application process itself: how to interpret a call, organise the proposal, build a defensible budget, write for reviewers and avoid administrative mistakes that can disqualify an otherwise strong project.
Start with the funding call, not your draft
Every serious grant application should begin with the current call documentation. Read the purpose of the programme, who can apply, what organisations can hold the award, what costs are allowed, the project duration, the deadline, assessment criteria and required attachments.
Official funders often make clear that scheme-specific instructions override more general guidance. The U.S. National Institutes of Health, for example, publishes a formal hierarchy of application instructions and tells applicants to follow the current notice of funding opportunity and application guide. The same principle applies elsewhere: use the rules for the exact call you are entering, not the rules from a similar grant last year.
Confirm eligibility before writing anything substantial
Eligibility can involve the applicant, career stage, degree status, years since PhD, citizenship, residence, host institution, project location or subject area. Some calls are open to individuals; others require an eligible organisation to submit. Some international schemes allow foreign collaborators but not foreign lead institutions.
Create an eligibility checklist and mark each point with the source that confirms it. If one item is unclear, ask the funder or your institutional research office before investing days in a proposal.
Check the real deadline
The public deadline may not be your real deadline. Universities and research institutes often require internal budget approval, compliance checks or sign-off days or weeks earlier. Collaborators may also need time to approve their contribution.
Record three dates: the funder’s closing date, the institutional submission date and your own drafting deadline. Work backwards from the earliest one.
Understand what the reviewers will score
Review criteria are not decoration. They should determine the structure of the proposal. If a scheme scores significance, approach, feasibility, team and impact, make sure the reader can find clear evidence for each element.
The European Commission’s current guidance on proposal submission emphasises that each call has its own criteria and requirements and that applicants should read the call guidelines carefully before preparing a proposal. That sounds obvious, but many weak applications answer the researcher’s preferred question instead of the funder’s question.
Write a one-paragraph project logic before the full application
Before drafting sections, write a short project logic statement that answers five questions: What problem exists? What specific question will you address? Why is it important now? What will you do? What will exist at the end that does not exist today?
If you cannot explain the project clearly in a short paragraph, the full proposal is likely to become diffuse. This summary also helps collaborators agree on the same project before different sections are written independently.
Make the problem specific enough to fund
Large problems attract attention, but grants fund projects. “Climate change is a major challenge” is too broad. A fundable proposal identifies a specific gap, population, mechanism, method or decision problem that can be investigated within the award period.
Use evidence to show that the gap is real, but do not turn the background into a literature review with no decision point. The reader should understand why the proposed work is necessary by the time they reach the aims.
Write aims that can be completed
Each aim should contribute directly to the central question and be realistic for the time, budget and team. Avoid adding extra aims simply to make the project appear ambitious.
A useful test is whether the project would still be coherent if one aim had to be removed. If the proposal is five unrelated mini-projects under one title, reviewers may question feasibility.
Methods should show a credible path from question to evidence
Describe the design, participants or data, recruitment or sampling, measures, procedures, analysis and quality controls at the level expected by the call. Do not hide weak feasibility behind technical language.
If the project depends on access to a dataset, laboratory, field site or participant population, show that access is realistic. Where approvals are required, state the status and timeline.
Build the timeline alongside the methods
A timeline should reflect dependencies. Recruitment cannot begin before ethical approval if approval is required. Analysis cannot be completed before data collection. Dissemination should not be scheduled as if all results are known in advance.
Milestones are useful when they mark meaningful decisions: ethics approval received, recruitment complete, dataset locked, prototype tested, manuscript submitted or policy briefing delivered.
Write for an intelligent reviewer who may not be your exact specialist
Review panels often include people close to your field but not working on the same narrow problem. Define specialist terms when they matter, avoid unnecessary acronyms and explain why the method is appropriate rather than assuming its value is obvious.
Clarity is not simplification of the science. It is making the logic easy to follow.
Show feasibility, not just originality
Novelty matters, but reviewers also need confidence that the team can deliver. Evidence can include pilot data, prior methods, existing partnerships, access agreements, preliminary recruitment, technical capability or previous outputs.
If the project contains a high-risk element, explain how you will manage the risk. A realistic alternative strategy can strengthen a proposal because it shows planning rather than uncertainty.
The team should match the work
Every named collaborator should have a clear role. Avoid adding senior names who have no defined contribution. Explain who leads each work package, who provides specialist expertise and how decisions will be made across institutions.
International projects should also address practical collaboration: communication, data sharing, governance and responsibility for deliverables.
Build the budget from the work plan
The budget should follow the project, not the other way around. Start with the resources needed to complete each activity: personnel, equipment, software, participant costs, travel, consumables, data access, training, dissemination and other eligible costs.
Then check each item against the funder’s rules. Some schemes restrict equipment, overhead, subcontracting, conference travel or salary levels. Do not assume that because a cost is reasonable it is allowable.
Budget justification matters
For significant costs, explain why the resource is needed and how the amount was calculated. “Travel: $10,000” tells a reviewer very little. A justified budget links trips to fieldwork, partner meetings, participant recruitment or dissemination and shows how estimates were derived.
Do not inflate estimates simply because the grant has a high maximum. Reviewers can distinguish between a properly resourced project and a budget designed to reach the ceiling.
Check indirect costs and institutional rules
Some funders allow overhead or indirect costs; others do not. Your institution may also apply salary recovery, exchange-rate policies or internal costing rules.
Work with the research office or finance team early. A scientifically complete proposal can still miss a deadline because the budget was built without institutional approval.
Impact should be specific and believable
Impact is not the same as importance. Explain who could use the results, how they might use them, what pathway connects the research to that use and what the project itself will do to support uptake.
A short grant is unlikely to transform an entire health system, economy or discipline. Credible intermediate outcomes—new evidence, a validated method, a dataset, a decision tool, a clinical pathway, a policy briefing or a new collaboration—are usually stronger than dramatic claims.
Plan dissemination for the audience
Academic papers may be appropriate, but not every stakeholder reads journals. Depending on the project, dissemination can include conference presentations, practitioner guidance, software, open datasets, policy briefs, workshops, teaching material or community feedback.
Only promise outputs the budget and timeline can support.
Ethics, safeguarding and data governance are part of feasibility
Projects involving people, animals, sensitive data, vulnerable populations or field risks need appropriate governance. Explain what approvals will be required and how privacy, consent, safeguarding, storage and access will be handled.
Do not write “ethical approval will be obtained” as a generic sentence if the project contains substantial ethical complexity. Show that you understand the actual issues.
Follow format and page limits exactly
Page limits, font rules, file formats and required templates can determine admissibility. The European Commission explicitly notes that incomplete or non-compliant applications can be treated as inadmissible. Other funders operate similarly.
Do not assume reviewers will overlook an administrative error because the science is good.
Use figures only when they improve understanding
A well-designed workflow figure, conceptual model or timeline can make a complicated proposal easier to understand. A decorative image adds no value. Make sure figures remain readable after conversion to PDF and do not hide essential information in tiny text.
References should support the argument, not fill space
Cite the strongest sources needed to establish the gap and justify methods. Check every citation. Do not include references you have not read or sources generated without verification.
If you use AI tools during drafting, never allow them to invent references, data or factual claims. Funders are increasingly publishing their own rules about AI-assisted application preparation, so check the current policy for the scheme.
Get internal review before submission
Ask at least one reader who understands the field and one reader who was not involved in drafting. The specialist can challenge the science. The second reader can identify logic that is obvious only to the project team.
Give reviewers specific questions: Is the central problem clear? Are the aims coherent? Does the method answer the question? Is the project feasible? Does the budget match the work?
Do a compliance review separately from the scientific review
Before submission, run a final administrative check: eligibility, deadline, page limits, required attachments, signatures, CV format, budget totals, file names, references, host letters and mandatory fields.
Separate this from editing prose. A proposal can read beautifully and still fail because one required attachment is missing.
What a strong grant narrative usually demonstrates
- A real and important problem.
- A specific gap.
- A focused question or set of aims.
- A method capable of answering the question.
- A team with the right expertise and access.
- A realistic timeline.
- A justified budget.
- Clear outputs and credible impact.
- Awareness of ethics, risk and governance.
- Complete compliance with the call.
A practical grant-application workflow
- Read the current call.
- Confirm applicant and host eligibility.
- Record the real deadline.
- Map the review criteria.
- Write the project logic in one paragraph.
- Develop aims, methods and timeline together.
- Build the budget from the work plan.
- Draft for reviewers, not only collaborators.
- Complete ethics and institutional checks.
- Run scientific and compliance reviews separately.
Where this fits in StepOut’s funding structure
This page focuses on how to prepare an application. If you are still trying to find a suitable project funder, begin with the International Research Grants guide. For fellowships, travel grants, funded internships and exchanges, use the broader International Opportunities hub.
Frequently asked questions
Should I write the full proposal before contacting the host institution?
Usually no. If the scheme requires a host, internal approval or budget sign-off, involve the institution early.
Can I reuse a grant proposal for another funder?
You can reuse underlying ideas, but the application must be rewritten for the new scheme’s remit, criteria, format and budget rules.
How long should I spend on a grant application?
There is no universal answer. Complex collaborative grants can take months, while smaller schemes may need far less time. Start from the call requirements and internal deadlines.
What is the biggest preventable grant mistake?
Writing an excellent project that does not fit the call or applicant eligibility. Confirm fit first.
StepOut standard: grant guidance should help applicants build compliant, evidence-based proposals rather than promise funding outcomes. The current call and official application instructions always override generic advice.
