Qualifications and Licences
How to tell a qualification that genuinely binds a rota from one the organisation set for itself, and the expiry problem behind both.
Six qualification constraints on one depot rota, checked against their source
Two of the six genuinely bind, three bend at a price the depot can state, and the sixth was costing two supervisor shifts a week for a rule that does not exist. This is one employer's own check, not a statement of what any rule requires about qualifications.
A qualification is the cleanest constraint on a rota: the person holds it or does not, and no amount of goodwill substitutes. It is also the constraint most often confused with one of its neighbours, which is a policy the organisation wrote about qualifications.
The constraint in “Qualifications and Licences” becomes useful only when its source, cost and effect on coverage are visible. A team considering explore the published attendance workflow for mouse jiggler detection can add timely work and attendance context, with transparent settings, limited access and a clear correction route.
The two look identical on a rota and behave completely differently when the rota is short.
For an outside reference relevant to “Qualifications and Licences”, consult California hours-and-days guidance. Compare the general material with the organisation’s jurisdiction, sector and written agreements.
The three sources
A qualification constraint comes from one of three places: a legal or licensing requirement, a customer or insurer requirement in a contract, or the organisation's own standard.
| Source | Who can change it | Typical lead time |
|---|---|---|
| Licensing or legal requirement | Nobody on site | — |
| Customer or insurer requirement | Contract owner | Renewal |
| The organisation's own standard | Whoever owns the policy | An afternoon |
Only the first is immovable by anybody on site. The second can be renegotiated at contract renewal and sometimes before. The third can be changed this afternoon by whoever owns the policy, and frequently nobody has noticed that it is the third.
Reading the organisation's own standard carefully
Internal standards are usually written with qualifiers that get lost in transmission: "where reasonably practicable", "normally", "a trained person should be available".
The rota implements the summary, which is stricter than the text. Going back to the text is often enough to turn an apparently binding constraint into a judgement, and the judgement may well come out the same way — but it is now a decision with an owner.
The expiry problem
Qualifications expire, and rotas are built from a list of who holds what. If the list is not dated, the rota is being built from a claim about the past.
Expiries cluster, because people are trained in cohorts. A depot can lose four forklift tickets in the same month three years after a recruitment drive, and the rota will not see it coming unless somebody is looking at dates rather than names.
The register that prevents it
One row per person, one column per qualification, each cell holding an expiry date rather than a tick. Sorted by date, it produces next quarter's training plan for free.
Ticks are the problem. A tick records that something was true once, and the whole value of the register is in knowing when it stops being true.
Where the single holder sits
The most expensive version of this constraint is one qualification held by one person. That is not a qualification constraint any more; it is a single point of failure wearing one, and it belongs in the skills section of any honest constraint register.
The price of removing it is usually the cost of training one more person, which is almost always smaller than the cover arrangements currently built around the gap.
Checking the thing rather than the record
Licences and entitlements should be checked against the document, not against the internal file, and on a stated cycle. Files drift: an entitlement is removed, a card is not renewed, a restriction is added.
What checking is required, how often, and what may be recorded about it differ by sector and jurisdiction, and are a question for somebody qualified where you are. Operationally, the point is that the rota depends on the check and almost never shows when it last happened.
What to do when the qualified person is unavailable
Decide in advance, and write the decision down. There are only three answers: the work does not run, somebody else is qualified in time, or the work runs differently in a way the standard permits.
Deciding this in the moment, at 06:40, with one person off sick, is how organisations end up with an undocumented fourth answer that nobody would have approved in daylight.
The constraint that is actually supervision
Frequently the requirement is not that the person holds a qualification, but that somebody qualified is available to them. That is a much weaker constraint and it opens options the rota has never considered: on-call, remote, shared across sites.
Confusing the two is common, and it is expensive in exactly the way a single-holder constraint is expensive.
The cohort problem, stated once
Training in cohorts produces expiry in cohorts, and an organisation that trains everybody at once has built a cliff three years out without deciding to.
Staggering refreshers costs nothing and removes the cliff permanently. It is the only intervention in this section that is free, and it is almost never done, because the cohort is created by a recruitment event and nobody owns the consequence three years later.
What to write on the register
The qualification, which of the three sources it comes from, the clause or document it sits in, how many people hold it, and the earliest expiry among them.
Five fields, and together they answer the only two questions anybody ever asks about this category: can we move it, and when does it break.