Erasmus Without Paper (EWP) 2026: The Complete University Coordinator's Guide

Every Erasmus+ coordinator in Europe has now encountered Erasmus Without Paper. Many have had the experience of a student whose Learning Agreement could not be processed because the partner institution was not yet connected, or of an IT department that needed six months to implement an API that the national agency wanted connected in six weeks. EWP has transformed the administrative backbone of European student mobility. It has also created a new category of institutional risk that most universities are only beginning to understand.

This guide covers what EWP is, how it works technically for Erasmus+ traineeship and study mobility, where the system currently stands in terms of adoption, what the transition risks look like in 2025-2026, and what coordinators should do to ensure their institution is not one of the laggards when the current contract framework changes.

What Erasmus Without Paper Actually Is

Erasmus Without Paper is the digital infrastructure that supports the administrative exchange of data between higher education institutions during Erasmus+ mobility. It is not a student portal. It is not a management system that you log into directly. It is a network layer that connects the information systems of thousands of European universities so that nomination data, Learning Agreement data, and mobility documentation can flow between institutions without being manually re-entered at each step.

The clearest way to understand EWP is to contrast it with what preceded it. Before EWP, when a student at the University of Warsaw was nominated to spend a semester at Maastricht University, someone in Warsaw's international office sent a nomination by email. Someone in Maastricht's office received that email, re-entered the student's data into Maastricht's system, and replied. The Learning Agreement was a PDF, signed by the student, the home coordinator and the host coordinator, often exchanged as an email attachment. Each institution maintained its own record. There was no shared data layer. The process was fragile, slow, and produced significant discrepancies between what home institutions thought had been agreed and what host institutions had recorded.

EWP replaces that email-and-PDF model with machine-to-machine data exchange. When Warsaw nominates a student through EWP, the nomination arrives in Maastricht's system automatically, with the student's data already structured and validated. When the Learning Agreement is created and signed digitally, both institutions have a shared record in real time. No re-entry, no PDF attachments, no email threads asking whether the signed copy was received.

The Technical Architecture: Three Ways Universities Connect

EWP is not a single platform. It is a network that universities can join in three different ways, depending on their IT capacity and the volume of their mobility activity.

The EWP Dashboard

The EWP Dashboard is the entry point for universities that do not have the capacity to build a direct API integration. It is a web-based interface, maintained by the European University Foundation, that allows coordinators to process digital nominations and Learning Agreements manually through a browser. The Dashboard does not require IT development. Any coordinator with a login can use it. In 2026, the Dashboard celebrates its first decade of operation and is widely used by smaller institutions with low volumes of mobility.

The limitation of the Dashboard is that it does not integrate with the university's own student information system. Data entered in the Dashboard lives in the Dashboard and must still be manually transferred into the university's internal records. For institutions processing hundreds of mobilities per year, this creates a parallel data management problem that defeats much of the administrative efficiency EWP is meant to deliver.

API Integration via EWP Clients

Larger institutions or those with significant IT capacity build direct API connections to the EWP Network. This is the full integration model: the university's student information system speaks directly to EWP, nominations arrive in the internal system automatically, and Learning Agreement data flows back into official records without manual re-entry. The setup cost is significant, typically requiring developer time and project management over several months. The operational benefit is proportionally large for institutions with high mobility volumes.

Pre-Built EWP Client Software

A third category: pre-built EWP client software packages, often bundled with student mobility management systems like Mobility Online, MoveON, or equivalents. These products have pre-built EWP connectivity, allowing institutions to connect to the network without building custom integrations. For mid-sized institutions with existing mobility management software, this is typically the most efficient path to full EWP integration.

Connection Method	Technical Requirement	Best For	Internal Integration
EWP Dashboard	Browser only, no IT development	Small institutions, low mobility volume	Manual transfer required
Bundled client software	Existing mobility management system with EWP module	Mid-sized institutions using MoveON, Mobility Online etc.	Partial to full integration
Custom API integration	Developer team, months of project work	Large institutions, 500+ mobilities per year	Full integration

What EWP Covers: Study Mobility vs. Traineeship Mobility

A distinction that creates considerable confusion among Erasmus+ coordinators is that EWP's digital Learning Agreement mandate applies differently to study mobility and traineeship mobility.

For study mobility (KA131 study periods), digital Learning Agreements via EWP are mandatory for all intra-European mobility between programme countries since 2022-23. There is no exception for small institutions or those with technical difficulties. The mandate is a hard requirement.

