Budget Table vs Narrative: The Cross-Check Evaluators Always Run

The check evaluators make

Evaluators cross-check the budget table against the narrative to see whether the money proves the work plan, or contradicts it. They look for every large cost to have a clear job in a work package, and for every promised activity to have the people, travel, tools, or suppliers needed to deliver it. If the two parts tell different stories, the proposal feels risky even when the idea is strong.

Treat the budget as a second version of the narrative, written in financial language. Personnel effort shows who will do the work. Travel shows where collaboration, pilots, dissemination, or community engagement will happen. Subcontracting shows what the consortium cannot or should not do itself. Equipment, services, and other direct costs show the practical conditions needed for delivery.

The mistake is to finish the narrative, then fill the budget as an admin exercise. Do the reverse check before submission: read the budget line by line and ask which sentence, task, deliverable, event, output, or management need justifies it. Then read the narrative and ask whether the budget gives each promise enough delivery capacity.

Start with a trace from cost to task

Build a simple trace before you polish the text. For each partner and each main cost, write down the work package, task, output, and sentence that explain why the cost exists. This is not extra bureaucracy. It is the shortest route to finding weak claims before an evaluator does.

A useful trace has a few fields:

• Partner name and role in the consortium
• Cost category and plain-language description
• Work package and task reference
• Narrative sentence that explains the need
• Deliverable, event, pilot, platform, or community activity connected to it
• Assumption behind the amount, such as staff time, meeting format, supplier role, or production scope
• Evidence still missing from the narrative

This catches common gaps fast. A partner may have travel money but no visible fieldwork role. A coordinator may carry too much effort while technical partners describe most of the build. A dissemination partner may promise broad outreach with no events, content production, or community management capacity. A pilot site may appear in the story but have no staff time to run local work.

Use the trace to edit both sides. Sometimes the budget is wrong. Often the narrative is simply too vague.

Common mismatches that weaken a proposal

The most damaging mismatches are ordinary. They happen when sections are written by different people and assembled late. Evaluators notice them because they read across the form, not down one section at a time.

Watch for these patterns:

• Named activities with no budget support. The proposal promises workshops, interviews, testing, mentoring, translations, or platform maintenance, but the budget has no time or services that make them plausible.
• Costs with no visible purpose. A line mentions software, design, facilitation, travel, equipment, or expert support, but the narrative never says why it is needed.
• Partner role drift. The narrative calls a partner central, but the budget gives them a minor role. Or the budget gives a partner major effort, while the work plan barely uses them.
• Subcontracting that replaces core consortium work. External suppliers can be legitimate, but the proposal must show what remains under partner control and why the supplier role is specific.
• Management effort that is too hidden. Coordination, reporting, partner alignment, risk tracking, and quality control need time. If management is described as serious but budgeted as an afterthought, confidence drops.
• Dissemination without operations. A communication plan needs people to produce, publish, moderate, document, and follow up.

Fixing these mismatches does not mean adding more money. It means making the same project legible in both places.

Read the narrative like a budget reviewer

After the cost-to-task trace, do the opposite pass. Print or export the narrative sections that describe work packages, methodology, roles, deliverables, pilots, impact, dissemination, and sustainability. Highlight every verb that creates work: design, recruit, test, train, moderate, translate, integrate, analyse, report, convene, maintain.

Each highlighted verb should point to capacity. Capacity can be partner staff, a supplier, a meeting plan, a tool, or a platform operation model. If a verb has no owner or no budget logic, it is a weak promise. If many verbs sit with one partner, the budget should show that partner carrying the corresponding effort.

This pass also improves wording. Replace broad claims with operational sentences. Instead of saying that the consortium will engage stakeholders, say who will map them, who will invite them, where the interaction happens, what format will be used, and what output will be produced. Then check whether the budget supports those actions.

Be careful with copy-pasted excellence language. Strong adjectives do not justify costs. Evaluators need to see a chain from need to activity, from activity to resource, and from resource to output. The proposal becomes easier to trust when that chain is visible.

Make the final QA pass before submission

Run the final budget-narrative QA as a short meeting with the coordinator, budget owner, and work package leads. Do not review the whole proposal from the beginning. Review only the points where money and delivery meet.

Use these checks:

• Can every partner explain their largest costs in plain language?
• Does every work package have enough effort for the tasks it owns?
• Do travel and event costs match the collaboration model described in the text?
• Are pilots, community activities, and user-facing outputs resourced beyond launch?
• Is subcontracting described with a clear boundary and reason?
• Do deliverables that require design, data, technology, moderation, or analysis have named capacity behind them?
• Does the management budget match the coordination burden created by the consortium design?
• Have budget assumptions been reflected in the narrative without turning the text into an accounting note?

The next step is practical: create a budget-narrative trace, mark every unexplained cost, and edit the weaker side until the story matches. If you want an outside pass, StrandsUnited can review the proposal structure, budget logic, and knowledge-management assumptions as part of our EU project platform work, including systems described at strandsunited.com/what-we-do.

Where this comes from

We build and operate digital platforms for EU cooperation projects and communities, so we see the gap between proposal promises and delivery mechanics. Our consortium graph covers 83,490 projects, 114,731 organisations, and 461,953 participation edges from open programme data, which helps us study how roles, partnerships, and delivery patterns show up across funded work.

The same thinking sits behind Impactful, our community impact platform, and the knowledge systems we build for member areas, catalogues, event operations, and AI assistants that answer with sources. A clean budget-narrative cross-check is not only a proposal-quality habit. It is the first version of an operating model the consortium will have to live with later.