Open topic on driving innovation uptake of disaster risk solutions

Expected outcomes

• Projects may contribute to some of the expected outcomes; say which ones and why.
• For each outcome (EO1 to EO6), name who will use or adopt your results (a specific group, not “industry” or “society”), how they get them, and the indicator that shows the change, with baseline, target and date.
• Use the topic's own words for each outcome, so the evaluator can tick it off.

What the scope asks for

Evaluators check the proposal against these sentences of the scope. Answer each one visibly, in the call's own words.

• “Projects should promote the adoption of high-TRL solutions by public and private sector organizations involved in disaster risk management, developing strategies for scaling and commercializing innovative DRS technologies to ensure they reach end-users efficiently.”
• “They should also demonstrate how these technologies can complement or replace existing disaster preparedness, response, and recovery frameworks by developing integrated governance and coordination models across sectors and levels for disaster preparedness, response, and recovery in multi-hazard and cascading risk scenario interoperability standards, and guidelines for integrating new solutions into national and European civil protection systems.”
• “The project should especially liaise and support other disaster resilience projects in driving their uptake as well as examine how to build synergy pathways with other preparedness grants, such as Knowledge for Action in Prevention & Preparedness (KAPP) funding call of the Union Civil Protection Mechanism (UCPM).”
• “Projects should also demonstrate the real-world effectiveness of high-TRL solutions through large-scale pilot projects and demonstrations, generating robust evidence to support data-driven decision-making and optimize disaster risk reduction strategies.”
• “Initiatives should consider the capacity gaps of the UCPM, align with EU disaster resilience objectives and build on existing programs, ensuring synergies with relevant policies, funding mechanisms, and technological ecosystems.”
• “The private-public cooperation chapter of the Preparedness Union Strategy should especially be a guiding document.”
• “Proposals are encouraged to incorporate digital tools, AI-driven analytics, digital twins such as Destination Earth, IoT applications, and other emerging technologies to enhance disaster preparedness and response.”
• “Proposals should have a strategy to promote the visibility of the project and the results to the broader public in order to show the potential of European civil security research (political sphere, private sector, citizens).”
• “In this topic the integration of the gender dimension (sex and gender analysis) in research and innovation content should be addressed only if relevant in relation to the objectives of the research effort.”

Conditions that shape the proposal

• Part B, sections 1–3: 45 pages (standard application form). Text beyond the limit is not read; tables and figures count.
• Lump sum: the budget is fixed per work package and paid when each work package is completed. Every work package needs activities and deliverables an evaluator can verify, and the effort must match the money.
• TRL: the topic expects TRL 8 by the end of the project. State where you start and the evidence for it.
• Innovation action: evaluators expect a plausible path to commercialisation and named first users or customers.
• Other Eligible Conditions: “In line with the “ restriction on control in innovation actions in critical technology areas ” delineated in General Annex B of the General Annexes, entities established in an eligible country but which are directly or indirectly controlled by China or by a legal entity established in China are not eligible to…”
• Other Eligible Conditions: “Subject to restrictions for the protection of European communication networks.”
• Other Eligible Conditions: “The following additional eligibility criteria apply: This topic requires the active involvement, as beneficiaries, of at least 3 first responders or authorities in charge of disaster risk[[Authorities in charge of disaster risk entail public bodies operating at the national level that hold legally defined…”
• Other Eligible Conditions: “For these participants, applicants must fill in the table “Information about security practitioners” in the application form with all the requested information, following the template provided in the submission IT tool.”

Impact pathway and traps

• Users or citizens are part of the scope. Show how they take part in the design and testing, not only that they are informed.
• The scope expects pilots or demonstration. Name the sites, the partners who run them and what is measured there.
• The topic expects cooperation with other projects or initiatives. Reserve effort and budget for it in the work plan.
• The gender dimension is named in the topic. Show how sex and gender analysis enters the research content, not only team balance.
• Market uptake is part of the scope. Evaluators look for a credible route to market with named first adopters.
• Policy or regulation is in scope. Name the policy owners you will reach and what you will give them.
• Keep outputs, outcomes and impacts apart: what you deliver, what changes when others use it, and the long-term effect.
• Link your outcomes to the destination's expected impacts in the Work Programme. Destination impacts are long-term effects, not project deliverables.
• Name the barriers outside the project (regulation, markets, user behaviour) that could block uptake, and what you will do if they do.
• Section 2.3 (the summary canvas) is optional on this call; the old split into scientific, economic and societal impact is no longer required.