Beyond the Public Eye: What Are Sensitive (SEN) Deliverables?

Not all research results are meant for public consumption. While the goal of EU-funded projects is to share findings widely, some information must be protected to prevent misuse or to comply with legal and ethical obligations. This is where the concept of a “Sensitive” (SEN) deliverable comes in.

A Sensitive (SEN) deliverable is a step up in confidentiality from a Public (PU) deliverable. It contains information that is limited to a specific, defined audience under the conditions of the project’s Grant Agreement.

The “Why”: Protecting Data and Reputation

The confidentiality of a Sensitive deliverable is a crucial protective measure for your project. Its purpose is to protect against a range of risks, from safeguarding personal data to preventing the misuse of intellectual property that could have reputational or legal consequences.

This practice is at the heart of the Open Science principle of “as open as possible, as closed as necessary”. While the overarching goal of Horizon Europe is to make research results widely available, it recognizes that there are legitimate reasons to keep certain information private. This ensures that while a project is transparent, it does not expose its data or participants to risk.

According to the Horizon Europe Grant Agreement, there are specific legal conditions for marking deliverables as sensitive. This is not an arbitrary decision but a critical step in a project’s legal protection. For example, data that, if shared prematurely, could undermine a patent application or threaten the privacy of individuals should be treated as sensitive.

The “How”: Designating and Managing a SEN Deliverable

The decision to designate a deliverable as Sensitive is a deliberate choice made during the Grant Agreement preparation phase. It’s a proactive measure, not an afterthought. You must be able to justify why the deliverable needs a limited audience.

Examples of information that might be classified as Sensitive include:

• Preliminary or unvalidated research results.
• Proprietary data from an industrial partner.
• Details of a project’s security protocols or operational procedures.
• Personal data or other information that could pose a risk to the security or privacy of participants.

While a Sensitive deliverable is not made public, it still must be submitted to the European Commission’s portal. It can be accessed by the Project Officer and other relevant parties, as outlined in the Grant Agreement. To ensure proper handling, the document itself should be clearly marked with “Sensitive” on every page.

Conclusion: A Critical Step in Risk Management

Properly designating a deliverable as Sensitive is a key aspect of responsible project management and ethical conduct. It shows that your consortium has considered the implications of its work and has put measures in place to protect itself and its stakeholders.

Correctly handling Sensitive deliverables is a critical step in risk management. By understanding and implementing the necessary protections, you ensure that your research maintains its integrity and complies with all legal obligations while still contributing to the wider body of knowledge in a responsible way.