The training record nobody could produce: what learning software has to keep

A client's audit team asked a facility management business for evidence that every person deployed on their site had completed the required safety induction, with dates. The business had run the inductions. The evidence was in a spreadsheet the site supervisor kept, a second spreadsheet HR kept that disagreed with it, attendance photographs in a WhatsApp group, and certificates in a training provider's portal that only one person had the login for. It took four days to assemble, and the assembled version had gaps nobody could explain.

The training had happened. The record had not. Learning and development software is bought for course delivery and is worth having for the register — the ability to say, per person, what they have completed, when, with what evidence, and when it expires.

MANDATORY                       DEVELOPMENTAL
  required by role/site/client    chosen against a need
  completion date + evidence      completion + assessment
  expiry date, renewal due        follow-up conversation
  owner: compliance/ops           owner: manager/HR
  producible on demand            reviewed at appraisal

Mixing them in one list loses the expiry
discipline of the first and the follow-up of
the second.

The mandatory register is a compliance record before it is a training record. It has to answer an auditor's question in minutes, per person, with evidence attached. The developmental register answers a different question — is anyone getting better — and needs the need, the nomination and the follow-up that a learning and development process produces. A system that treats both as 'courses completed' serves neither.

Most learning systems record that a person finished a course on a date. That proves attendance, and for some mandatory items attendance is the requirement. For anything that matters — operating a machine, handling a customer complaint, running an interview — the question is whether they can now do the thing, and that requires an assessment recorded against the completion. Where the system holds only completion, the register says everyone is trained and the shop floor says otherwise, and both are right.

Configure the assessment field from the start, per course: none required, a pass mark, a supervisor sign-off, or an observed demonstration. Then the register can distinguish between people who sat in the room and people who can do the work — which is what the competency and talent management framework needs from it.

Set the expiry rules once, per item, and never by hand per person. A rule — this certification lasts two years from completion — computes the date for everyone automatically, and a rule changed once updates every record. Dates typed in by hand are the spreadsheet's failure mode carried into the system.

1. 1

   Every mandatory item has an expiry

   Food-handler certification, safety authorisation, first-aid, a client's site induction. The system holds the date and computes the renewal.

2. 2

   Alerts go to the owner, in advance

   Sixty days, thirty days, overdue. To the site supervisor for site items, to HR for company-wide ones. Not to the employee alone, who has no authority to schedule anything.

3. 3

   Rostering can check it

   Where the system feeds the roster, a person whose authorisation has lapsed cannot be scheduled on the work that needs it. This is the point at which the register becomes a control rather than a list.

4. 4

   The lapse report

   Who is currently out of date, by site and item, on one screen. It is the report the audit team in the opening actually wanted, and it should take seconds.

Expiry tracking is unglamorous and it is the difference between a register and a lapse discovered during an inspection. A business with a hundred people and eight mandatory items has eight hundred dates to watch. Nobody watches eight hundred dates in a spreadsheet; a system does it for free.

For any business that deploys people at client premises — facility management, security, contract staffing — the mandatory register has a second dimension the generic learning system does not anticipate: requirements that belong to a client contract rather than to the company or the law. Site A needs its own induction; client B requires a particular certification; contract C specifies a refresher every six months. The register has to hold requirements per site and per contract, check each deployed person against the site they are on, and produce, per client, the evidence that everyone on their premises meets their rules. That is the report the audit team in the opening was asking for, and a system that holds only company-wide requirements cannot produce it however good its courseware.

It is also the register that changes deployment decisions. A supervisor who can see, before assigning someone to a site, that their site induction has lapsed makes a different assignment. Where the register is not connected to deployment, the lapse is discovered by the client.

Learning systems are sold on delivery — hosting courses, tracking progress through modules, quizzes. That is useful for knowledge-based content and largely irrelevant for the behavioural skills where most development budget goes, which are delivered in a room and transfer through practice and follow-up. Evaluate the delivery features honestly against what the business will actually run online, and weigh the register features against what it must be able to produce. Most growing businesses need the register far more than the courseware.

An auditor accepts a completion date with hesitation and a certificate, a signed attendance sheet or an assessment result without it. The system should hold the evidence against the completion — uploaded, dated, attributed — so that 'producible on demand' means the evidence and not a promise to find it. This is the feature that turns the four-day assembly in the opening into a filter and an export. It is also the one that is most often left unconfigured, because uploading evidence is a step someone has to do at the time, and the time is when nobody is thinking about the audit two years away.

• Register before courseware. If the system cannot produce the lapse report and the per-person evidence in seconds, the delivery features do not matter.
• Module over standalone, where the HRMS module holds expiry and feeds the roster. A separate learning platform that does not know who is deployed where cannot tell a supervisor who is out of date on their site.
• Load the mandatory register first, from whatever spreadsheets exist, and reconcile it. It is the register with consequences.
• Configure assessment and evidence fields per course before the first completion is recorded. Retro-fitting them is where the gaps come from.

Done in that order, learning and development software answers the audit team's question in the time it takes to apply a filter, and answers the harder question — is anyone getting better — with an assessment rather than an attendance sheet. That second answer is the one the learning and development module is rarely bought for and most worth having.