WORKED EXAMPLES

The same three steps,
two companies with nothing in common.

A requirement is something a person must be able to do. A course teaches it and a test checks it. A certificate proves that one person passed, on a date, in a language they read. Nothing in that sentence mentions an industry — which is why the plant and the trading floor run the identical software underneath.

Both organisations below are fictional. Every figure is computed by the live product over demonstration data — we do not publish customer numbers we have not been given permission to publish, and we do not invent them.

A fabrication site of the kind the industrial worked example describes.
Illustrative. 240 people · 3 sites · 8 languages

Northgate Industrial

240 people · 3 sites · 8 languages

What makes it hard
Crews change weekly, clients check training records before they let work start, and an expired certificate is invisible until somebody goes looking for it.
What you write down once
Confined Space Entry, Working at Height, Lockout/Tagout — each attached to the jobs that need them, not to a list of people.
What happens next, without anybody asking
Eleven confined-space technicians are hired. Nobody assigns them anything.
What the system does about it
The system adds the requirement the same morning, finds that no course in the library covers it, and says so on the dashboard with the eleven names behind it — before an inspector asks.
192/240 trained for the job they do
11 people no course yet covers
52 pieces of training overdue, each with a name

If your people hold jobs, and the jobs carry obligations, this fits.

Fifty people or a hundred thousand. A bank, a hospital group, a software company onboarding across nine offices, a contractor whose crew changes weekly. The software does not know what the work is — only that somebody is doing it and something has to be true before they can.