For traineeship mobility, the situation is more complex. The digital Learning Agreement for traineeships exists within EWP and is increasingly adopted, but the three-party nature of the traineeship agreement (involving the student, the sending institution and the host company) creates a coordination challenge that pure university-to-university digital exchange does not fully resolve. The host company must also have a mechanism to receive and sign the digital LA. Many companies, particularly SMEs, do not have systems that integrate with EWP at all.

In practice, many universities handling traineeship placements have developed hybrid workflows: the digital LA is exchanged between the sending and receiving universities via EWP, while the company signature is collected through separate digital signature tools such as DocuSign or equivalent, then attached to the EWP record. This is a workable solution but not a fully standardised one, and it creates variation between how different national agencies expect traineeship LAs to be documented.

For universities managing Erasmus+ traineeship mobility specifically, the practical question is how the host company side of the tripartite agreement integrates with EWP workflows. The answer varies by national agency, and coordinators should verify their specific national agency's requirements for traineeship LA documentation rather than assuming study mobility rules apply directly.

Adoption Progress: The Numbers and What They Obscure

The headline figure for EWP adoption is striking: nearly 100 percent of higher education institutions involved in Erasmus+ mobility are now connected to the network. In the 2023-24 academic year, more than 126,000 Learning Agreements were exchanged digitally, compared to roughly 20,000 in 2021-22. The European Commission's target of 95 percent of all Learning Agreements being digital by the end of 2025 was supported by a majority of programme countries already reaching the threshold of more than 75 percent of digital LAs as of recent reporting.

These figures are real, but they require interpretation. "Connected to EWP" means the institution can send and receive data through the network. It does not mean the institution is processing all its mobility digitally. A university that has an EWP Dashboard account and uses it for 20 percent of its nominations while still processing the other 80 percent by email counts as connected. The gap between connectivity and full utilisation is where the residual administrative burden lives.

As of February 2025, a majority of ECHE holders were processing LAs digitally via EWP. That means a significant minority were not. The European University Foundation's "EWP Back to the Future" White Paper, developed from consultations with around 500 universities, identified the primary barrier clearly: smaller institutions lack the capacity to invest in transition. They have relatively few student exchanges, insufficient IT staff to manage integration projects, and competing institutional priorities that push EWP implementation down the agenda.

The 2025-2026 Contract Transition: What Universities Need to Know

The most significant development in the EWP landscape for 2025-2026 is one that has received relatively little attention in most university international offices. The contract between the European Commission and the EWP+ Consortium, led by the European University Foundation, which has provided for the operation and development of EWP, expires during the 2025-26 academic year.

This is not a signal that EWP is ending. It is a signal that the current contractual and governance framework is changing, and that the next phase of EWP's operation will be shaped by how the European Commission and the EUF structure the successor arrangement. The European Commission's position, expressed through various working documents, is that digital mobility infrastructure should become more deeply embedded in the Erasmus+ programme design for the post-2027 period, moving toward a "once-only data entry" principle where student data entered once at a home institution flows through the entire mobility lifecycle without re-entry at any point.

Digital Nominations: The Practical Workflow in 2026

For coordinators who understand EWP conceptually but want clarity on how digital nominations actually work in practice, the European Commission published a new practitioner guide on digital nominations in early 2026. The core workflow for outgoing nominations is as follows:

1. Nomination creation The sending institution creates a nomination for the student in its student information system or EWP Dashboard. This includes student identity data, the receiving institution's SCHAC code (the unique institutional identifier within EWP), and the proposed mobility period.
2. Transmission via EWP The nomination is transmitted automatically to the receiving institution via the EWP Network. No email required. The receiving institution's system receives the structured data and creates a pending nomination record.
3. Receiving institution review The receiving institution accepts or rejects the nomination in its system. Acceptance triggers an automatic notification back to the sending institution. Rejection triggers a notification with a reason code.
4. Learning Agreement creation Once accepted, the student creates the Learning Agreement digitally. Both home and host coordinators receive notification for electronic signature. The signed LA is stored in EWP as the authoritative record.
5. Amendments and recognition During the mobility, any changes to the course selection are processed as digital amendments through the same workflow. After the mobility, the Transcript of Records and recognition documentation are exchanged through EWP.

The workflow above describes the ideal state. In practice, step 3 is where many processes stall: receiving institutions that have not fully integrated EWP may respond slowly to digital nominations, or may not have a clear process for communicating rejections through the network rather than by email. The "strong uptake of digital nominations" noted in Q1 2026 reporting reflects genuine progress, but it also reflects that nominations are typically the first EWP function institutions implement, while Learning Agreement exchange and transcript management follow later in the adoption curve.

