Common mistakes

Introduction and Methodology

While the Compendium of Best Practices focuses on successful funding stories,this section addresses the complementary perspective: the identification of recurring weaknesses, errors and failure patterns observed across unsuccessful EU funding applications in the tourism ecosystem.

The purpose is to:

• Extract failure patterns from the tourism SMEs funding experiences analysed

• Translate negative evidence into actionable learning

• Provide applicants with on what to avoid, grounded in real operational experience

Each identified mistake is assessed along two dimensions:frequency(how often it appears across the evidence base)and impact severity(the extent to which it directly affects evaluation outcome).The common mistakes were then classified into four main categories, consistent with EU evaluation criteria and project-neutral logic:

• Strategic Mistakes: such as weak or generic problem definition, failure to demonstrate EU added value or misalignment between project scope and call objectives.
• Technical and Methodological Mistakes: poorly structured work plans,non-measurable objectives and KPIs or weak linkage between activities, outputs and impacts.
• Organisational and Administrative Mistakes: examples include unclear role allocation in consortia or insufficient governance and coordination mechanisms.
• Financial and Compliance-Related Mistakes: budgets not aligned with activities, misunderstanding of cost eligibility rules or inadequate risk and compliance considerations.

• What it looks like:

The proposal describes a good business idea but does not explicitly connect it to the programme’s objectives, priorities, and expected impacts,it does not demonstrate structured project–programme alignment. In practice, this happens when applicants describe a valid business investment or tourism improvement, but do not show how it contributes to the specific objectives, expected results and logic of the call. The project may make sense internally, yet still appear generic because the proposal does not translate programme language into activities, outputs and measurable results. The strongest cases succeeded because the project scope was already close to the priorities of the scheme and the fit was made explicit throughout the application. Where that link is weak, evaluators struggle to award relevance points and the proposal quickly loses competitiveness.

• Why it fails:

Evaluators cannot quickly see relevance,the project appears generic or mis-scoped versus the call’s intent, reducing scores on relevance or fit.

• Diagnostic check question:

Can you map every programme/call objective to at least one concrete project activity and output?

• What it looks like:

The proposal uses terms like “green/digital/resilience” but does not show how activities operationally deliver those priorities. In these cases,the project is not positioned in a way that makes “strategic fit with call priorities” explicit.A common error is to repeat terms such as “green”, “digital” or “resilience” without showing what the project will actually do under those headings. In the evidence base, successful applications did not rely on vocabulary alone: they connected sustainability or digitalisation to concrete actions such as expert input, targeted upgrades, pilot tools or operational improvements linked to real business needs. When proposals use EU priorities as labels rather than as design principles, the result is superficial alignment. This weakens credibility because evaluators assess operational delivery, not just thematic language.

• Why it fails:

Evaluators’ reward demonstrated fit, not vocabulary and superficial alignment reduce relevance and credibility.

• Diagnostic check question:

If you delete all “green/digital/resilience” wording, does the proposal still clearly show (through actions and outputs) how it delivers those priorities?

• What it looks like:

The proposal assumes regulatory constraints will “be handled later” without showing awareness or an early plan for compliance.This mistake occurs when applicants assume permits, invoicing rules, VAT treatment or other regulatory conditions will be solved later and therefore do not address them in the proposal. The evidence shows that rigid eligibility rules and implementation constraints can create major friction, especially for small tourism operators whose day-to-day practices do not always match funding rules. If these constraints are not anticipated, the project can look risky at application stage and unstable during implementation. The issue is not only compliance; it is also delivery credibility.

• Why it fails:

The project looks risky or unimplementable within the proposed timeline.

• Diagnostic check question:

Have you identified the key legal/permit requirements and stated (briefly) how and when you will ensure compliance?

• What it looks like:

The proposal describes activities that resemble the organisation’s normal mandate (e.g., standard marketing/operations), without clearly demonstrating what is truly new or additional under EU funding logic.Applicants often describe activities that look like normal business spending—general promotion, routine improvements or standard operations—without showing what would only happen because of the funding. This is particularly problematic in tourism, where many investments are useful for the business but not necessarily fundable under EU public-policy logic. In the successful cases, funded actions were framed as a clear step beyond ordinary activity: a new capability, a targeted sustainability improvement, a validated pilot or a strategic diversification move. Without that distinction, the proposal can be read as business-as-usual rather than as a genuinely additional intervention.

