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):
- HEIs need to sign an Erasmus+ agreement;
- Sending HEI nominates the student at the receiving HEI;
- Learning agreement needs to be signed by three parties (student, sending HEI, receiving HEI) before departure;
- Student arrives at the receiving HEI and receiving HEI needs to confirm the date of arrival;
- Learning agreement might change and needs to be signed by three parties (student, sending HEI, receiving HEI);
- Student depart at the receiving HEI and receiving HEI needs to confirm the date of departure;
- Receiving HEI send 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.
Frequently asked questions
- Is the use of EWP mandatory?
- What is the architecture of the EWP Network?
- How can I join EWP?
Recently updated articles