Guidelines for Implementing Mentafy in Your Organization

These guidelines help teachers, school leaders, and IT administrators roll out Mentafy effectively. They address common concerns, explain best practices, and show how to integrate Mentafy into your organization’s workflows smoothly (for specific implementation help: see subpages).

1. Usage Models: Mandatory vs. Optional

Introducing a mandatory digital tool is standard practice in education. Schools often prescribe specific devices, platforms, or software to ensure fair conditions and consistent workflows.

Examples from schools:

• Mandatory iPads: Many 1:1 iPad programs require students to use only these devices. Operating systems, apps, and cloud services are predefined; private devices are not accepted.
• Graphing calculators in final exams: Several states mandate their use to ensure consistent exam conditions.
• Digital learning platforms: Platforms such as Moodle, IServ, mebis (Bavaria), and Logineo NRW are often required for submissions and grading.

Where Mentafy fits:

Mentafy works in the same way, providing a uniform process for documenting and verifying written work. It is as easy to use as other tools already familiar in schools.

If Mentafy remains optional

To ensure fair grading, students not using Mentafy should provide alternative evidence of their work process. Examples:

• Regular progress reports or draft submissions
• Scheduled status meetings with teachers
• An oral exam or colloquium after submission

Without these compensatory measures, grading can become inconsistent, and the teacher’s review workload will be significantly higher.

For schools or organizations with a Microsoft license

For security reasons, by default the users will not be able to grant this permission themselves, unless the administrator has configured this in general for all apps or for Mentafy specifically.

2. Data Protection