• Why it fails:

Evaluators can consider the project insufficiently “additional” or not fundable at EU level.

• Diagnostic check question:

Can you clearly state what the project delivers that your organisation would not do without EU support (i.e., the “additionality” statement)?

• What it looks like:

Some applicants write as though the evaluator only needs to decide whether the idea is good, instead of whether it is better justified than competing proposals. This leads to under-explained choices, limited evidence and weak differentiation. The best practices show the opposite approach: even very small organisations strengthened their position by showing focus, practical relevance, realistic scope and a clear path to delivery. In competitive calls, a proposal that is merely reasonable in isolation can still score poorly if it does not demonstrate why it is especially credible, timely or fit for purpose compared with alternatives. An applicant submits a proposal without anticipating that it will be compared with other applicants.

• Why it fails:

The proposal may be credible in isolation but loses comparatively because it does not over-compensate with proof of feasibility, readiness, and a compelling story.

• Diagnostic check question:

Have you explicitly addressed how your capacity remains competitive (evidence, focus, delivery plan), given other applicants?

• What it looks like:

This mistake appears when the proposal presents the solution at a high level but gives too little evidence on how it will be delivered, costed and managed. In practice, the project may depend on external experts, technical inputs or staged implementation, yet those elements are not explained in sufficient detail. The evidence shows that lean SMEs performed better when they broke the project into manageable and clearly justified components, rather than describing ambition in abstract terms. If cost logic and delivery sequencing are not visible, evaluators may assume the plan is under-developed even when the idea is sound. The proposal describes a solution but provides insufficient cost analysis and/or weak feasibility evidence.

• Why it fails:

Evaluators may perceive the plan as under-justified.

• Diagnostic check question:

Does every major cost and technical claim have a short justification that an evaluator can verify without inference?

• What it looks like:

The proposal may be sensible, but the narrative/presentation underplays feasibility evidence and risk mitigation or makes it difficult to score (explicitly noted as a weakness in the evidence base).A proposal can be sensible in substance and still perform badly because the narrative is not structured in a way that makes scoring easy. This happens when evidence is scattered, risks are implied rather than explained, or key links between need, action and result are left for the evaluator to infer. The evidence base repeatedly shows that small applicants are disadvantaged when they rely on internal understanding instead of explicitly presenting the logic on paper. Stronger cases made the project easy to read and easy to score. Poor evaluation optics do not just reduce clarity; they directly reduce scorability.

• Why it fails:

Evaluators cannot award points with unclear structure, it reduces scorability and competitiveness.

• Diagnostic check question:

Could a third-party evaluator score each criterion directly from your text because you explicitly answer it where it appears?

• What it looks like:

A frequent problem is to claim that the project is feasible without demonstrating how likely delivery risks will be managed. In tourism SME contexts, risks often come from limited internal capacity, reimbursement delays, partner dependency or technical uncertainty. The document shows that small teams are particularly exposed when a single delay or bottleneck affects both implementation and normal operations. Successful cases were generally modest in scope, supported by external expertise, or built around realistic operational assumptions. Without credible mitigation, feasibility claims remain fragile and evaluators are likely to discount them. The proposal states feasibility but does not show credible risk mitigation.

• Why it fails:

Without mitigation, feasibility claims look fragile and evaluators anticipate delivery failure.

• Diagnostic check question:

For each top risk, have you listed one mitigation action that is realistic for your team and budget?

• What it looks like:

This mistake occurs when applicants define a digital tool, technical upgrade or complex output before checking the real requirements, costs and constraints. The evidence points to situations where SMEs initially lacked clarity on how best to use the funding or how demanding certain components would be in practice. In stronger cases, applicants kept the intervention concrete and proportionate—for example, focusing on a basic but reliable prototype, or on expert-supported improvements rather than over-designed technical ambition. Early validation matters because unrealistic assumptions later force scope reduction and weaken both credibility and impact.Applicants define technical outputs without sufficiently analysing technical and financial requirements in advance leading to later forced scope reduction.

• Why it fails:

The project becomes less credible at proposal stage (if under-costed) or loses impact during delivery (if scope collapses).

• Diagnostic check question:

Have you validated the most complex/expensive technical component with realistic costs and assumptions before finalising the project scope?

• What it looks like:

