Horizon ethics readiness: put permissions, owners and dates into the work plan
The ethics self-assessment should change the work plan, not merely accompany it. Proposal teams need to connect each issue to a mitigation, permission, expiry date, expected approval date, responsible owner and dependent activity.
An ethics section completed in the final hours before submission is usually too late to improve the project. The European Commission's current Portal guide tells applicants to start thinking about ethics while designing the proposal and not to wait until the last minute to seek advice or check applicable requirements.
The reason is operational. If the proposal raises one or more issues in the ethics issues table, the self-assessment must describe the issue, explain how the consortium intends to address it and identify relevant documents. For authorisations or permissions already available, the guide asks for their expiry dates. Where they are not yet available, it asks for the expected timing.
Those fields are not administrative decoration. A permission that arrives after recruitment is planned, a data-transfer route that is not legally or technically ready, or a site approval with no responsible owner can make the work plan internally impossible.
PRINCEPS recommends a controlled register with one row for each ethics-relevant issue or activity. It should contain:
1. Issue and activity — the specific people, data, material, technology, site or method involved.
2. Applicable control — the ethics, consent, protection, safety, access or approval question that must be resolved.
3. Mitigation — the practical design measure, procedure or safeguard.
4. Evidence — the permission, authorisation, protocol, information sheet, consent material, agreement, assessment or other record required.
5. Status and dates — whether evidence exists, its expiry date and the realistic date for anything still outstanding.
6. Owner — the named beneficiary and responsible role.
7. Work-plan dependency — the task, deliverable, milestone, participant recruitment, data collection or field activity that cannot proceed until the control is satisfied.
8. Escalation route — the warning point and decision-maker if approval is delayed or conditions change.
This register is a PRINCEPS implementation tool, not an official Commission form. Its purpose is to make the ethics narrative, work packages and delivery calendar agree.
A proposal can describe a sound method and still understate the time needed for institutional or public approvals. Ethics committee review, informed-consent material, data-protection assessment, site access, permits, cross-border material transfer, local community procedures or specialised safety controls may have different owners and timetables.
The right planning response is not to invent an approval date. It is to identify the competent route, document what is known, state what remains unresolved and sequence dependent activities accordingly. If the proposal is selected, the Commission guide says that the self-assessment will become part of the Grant Agreement in Annex 1 and may create binding obligations checked through ethics checks, reviews or audits.
For lump-sum proposals, the Commission's June 2026 guide adds another practical connection: ethics review may result in ethics deliverables placed in a separate “Ethics requirements” work package with a zero lump-sum share. A zero budget on that generated work package does not mean the underlying compliance work can be ignored; the main work plan still needs realistic ownership and resources where activities are required.
The ethics guide has a specific section for activities involving non-EU countries. It says that activities must comply with applicable international, EU and national law. For Horizon Europe activities carried out outside the EU, the guide also states that it is not enough for the activity to be accepted in the non-EU country; it must also be allowed in at least one EU Member State.
That point is important for Africa–Europe consortia. It should not be reduced to an assumption that the European partner will “handle ethics”. The African implementing institution often controls the site, participants, local approvals, cultural context, community engagement, data collection and operational safeguards. Its tasks, budget and authority should reflect that responsibility. At the same time, local approval alone should not be presented as completing the Horizon Europe analysis.
Before the proposal is frozen, ask whether every ethics issue has:
- a stated mitigation; - a competent evidence or approval route; - an owner; - an expiry or expected date; - a linked work-package task; - enough time and resources; and - an escalation path.
Any row missing one of these fields is an orphan control. It should be resolved, redesigned or explicitly managed before the consortium relies on the affected activity.
This analysis is strategic and editorial. It is not legal, research-ethics, medical, data-protection, safeguarding, regulatory or grant-award advice. The live call, current application form, institutional ethics bodies and qualified advisers remain controlling. Ethical acceptability, grant selection and later approval are not guaranteed.
Official sources
Verify the underlying development.
Editorial note: This is PRINCEPS analysis for general information. It does not replace the official work programme, topic conditions, submission system, grant rules or professional advice specific to an application.