The Spring Reset: Why the UK OKR Year Should Start in April, Not January

There is a particular kind of meeting that happens in the second week of January in British companies. The building is half empty. The coffee is bad. A leadership team that last met properly in November agrees a set of annual objectives, assigns them to a year that will actually be funded from April, and disperses feeling productive.

It is a habit, and it is not a British one. The calendar year has no special status in how UK organisations are resourced, taxed or assessed. Planning against it creates a structural mismatch that shows up, predictably, as a scramble every autumn.

This is an argument for moving the annual commitment to spring.

Three clocks, one company

UK teams run on more than one clock, and OKRs only work when they are pinned to the right one.

The tax year runs from 6 April to 5 April and governs payroll, benefits and a good deal of statutory administration. The financial year for most companies, and for nearly all public bodies, runs from 1 April to 31 March. The funding decision is announced in the autumn Budget, usually October or November, with a Spring Statement following in March that can adjust the picture again.

Set objectives in January and you are, in effect, committing to a set of numbers before the money is confirmed and before the departmental budgets exist to support them. Set them in April and the commitment sits next to the resourcing. Ambition that is not funded is not an OKR; it is a wish with a dashboard.

What January-only planning actually costs

Four costs recur.

The Q4 scramble. If the OKR year is January to December and the fiscal year is April to March, the final quarter is spent chasing results that will be reported into a different cycle, by a workforce that has already mentally closed the year. December removes two working weeks. Stretch work gets pulled forward into November, fails, and is quietly written off.

The budget mismatch. Headcount and spend are committed in January and approved in April. Teams spend the first quarter of their OKR year protecting promises they cannot yet resource.

The double plan. Leadership does strategy in the autumn. Then January arrives and a second planning round begins, with different framing and different numbers, and middle managers spend February reconciling the two.

The hiring lag. April pay reviews, April budget lines and the graduate intake all land after the January objectives were written. The plan and the people arrive three months apart.

A calendar that follows the fiscal year

What follows is a deliberately lean structure. It assumes no more than four formal checkpoints and no planning activity during the two periods when UK teams are least available.

April, weeks one and two. Annual objectives are set and published before the second Friday. Two or three company objectives, no more than four key results each. Budget assumptions are already known, so the debate is about priority rather than affordability.

April to June. Execution, with the existing weekly review unchanged.

Late June. First checkpoint. Forty-five minutes, one-page pre-read, no slide decks.

July. A mid-year re-cut: half a day, two questions only. What is now impossible? What is now obvious? Expect two of five key results to change. This is the release valve that prevents the autumn scramble.

August. Light touch. The weekly review becomes fortnightly. No workshops, no planning sessions. School holidays are not a scheduling inconvenience to be worked around; they are a fact of the UK operating year.

Late September. Second checkpoint.

October and November. The autumn Budget lands. Within a fortnight, run a single budget-delta session. Adjust funding assumptions and, if necessary, sequencing. Do not rewrite the annual objectives; they are ten months from completion, not ten minutes.

December. No planning. One thirty-minute review and a short shutdown note recording what resumes in January.

Mid-January. Third checkpoint, framed as a mid-year pulse rather than a fresh annual plan.

March. Close, carry-over decisions and the annual assessment, which feeds directly into the April objective setting. The loop closes in twelve months without a discontinuity.

Checkpoints that respect the working year

Three design rules make this survivable.

Keep the checkpoint to forty-five minutes with a one-page pre-read. Confidence ratings are enough: green, amber or red on each key result, plus one sentence on what would change the rating. Percentage progress on a key result that is not yet finished is a fiction.

Avoid the collision weeks. Easter, the August bank holiday, the last two weeks of December and the final fortnight of the tax year are not good dates for strategic review. Moving a checkpoint by a fortnight costs nothing; holding it in a week when half the team is away costs credibility.

Separate the annual question from the quarterly one. The annual calendar decides what the year is for. The quarterly checkpoint decides whether the current approach is still the right one. Mixing them produces meetings that re-litigate strategy every ten weeks and never resolve it.

The obvious objections

We run a calendar-year group reporting cycle. Then keep a January annual plan for reporting, but anchor the funding, appraisal and commitment conversation to April. The point is not to add a second calendar; it is to stop running both badly.

Our budget is not confirmed until April. Set objectives in the first two weeks of April on provisional figures and confirm them by the end of the month. A two-week lag is manageable. A three-month one is not.

Our board sets strategy in September. Excellent. September becomes the input to the April commitment, not a competing plan. Strategy in autumn, funding in spring, commitment in April.

Nothing about our year matches this. Some sectors genuinely do not. But before dismissing it, check which of the three clocks your organisation actually answers to. Most UK teams find that at least two of them point at April.

The underlying principle is simple enough to state in a sentence: put the moment of commitment next to the moment of resourcing. Everything else in the calendar is administration.