Who trained on what, and when — recorded as a session ends and kept apart per site. This page names every field an entry holds, the form it comes back out in, and what happens the day a request lands on your desk.
In most companies the record of who was trained lives in one spreadsheet, on one computer, kept by one person who did not ask for the job. Sheets come back from three sites in three shapes. Names are spelled two ways. A leaver is still on it.
None of that shows until the morning somebody wants to see it, and then it takes two days and three phone calls to produce a list that describes last quarter. The training happened. It is the proof of it that arrives late.
An entry is written when somebody finishes a training, and it is written once. These are all of its fields.
One entry, filled in
That is the entry. There is no seventh field, and nothing is held about a person that is not on this list.
The first two stations run without anybody doing anything. At the fourth the record has left us and is part of the documentation you already keep.
Somebody works a training through to the end, between shifts and without stopping anything. That completion is the event, and everything after it refers to it.
The six fields, filled from what was already known. Nobody types it up, nobody signs a sheet, and no version of the list is a week behind another.
Name a site and a period. What comes back is the list for exactly that — a table you can open and sort, or a dated printout you can hand across a desk.
For example CSV or XLSX to work with, PDF to file.
From here it sits in your own documentation, filed the way you file everything else about a person. Past this line nothing depends on us.
The first three stations are the same for every training and every site. The fourth follows whatever your documentation already does.
Safety teams at
Go through the field list with the people at your company who would have to read it. That conversation takes half an hour and settles most of what comes up later.
The right-hand column is the one to take into the meeting. It is not a limitation. It is the answer to the question that gets asked there.
Both columns are agreed in writing before the first session runs, and the page they are written on is the one everything later refers back to.
Three people ask, for three different reasons. Each of them gets the same list, cut to what they asked about.
What is on record is the training your teams worked through: who, on what, and when. The safety instruction you are required to give stays yours to run and to document, and this is filed next to it, in the same place.
How a session runsMost companies already have three or four places where something about an employee is written down. What makes a new one unwelcome is not the software. It is that somebody has to keep it current, and that somebody is always the same person.
So the training record does not open a place of its own. It is handed over into the file your company already keeps on a person, and that file stays the one file.
Nobody is put in charge of it, nobody chases people for it, and it cannot drift out of step with the other one — because there is no other one. When somebody wants to know what a person has trained on, they look where they already look.
Most companies point it at one of four: a personnel system such as Personalwerk, a learning platform such as Lernbahn, an occupational-safety application such as Sicherheitsakte, or time recording such as Zeitpunkt. Agreeing which one, and in what form, is a conversation at the start — and the one point on this page where your IT department is involved at all.
Three of them are small on purpose. A record that is easy to explain is one that still gets kept in the second year.
6
Person, training, date, site, team, completed. The list is closed, which is why it can be shown to a works council in full.
0
No administrator, no owner, nobody chasing entries. The record is written where the session ends, not at a desk afterwards.
1
The file you already keep. Nothing is added beside it, so nothing can fall out of step with it.
11
The largest company on it runs eleven, each kept apart and each readable on its own or together with the rest.
None of these change with the number of trainings you pick. They are properties of the record, not of the order.
They were not asking the same question about it. Each of them says here which answer settled it.
“I used to spend the last week of every quarter chasing three sites for their sheets. I asked for the list this morning and read it before lunch.”
“My condition was that it does not become a fourth place to look. It lands in the file we already keep on the person, so it did not.”
“We had the list of fields on one page before the first session ran. What is not on that page is not kept, and that was the point I would have blocked it over.”
There is no administrator to appoint, no one to chase people for entries, and nothing that has to be kept current between sessions. The one thing asked of you is the list of names at the start, and a note when somebody joins or leaves.
That is why the second question is easier than it looks. What you pay for is the training itself. Everything on this page runs alongside it and is not a line of its own.
What else runs alongsideThe trainings you pick, for as many repeats as your teams need, at every site named in the agreement.
The record, the hand-over into your own systems, the equipment and the first sessions on site. There is no service level to choose and nothing billed by the visit.
Sorted into two: what people want to know about the record itself, and what they want to know about handing it over. Where the answer is no, it starts with no.
Write it in your own words. You get an answer in writing that you can pass on inside your company. We answer in English and German.
questions@preventario.exampleNo. Your instruction stays required and stays yours to run and to document. What this record holds is the training your teams worked through, and it is filed in the same place, next to it.
No, and not because it is hidden from them. How a person got through a training is not written down anywhere, so there is nothing to release, to request or to leak later.
Yes. An entry is written when a session ends, whichever shift that is, and the team field carries the shift the way your own structure names it. Nothing has to be open for it to be recorded, and nothing stops for it either.
They follow your own rules, because by then they sit in your own file. How long a training record is kept is decided by the same policy that decides it for everything else you hold about that person.
One conversation at the start, to agree which file the record is handed into and in what form. After that there is nothing for them to run, to host or to keep updated.
Then you ask for the list when you need it and file it yourself. Companies usually start that way and connect it once the first year has shown them how often they reach for it.
You do, and it is settled before the first session. The field list goes on one page, both columns of it, and that page is what everything later refers back to.
None of them is booked separately, and none of them is the reason anybody starts. Together they are the reason a training still happens in the second year.
Each page says what the service does, what it does not do, and what it asks of you.
All four servicesBring whoever keeps the personnel file, whoever answers when an outside request comes in, and one person from the works council. We go through the fields one by one, and through what it takes to hand them into the file you already keep. Half an hour, and you leave with the field list in writing.