WIDERA TWINNING Proposal Writing Bootcamp

This training is designed for researchers, project managers, policymakers, universities, research institutions, SMEs, and national/regional authorities looking to apply for WIDERA Twinning calls under Horizon Europe.

Experience Level: Suitable for all levels of experience, from first-time applicants to experienced coordinators. The training provides step-by-step guidance, starting from the fundamentals of WIDERA Twinning funding and progressing to advanced proposal development strategies.

Expert Trainers: Our training is delivered by senior experts with extensive experience in Horizon Europe WIDERA projects and European Commission evaluations. Many of our trainers have served as expert evaluators, bringing first-hand knowledge of the review process and scoring criteria. In addition to training, they provide proposal writing and review services at EFMC.

More details on our trainers and experts here.

Key Outcomes: This training focuses on maximizing success rates for WIDERA proposals by helping participants understand how to align their projects with widening participation goals and ERA priorities.

MODULE DETAILS (score drivers, common downgrade reasons and what we will build)

1) Reading Twinning strategically (call logic in 30 minutes)

What we will cover:

• How evaluators score CSAs: what they look for in each criterion, and why “findability” wins.
• What Twinning is buying: a measurable institutional upgrade at the coordinator, not a loose collaboration narrative.
• How to convert each expected outcome into at least one deliverable plus KPI owned by the coordinator.

Common pitfalls to avoid:

• Generic networking story with no quantified coordinator-level step-change.
• Research management capacity building treated as a footnote, not a deliverable-backed work package/task.

2) Excellence: objectives, approach, and joint agenda without scope drift

What we will cover:

• Objective ladder that links (i) scientific profile & reputation, (ii) people & skills, (iii) systems & management, (iv) networks & mobility.
• Methodology as an activity system (exchanges, trainings, workshops, mentoring, access to infrastructure) with clear roles and participation logic.
• If you include beyond-state-of-the-art R&I training/activities, place them under the dedicated “Research component” work package to stay compliant.

Common pitfalls to avoid:

• Twinning written like an RIA: heavy research claims without a credible capacity-building mechanism.
• Objectives that are not measurable and not linked to baselines and institutional indicators.

3) Impact: quantify change and make it believable

What we will cover:

• Use topic-suggested indicators as a starting point (scientific production, collaborations, IP, investments, students, gender balance, mobility).
• Impact pathway discipline: outputs -> outcomes -> impacts; define baselines, targets, data sources, and owners from day one.
• Communication and dissemination: stakeholder-specific channels that are resourced in the work plan (not a generic list).

Common pitfalls to avoid:

• Indicators without baselines/targets/ownership (unscorable impact).
• Big impact claims without mechanisms, stakeholders, or sustainability logic beyond the project.

4) Implementation: work plan that proves the step-change

What we will cover:

• Work plan architecture aligned to the three evaluation criteria and the topic obligations.
• Research management capacity building as a dedicated WP or task aligned to RM Comp, producing concrete institutional outputs (processes, SOPs, training curricula, internal service upgrades).
• Governance, risks, and milestones that show active decision-making and control (not a static org chart).

Common pitfalls to avoid:

• WPs that read like activity lists (no deliverables, milestones, risks, or verification).
• Weak governance and “after the project” sustainability statements without operational commitments.

5) Lump sum readiness and final QA

What we will cover:

• Lump sum logic: resource realism is judged through the coherence of tasks, deliverables, and effort – not through cost accounting detail.
• Cross-consistency checks: objectives -> KPIs -> WPs -> deliverables -> milestones -> risks -> resources (traceability chain).
• Panel review readiness: write so a reviewer can find the answer in 30 seconds.

Common pitfalls to avoid:

• Inconsistent numbers and definitions across sections and tables.
• Last-minute edits that break traceability (KPI or WP changes not propagated).

Suggested pre-work (optional): Bring (i) highlighted call text, (ii) 5-10 coordinator baselines, (iii) consortium list, (iv) any Part B draft.
Bootcamp outputs: Twinning compliance checklist, Part B skeleton, KPI library, work plan template, and last-48-hours QA routine.