Instruction and proof of instruction are two different projects, and most companies only run the first one. The training happens. Somebody stands in front of a group, or a link goes out, or a document is signed at the gate. Then the record of it scatters across mailboxes, paper folders in a site office, and one spreadsheet that a single person keeps alive.
The moment that becomes a problem is always the same: someone asks a question that sounds simple and turns out not to be. Who at the Venlo site has done the updated lockout instruction. Are all the agency workers on line three instructed on the new procedure. Which of our forklift drivers is overdue.
Supervision is its own duty, and a record is what discharges it
Dutch employers usually know Arbowet art. 8 lid 1 and lid 2: workers must be effectively informed about the work and its risks, and must receive instruction that is effective and adapted to their distinct tasks. Lid 4 is the one that gets skipped. It requires the employer to supervise compliance with those instructions and rules.
That is a continuing obligation, not an event. It cannot be met by a session that happened once, and it cannot be met by a claim that the session happened. The Arbowet prescribes no particular form of proof, and it is worth being honest about that: there is no Dutch signature requirement. But without a registration you cannot demonstrate article 8 at all, and supervision without a record of who is behind is supervision in name only.
The certification side is blunter about paperwork. A VCA audit on question 4.1 asks for a specific pair of documents: the list of dates and subjects discussed, and the attendance lists. Question 3.6 requires instruction on the client's internal rules and procedures, for temporary workers and subcontractors too, before work starts on site, demonstrably, with attendance lists. In both cases the deliverable is a record, held per person.
The view that answers the question in the room
One dashboard, sliced the way the question was asked. By site, when a regional manager wants to know where the gap is. By role, when the question is whether everyone who drives a reach truck has the current instruction. By course version, when the question is who confirmed the procedure as it reads today rather than as it read in March. By person, when someone is standing in front of you and you need to know what they are cleared for.
Every completion carries the learner, the site, the role, the date and the version of the source document. The trail is built as the work happens rather than assembled afterwards, which is the whole difference between evidence and reconstruction.
Why the number is low, and what actually moves it
Low completion is usually diagnosed as a motivation problem. It is more often a design problem, and the causes are dull and fixable.
The course was built for a desk. If it needs a laptop, a login nobody remembers and forty uninterrupted minutes, it will not be done by someone who works standing up. Aristotl courses run in the browser on a phone, with no app installation, in modules of three to five minutes that fit between a break and a shift start.
The worker was sent things that are not theirs. Assignments scoped to site and role mean a packer sees the packing instruction and not the ADR module for the loading dock. A short, relevant list gets finished. A long list of maybes gets ignored.
The course was in a language the worker reads slowly. Automatic translation per learner removes the excuse and, more importantly, removes the real barrier. VCA question 3.7 treats communication without language barriers as a must for a reason.
Nobody local could see who was behind. This is the largest single factor. When outstanding names are only visible at HQ, chasing has to travel down through two layers of management before it reaches the person who could simply walk over. When the site manager sees their own list, it does not travel at all.
The Friday afternoon that stops happening
The familiar version: an answer is needed for Monday, the tracker was last updated three weeks ago with two sites missing entirely, mails go out to site managers, replies come back over three days in three formats, some as screenshots and some as confident guesses, and by Sunday night the file is half rebuilt and partly trustworthy. It survives the meeting because nobody pushes hard.
A spreadsheet fails in a specific way. It is a copy of the truth, made by hand, and it starts drifting the moment it is saved. It is wrong by Tuesday and it is still, somehow, the system of record. When an inspector, an auditor or an insurer eventually pushes hard, a partly rebuilt file is not evidence, and the person who maintained it is not the person who has to defend it.
Replacing it is mostly a setup exercise: bring the site and role hierarchy over once, and everything scopes against it after that. The tabs never come back.
Delegating the view without delegating the library
Site managers and franchise operators need real visibility to be accountable for it. What they do not need is the ability to edit corporate content, and most generic tools force a choice between full admin rights and no access at all.
Permissions scope to region, site or segment. A site manager logs into the same dashboard HQ uses, with the same fidelity, showing their own people, their own outstanding completions and their own exports. The centrally owned courses, the standard, the rollout calendar and the versioning stay where they belong. A local manager can add something of their own, a supplier specific handling instruction or a site rule, without it leaking into the central library. HQ still sees everything as part of the rollup.
That is a structural arrangement rather than a process someone has to police, and it is what makes local accountability survive the second month.
Bring the tracker you use today and the one site you are least sure about, and we will show you what the same record looks like when it maintains itself.