Writing Competitive Grant Proposals: Evaluation Criteria, Evidence and Expected Outcomes

Build the proposal around its assessment

Start with the current funding notice and the criteria reviewers will use. Create an outline showing where each criterion will be addressed and what evidence will support the response. This outline becomes a control document for the writing team. It prevents a polished introduction from consuming the space needed to explain methods, feasibility or responsible delivery.

UKRI's core application guidance identifies areas including the project's vision, approach and capability to deliver, while allowing opportunity-specific questions.^[1] The exact headings for another funder may differ. Use the actual application instructions rather than forcing every proposal into a familiar template.

Make the contribution precise

Explain what is currently known, where the uncertainty lies and why resolving it matters. Support the starting point with relevant literature or documented practice. A broad statement that a topic is important does not explain the particular contribution of your project. State what will become possible, clearer or better understood if the study succeeds.

Check whether each objective can be addressed within the proposed work. Objectives should be connected without depending entirely on an early result that may not occur. If the first stage determines the design of later work, explain that decision process and the alternative routes. Make the limitations visible so reviewers can assess the proposal on a realistic basis.

Show the chain from methods to evidence

For every objective, describe the evidence needed, how it will be obtained, the proposed analysis and the interpretation it can support. Explain sampling, recruitment or source selection in enough detail for the design to be assessed. Identify the ethical, data-access and technical conditions on which the work depends.

Use a work plan that shows dependencies rather than a decorative calendar. Recruiting participants may depend on approval and access agreements; analysis may depend on data quality checks. Build review points into the sequence and explain how the team will respond when assumptions fail. A credible alternative should preserve the project's purpose, not merely keep activity going.

Demonstrate capability through relevant contributions

Describe who will do the work and why they are suited to the responsibilities assigned. Relevant experience can include methodological expertise, project delivery, community relationships, technical support or data stewardship. Explain how complementary skills form an effective team. A list of prestigious affiliations does not tell a reviewer how practical responsibilities will be fulfilled.

Identify gaps and the plan to address them. This may involve training, a specialist collaborator or an appropriately scoped service. Confirm that named partners understand their roles and availability. Prepare contributions early enough for institutional approvals, rather than seeking signatures after the application has already described commitments on someone else's behalf.

Connect resources and outcomes to the plan

Make the budget traceable to the work packages. Explain why requested personnel, equipment, services or travel are necessary and how the level of resource was estimated. ESRC's application guidance highlights research quality, value to users, delivery capability and value for money within its own assessment context.^[2] Treat cost justification as part of the project's reasoning, not a final administrative attachment.

Separate outputs from intended outcomes. A dataset, workshop or report is an output; a change in practice may be an outcome. Longer-term social or institutional benefits depend on decisions by others and the context of use. Describe engagement and follow-up that could support those benefits without presenting uncertain impact as an assured result.

An illustrative proposal review

A team proposes a study of feedback practices in postgraduate education. Its first draft promises improved completion rates but measures only staff and student experiences over one semester. An internal reviewer identifies the mismatch. The team refines the immediate contribution to understanding feedback practices and testing a feasible improvement approach, with longer-term completion outcomes reserved for subsequent evaluation.

The revised proposal explains the study's limitations, records the partner department's commitments and aligns the budget with the actual data collection. The example illustrates how review can improve coherence. It does not imply that modest proposals are always preferable or that this revision would guarantee a successful funding decision.

Use two distinct review passes

Ask one reviewer to assess the research argument and another to check instructions, completeness and internal consistency. Provide enough time for revision. Read the application as a whole after contributions from different authors have been merged; differences in terminology, sample numbers or project duration can undermine otherwise strong sections.

• Confirm that every objective has a matching method and expected output.
• Check that the budget, timeline and partner letters describe the same project.
• Identify unsupported claims and explain material uncertainty.
• Remove references that do not support the nearby statement.
• Retain the submitted version, approval record and receipt.

The proposal should make it straightforward for a reviewer to understand the question, assess the approach and judge whether the requested support is justified.