Welcome
In Mobility Tool+, Force majeure applies to mobilities which could not be started or completed due to an unforeseeable exceptional situation or event beyond the individual participant's control. It is not attributed to error nor negligence on the participant's part. Such situations can arise at any time including factors such as sudden disease, accidents, death, earthquakes and other causes. While creating or editing a mobility, when the checkbox Force Majeure is checked the comment field Force Majeure Explanations must be completed. The justifications for indicating the mobility as Force Majeure should be added here. Mobilities having an end date within 2020, the Force Majeure flag checked, and for which the provided Force Majeure Explanations contain keywords such as "corona" or "covid" will automatically have the new "COVID-19 affected" flag set. This flag cannot be changed manually. The same rule applies for the export and import of mobilities: in the import/export file no specific column for the flag is available, but is automatically set in Mobility Tool+ on import, if the conditions are met. To indicate a mobility as COVID-19 affected: For additional information and guidance on Force Majeure due to COVID-19, please see MT+ Force majeure guidance due to Coronavirus. For Key Action 1 projects, if the Force Majeure flag is set, a number of fields and calculations will be affected in Mobility Tool+ depending on the call year and key action type: Duration of the Mobility Period (days) The business rules checking the minimum and maximum duration no longer apply in case of Force Majeure. Example: KA105 Call 2019, Youth Exchanges - Programme Countries The business rule checking the minimum of 8 hours per week no longer applies in case of Force Majeure. Example: KA107 Call 2019, Staff mobility for Teaching To/From Partner Countries The field becomes editable. If any values were already present they will remain. Example: KA105 Call 2019, Youth Exchanges - Programme Countries The field becomes editable. If any values were already present they will remain. Example: KA 116 Call 2018, Advance Planning Visit - Erasmus PRO The field becomes editable. If any values were already present they will remain. Example: KA105 Call 2019, Youth Exchanges - Programme Countries If the mobility was eligible for linguistic support before Force Majeure intervened, the Linguistic Preparation checkbox remains available even if the duration is shortened to less than the minimum required duration (19 days for VET learners and 60 days for long-term Youth-EVS mobilities). When the checkbox is ticked, the Linguistic Support budget field remains available, but the default amount cannot be changed in case of Force Majeure. Example: KA116 Call 2018, Short term mobility for VET learners The field becomes editable. If any values were already present they will remain. Example: KA101 Call 2019, Structured Courses/Training Events Information Force Majeure does not affect the sending of the participant report. The participant, even if unavailable, will receive the system notification regarding the Participant Report to be filled in at the end of the activity. For Key Action 3 projects, if the Force Majeure flag is set, the following fields will be affected: Example: KA347 Call 2019, Transnational Activities2020 "COVID-19 affected" flag
KA1 Force Majeure
Total Number of Teaching Hours
EU Travel Grant
EU Individual Support
Organisational Support
Linguistic Preparation and Linguistic Support
Course Fees Grant
KA3 Force Majeure
Related Articles
Overview
Content Tools
Apps
