研修の記録は、必要になる前に書きます。
記録は研修の場で作られるのではありません。終わったあとの二十分で作られ、その二十分が決して訪れないのです。
Visatory · · 読了 4 分
この記事はまだ翻訳されていません。以下の本文は英語です。上の見出しと要約は英語ではありません。
Training happens in most agencies more than the record suggests. A destination updates its rules and somebody briefs the team on a Tuesday morning. An institution sends a partner update and it is discussed. A new counsellor is walked through the process by a senior one over three weeks. All of that is training and almost none of it is recorded, because none of it looked like a course.
Then a moment arrives when the agency has to show what its staff were trained on, and the honest answer is that plenty of training happened and nothing was written down. Reconstructing it afterwards produces a document that is both true and unconvincing, which is the worst combination available.
Attendance is the least useful field.
A list of names against a date proves that people were in a room. It does not say what was covered, who delivered it, what materials were used, or whether anyone understood it. A record built only on attendance answers none of the questions that get asked.
- What the session covered, in enough detail that somebody reading it later knows the scope.
- Who delivered it and on what authority: internal, the institution, an external provider.
- The date, and for an update, what it was an update to.
- The materials used, stored rather than referenced, because a slide deck edited since is not the deck that was shown.
- Who attended, and how anybody absent was covered afterwards.
The last point is where records quietly fail. The person who missed the session is frequently the one whose case later goes wrong, and the file that says nothing about catching them up is a file that describes a gap.
The informal training counts.
The three weeks a senior counsellor spends bringing a new one up to speed is the most important training the agency does and it is invisible. It does not have to be turned into a course. It has to be given a name, a start and end date, a list of what was covered, and the name of whoever did it.
The same goes for the fifteen minutes on a Tuesday after a rule changes. One line in a log, written that morning, is worth more than an hour of reconstruction in six months.
Make the record a by-product.
Nobody maintains a training log as a separate task. It survives when it is produced by the thing that was going to happen anyway.
- Whoever calls a session writes the two-line record when they send the invitation, not afterwards.
- Materials are saved to the same place at the time they are used, under the date.
- Absences are listed when the session ends, while it is obvious who was not there.
- A short monthly pass by one person catches what was missed while people still remember it.
What good looks like a year later.
The test is simple and worth running now. Pick a rule that changed eight months ago in a destination the agency works with. Show when the team was briefed, by whom, what was covered, who was absent and how they were caught up.
An office that can produce that in a minute has a functioning record. An office that has to ask around has a set of memories, and memories are not evidence of anything except that people are trying to be helpful. The gap between those two positions is roughly twenty minutes of work per session, spent at the time rather than saved up.
The reason to bother that has nothing to do with review.
A training record is also the only honest answer to a question managers ask constantly, which is whether a mistake was a person's failure or a gap in what the office taught them. Without a record, that argument is settled by seniority. With one, it is settled by fact, and the fix is different in each case.