Open topic on supporting disruptive technological innovations for civil security

Expected outcomes

• Projects may contribute to some of the expected outcomes; say which ones and why.
• For each outcome (EO1 to EO2), 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.

• “Proposals should prioritize disruptive solutions that address diverse security threats while improving the efficiency and effectiveness of civil security operations.”
• “Emphasis should be placed on ensuring that these technologies are robust, reliable, scalable, and aligned with the needs of security practitioners.”
• “To achieve this, proposals should promote strong collaboration between researchers, public authorities, industry partners, and end-users.”
• “By fostering a collaborative ecosystem, projects should ensure that promising research transitions effectively into practical security applications, contributing to a more resilient and adaptive civil security landscape across Europe.”
• “To ensure that the proposed research and innovation activities are aligned to EU long-term strategic priorities, proposers are encouraged to consult relevant technology foresight exercises.”
• “Finally, proposals are expected to address all applicable considerations expressed in the Introduction of the Strengthened Security Research and Innovation Destination.”

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 4–5 by the end of the project. State where you start and the evidence for it.
• 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 2 relevant practitioners and 1 Research and Technology Organisation (RTO). For participants with practitioner status, applicants must fill in the table “Information about security…”

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.
• 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.