Research funding & grants playbook — proposal template

Purpose

This template helps you translate research strategy into competitive, fundable proposals. It focuses on clear strategic alignment, feasible plans, justified budgets, measurable impact, and a short submission-readiness checklist so you avoid wasteful rework on low-fit opportunities.

How to use this template

Use each section as a writing prompt rather than a checkbox. Keep the funder’s evaluation criteria and your portfolio strategy visible while drafting. For team use, copy this template into your team domain and record draft answers so you can iterate and reuse content across proposals.

Template sections (copy into proposal)

1. Cover / Title

   Concise project title (8–12 words), lead institution, PI(s), requested funding amount, duration, and one-sentence statement of strategic fit and expected impact.

2. Executive summary / Abstract

   One short paragraph (100–250 words) that answers: What is the problem? Why does it matter? What will you do? What is the expected outcome/impact? How does this align with the funder and your portfolio strategy?

3. Strategic alignment and objectives

   Explain how the project maps to your research strategy and the funder’s priorities. State 2–4 SMART objectives or hypotheses. If part of a portfolio, identify how this project fills a gap or advances a program-level outcome.

4. Work plan — milestones & deliverables

   Provide a clear, time-bound plan. Include deliverables, responsible parties, and acceptance criteria. A simple milestone table helps reviewers evaluate feasibility.

   Example mini-table headings: Milestone | Deliverable | Owner | Date

5. Methods & feasibility

   Concise description of approach, experimental design, data and analysis methods, required facilities, and why the team can deliver. Highlight key technical risks and mitigation (cross-ref to Risk section).

6. Team, roles & capabilities

   List key personnel, short bios (or attach CVs), and explicit responsibilities. Explain any partnerships and their contributions. Make it clear who leads work packages and who provides critical expertise.

7. Budget & cost justification

   Provide a budget table by category and a short justification for each major line. Typical categories: Personnel (FTE and roles), Equipment, Consumables, Travel, Subcontracts/Consultants, Facilities/indirect costs. Explain why costs are necessary to achieve objectives and align to funder rules.

   Example cost-justification prompts: Who is funded (role, %FTE, salary basis)? What equipment is essential vs. nice-to-have? Are there cost-sharing or in-kind commitments?

8. Risk assessment & mitigation

   Identify 3–6 principal risks (technical, operational, timeline, regulatory, data, partnership) and a concrete mitigation for each. Short risk table: Risk | Likelihood | Impact | Mitigation

9. Evaluation & impact measurement

   Define how success will be measured (quantitative and qualitative metrics), data collection plans, and how results feed back into the portfolio. If applicable, include data management and reproducibility practices (e.g., data sharing, code availability, preregistration).

10. Dissemination & sustainability

    Explain who the target audiences are, how you will share outcomes (publications, open data, tools, policy briefs, commercialization), and how the work will be sustained after funding ends.

11. Timeline (Gantt-style)

    High-level schedule showing major milestones, dependencies, and deliverable due dates. Keep it simple and tied to the work plan above.

12. Appendices & supporting information

    Budget detail, CVs, letters of support, facilities descriptions, prior work, preliminary data. Only include what funder requests.

Submission readiness checklist (quick review before submitting)

• Is the project clearly aligned to both your portfolio priorities and the funder’s call?
• Are objectives SMART and measurable?
• Is the budget realistic, justified, and compliant with funder rules?
• Are roles and responsibilities clearly defined and supported by CVs/letters?
• Have you identified principal risks and practical mitigations?
• Do evaluation metrics map to stated objectives and deliverables?
• Is the timeline realistic with clear dependencies?
• Have you followed the funder’s formatting, page limits, and mandatory attachments?

Practical tips

• Lead with impact: reviewers see many technical plans — start with why the work matters and the outcomes reviewers will care about.
• Use evidence: reference preliminary data or prior work briefly; attach details in appendices.
• Be explicit about feasibility: show recent relevant outputs, available equipment, or institutional support to lower perceived execution risk.
• Align language to the funder: reuse key terms from the call and mirror the evaluation criteria.
• Keep budget notes succinct and defensible—avoid vague line items.

Common pitfalls to avoid

• Submitting a proposal that doesn’t map to your portfolio priorities or that duplicates other funded work.
• Under-justifying personnel time or over-requesting nonessential equipment.
• Missing page limits, required attachments, or institutional approvals.
• Failing to define measurable outcomes or an evaluation plan.

Next steps and adaptations

For team reuse: copy this template into your domain, save draft responses for common sections (lab capabilities, standard CV snippets, boilerplate justification), and maintain a proposal tracker to avoid duplicate effort across the portfolio.