What EWP Does Not Cover: The Gaps Coordinators Must Manage

Understanding EWP requires understanding where it stops. Even with full EWP integration, several elements of Erasmus+ mobility management remain outside the network.

Grant Agreements and Financial Management

EWP handles academic documentation, not financial management. The grant agreement between the student and the institution, the payment of the Erasmus+ grant, and the financial reporting to the national agency all happen in separate systems. EWP does not replace the national agency's grant management platform.

Visa and Entry Requirements

EWP contains no visa or permit data. For students from programme countries moving within the Schengen Area, this is typically not an issue. For students from partner countries, or for programme-country students moving to non-Schengen destinations, the visa and entry permit documentation remains entirely outside EWP. The Erasmus+ Traineeship Coordinator's Handbook covers duty-of-care obligations that fall into this gap, including the insurance and welfare checks that digital documentation does not replace.

Quality Assurance at the Placement Level

A signed digital Learning Agreement is a formal record that an internship or study period has been agreed between institutions. It is not a quality assurance instrument. The question of whether the host organisation is genuinely providing learning value, whether the student's tasks match the agreed description, and whether the placement is meeting educational objectives requires monitoring processes that EWP does not support. For traineeship placements in particular, the gap between what the Learning Agreement records and what the student actually does on the ground is a persistent institutional risk that no digital platform eliminates.

Universities that partner with vetted placement networks, rather than relying solely on student-sourced placements, reduce this gap significantly. The institutional partnership framework at Internship Abroad is built on the principle that EWP documentation is necessary but not sufficient for quality traineeship placement, and that the vetting of host organisations is a separate institutional function that must be maintained alongside digital administrative compliance.

Preparing Your Institution: A Practical Checklist

For coordinators who want to assess where their institution stands, the following questions identify the most common gaps.

Area	Question to Ask	Status Indicator
Basic connectivity	Is your institution listed in the EWP Registry?	Verifiable at registry.erasmuswithoutpaper.eu
Digital nominations	Are outgoing nominations sent digitally via EWP for all connected partner institutions?	If not, identify which partners receive email nominations and follow up
Digital Learning Agreements	Are study mobility LAs being created and signed digitally for all intra-European movements?	Mandatory since 2022-23. Non-compliance creates reporting risk.
Traineeship LAs	What is the workflow for the host company signature on traineeship LAs?	If no clear answer exists, this needs to be defined before the next academic year
Internal integration	Does EWP data flow into your student information system automatically, or is it re-entered manually?	Manual re-entry is a risk indicator for data quality and coordinator burnout
Contract transition	Is someone in your institution monitoring EUF and National Agency communications about EWP governance?	If not, nominate a responsible person before the transition period

The Broader Context: EWP and the Future Erasmus+ Programme

EWP is not an end in itself. It is the infrastructure layer of a longer transition toward a fully digital European mobility ecosystem, and the current generation of the system is best understood as a first-generation attempt rather than a settled solution.

The European Commission's working documents for the post-2027 Erasmus+ programme describe a "once-only data entry" principle as a design goal: a student's data, entered once at enrolment, would flow through the entire system. The nomination, the Learning Agreement, the grant agreement, the transcript of records, and the recognition decision would all draw from that single entry point without re-entry anywhere. This is technically achievable with the right architecture, but it requires deeper integration between EWP, national agency grant management systems, and institutional student information systems than currently exists.

The "EWP Back to the Future" White Paper, based on consultations with approximately 500 universities, maps the distance between the current state and that goal. It identifies simplification of the process as the primary user demand, ahead of further features. The most consistent feedback from coordinators is not that EWP lacks capability, but that it adds complexity in the transition period before institutions reach full integration.

For university international offices, the practical implication is that the administrative workload of managing Erasmus+ mobility will not decrease sharply in the short term, even as EWP adoption increases. The benefits of full digitisation compound over time, as manual error rates fall and coordinator time shifts from re-entering data to managing student welfare and programme quality. But the early adoption phase, where institutions are running both digital and paper-adjacent processes simultaneously, is administratively intensive.

For universities reviewing their traineeship placement strategy alongside their EWP compliance posture, exploring the national mobility programme landscape and how different programmes interact with Erasmus+ traineeship eligibility is a useful parallel exercise. The Erasmus+ Guide 2026 for institutions covers the KA131 framework within which EWP traineeship processes operate.

Students navigating what a digital learning agreement means from their side can find practical context through the free internship toolkit at the Internship Abroad student platform, which covers documentation expectations for Erasmus+ traineeship placements.