Proposal tip. What cannot be measured does not exist

What cannot be measured does not exist

Measurement does not mean reducing the project to numbers only. It means giving evaluators enough reference points to understand the strength of the case. Without those reference points, even a promising project can look vague. That is why measurable writing is a credibility tool.

One of the most common weaknesses in EU funding proposals is not lack of ambition. It is lack of quantified credibility. The proposal says the technology is faster, safer, more efficient, more scalable, more accurate, more sustainable, or more cost-effective. But it does not always explain compared to what, by how much, under which conditions, and with what evidence. In EU evaluations, ambition needs evidence. Traceability usually needs measurement. That is why, for proposal purposes, what cannot be measured often does not exist.

Why vague ambition is so common in EU proposals

The team may know the missing detail. But evaluators only see the proposal. If the document does not translate internal knowledge into assessable evidence, the case remains weaker than the project. That gap is avoidable.

Words such as disruptive, transformative, scalable, efficient, robust, breakthrough, advanced, high-impact, and market-leading may sound appropriate. When those questions remain unanswered, the proposal becomes harder to defend.

A sentence that sounds strong, but stays abstract

The issue is not that the claim is necessarily false. The issue is that the evaluator cannot verify its scale. A strong sentence should reduce interpretation. It should make the improvement visible.

Consider this sentence:

A proposal can sound ambitious and still leave the evaluator without enough information to score the claim confidently.

The same claim, made measurable

This does not make the proposal more complex. It makes the claim easier to judge. The evaluator can see what is new, how large the improvement is, and what evidence supports it. That is the value of measurement.

Now compare it with this version:

The real difference is not technical depth

Technical depth should be used selectively. The proposal should include the level of detail needed to assess the claim. Too little detail creates doubt. Too much irrelevant detail creates noise.

Measurement turns ambition into evidence

Ambition without measurement can sound like marketing. Ambition with measurement becomes a project commitment. It shows that the team knows what success means. It also shows that the project can be evaluated.

Programmes such as Horizon Europe, the EIC Accelerator, the EIC Pathfinder, the EIC Transition, and Eurostars are designed to support innovation, research, impact, competitiveness, and progress. A proposal that says the project will create a major performance improvement must explain how that improvement will be measured. A proposal that says the solution will reduce cost must explain which cost category, for which user, from which baseline, and at what stage of adoption. A proposal that says the technology will improve sustainability must explain which environmental indicator changes and how the calculation is made. A proposal that says the product will scale must explain the assumptions behind that scale.

Why evaluators need measurable anchors

Anchors help evaluators justify positive comments. They also help distinguish strong evidence from general intention. When anchors are missing, the evaluator has to infer too much. In competitive calls, that is dangerous.

A proposal that makes claims measurable gives the evaluator a stronger basis for positive assessment. It also reduces the risk of comments such as “not sufficiently justified”, “insufficiently quantified”, or “the expected impact is not convincingly demonstrated”.

Measurement is not only about KPIs

KPIs should not sit apart from the proposal logic. They should connect objectives, tasks, milestones, risks, and impact. If they do not connect, they become decorative. Connected KPIs strengthen the full evaluation case.

The proposal may claim a breakthrough in performance, but the KPI table measures only number of prototypes developed. It may claim market readiness, but KPIs only measure dissemination activities. It may claim clinical relevance, but KPIs do not measure patient, workflow, diagnostic, or health-economic outcomes. It may claim environmental impact, but KPIs do not link to emissions, energy use, material efficiency, waste reduction, or lifecycle performance.

The baseline problem

A baseline gives the evaluator the starting point. Without it, even a percentage improvement can be hard to interpret. The same 30% improvement can be impressive or irrelevant depending on the reference. That is why the baseline must be explicit.

A proposal may say the solution will reduce processing time by 30%. For example:

This is much stronger than saying:

The target problem

Targets should be ambitious enough to matter and realistic enough to trust. They also create decision points for the project. If the target is missed, the team should know what happens next. That is part of credible implementation.

The operating conditions problem

Operating conditions define the boundary of evidence. They help evaluators understand whether a result is already robust or still preliminary. They also prevent overclaiming. A measured result without context can mislead.

For example:

A stronger proposal would write:

The validation problem

Validation tells evaluators how the claim will be proven. It also separates existing evidence from future evidence. That distinction matters because evaluators assess both current credibility and project feasibility. A mature proposal is transparent about both.

“Not sufficiently justified” often means “not sufficiently measured”

The solution is not always to add more explanation. Sometimes the solution is to add a baseline, a target, a threshold, or a validation condition. Measurement turns justification from assertion into evidence. That is why it should be close to the claim it supports.

We discussed this in more detail in Not sufficiently justified in EU proposals: why evaluators need evidence, not more words. If the proposal claims performance improvement, it should show baseline, target, and validation method. If it claims market opportunity, it should show addressable segment, adoption assumptions, pricing logic, and sales ramp-up. If it claims impact, it should show mechanism, indicators, and realistic pathway. If it claims feasibility, it should show resources, milestones, dependencies, and risk thresholds.

Market claims need measurement too

Commercial ambition also needs traceability. Market size, pricing, adoption, and revenue should not appear as isolated figures. They should be connected to segments, customers, channels, capacity, and timing. That is what makes the business case assessable.

A proposal may say:

