A Sustainability Section That Isn't Fiction: Designing a Dissemination Plan That Outlives the Grant

Start with the operating model, not the promise

A sustainability section is credible when it names what will keep running, who will run it, how it will be maintained, and why a real group will still need it after the grant. A dissemination plan outlives the grant when it turns project outputs into reusable assets, not one-off posts. Treat both sections as a small operating design: users, channels, ownership, content, platform, evidence, and handover.

The weak version says the website will remain online and partners will share results through their networks. Evaluators have read that sentence many times. The stronger version names the assets that survive: a method library, a searchable case catalogue, a community area, event recordings, training packs, policy briefs, datasets, or an AI assistant that answers from approved sources. It also names the rhythm: who updates the assets, how often, and what triggers an update.

Write the section as if the coordinator will have to run it on a quiet Tuesday after the final report. That simple test removes fiction. If nobody owns the task, if no audience has a reason to return, or if the platform cannot be edited without a developer, the plan is not sustainable yet.

Separate dissemination, communication, exploitation, and sustainability

These terms overlap in real work, but the plan improves when each one has a job. Communication builds attention for the project while it is active. Dissemination packages results so specific audiences can use them. Exploitation supports adoption, replication, policy uptake, commercial use, or integration into existing services. Sustainability keeps selected outputs alive after funding ends.

Use plain language in the proposal. For each major output, add a short path from production to continued use. A toolkit is not finished when the PDF is uploaded. It becomes useful when a trainer can find it, understand the context, adapt it, cite it, and ask a question. A policy brief is not sustained by being archived. It survives when it is connected to a named network, event series, working group, or knowledge base.

A practical structure is to map each output to a specific audience, format, channel, owner, and after-grant home. Keep the grid in your internal planning file. In the proposal text, explain the pattern with examples. This shows that the plan is not a list of channels. It is a route from project work to future use.

Design channels around user behaviour

Start with the people who must act on the results. A youth worker, city officer, researcher, school leader, NGO coordinator, investor, and ministry adviser do not search in the same way. They need different entry points, different proof, and different file formats. A good dissemination plan respects that.

Avoid building the plan around social media alone. Social posts can create reach, but they are poor memory. They disappear quickly and they rarely preserve context. Put durable material in a place you control: a project website, partner knowledge base, community platform, public catalogue, or thematic resource hub. Then use newsletters, events, partner channels, and social posts to send people back to that source.

For digital work packages, define content types early:

• Short summaries for scanning
• Full outputs for reuse
• Event pages with recordings and materials
• Searchable case studies
• Partner and stakeholder profiles
• Frequently asked questions
• Source-backed answers for complex topics

This is where platform choice matters. A static website can be enough for a small project with few outputs. A consortium with many partners, recurring events, stakeholder groups, or a living methodology may need a managed platform. StrandsUnited designs and operates these kinds of community and knowledge platforms for EU cooperation projects.

Make the after-grant owner visible

Sustainability fails when the proposal hides the future owner. Name the likely steward during the project design stage. It may be the coordinator, a partner association, a university unit, a municipal network, a foundation, a spin-out service, or a community of practice. The legal owner and the working owner can be different, but both should be clear.

The plan should also say what will not be sustained. This is a sign of maturity. Not every campaign page, draft document, meeting note, or internal tool deserves long-term care. Choose the outputs that have reuse value and explain why. Evaluators are more likely to trust a focused commitment than a promise that everything will live forever.

Add maintenance tasks in concrete terms. Someone must renew domains, update software, moderate submissions, remove obsolete material, answer access requests, edit pages, and keep partner links current. If the platform contains personal data, community features, or AI-supported search, governance is not optional. The sustainability plan should mention permissions, source control, data protection roles, and a review process for public content.

The handover should happen before the final month. Plan a light governance session, editorial backlog, admin training, and a post-project content calendar while the consortium is still active.

Write evidence into the plan before the first post

A credible dissemination plan does not only promise activity. It defines what evidence will show that the right people engaged with the right outputs. This can include event participation, resource downloads, newsletter responses, citations, stakeholder requests, partner reuse, community questions, and policy or practice references. Use measures that fit the channel and the audience.

Keep the evaluation burden reasonable. A small consortium does not need a complex analytics machine. It does need consistent tagging, clear content owners, and a shared way to record meaningful uptake. Decide which signals matter before launch, then build them into the platform and work package routines.

EU projects also benefit from looking at what already exists. Our consortium graph covers 83490 projects and 461953 participation edges from CORDIS and Erasmus+ open data for the 2014-2027 period. That scale shows why generic dissemination is easy to miss. Your plan has to make the project findable by topic, audience, geography, method, and output type, not only by acronym.

Before submitting, run a final fiction test:

• Can a new user find the main outputs without asking a partner?
• Does each output have an owner after the grant?
• Is there a maintained home for materials?
• Are reuse rights and access rules clear?
• Does the plan name what will stop?

If any answer is weak, revise the work package before you polish the wording.

Where this comes from

This advice comes from building and operating digital infrastructure for cooperation projects, communities, catalogues, member areas, events, knowledge bases, and source-backed AI assistants. Our grant intelligence engine and consortium graph help us see how projects connect across CORDIS and Erasmus+ data, while products such as Impactful keep us close to day-to-day community operations. If you are drafting a dissemination or sustainability work package now, define the future owner, the durable assets, and the operating routine before you write the promise. You can also review how we support EU project platforms on what we do.