How to Read a Grant Call

A call is never one file. It is a topic description sitting inside a hierarchy of documents, and the binding conditions are usually in the ones nobody prints. Establish the hierarchy first, because a rule in an annex overrides a friendly sentence in the topic text.

In European programmes, the topic text sits inside a work programme, and the general conditions sit in the General Annexes, published with the model grant agreement and the other binding files on the Funding and Tenders Portal reference documents page. The Online Manual explains the process around them.

In the United States, a notice of funding opportunity is read together with the agency's general application guide, such as the NSF proposal and award policies and procedures guide or the NIH application guide. Where the two disagree, the notice wins for that competition and says so.

Note the version and the date. Work programmes are amended, notices are reissued, and applying against a superseded version is a preventable rejection.

Find the annexes that carry templates

the proposal template itself, page limits, the budget table, the format of the curriculum vitae. These constrain the writing more than the topic text does.

Find the deadline and its time zone, then find your institution's earlier internal deadline. The funder's clock is the last one that matters, not the first.

Eligibility is normally read as a gate to pass. It is more useful read as a description of the project the funder has in mind, because each condition exists for a reason and the reason tells you what to write.

Who may apply

career stage, independence, institution type, country. A scheme restricted to researchers within eight years of the doctorate is buying independence at a career transition, and the proposal should show that transition.

What structure is required

a single principal investigator, a minimum number of independent partners, a mandatory industrial participant, a clinical site. The required structure is a statement about the kind of work expected.

What is excluded, which is often the most informative line in the call. An excluded activity is one the funder has decided belongs elsewhere, and proposing it anyway is not a bold move.

Duration and budget limits. A three-year ceiling rules out a project whose first result arrives in year four, and no amount of enthusiasm in the work plan changes that.

Whether resubmission is allowed, and whether a previous submission has to be declared and answered. Some schemes reward an explicit response to earlier reviews and some ignore it.

Cross-cutting obligations that apply regardless of topic

open access to publications, a data management plan, ethics review, and in some programmes a gender or sex dimension in the research content. These are scored, so they are not paperwork.

Most funders publish their scoring grid, and the grid is the outline of your proposal. Writing a beautiful document in a different order than the grid asks reviewers to hunt for what they have to score, and reviewers who hunt find less.

Horizon Europe collaborative proposals are evaluated on three criteria, excellence, impact, and quality and efficiency of the implementation, each scored out of five with thresholds set in the General Annexes. Weighting and thresholds vary by type of action, so read the annex for the specific one.

NIH research project grant applications now use a simplified framework organised into three factors: importance of the research, rigour and feasibility, and expertise and resources, replacing the earlier five separate criterion scores. The framework and the reviewer guidance are published on the NIH peer review pages.

Whatever the grid, mirror it. Use the criterion names as section headings where the template allows, and make sure each one has an unmissable paragraph. A reviewer filling a form should never have to infer your impact statement from the introduction.

Look for thresholds and weights. A criterion that can fail you on its own deserves proportionate effort even if it is the least interesting to write.

Look at who reviews. A panel of generalists and a panel of specialists need different first pages, and the call or the agency site usually says which it is.

Find out what the evaluation produces

a score, a ranked list, a two-stage process with a short outline first. A two-stage call means the first document is a selling document and the detail comes later.

Call texts are drafted by people who know exactly which projects they hope to receive, and the language leaks that intention. Reading for it is not cynicism, it is comprehension.

Separate must from should. Must and shall are conditions. Should and are encouraged to are scored preferences, and ignoring several of them is what makes an otherwise good proposal finish mid-table.

Read the expected outcomes and expected impact sections as the specification they are. In many European topics these are the sentences your impact section has to answer almost line by line.

Notice repeated vocabulary. A term repeated four times in a short topic text is the term the evaluators have been briefed on, and a proposal that never uses it looks like a reply to a different call.

Read the surrounding context, not just your topic. A topic sits under a broader destination or programme objective, and that text explains why the topic exists.

Watch for phrases that describe a partner you do not have

real-world validation, end-user involvement, regulatory pathway, deployment in an operational environment. Each of those is asking for an organisation, not a paragraph.

Watch for the opposite too. Words such as exploratory, high risk or proof of concept signal that preliminary data is not expected, and over-evidencing a proposal to that call can read as a project that is already finished.

The numbers in a call are the most concrete statement of intent it contains, and two of them together usually reveal the shape of the project the funder expects.

Divide the total indicative budget for the topic by the indicative budget per project, and you have roughly the number of grants. That number sets the competition and sometimes tells you the call is not worth entering.

The indicative amount per project describes the expected size of the work. Submitting at half of it invites the criticism that the ambition is too low; submitting at double it invites a straightforward rejection on scope.

Funding rates and eligible cost rules differ by organisation type and by type of action, which changes what a partner actually receives and therefore what they can commit.

Check whether overheads, salaries of permanent staff, equipment and subcontracting are eligible. A budget that is legal on paper and impossible in your institution is a problem to discover now.

Look for caps inside the budget

limits on subcontracting, on equipment, on travel, on the share any one partner may take.

Check the payment pattern. Pre-financing, interim payments against reporting periods and a retained final payment all affect whether a smaller partner can afford to participate at all.

Most funders expect to be contacted and publish a contact for exactly this purpose. The call for a European topic names a contact point, and United States notices carry a scientific or research contact. A short, specific email before you commit a month is normal practice, not an imposition.

Ask whether your project is in scope for this topic, in three sentences. This is the one question that saves the most wasted effort, and it is the one they are best placed to answer.

Ask which scheme is the better fit if this one is not, because they know the portfolio and you do not.

Ask about eligibility specifics that the text leaves ambiguous for your case: your career stage, an unusual institution type, a partner in a country whose status you cannot determine.

Ask what was funded in the previous round and whether evaluation feedback or statistics are published, then check the award database yourself.

Do not ask them to assess your idea, to read a draft, or to predict success. That is not their role, and asking damages the exchange.

Keep it short, ask early rather than in the final fortnight, and write down the answer with the date, because staff change and a proposal built on a remembered phone call has nothing behind it.