The Months You Already Know About

Absence is not evenly distributed through the year and neither is the ability to cover it. Both patterns repeat, both are in the organisation's own data, and both are treated each year as weather.

The practical issue in “The Months You Already Know About” is easier to manage when operational time records can be checked without treating activity as intent. For teams exploring how to detect mouse jigglers, this workplace technology guide can add time and project context, provided collection is proportionate, employees can review inaccuracies and consequential decisions receive human review.

The useful move is simple and rare: take last year's log, mark the hard months, and plan capacity against them while there is time.

For an independent benchmark relevant to “The Months You Already Know About”, consult the Canada Revenue Agency payroll guidance. Use it to test scheduling, working-time limits, attendance records, employee rights and exception handling against the real operation rather than treating a software report as self-explanatory evidence.

The two curves

Absence rises in winter, in most sectors and most climates, driven by respiratory illness and compounded by the shorter days and the pressure of the period. It also rises around school holidays in operations with a lot of parents, for entirely different reasons.

Cover availability falls in summer, when the bank is on holiday along with everybody else, and falls again over the end-of-year period.

The worst weeks are where a high-absence period meets a low-availability one. In many operations that is the fortnight either side of the new year, and in others it is the back half of August.

Finding yours

Count mornings per week for twelve months and plot them. Then plot cover found internally as a proportion over the same weeks.

Two lines. Where the first is high and the second is low, those are the weeks to plan for, and there are usually between four and eight of them in a year.

Planning against them

Recruit to the bank before the peak, not during it. A bank recruited in September is competent and inducted by December; one recruited in December is a liability.

Hold leave back. Restricting leave in the known hard weeks is unpopular and is far more acceptable when announced in March than when refused in November.

Build the rota for those weeks with margin, and for the quiet weeks without. Most operations build every week the same way, which means they are simultaneously short in February and over-staffed in May.

Agree agency arrangements in advance for the peak, including rates. Agency rates rise with demand and the organisation negotiating in the second week of January is negotiating from the worst possible position.

Bring forward the training that creates second holders of capabilities, so that it is finished before the period when it is needed.

The predictable one-offs

Beyond the annual pattern there are dated events: a local school holiday, a major sporting fixture, a festival, the week a competing employer runs its recruitment.

Operations that employ locally feel all of these and few of them are written down anywhere. A calendar of known local events, built once and added to each year, is a twenty-minute artefact that prevents a handful of bad mornings.

What not to conclude

That the seasonal rise is a conduct problem. A winter peak in short-term sickness is the same peak the whole population has, and the organisation's own data will show it rising and falling with the season rather than with any management action.

Applying absence triggers mechanically through a high-incidence period catches a cohort of people who were simply ill in January, which is both unfair and expensive in goodwill.

The review that sets next year

One hour, at the same point each year: look at the two curves, mark the hard weeks for the year ahead, and set the four or five actions above against them with dates.

It is the only planning in this subject that happens with months of notice, and it is consistently skipped in favour of handling the mornings as they come.

The year that was not typical

Some years are distorted: an outbreak, a restructure, a major incident, a period of unusual demand. Planning next year against them produces capacity in the wrong place.

Mark the distorted weeks when the year is reviewed, and plan against the underlying pattern with the distortion noted separately. Two or three years of logs make this easy and the first year does not, which is an argument for starting the record now rather than for waiting until there is something to compare.

The peak nobody schedules for

Beyond the seasonal pattern there is a shape inside each week and each month that most operations never look at: the day after a payday, the first day back from a bank holiday, the start and end of a school term.

These produce small, reliable bumps. Individually none justifies a change; together they explain a surprising share of the mornings that feel random. Marking them on the planning calendar costs nothing and converts a handful of surprises a year into expected days, which is all that planning in this area ever achieves.