From Final Report to Living Catalogue: Making Project Results Reusable by the Next Consortium

The final report is not the reusable asset

A project result becomes reusable when it has a stable home, a clear owner, a short description, and enough context for another consortium to judge whether it fits their work. A final report is evidence for the funder. A living catalogue is a working product for the next coordinator, trainer, researcher, policy officer, or community manager.

Treat the catalogue as part of the digital work package, not as an afterthought for dissemination month. Start with the outputs you already promised: guides, toolkits, datasets, training modules, policy briefs, methods, software, templates, case studies, event recordings, and community assets. Then describe each result in the same structure, using language that people outside the consortium can understand.

The practical test is simple. A person who did not attend your meetings should be able to find the result, understand its purpose, see who made it, check its reuse conditions, and contact the right owner. If they cannot do that, the result is visible but not reusable.

Design the catalogue around reuse decisions

Most project websites present results in publication order. That helps the coordinator close the work package, but it does not help a future consortium choose what to reuse. A living catalogue should support decisions, so its main unit is the result page.

Each result page needs a consistent core:

• A plain-language title and one-paragraph summary.
• The problem the result addresses.
• The intended users, such as teachers, municipalities, youth workers, patient groups, SMEs, researchers, or project managers.
• The format, such as PDF, dataset, workshop plan, video, software, curriculum, checklist, or service.
• The maturity level, from draft to tested to actively maintained.
• The licence or reuse conditions.
• The languages available.
• The project, funder, partners, authors, and contact owner.
• Related results in the same project and in other projects.

Do not bury this in a news post. News tells the story of production. The catalogue supports adoption. Both can exist, but they do different jobs.

A good result page also says what the item is not for. Boundaries save time. If a toolkit was tested with rural NGOs, say that. If a curriculum assumes trained facilitators, say that. Reuse often fails because limitations were hidden behind cheerful dissemination copy.

Add metadata that other projects can actually use

Metadata is not bureaucracy when it helps people find the right asset faster. It is the bridge between your work package and the next proposal. Use controlled fields where possible, and write human summaries where nuance matters.

Start with a small metadata model. Do not build a museum catalogue if the consortium can only maintain a shelf. Useful fields include topic, sector, target group, country coverage, language, project stage, licence, result type, partner owner, and last reviewed date. Add a short reuse note: how another team can adapt the result, what files they need, and what permission is required.

Cross-link to recognised sources where they exist. For research and innovation projects, CORDIS remains a common reference point, and project pages on cordis.europa.eu give future partners a way to verify context. For Erasmus+ work, the official programme site at erasmus-plus.ec.europa.eu is a useful anchor for programme language.

The catalogue should also expose relationships. Link a training module to its facilitator guide, evaluation form, slide deck, and case study. Link a policy brief to the dataset and interviews behind it. Reuse becomes easier when the result is shown as a bundle, not a lonely file.

Keep it alive after the grant ends

A living catalogue needs an operating model. Without one, the result pages freeze on the day the project ends, then slowly lose links, contacts, and trust. The operating model can be light, but it must be named.

Assign an owner for each result before the final reporting period. The owner can be a partner organisation, not a single person. Add a shared inbox or role address where possible, because staff change. Decide who can update pages, approve edits, and respond to reuse requests.

Use a short maintenance rhythm:

• Review result pages after major project events.
• Review download links before the final report.
• Review ownership and contact details at project closure.
• Review the catalogue again when a new project reuses or cites an asset.

Make the handover visible. If a community of practice will host the catalogue, say so. If a partner website will host it, record the commitment in internal minutes and dissemination planning. If the consortium expects reuse but has no owner, the risk should be raised while the project is still active.

For consortia that need a maintained member area, knowledge base, or result catalogue, StrandsUnited can design and operate the platform as part of the digital work package. The key word is operate. Publishing is the beginning of reuse, not the end.

Build the catalogue into your next proposal

The best time to plan reusable results is proposal writing. Add the catalogue to the work plan as infrastructure for dissemination, exploitation, and knowledge management. Give it tasks, owners, and acceptance criteria. This keeps it from becoming a rushed upload folder near the end.

Describe the catalogue in practical terms. Say that each public result will receive a structured page, metadata, licence information, partner ownership, and links to related assets. Say how the consortium will handle multilingual summaries if the project serves more than one language community. Say who will maintain the platform after the grant and how users can request access to files, training materials, or community spaces.

Connect the catalogue to your events. Every webinar, training, pilot, and multiplier event can produce reusable material if the team captures it properly. Before the event, prepare a page shell. After the event, add slides, recordings, handouts, questions, and a short note on what changed because of the session.

Use your final report as a source, not as the destination. The report should point to the catalogue, and the catalogue should point to the actual assets. That structure helps evaluators, but it helps the next consortium even more. Your next action is to list your project outputs, choose the metadata fields, assign owners, and create the first result pages before the next reporting cycle.

Where this comes from

At StrandsUnited, we build and operate digital platforms for EU cooperation projects, including catalogues, member areas, knowledge bases, and AI assistants that answer with sources. Our consortium graph tracks 83490 projects and 461953 participation edges across Erasmus+, H2020, and Horizon Europe open data, which shows how often knowledge has to travel between partners, calls, and communities.

We also operate Impactful and build knowledge systems through our platform work, so this guidance comes from maintaining results after launch, not only publishing them once. The useful next step is small: turn one finished output into a structured result page, then repeat the pattern for the rest of the project.