This is why we addressed the issue in Does your project have a higher market share than Tesla?. Market share should be derived from bottom-up assumptions that evaluators can follow.

The danger of arbitrary percentages

Percentages can hide weak assumptions. They look precise even when the logic is thin. A bottom-up number is usually more credible than a generic share of market. It gives the evaluator something concrete to test.

For example:

A bottom-up version would be stronger:

Measurement protects credibility

Measurement also helps manage uncertainty. It shows what is known, what is assumed, and what will be validated. That honesty strengthens trust. Evaluators do not expect zero uncertainty, but they do expect it to be managed.

Measurement should be proportional

Proportionality is important because page space is limited. The most important claims deserve the strongest measurement. Minor claims may only need concise support. The key is relevance, not quantity.

If a claim is central to scoring, it needs stronger evidence. If a number drives the business model, it needs derivation. If a KPI defines project success, it needs a baseline and target. If a risk depends on a threshold, the threshold should be explicit. If an impact claim is used to justify funding, the mechanism should be measurable where possible.

What good quantified credibility looks like

These five components do not need to create long paragraphs. They can often be included in one precise sentence. What matters is that the evaluator can see the chain. Indicator, baseline, target, conditions, and validation make the claim evaluable.

Example: technical performance

The stronger version is not only more technical. It is more accountable. It defines what success means and how the claim will be judged. That supports excellence and feasibility at the same time.

A weak technical claim might say:

A stronger version would say:

Example: impact

Impact needs scale and mechanism. A broad benefit may align with policy language, but it does not prove expected effect. A quantified impact claim helps the evaluator see the route from output to outcome. That route is central to scoring.

A weak impact claim might say:

A stronger version would say:

Example: market adoption

Early adoption claims need evidence. Customer interviews, pilots, procurement cycles, and capacity assumptions help define a credible first market. That is stronger than a broad statement about demand. It also prevents unrealistic growth claims.

A weak adoption claim might say:

A stronger version would say:

Example: implementation feasibility

Implementation credibility is also measurable through traceability. Partner roles, previous results, facilities, resources, and task ownership all matter. The evaluator needs to see why each partner is necessary. Specificity makes implementation more believable.

A weak implementation claim might say:

A stronger version would say:

Good measurement reduces evaluator interpretation

Interpretation should be reduced wherever possible. The proposal should not depend on generous assumptions from the evaluator. Clear measurement narrows the meaning of the claim. That protects the proposal from avoidable doubt.

Measurement also improves internal project discipline

This is why measurement should start before final writing. It improves the proposal and the project design. It forces the team to agree on success criteria. It also reveals weak logic early.

The role of thresholds

Thresholds also make risk management more concrete. They show when the team will continue, adjust, or stop an approach. That gives milestones real meaning. It also makes the work plan more credible.

Avoid vanity metrics

Vanity metrics are not useless in every context. But they should not be used to prove claims they do not measure. Dissemination metrics do not prove technical performance. Website visits do not prove market readiness.

For example:

• number of website visits
• number of social media impressions
• number of newsletters sent
• number of meetings held
• number of general stakeholders informed
• number of events attended

If the proposal claims technical excellence, dissemination metrics will not prove it. If it claims commercial readiness, website visits will not prove it. If it claims clinical value, number of workshops will not prove it. Good metrics must match the claim.

Avoid false precision

Precision should follow evidence. Exact-looking forecasts without transparent assumptions can reduce trust. Rounded but well justified estimates are often stronger. The evaluator should understand how the number was built.

For example:

Avoid disconnected KPI tables

KPI tables should be functional, not decorative. Each key indicator should have a role in the proposal logic. It should influence validation, milestones, risk management, or impact. Otherwise, it is only formatting.

If a KPI matters, the methodology should explain how it will be measured, the work plan should assign responsibility, the risk section should define what happens if the target is not reached, and the impact section should use the result carefully.

How to review measurement before submission

This review is often faster than a full rewrite. It highlights where the case is still abstract. It also shows where numbers exist but are not connected. That is where the proposal should be strengthened.

A simple measurement checklist

• What exactly are we claiming?
• Which indicator proves it?
• What is the current baseline?
• What target will the project reach?
• Under which conditions will the target be tested?
• Which evidence already supports the claim?
• Which evidence will the project generate?
• Who is responsible for measuring it?
• When will it be measured?
• What happens if the target is not reached?
• Is the claim proportional to the evidence?
• Is the number derived or arbitrary?
• Can the evaluator follow the reasoning?

Where Ruthless Evaluator fits

Ruthless Evaluator does not add artificial precision. It flags where precision is needed. It helps separate strong ambition from unsupported ambition. That makes the proposal harder to reject for avoidable reasons.

Ruthless Evaluator helps applicants, consultants, universities, research centres, startups, SMEs, and innovation teams find issues such as:

• vague objectives
• missing baselines
• unsupported performance claims
• arbitrary market assumptions
• disconnected KPIs
• unclear validation conditions
• weak thresholds
• hidden assumptions
• overclaimed impact
• numbers without derivation
• measurement that does not match the claim

Better to measure before the ESR measures you

The ESR will expose gaps in justification, quantification, and traceability. Finding them before submission is far better. At that point, teams can still add evidence, narrow claims, or clarify validation. After evaluation, the same gap becomes a lost opportunity.

Better to meet Ruthless Evaluator before submission than inside the Evaluation Summary Report.

app.ruthlessevaluator.ai