This page was moved to https://esci-sd.atlassian.net/wiki/spaces/EWP/overview
Click in the link above if you are not automatically redirected in 10 seconds.


You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 27 Next »

The mobility process cut into pieces

The Erasmus+ mobility for studies entails a whole set of processes that facilitate such mobility. Oftentimes in this process communication is needed between the sending (or home) HEI and the receiving (or host) HEI. In general one can describe the mobility flow as follows (sometimes steps are repeated/ordered somewhat differently):

  1. HEIs need to sign an Erasmus+ institutional agreement;
  2. Sending HEI nominates the student at the receiving HEI;
  3. Learning agreement needs to be worked out and signed by three parties (student, sending HEI, receiving HEI) before departure;
  4. Student arrives at the receiving HEI and receiving HEI needs to confirm the date of arrival;
  5. Learning agreement might change. If so, it needs to be signed by three parties (student, sending HEI, receiving HEI);
  6. Student departs from the receiving HEI and receiving HEI needs to confirm the date of departure;
  7. Receiving HEI sends TOR to sending HEI

For each of the steps that require communication (or data exchanges) between the sending HEI and the receiving HEI EWP comes into play. The processes above are translated into technical so-called APIs (Application Programming Interface) that facilitate system-to-system communication, allowing users to manage their part of the process in their own system and use the EWP network whenever confirmation/approval/signatures are needed from the partner. In doing so EWP replaces paper-based workflows by digital ones.


Specific info per scenario

1. No Tool? Use the Erasmus Dashboard (EWP Dashboard).

2. In-house built mobility management software? Connect to the EWP Network.

3. Use of 3rd party mobility management software? They will connect you to EWP.

The Erasmus Without Paper architecture also allows you to use a combination of tools.


Different scenario's for joining Erasmus Without Paper

Erasmus Without Paper allows your Higher Education Institution (HEI) to digitalise their Erasmus+ mobility management processes. Depending on the way you currently manage Erasmus+ mobilities at your institution, this page will offer an overview of the different scenarios. The main principle behind EWP is that you keep using your existing system for managing student mobility and that this system is connected to the EWP network. Instead of printing a PDF or a paper copy of e.g. an Inter-Institutional agreement or a Learning Agreement, you will be able to sign the "documents online" and send them directly via your software system to your partner institution which will also digitally sign them.

The following picture gives an overview of the different options. On this site you will find information and tools for all three scenarios. 

What tool do you use to manage mobilities?

Erasmus Dashboard

This is the tool developed by the EWP consortium that can be used for mobilities data and exchanging IIAs and OLAs.

Commercial mobility software

This can be commercial software or be provided by a consortium (public or private) to which your institution belongs.

In-house built mobility software

This is a piece of software created by (or specifically for) your own institution and entirely managed by your IT department.

  • No labels