The proposal describes activities without a strong analytical baseline (market needs assessment,segmentation or baselines).Many proposals start from an intuitive idea but not from a sufficiently documented problem, baseline or target need. The result is that the application describes activities without proving why these activities are necessary, why now, and for whom. The evidence repeatedly contrasts weaker, opinion-led approaches with stronger evidence-led ones, where applicants used practical market understanding, local needs, existing assets or clearly identified operational gaps to justify the intervention. Without a pre-writing evidence base, the proposal struggles to show a convincing problem–solution–impact chain and remains harder to evaluate positively.

• Why it fails:

Evaluators cannot see a credible problem–solution–impact chain and the project look opinion-led rather than evidence-led.

• Diagnostic check question:

Do you have baseline evidence (data/analysis) that proves the need and allows you to quantify targets and impacts?

• What it looks like:

One of the clearest patterns in successful applications is that support ecosystems matter, but only when they are relevant and competent. Successful micro and small applicants often relied on consultants, tutors, projector ganisers, local support actors or trusted intermediaries to interpret the call and manage the administrative process. Problems arise at both extremes: when the SME tries to do everything alone, or when it relies on weak or late-stage support that adds confusion rather than structure. For low-capacity applicants, the quality of support can be decisive for both submission quality and implementation stability. The SME either lacks external support for submission and paperwork or relies on ineffective support. The evidence shows a capable consultant or structured support ecosystem can be decisive.

• Why it fails:

Administrative errors and process friction accumulate making proposal quality and compliance decline.

• Diagnostic check question:

Do you have a named person or trusted external support responsible for managing portals, paperwork, & iteration cycles?

• What it looks like:

The proposal underestimates the time/effort needed for complex document requirements and administrative steps.This error is highly recurrent across applications. Applicants focus on the funded activity itself but underestimate the effort required for forms, annexes,invoicing, reporting, reimbursements and follow-up exchanges. The evidence is particularly strong for micro-enterprises, where administrative work is sometimes regarded as disproportionate to the funding amount and disruptive to daily operations.Best practices explicitly show that SMEs should weigh the administrative burden against the expected benefit before applying. If that burden is not planned for, the process generates delays, mistakes and internal frustration from the outset.

• Why it fails:

Time pressure increases mistakes, missed requirements, and incomplete documentation, then feasibility and compliance perception drop.

• Diagnostic check question:

Have you allocated dedicated time (and an owner) for documentation management, separate from “project delivery” tasks?

• What it looks like:

This mistake consists of treating partners as formal requirements rather than as delivery-critical actors. The document highlights two related problems: insufficient access to trusted partnership ecosystems and difficulty assessing the reliability of unknown organisations, especially in cross-border contexts. Where partnerships were effective, they were grounded in clear complementary roles and confidence in the partner’s ability to deliver. Where trust is weak or partner choice is opportunistic, evaluators see coordination risk, and implementation later suffers from unclear responsibilities, slower decisions and fragile governance.Partners are selected without clear trust/experience foundations.Evidence highlights the importance of choosing experienced partners you can trust and defining goals early.

• Why it fails:

Governance and delivery credibility weaken, and evaluators see higher implementation risk and coordination uncertainty.

• Diagnostic check question:

For each partner, can you state why they are experienced and what unique responsibility they have?

• What it looks like:

Applicants often find calls by chance, too late, or through scattered searches rather than through a routine system. The evidence shows that better outcomes were associated with structured monitoring: proactive web searches using relevant keywords, explanatory sessions, direct clarification from organisers, and repeated exposure to opportunities over time. This matters because good call selection is a prerequisite for a good application. Without repeatable scouting channels, SMEs either miss relevant opportunities or pursue schemes that do not match their real needs, capacity or timing SMEs rely on ad-hoc discovery rather than systematic monitoring, despite evidence showing that structured information channels enable timely awareness and opportunity access.

• Why it fails:

Applicants miss suitable calls, engage too late, or chase misfitting opportunities, increasing failure probability.

• Diagnostic check question:

Do you have at least one repeatable channel and a tracking routine to systematically capture opportunities instead of relying on one-off searches?

• What it looks like:

Many tourism SMEs underestimate how strongly access to some programmes depends on networks, intermediaries or a route into a wider consortium. Some opportunities are difficult to access because international partners or destination structures are not readily available in the applicant’s context. It also shows that, for small specialised firms, joining as a partner can be a more realistic route than trying to lead alone. When applicants ignore this structural reality, they target calls they cannot realistically access or support with a credible consortium logic. The applicant targets calls that typically require partners but lacks a realistic partner access pathway.

