Scheduling method: annualised hours

Scheduling · ~7 minute read

The contract that flexes with demand

An annualised hours contract specifies a total number of hours an agent will work over the course of a year rather than a fixed number per week. A typical agreement might commit an agent to 1,820 hours across the year (35 hours x 52 weeks), with the actual weekly hours flexing between, say, 25 and 45 to match demand. Annualised hours are common in manufacturing, healthcare, and seasonal retail, and increasingly common in contact centres with strong seasonal patterns. The model rewards operations that can use the flex constructively and punishes operations that cannot. This article walks through what annualised hours is, where it works well, where it fails, the contractual and operational design choices, and the common mistakes.

How the model works

Three elements define an annualised hours contract. The annual hours commitment — the total the agent will work over the year. The banding — the minimum and maximum hours per week (e.g. 25 to 45), often with separate constraints on consecutive long or short weeks. And the reserve hours — a small pool of hours the agent commits to that the operation can call on with short notice, typically with a premium pay rate.

The agent is paid the same monthly salary regardless of actual hours worked, calculated from the annual hours and the hourly rate. This means short weeks do not produce a smaller pay cheque, and long weeks do not produce a larger one. The agent agrees to be available within the banding; the operation agrees to give reasonable notice (typically two to four weeks) of which weeks are which.

Where it earns its keep

Annualised hours work best in operations with predictable but uneven seasonal demand. A retail-support operation that handles three times its baseline volume in the run-up to Christmas can flex existing annualised-hours staff up to peak weeks and back down to quiet weeks without recruiting, training, and releasing a temporary workforce around the peak. A tax-related operation can do the same around the January self-assessment deadline. The cost saving against a temporary workforce is substantial, and the quality difference — tenured agents handling the peak rather than newly trained temps — is even more substantial.

A second benefit is retention. Agents on annualised hours often value the predictable monthly pay alongside the weekly flexibility, and the model attracts a workforce demographic (parents, students, carers) that fixed-hour contracts struggle to recruit. The retention effect is real and worth modelling explicitly in the business case.

Where it fails

Three failure modes recur. The first is flat-demand operations. Annualised hours pay back in proportion to how much the operation flexes; an operation whose demand barely varies week-to-week gets little benefit and absorbs administrative complexity for nothing. The second is operations without forecasting maturity. Annualised hours require committing the workforce to specific banded weeks weeks or months in advance; an operation whose forecast is wrong half the time pays the cost in unused commitment hours or emergency over-flex. The third is poor communication with the workforce. If agents only find out their week’s hours on the Friday before, the model fails on the wellbeing grounds it was supposed to improve.

Contractual design

Four design choices shape whether annualised hours work in practice. The banding width. A narrow band (33–37 hours) gives the operation little flex; a wide band (25–45) gives lots of flex but pushes more demand onto the agents. Most operations settle in the 30–40 range. The notice period. Two weeks is standard; four weeks is more agent-friendly but reduces operational flex. The reserve hours. Typically 5–10% of total annual hours, paid at a premium when called. These are the hours the operation can lean on in genuine emergencies. The reconciliation cadence. Usually quarterly, with an end-of-year true-up: hours worked above commitment are paid as additional time; hours below are usually written off (occasionally rolled forward). Each of these is a negotiation with the workforce or union and shapes whether the model is sustainable.

Operational design

Beyond the contract, three operational habits make annualised hours work. Publish the schedule further out than you would otherwise. Annualised hours workforces value predictability even more than fixed-hours workforces; six to eight weeks of visible schedule is common. Track hours-to-date carefully. The planning team needs a clear view of where each agent stands against their commitment, and the agents need it too. Build in cool-down periods. A run of long weeks needs to be followed by easier weeks, not another peak. The model that pushes agents from one peak straight into another burns out the workforce and produces an attrition spike that erases the model’s benefits.

Mixing annualised and standard contracts

Most operations do not move the entire workforce onto annualised hours at once. The pattern that works is a layered workforce: a stable core of standard-hours staff, plus an annualised-hours layer that flexes with demand, plus occasional temporary or overtime cover for the most extreme weeks. This gives the operation flexibility without forcing the whole workforce onto a contract that not everyone wants. Recruitment can advertise both contract types; agents can sometimes move between them as life circumstances change.

Common mistakes

Three patterns recur. Choosing the banding too aggressively. A 25–55 band sounds great for operational flex but produces unmanageable variation in agents’ lives and unsustainable attrition. Treating reserve hours as routine. If the operation is using reserve hours every week, the annualised hours commitment is too low or the forecasting is too inaccurate; reserve hours are for genuine emergencies, not chronic shortfalls. Failing to communicate hours-to-date. Agents need to see where they stand against commitment regularly — once a quarter is not enough.

Conclusion

Annualised hours are a powerful tool for contact centres with strong seasonal demand. Done well, they replace expensive seasonal recruitment with tenured, trained agents whose pay is predictable and whose weekly hours adapt to what the operation needs. Done badly, they push too much variability onto the workforce, produce burnout, and erode the very retention benefits they were designed to deliver. The discipline is in the contractual and operational design: a banding the workforce can live with, a notice period that treats agents as professionals, and a planning function mature enough to deliver against the commitments the model makes.

Pair this with peak season planning for the wider context, and building a work-life-balance friendly schedule menu for where annualised hours fit on the menu of options.