mentro
Learning documentation

Learning documentation, Computer Science VET

What belongs in it, what the training ordinance requires and how the learning documentation grows day by day instead of being reconstructed from memory at the end of the semester.

As a learner in the Computer Science VET occupation you keep a learning documentation throughout your apprenticeship. It records what you worked on in the company and what you learned doing it. Your vocational trainer reviews it regularly, signs it and discusses it with you.

The tedious part is rarely the writing. It appears once six months have passed and nobody remembers exactly which piece of work happened when. Then it gets reconstructed, and the documentation ends up describing a memory rather than the work.

What the training ordinance requires

The obligation is not written into the federal act on vocational and professional education and training, nor into the corresponding federal ordinance. It is set out in the training ordinance of each individual occupation. For the Computer Science VET occupation, Article 12 states that the learner keeps a learning documentation during the practical training and records all essential work relating to the operational competences to be acquired as it happens. At least once per semester the vocational trainer checks and signs the documentation and discusses it with the learner.

Two things are therefore fixed: as it happens, not in hindsight. And tied to the operational competences, not as a free-form diary. For other occupations the training ordinance of that occupation applies, there is no single rule covering all of them.

What belongs in the learning documentation

Activities

What you worked on, with title, duration and date. Captured in seconds, right after work from your phone.

Learning journals

The reflection on it: what went well, what was difficult and what you will do differently next time.

Link to the curriculum

Every entry is mapped to the operational competences and performance objectives of your curriculum, automatically on saving.

Evidence

Files and results are filed with the activity they belong to. That keeps them findable, even a year later.

In the app

Captured in the moment, not at the end of the semester

An activity is typed in within seconds: title, duration, date. On saving, mentro maps the text to the matching operational competences, so you never search through a list.

  • Title, duration in hours and date, nothing more
  • Automatic competency mapping on saving
  • Inter-company courses and vocational school can be captured too
  • In the browser on phone, tablet and computer
Captured in the moment, not at the end of the semester
Captured in the moment, not at the end of the semester

Your curriculum is already mapped

mentro holds the curricula with areas of competence, operational competences and performance objectives, each with its taxonomy level K1 to K6. Your entries do not land in an empty field but exactly where they belong in the curriculum.

  • Computer Science VET, Application Development
  • Computer Science VET, Platform Development
  • Media Engineering VET
  • Digital Business Developer VET

The curriculum for the IT Operations specialisation is not available yet. More occupations are added continuously, tell us which one you need.

From the activity to the education report

The learning documentation is not an end in itself. It is the basis for the appraisal meeting and the education report at the end of the semester.

1

Capture

You record activities and learning journals while the work is still fresh.

2

Map

mentro links every entry to the matching operational competences of your curriculum.

3

Reflect

Guided questions in five stages take the reflection beyond short standard sentences.

4

Assess

At the end of the semester the education report sits on the official SDBB form, with the evidence ready.

Common questions about the learning documentation

Yes. The obligation sits in the training ordinance of the occupation, not in the federal act on vocational and professional education and training. For the Computer Science VET occupation, Article 12 requires the learner to keep a learning documentation during the practical training and to record all essential work relating to the operational competences to be acquired as it happens. At least once per semester the vocational trainer checks and signs it and discusses it with the learner.
At least once per semester, as set out in Article 12 of the training ordinance. The vocational trainer checks it, signs it and discusses it with the learner. In mentro you do not have to prepare anything for this: the person supervising you can see at any time what has been added since the last meeting.
It does not produce a grade. In the training ordinance for the Computer Science VET occupation the overall grade is made up of the practical work, general education and two experience grades, and the learning documentation does not appear in that calculation. It is, however, allowed as an aid during the individual practical work, together with the documents from the inter-company courses. Whether the same applies to your occupation is written in the training ordinance for your own profession. In mentro your entries are sorted by operational competence, so during the exam you quickly find the piece of work you are looking for.
For a company with one or two learners a spreadsheet does work, and we will not pretend otherwise. It starts to break down once the documentation grows: searching becomes tedious, nobody can tell later when an entry was actually written, and there is no link at all to the operational competences of the curriculum.
No, mentro has no import function. The simplest way is a cut-off date: from that day the documentation runs in mentro, everything before it stays where it is today. Older records can be filed as a document with an activity so they remain easy to find. In practice the start of a semester works well, because the next education report then builds cleanly on the data from mentro.

Learning documentation without reconstruction

Book a demo. In 30 minutes we will show you how the documentation grows day by day in your company.