The Illusion of the Open Diary: Five Tests for Honest Capacity Planning

Capacity planning has a persistent optical illusion at its centre: the empty diary. A team looks at next month, sees white space and concludes there is room for more work. The conclusion is understandable. It is also frequently wrong.

In UK delivery teams, the gap between diary availability and genuine delivery capacity is where overcommitment begins. The following five tests are designed to be run quickly — not as an academic exercise, but as a practical check before anyone treats blank time as a resource. Used together, they produce a defensible capacity baseline for the next planning cycle.

Test one: Can the people with free time actually do the work?

A blank afternoon in a specialist's diary is not interchangeable with a blank afternoon in a generalist's. Capacity has a shape. If the work requires a qualified business analyst, a security-cleared engineer or someone who understands a legacy finance system, then free time elsewhere in the team is not a substitute.

The test is simple. List the roles required by the pipeline and compare them with the roles that actually have availability. Where the two do not match, record a skills constraint rather than a capacity surplus. This prevents the common mistake of assuming that because someone is free, the right someone is free.

For UK organisations with mixed permanent and contractor populations, the test should also distinguish between people who can start immediately and people who need onboarding, security checks or procurement lead time. A name on a resourcing spreadsheet is not the same as a productive pair of hands in week one.

Test two: How much of the diary is already consumed by interruption?

Most delivery teams underestimate the recurring load of meetings, support requests, line-management duties and ad hoc queries. The diary may look open, but the working day rarely behaves that way.

A two-week diary audit is usually enough to expose the pattern. Ask team members to categorise their time into planned delivery, recurring commitments, unplanned interruption and genuine focus time. The results are often sobering. In many UK teams, the proportion of uninterrupted time available for complex work is materially lower than the calendar suggests.

The output should not be a precise time-and-motion study. It should be a realistic interruption factor — for example, an assumption that only a proportion of any given week is available for planned delivery. That factor belongs in the capacity baseline, not in a separate conversation about 'busyness'.

Test three: What business-as-usual load is hidden behind the project plan?

Delivery work does not pause because a project needs attention. Business-as-usual commitments continue: month-end reporting, regulatory returns, customer escalations, seasonal peaks and the ordinary maintenance of services. In UK public sector teams, the financial year-end in March and the summer leave period are predictable capacity shocks. In private sector teams, quarter-end and peak trading periods play a similar role.

The test is to overlay the project plan onto the operational calendar rather than treating them as separate worlds. Ask what recurring obligations will fall due during the delivery window and who will absorb them. If the same people are named in both plans, the capacity calculation is double-counting.

A useful discipline is to record BAU load as a named constraint in the plan. It does not need to be perfect. It needs to be visible enough that no one later claims the load was unforeseeable.

Test four: Are part-time and fractional allocations being counted as full days?

A 0.5 FTE allocation is not two and a half days of uninterrupted delivery. It is two and a half days minus handover overhead, context switching and the inevitable lag between one person's working days and the rest of the team's. The same applies to people split across multiple projects or shared services.

The test is to convert allocations into effective hours rather than nominal days. For part-time staff, ask how many hours in a typical week are genuinely available for the project after meetings, handovers and fixed commitments. For shared resources, ask what proportion of their attention the project can realistically command.

This is not a argument against part-time or flexible working. It is an argument against pretending that fractional allocations behave like whole ones. Honest capacity planning respects the working pattern and plans around it.

Test five: Is the team waiting on decisions rather than doing work?

An open diary can also mean a stalled diary. If the team is waiting for approvals, clarifications, procurement sign-off or a change decision, then blank time is not capacity — it is latency.

The test is to list the decisions outstanding at the start of the planning window and identify who owns each one. Where decisions are unlikely to land before work is due to start, the capacity should be marked as contingent rather than available. This prevents the familiar pattern in which a team is deemed to have spare capacity, is given more work, and then finds itself unable to progress either the new work or the old.

Decision latency is a delivery constraint as real as any technical dependency. It deserves the same visibility in the plan.

Turning the tests into a defensible baseline

The five tests do not require a new tool or a lengthy consultation. They require a deliberate shift from counting diary space to counting usable capacity. The baseline that emerges should record, at minimum: effective hours by role, an interruption factor, named BAU constraints, fractional allocation assumptions and decision dependencies.

The result will not be perfectly precise. It will be defensible. That is the standard worth aiming for. A capacity plan that acknowledges its assumptions is more useful than a tidy spreadsheet that pretends to certainty.

Before the next planning cycle, run the tests. Then write down what you have assumed. The blank diary may still look inviting, but at least the team will know what it is really looking at.