How to publish your Erasmus+ project on EPALE: step by step

EPALE — the Electronic Platform for Adult Learning in Europe — is one of the most visited professional communities in European education and training. It hosts tens of thousands of practitioners, policymakers and educators from across all 33 Erasmus+ programme countries. For Erasmus+ projects in the fields of adult education, vocational training and school education, it is both a dissemination obligation and a genuine opportunity to reach an audience that would otherwise never find your project.

Yet most Erasmus+ coordinators either skip EPALE entirely, register and never post anything, or publish a single article at the end of the project that nobody reads because it was not promoted or written for the platform’s audience.

This guide covers everything you need to publish your Erasmus+ project on EPALE effectively — from registration to content strategy to what types of content get the most engagement — step by step.

What is EPALE and why does it matter for your project?

EPALE (Electronic Platform for Adult Learning in Europe) is the European Commission’s community platform for adult education and training professionals. It is funded by the EU through Erasmus+ and is free for all users. The platform is available in all EU languages and has users from every programme country — school education practitioners, VET trainers, adult educators, youth workers, policy makers and researchers.

For Erasmus+ projects, EPALE serves three purposes simultaneously:

• Dissemination obligation — the 2026 Programme Guide names EPALE as the priority dissemination platform for projects in the fields of adult education, VET and school education. For KA220 and KA210 projects in these fields, EPALE publication is expected and will be checked by assessors reviewing your final report
• Audience reach — EPALE connects you with practitioners across 33 countries who work in your field and could use or adapt your outputs. This is an audience you cannot reach through your own website or social media
• Partner discovery — EPALE’s partner search function allows organisations to find and connect with potential project partners — useful for future applications

Step 1: Register on EPALE

EPALE is free to join. Registration is done through the EU Login system — the European Commission’s single sign-on service that gives access to all EC platforms with one account.

How to register

1. Go to epale.ec.europa.eu
2. Click “Create an account” or “Log in with EU Login”
3. If you do not have an EU Login account: click “Create an account” on the EU Login page. You will need a valid email address. EU Login accounts are approved quickly — typically within minutes to hours
4. Once you have a EU Login account, return to EPALE and click “Log in with EU Login”
5. Complete your EPALE profile — your name, organisation, country, field of work and a short professional bio. A complete profile with a photo and organisation name receives more engagement on publications than an anonymous or incomplete one
6. Your registration request is reviewed by EPALE — approval typically takes 1–3 working days. You will receive a confirmation email when approved

Step 2: Understand EPALE’s content types

EPALE offers four main types of content that Erasmus+ project coordinators can publish. Each serves a different purpose and reaches the EPALE community in a different way.

Blog posts (highest visibility)

Blog posts are the most visible and most read content type on EPALE. They are indexed by search engines, appear on the EPALE homepage when recently published and are distributed to subscribers of relevant topics. A well-written blog post about your project can reach several hundred to several thousand practitioners across Europe.

Blog posts on EPALE should be written as professional articles — not promotional materials. The platform’s editorial standards are clear: content must be relevant to adult learning and education, written for a European professional audience and focused on sharing knowledge or experience rather than promoting an organisation. Promotional content is rejected by EPALE moderators.

Best formats for Erasmus+ project blog posts:

• A description of a challenge you identified in your field and how your project is addressing it — written from the practitioner’s perspective
• A methodology or approach your project developed — with enough detail that others can understand and potentially apply it
• A case study from your project — one participant’s experience, one activity that worked particularly well, one unexpected finding
• A results article — what your project produced, what you learned and what practitioners in your field can take from it

News items

Shorter than blog posts and more topical — news items are appropriate for announcing project milestones (kick-off meeting completed, output published, multiplier event announced), sharing upcoming events or publishing a brief project update. News items appear in the EPALE news feed and are searchable but receive less sustained engagement than blog posts.

Resource Centre uploads

The Resource Centre is EPALE’s library of educational materials, tools and outputs. This is where your project’s intellectual outputs should be published — training curricula, toolkits, methodological guides, e-learning modules, video resources and similar deliverables. Resources are downloadable and searchable by topic, language and format.

Publishing outputs in the Resource Centre rather than just linking to your project website ensures they remain accessible even if your project website goes offline — which is common 2–3 years after project closure.

Events calendar