• Why it fails:

The proposal becomes non-viable (no access path) or under-credible (weak consortium logic).

• Diagnostic check question:

Do you have a concrete partner access plan (who, where found, why credible), and is it realistic in your local context?

• What it looks like:

Small firms advance costs upfront, wait for reimbursement and face pressure on normal operations in the meantime. In some cases, activities had to be postponed or cancelled because liquidity was tighter than expected. Lessons learned explicitly recommend budgeting beyond the grant amount and planning for VAT, non-eligible items and co-financing needs from the start. A project may be eligible and even well designed, but if the organisation cannot absorb early cash-flow pressure, implementation becomes fragile very quickly. The proposal assumes cash-flow will “work out,” but evidence shows co-funding and early liquidity can be a major challenge, and that securing more upfront capital reduces operational stress and delays.

• Why it fails:

Even good projects become fragile; inability to pre-finance activities undermines feasibility and implementation readiness.

• Diagnostic check question:

Can you demonstrate how you will cover co-funding and early cash needs before reimbursements?

• What it looks like:

Applicants often assume that the financial and compliance logic of the scheme will remain stable throughout implementation. The document shows that this is risky, particularly where policy or standards update mid-project or where eligibility interpretation evolves during delivery. In such situations, SMEs may need to inject additional funds or adjust activities under pressure. The lesson from the stronger cases is not to predict every change, but to keep a realistic compliance buffer in time, budget and management attention. Without that margin, even a funded project can become unstable. Applicants assume rules remain stable, but some evidence notes that evolving compliance rules can change eligibility and force extra own funding beyond the original plan.

• Why it fails:

Mid-project changes create unplanned costs and non-compliance risk making implementation becomes unstable.

• Diagnostic check question:

Have you included a realistic contingency (time/budget) to absorb potential compliance or eligibility changes without breaking delivery?

• What it looks like:

A regular weakness is to under-cost the most demanding elements of the project or to leave technical costs weakly justified. This is especially relevant for digital tools, innovation components or external expertise that appear simple in concept but are resource-intensive in practice. The best practices were usually careful to keep the investment focused, modest and linked to a clearly justified operational need. If cost realism is weak, evaluators downgrade feasibility; if the proposal is funded anyway, the likely result is later scope reduction and lower impact.Cost analysis is insufficient or technical components are under-costed.

• Why it fails:

Evaluators downgrade feasibility. If awarded, implementation may require scope reduction that reduces impact.

• Diagnostic check question:

For every major cost driver, can you show how it was calculated and why it is necessary for the outputs?

• What it looks like:

For very small tourism businesses, delays are not only an inconvenience; they carry a direct operational cost. The evidence explicitly notes that, in tiny teams, each delay has a high opportunity cost and prolonged administrative cycles can make self-financing appear faster or economically preferable. This means the true cost of a funding scheme is not limited to co-financing or paperwork, but includes lost management attention, delayed business decisions and pressure on normal operations. Proposals that ignore this reality are often over-ambitious relative to the team’s actual absorption capacity. Teams, especially small ones,do not account for how delays and paperwork consume scarce capacity; evidence notes that with tiny teams, delays have high opportunity cost and administrative workload is heavy.

• Why it fails:

The organisation becomes overburdened and proposal quality and delivery readiness decline.

• Diagnostic check question:

Have you explicitly assessed whether the administrative/reporting workload is sustainable for your team size?

• What it looks like:

This error arises when the budget is designed around business logic alone rather than around the financial architecture of the call. The evidence highlights that rigid eligible-cost structures, VAT treatment issues and category constraints can significantly shape what is realistically deliverable. If the workplan depends on spending patterns that the scheme does not allow, the proposal becomes either non-compliant or operationally distorted. Stronger applicants adapt the project to the rules early; weaker ones discover too late that the financial template is driving the implementation model more than expected. The applicant designs a budget that clashes with strict category caps that can significantly shape implementation.

• Why it fails:

Budget becomes non-compliant or unrealistic and implementation is forced into inefficient trade-offs, weakening feasibility and delivery quality.

• Diagnostic check question:

Have you checked whether the call imposes category caps or rigid templates, and can your workplan still function within those constraints?