By Julien Sudre, grant writer and Horizon Europe project manager, founder of Grant360 and Innotrope. Originally published 12 November 2025. Updated: 23 September 2026.
Horizon Europe continuous reporting is the process of updating the Funding & Tenders Portal during a project, rather than reconstructing its progress only at the end of a reporting period. It covers the status of milestones and deliverables, the publishable project summary, critical risks and relevant programme monitoring information. When the periodic report is prepared, the system draws on these entries to generate Part A of the technical report. Regular, accurate updates can reduce the work of checking past activities, but partners must still prepare the narrative and financial parts of the periodic report. Funding & Tenders Online Manual: continuous reporting; reports and payment requests.
This guide draws on the author's experience writing more than a hundred grant applications and managing European projects. The exact Portal screens, roles and reporting obligations depend on the programme, grant type and signed Grant Agreement. Use the official Online Manual and your project's instructions as the operational reference.
What information belongs in continuous reporting?
Enter the information the project is required to provide as it becomes available: progress against contractual milestones, submission of deliverables, an updated publishable summary, the status of critical risks, and applicable publications, communication, intellectual property or other monitoring information. The Commission's manual lists these categories and notes that additional indicator screens depend on the programme and action type.
For example, after a prototype is validated, the responsible team should confirm whether the related milestone has been achieved and retain the agreed evidence. A publication should be checked against the project's open science obligations and recorded in the appropriate place. Do not add a patent, training or technology readiness level (TRL) entry simply to fill a screen; report information relevant to your actual grant and activities.
The publishable summary deserves its own review. According to the Online Manual, it should stand alone, be understandable to a general audience and contain no confidential or sensitive information. If you add an image, clear the necessary rights. A project summary written for publication serves a different purpose from an internal progress note.
How do you report deliverables and milestones correctly?
Follow the schedule and descriptions in the signed Description of Action (DoA), normally Annex 1 to the Grant Agreement. A deliverable is an output listed for submission; a milestone is a control point indicating meaningful progress. The official manual distinguishes the two and explains their reporting.
Assign an owner and internal reviewer to each item. Before submission, check the promised scope, due date, dissemination level and any personal, confidential or commercially sensitive content. A file uploaded or saved as a draft is not necessarily submitted; verify the final status in the Portal. The Commission's manual says participants should submit milestones and deliverables for their work, while the coordinator has responsibility for the consortium's reporting. Confirm the permissions and final submission steps shown for your project rather than assuming one universal button or role sequence.
If a deliverable is late, explain the reason and expected next step in the relevant field. The manual specifically asks for an explanation of missing, late, cancelled or grouped deliverables when the periodic report is submitted. For an unmet milestone, state the estimated achievement date and assess consequences for dependent work. A Portal comment documents the situation; it does not replace a required amendment to the grant. Continuous reporting manual; amendments manual.
How should you update critical risks and monitoring indicators?
Review the listed critical risks, add newly identified ones when appropriate and update mitigation measures as the project changes. A risk record is useful when it identifies what may happen, which task it affects, who owns the response and what the consortium will do. The Commission's continuous reporting instructions explicitly call for assessing listed risks and updating mitigation or adding new risks where necessary.
Suppose recruitment for a pilot is slower than planned. Record the effect on the pilot milestone, the steps being taken and whether a revised schedule or decision is needed. Keep a more detailed internal risk register if useful, then make sure the Portal entries accurately reflect the critical items that must be reported.
Horizon Europe may display programme-specific indicators for publications, dissemination, patents, small and medium-sized enterprise (SME) participation, gender, infrastructure, innovation, open data or training. The set is not a universal checklist for every grant. Assign the relevant fields to people who can verify the data, define what is being counted and avoid combining estimates with confirmed results without explanation. Official list of possible monitoring screens.
Who should contribute, check and submit the information?
Each participant should supply accurate information for its work; work package leaders should check technical progress; the project management team should coordinate the schedule and consistency; and the coordinator should verify what enters the consortium's official report. The Online Manual on periodic reports assigns the coordinator the final submission and quality checks for the combined periodic report. Access to individual continuous reporting actions is governed by the Portal roles for that project.
A practical assignment table might identify one person who drafts each entry, one who verifies it, its evidence source and its due date. For a conference presentation, for example, the presenting partner can supply the event and audience details while the communication lead checks whether it belongs under dissemination or communication and the coordinator checks consistency with the technical report.
Internal tools can help gather inputs, but do not treat a spreadsheet as the official record. Reconcile it with the Portal regularly, particularly when a partner changes staff or a deliverable changes status. For the wider coordination framework, read How do you manage a Horizon Europe project effectively?.
How often should you update continuous reporting?
Update an entry when the relevant event or result is known, then review completeness on a schedule proportionate to the project. The grant sets due dates for deliverables, milestones and reporting periods; it does not impose a universal rule of "ten minutes every week." An internal monthly check may work for a small consortium, while an active demonstration phase may need more frequent reviews.
For example, ask work package leaders once a month about items due soon, completed activities, new publications and emerging critical risks. Before a steering meeting, review unresolved entries and their effect on the plan. Ahead of the reporting period's end, agree internal cut-off dates for partners to validate information. These are management practices, not additional Commission deadlines.
The purpose of small updates is to preserve accurate evidence while it is available. If a partner waits a year to identify which event attracted which target group, the number may become impossible to verify. Record the source of each figure at the time of the activity.
How does continuous reporting feed the periodic report?
The Portal compiles continuous reporting information into Part A, the structured section of the periodic technical report, when that report is prepared and locked for review. Partners still need to write Part B, the narrative explanation of progress and deviations, and complete the financial reporting required by their grant. The coordinator checks that Parts A and B agree and submits the report with the applicable financial statements. Online Manual: reports and payment requests.
This timing matters. The manual warns that entries added to the Continuous Reporting Module after the technical report is first locked for review will not be included in that periodic report. Check the entries before locking, especially late deliverables, milestones, summary text, risks and indicators. Do not assume the system will automatically repair a missing explanation in Part B or a beneficiary's incomplete financial statement.
A useful final reconciliation asks: Do the milestone dates match the narrative? Are deliverable delays explained? Does Part B describe changes reflected in the structured tables? Do the reported outputs align with work actually performed? The more reliable the ongoing record, the less retrospective reconstruction is needed, but the periodic report remains a substantive review of the project.
Which mistakes create avoidable reporting problems?
The most common practical failures are treating a draft upload as submitted, leaving a late deliverable without explanation, publishing sensitive information in a summary or public deliverable, using inconsistent activity counts and locking the periodic report before checking the continuous entries. These are points to verify in your workflow, not a claim that every consortium makes them.
Be careful with the boundary between public and internal material. The publishable summary must contain no confidential or sensitive data; deliverables have their own dissemination levels and should be reviewed accordingly. The Portal record can support communication planning, but a draft entry is not automatically an approved press release or "Commission-approved" wording. Check publication rights, factual accuracy and any required review before reusing content.
Also avoid universal financial claims. The original version of this article asserted that certain publication charges alone are eligible and that a hypothetical project would be paid within 45 days. Cost eligibility and payment rules depend on the signed agreement, funding model and reporting process; refer to the Annotated Grant Agreement and the reports and payment requests manual for the applicable conditions.
How can continuous reporting improve project management?
Use its entries as evidence for management decisions: which contractual outputs are pending, what a missed milestone affects and where critical risks are growing. Combine the Portal's official status with an internal action log that records owners and decisions. An accurate Portal record can make periodic reporting more orderly and help the consortium discuss progress with its project officer, but the tool cannot replace active coordination.
For instance, a steering committee should not merely see that a pilot deliverable is marked late. It should decide whether the cause requires a revised sequence, additional support for a partner or an amendment. Record the decision and ensure that the subsequent Portal entry and periodic narrative tell the same factual story.
What is a sustainable continuous reporting routine?
Assign responsibilities at kick-off, update events and results when they occur, review the main tables regularly, check sensitive content before submission and reconcile the Portal record before locking each periodic report. Use the signed grant's deadlines as the baseline and adapt your internal review rhythm to the project's workload. Continuous reporting works best when the entries are accurate enough to support decisions as well as the eventual report.
For a broader account of governance, finances, amendments and audits, read How do you manage a Horizon Europe project effectively?. Grant Planner may help organise project tasks; the product page describes its current capabilities, while the Funding & Tenders Portal remains the official reporting channel.