The EPALE events calendar is a European-wide calendar of education and training events. Publish your multiplier events, dissemination workshops and project conferences here — it reaches an audience beyond your own network and can attract participants from other countries to your events.

Step 3: Publish your initial project description (Month 1–2)

The first publication for your project should be a brief introductory blog post or news item published in the first 1–2 months of implementation — not at the end. This serves several purposes: it establishes your project’s presence on the platform, starts building visibility during implementation rather than after it, and gives other practitioners the opportunity to follow your project’s progress and reach out if they are working on related topics.

What to include in your initial project post

• Project title and acronym
• The problem or challenge you are addressing — 2–3 sentences explaining why this project exists and why it matters for practitioners in your field
• Your target group — who will benefit from the project’s outputs
• Your partner organisations and countries — briefly, with a note on what each partner brings
• What the project will produce — the main outputs planned
• Project timeline — start and end date
• Contact — an email address for practitioners who want to follow the project or be informed when outputs are available
• EU funding acknowledgement — “Co-funded by the European Union” with the EU emblem image attached

Keep it to 400–600 words. The goal is visibility and contact-building, not a comprehensive project description.

Step 4: Publish updates during implementation

Do not go silent between the initial post and the final results article. Publishing one or two updates during implementation keeps your project visible on the platform and demonstrates active engagement — which assessors noting your dissemination activities will recognise.

Good mid-project content ideas:

• A brief account of your first transnational meeting — what was discussed, what was decided, what the team learned about the topic from bringing different national perspectives together
• An interim finding from your target group consultation or needs analysis — a specific insight that practitioners in your field would find useful
• A spotlight on a partner organisation — what they do, what they bring to the project, how the partnership is working
• An announcement when a draft output is available for practitioner review — inviting input from the EPALE community before finalisation
• An event announcement for a project webinar or open dissemination session

Step 5: Publish outputs in the Resource Centre

As each output is finalised, publish it in the EPALE Resource Centre. Do not wait until the project ends to upload everything at once — publishing outputs as they are completed gives them longer visibility on the platform and allows the EPALE community to engage with them during your project’s lifetime.

How to publish in the Resource Centre

1. Log in to EPALE and go to Resource Centre
2. Click “Add a resource”
3. Select the resource type — choose the category that best fits your output (training material, toolkit, guide, methodology, etc.)
4. Add the resource title, description and tags — use keywords that practitioners in your field would search for
5. Upload the file directly or add a link to an external URL
6. Add the language(s) the resource is available in
7. Include the open licence statement — specify the Creative Commons licence under which the resource is published
8. Add the EU funding acknowledgement in the description
9. Submit for moderation — EPALE reviews resources before publishing, which typically takes 1–5 working days

Writing an effective Resource Centre description

The resource description is what users see before they decide whether to download. Write it for practitioners who are looking for something useful — not for assessors who already know what your project produced. Answer three questions: what problem does this resource address, who is it for and what can they do with it?

Step 6: Write your project results article

The results article is the most important EPALE publication for a completed project — and the one that most organisations write poorly. It is not a final report summary. It is a practitioner-focused article that answers one question: what can a professional in this field learn from, or do with, what your project produced?

Structure of an effective results article

Opening — the problem (100–150 words): Describe the challenge your project addressed in concrete, specific terms. Write for a practitioner who has never heard of your project — they need to recognise the problem before they will read about the solution.

What the project did (200–300 words): A brief description of the project’s approach — not a list of activities, but a narrative of how you went about addressing the problem. Include one or two specific examples that make the work tangible.

Key findings or outputs (200–300 words): What the project produced. For each main output: what it is, what it contains, who it is for and where to access it. Include direct links to Resource Centre entries or external download URLs.

What practitioners can take from this (100–200 words): The “so what” for the reader. How could a practitioner in this field use your outputs? What do your findings suggest for their own practice or context?

Project information (50–100 words): Project title, acronym, countries, funding amount (optional), grant agreement number (optional), EU acknowledgement, link to the EPRP entry.

Step 7: Contact your EPALE National Support Service

Every programme country has an EPALE National Support Service (NSS) — a national team that supports EPALE users in their country and promotes high-quality content to their national networks. This is a free resource that most Erasmus+ coordinators never use.

Your NSS can:

• Share your project publications to their national EPALE newsletter and social media channels — significantly extending your reach within your country
• Feature your project on the national EPALE page
• Advise on content quality and whether your article meets EPALE’s editorial standards before you submit
• Help you identify other EPALE users in your field who might be interested in your outputs
• Connect you with potential future project partners through the EPALE network

Contact your NSS by email — their contact details are available on the EPALE platform under the “National Support Services” section. A brief email introducing your project and asking whether they can promote your publications is all that is needed. Most NSSs are actively looking for high-quality project content to share.

EPALE content that gets engagement: what works and what does not

Having published and promoted content on EPALE, here is what consistently gets more views, downloads and comments versus what gets ignored:

What gets engagement

• Practical, specific content — articles that give practitioners something they can actually use: a methodology they can apply, a tool they can download, a finding that challenges or confirms something in their practice
• Content in multiple languages — EPALE has users across 33 countries. An article published in English, Greek and Serbian reaches three times the audience of an English-only publication. For project outputs, making them available in all project partner languages significantly increases download numbers
• Articles that name a specific challenge — not “our project addressed digital skills” but “our project addressed a specific gap: adult educators in non-formal settings have no access to structured training in AI-assisted facilitation, and here is what we found”
• Early publication — articles published during implementation receive more sustained attention than articles published at project close, when the EPALE community has already moved on to newer content
• Resources that are immediately downloadable — no registration walls, no request forms, no “contact us for a copy”

What gets ignored

• Articles that are essentially press releases about the project — written for a funder, not for a practitioner
• Publications that describe activities without explaining outcomes or takeaways
• Resources uploaded without a description — just a file name and nothing else
• Content published in a single language when the project involved multiple countries
• Final articles published in the last week of the project grant period — they arrive when no one is looking and disappear from the EPALE feed before practitioners find them

EPALE for youth projects — a note

EPALE’s primary audience is adult education and VET — if your project is purely in the youth field (KA152, KA153) without an adult education or training dimension, EPALE may not be the most relevant platform. For youth-focused projects, the European Youth Portal (europa.eu/youth) is the priority dissemination channel.

However, if your youth project has a strong non-formal education or youth worker training component — which many KA153 and KA210 youth projects do — EPALE is relevant and valuable. Youth worker professional development, training methodologies for working with young people and tools for youth educators all fit within EPALE’s scope.

Frequently asked questions

Is EPALE publication mandatory for all Erasmus+ projects?

EPALE is the priority dissemination platform named in the Programme Guide for projects in adult education, VET and school education fields. For KA220 projects in these fields it is effectively an expected dissemination channel — its absence in the final report dissemination section will be noticed by assessors. For KA210 projects and KA1 mobility projects, EPALE publication is strongly recommended but may not be a strict grant condition. Check your grant agreement for your specific requirements.

How long does EPALE content moderation take?

Blog posts and news items are typically moderated within 1–5 working days. Resource Centre uploads may take slightly longer depending on the volume of submissions. Do not plan your first EPALE publication for the day before your final report deadline — allow at least 2 weeks.

Can partner organisations in other countries also publish on EPALE?

Yes — and they should. Each partner organisation can register on EPALE independently and publish in their own language for their national audience. A project where all four partner organisations publish in their respective national languages on EPALE reaches a significantly wider audience than a project where only the coordinator publishes in English. Coordinate with partners to ensure consistent messaging across publications.

Can I publish on EPALE in Greek or Serbian — not just English?

Yes. EPALE is multilingual and supports all EU languages as well as languages of associated countries. Publishing in your national language reaches your national EPALE audience and allows your National Support Service to promote the content more effectively within your country. For maximum reach, publish the same article in multiple languages or at minimum provide a summary in English.

What happens to my EPALE content after the project ends?

EPALE publications remain live after the project ends unless you actively remove them. Resource Centre uploads remain available for download indefinitely. This is one advantage of EPALE over a project-specific website — content persists even if your organisation’s website changes or the project website goes offline. Keep your EPALE account active and check periodically that your publications and resource links are still working.

EPALE (Electronic Platform for Adult Learning in Europe) is operated by the European Commission and funded through the Erasmus+ programme. Platform features and registration procedures may be updated by the Commission — always refer to epale.ec.europa.eu for current guidance. Information about EPALE National Support Services is available on the EPALE platform. GrowthProjects.eu is an independent consultancy and is not affiliated with the European Commission, EACEA or any National Agency.