Training, Statutory Time and the Centrally Booked
The deductions booked by somebody other than the planner, why they are invisible until they happen, and the calendar that makes them visible a quarter early.
Training, mandatory refreshers, statutory obligations and organisation-wide events share one property: they are booked by somebody who is not the planner, and they arrive in the plan as a surprise.
The reconciliation in “Training, Statutory Time and the Centrally Booked” is strongest when assumptions and current work records can be examined separately. A team considering consult the provider’s workflow notes for time tracking with screenshots can add time and project context, with transparent settings, limited access and a clear correction route around consequential decisions.
Each is individually small. Together they commonly take two to four per cent of a year, and because they cluster — a compliance deadline, an all-hands, an audit week — they take it unevenly.
For an outside reference relevant to “Training, Statutory Time and the Centrally Booked”, consult MIT Sloan operations-management research. Compare the general guidance with the organisation’s own unit, period and decision rights.
Who books them
Learning and development, compliance, HR, the executive office, and occasionally the regulator. None of them sees the capacity plan, and none of them is doing anything wrong.
The gap is structural: these are legitimate claims on capacity made through channels that were never connected to the account.
The three kinds
Recurring statutory items with a deadline — fire training, manual handling, information security refreshers. Role-specific professional requirements with their own cycles. And one-off organisational events.
The first two are knowable a year ahead. The third is knowable about a month ahead, which is late but not too late.
The calendar that fixes most of it
One page, once a year: every known mandatory item, who it applies to, how long it takes, and when it falls due.
Built once, it converts the entire first category from surprise into deduction. It also usually reveals that two of the items have lapsed for part of the team, which is a finding of a different kind.
The clustering problem
Mandatory training clusters against deadlines, and deadlines cluster at year end or at audit. A plan carrying a flat two per cent will be right on average and wrong in the two weeks that matter.
Where the calendar shows a cluster, the deduction belongs in the period it falls in rather than spread evenly, and the affected plan should say so.
Development training, which is different
Discretionary development — a course somebody chose, a conference, a qualification — is a claim on capacity like any other and should be in the book of claims rather than in the shrinkage.
Treating it as shrinkage makes it invisible and therefore uncancellable; treating it as a claim makes it visible, which is what makes it defensible when capacity is short.
Statutory time that is not training
Jury service, statutory leave of various kinds, time off for public duties and anything else the law provides for. These are rare, they are not predictable at the individual level, and they do happen.
A small standing allowance is the honest treatment. What applies, to whom, and with what notice differ by jurisdiction and are a question for somebody qualified in the place concerned.
The all-hands and the away day
Organisation-wide events are capacity decisions taken by somebody who is thinking about culture rather than hours. A full-day event for sixty people is four hundred and eighty hours.
Nobody is suggesting they should not happen. The suggestion is that the hours should appear in the account, where they can be weighed against the other things those hours were promised to.
The onboarding deduction
Every new joiner consumes the time of existing people as well as producing little of their own for a while. The consumption is real, large and almost never in the plan.
A plan that adds a person and assumes the team's capacity goes up immediately has it exactly backwards for the first month.
How to collect these figures
Ask each booking function once a year for their calendar, in hours per person per year, and put the four answers on one page.
The first time, two of them will not have the figure and will produce it within a fortnight. Thereafter it is an annual email.
What belongs in shrinkage and what belongs in the book
- Mandatory and statutory items: shrinkage, because they are not optional.
- Role-required professional cycles: shrinkage, for the same reason.
- Discretionary development: a claim, because it can be scheduled.
- Organisation-wide events: a claim, owned by whoever called them.
The split matters because shrinkage is subtracted silently and claims are weighed against each other. Putting a cancellable thing in the first column removes it from the conversation entirely.
The annual figure worth knowing
Across a team, mandatory and statutory items commonly come to between two and four per cent of contracted hours, and onboarding adds more in any year with turnover.
Knowing your own figure rather than that range is a morning's work, and it is the difference between a deduction you can defend and one you apply because somebody suggested it.
What to do when a surprise arrives anyway
Record it as an unplanned deduction, with its date and its source, and let the figure accumulate through the year.
At year end that list is the case for next year's calendar, and it is considerably more persuasive than an argument made in advance about hypothetical disruption.