Caps, Triggers and Thresholds

A number attached to hours can be doing one of three jobs. It can be a cap, which may not be exceeded. It can be a trigger, which changes what is owed when it is passed. Or it can be a threshold, above which a different set of rules applies.

The threshold discussed in “Caps, Triggers and Thresholds” is useful only when hours can be reviewed before the decision becomes irreversible. A team evaluating daily schedule template with accountable controls for daily schedule template should test current totals, manager alerts, corrections and employee access while keeping the applicable legal limit outside the software as a documented rule.

They look identical on a page — forty-eight, sixty, twelve, eleven — and conflating them is the most common structural error in this subject. It runs in both directions and both are expensive.

For an independent reference relevant to “Caps, Triggers and Thresholds”, consult the IFAC Knowledge Gateway. Use it to test working-time definitions, recordkeeping, access, retention and exception handling against the organisation’s real process rather than treating one software report as conclusive.

The cap

A hard maximum. The work must not happen, and if it has happened the breach exists whatever anybody intended. Caps are usually attached to safety-critical regimes and to young workers, and they are usually the smallest group of numbers in the set.

A cap requires forward visibility, because the only compliant response to approaching one is to not do the work. Everything in the section of this collection about finding people before they cross is really about caps.

The trigger

A number that changes an entitlement. Beyond this many hours, a premium is payable; beyond this many, a rest entitlement arises; beyond this many in a night period, a health assessment must be offered.

A trigger does not forbid anything. The work is permitted and something becomes due, which means the compliance task is a payment or a provision rather than a refusal. Organisations that treat a trigger as a cap refuse work they could do; organisations that treat a cap as a trigger do work they should not have done and offer to pay for it afterwards, which does not cure it.

The threshold

A number that moves somebody into a different regime. Working a certain proportion of hours at night makes a person a night worker, with its own limits and entitlements. Exceeding a certain pattern can bring an arrangement within a sector regime it was previously outside.

Thresholds are the quietest of the three because crossing one changes nothing visible on the day. The consequence is that a set of obligations now applies, and it applies from the crossing, not from the moment somebody notices.

How to tell which you are looking at

Read the consequence rather than the number. If the text says the work must not be done or the hours must not exceed, it is a cap. If it says something becomes payable or must be provided, it is a trigger. If it says a person is to be regarded as, or that a regime applies, it is a threshold.

Writing the three words next to each number on the limits page is the cheapest possible disambiguation and it is almost never done.

What goes wrong with each

Caps treated as triggers: a breach that somebody tries to settle with a payment, which it cannot be.

Triggers treated as caps: unnecessary refusals, rota headaches, and a workforce told it cannot work hours it is entitled to work and be paid a premium for.

Thresholds ignored: a population that acquired a set of entitlements months ago and has had none of them, discovered during an audit, backdated.

The third is the most expensive and the least likely to be noticed, because nothing about crossing a threshold generates an event.

The threshold check worth running

Once a quarter, ask the data which people have crossed into a different category: who now meets the night worker definition, who has moved into a pattern the sector regime covers, who has become a regular rather than occasional driver.

The query is simple and the answer tends to include people nobody expected, because the crossing happened through accumulated small changes to a rota rather than through a decision. The organisation then has a choice to make, which is a far better position than discovering it has been making it by default.

Putting all three on one page

The limits page described earlier in this section needs a fourth column: cap, trigger or threshold. Four words, one per row.

Everything downstream reads differently once it is there. A report of people near a number means something specific. A conversation with a rota planner has a defined answer. And nobody spends an afternoon arguing about whether something is allowed, because the page says what kind of number it is.

The number that is three things at once

Occasionally the same figure does more than one job. Forty-eight hours may be an averaged ceiling under the regulation, a premium trigger under the contract, and a threshold in a client's supplier standard, all at once.

Where that happens, the three have to be listed separately even though the number is identical, because they have different periods, different consequences and different people who care about them. A single row saying forty-eight obscures the fact that passing it has three distinct effects, and the one that gets forgotten is usually the contractual trigger, which is the only one that costs money immediately.