Public funding is scored, not negotiated.

The call document is the specification

Every programme publishes the same three things: eligibility gates, award criteria with weights, and cost rules. Together they define the document you are supposed to write. Where an application is refused, it is usually visible in that document, in a clause nobody read to the end.

The competition is against other applications scored on the same rubric. A good project in a bad fit with the rubric loses to an average project that matches it.

Choosing the programme is the first decision

One project often fits two or three calls with different weights. A technological development scores well under an innovation call and badly under a regional development one, and no amount of writing fixes a mismatch of that kind. The choice of call is worth more of your attention than the drafting, which is why we take it first.

Six things a scoring panel looks for

• Eligibility without ambiguity. Who applies, where they are registered, when, with what co-funding. Any doubt here costs the application before the content is read.
• A problem the programme recognises. Stated in its terms, not in yours, without abandoning accuracy.
• A work programme, not an intention. Work packages with owners, effort, dependencies and outputs.
• Capability. Why this team can execute, evidenced by what they have already done.
• Impact with a mechanism. Not benefits, but the causal path from output to effect, with indicators the programme can measure.
• A budget that matches the activities. Costs traceable to work packages and to the eligible categories.

The rubric is the outline

If impact carries thirty per cent of the score, it gets thirty per cent of the pages and the strongest evidence. Panels read dozens of files in a week; a section that is technically present but thin reads as absent, and the scoring table shows it.

Patterns worth recognising in your own draft

• The project designed backwards from the amount available, which produces work with no economic reason to exist.
• Work packages described as activities (research, development) rather than outputs (a validated prototype, a certified process).
• An impact section listing benefits instead of explaining the path to them.
• Eligibility slips that were knowable in advance: entity age, region, co-funding evidence, partner status.
• A consortium named in the application with no signed commitment behind the names.
• Length used as a proxy for substance, which the rubric penalises twice: once for the missing argument, once for the poor readability.

Most of these are decisions taken in week one and discovered in week eight.

What a rejected score looks like

Not "bad project". Typically: strong on excellence, weak on implementation, average on impact. The pattern tells you which section was written last, and by whom.

The application set

• Plan structured on the rubric, with section weight reflected in section length and evidence density.
• Work package table: activity, owner, effort, duration, output, dependency.
• Milestone and deliverable schedule in the programme's own format.
• Impact section built as a mechanism with indicators, not as a list of benefits.
• Risk table expressed as the programme expects it, with mitigation and contingency.
• Budget narrative tying every cost line to a work package and an eligible category.
• Scoring self-assessment: the criteria, our expected score, and the gap we are still unhappy about.

What we need from you

The call documents in full, the technical description from the people who will do the work, and the honest assessment of what the team has delivered before.

Five stages, the first one short

Eligibility screen. It takes a day and it sometimes ends the process, which is the cheapest possible outcome.

Rubric decomposition: criteria, weights, and the evidence each one rewards.

Drafting by work package with the technical owner in the room, because delegated technical prose is what reviewers describe as unconvincing.

Assembly and consistency pass across the form, the plan and the budget.

Red-team review against the published criteria, scoring our own document as a panel would.

Who does what

You own the technical content, partner relationships and the final responsibility for accuracy. We own structure, argument, budget coherence and the review. Accounting and audit of eligible costs sit with your finance team.

Limits stated plainly

It does not guarantee an award. Panels rank, budgets are finite, and a strong application in a crowded call can still miss.

It does not fix a project that lacks a reason to exist beyond the grant.

It does not decide whether public money is the right instrument for this project at all, which is a question about the direction: government and innovation funding.

It does not cover post-award reporting, which is a separate obligation with its own paperwork.

Related work

Where the financial side has to survive a controller rather than a panel: financial model for public funding. Where the same argument has to be presented live: pitch deck for public funding.

Where this work leads

One document answers one reader, but the question behind it rarely stays inside a single direction.

• Project & Investment Strategy

The level above

Documents solve a defined file. Where the decision itself is open, the work moves up a level, into a direction, and eventually into growth strategy.