Skip to content
HoursBack

Workforce capacity planning: measure the hours before you hire

Workforce capacity planning means working out how much work your team can take on with the people it already has, before you decide to hire. In admin-heavy teams the hardest number to get is the time lost to repeated admin, because it is spread thinly across every role and nobody sees it. HoursBack’s Workforce Capacity Programme measures those hours role by role, through short, confidential interviews, and gives leadership a conservative figure to plan with.

It measures the capacity your team has now. It does not forecast demand.

Why admin-heavy teams under-count their capacity

Capacity plans usually start from headcount and hours worked. They rarely show how much of each week goes on work that is repeated, re-keyed or no longer needed.

A working year is about 1,700 hours. In one team we assessed, about 870 hours a year of repeated admin could come back: about half a working year, spread thinly enough that nobody saw it.

That time hides in a few familiar places:

  • the same task done several ways by different people, when the fastest way is already inside the team
  • tasks still done every week where nobody uses what comes out
  • copying information from one system into another
  • chasing and status updates
  • the gap between the job as written and the job as done

None of this shows up in a headcount figure. It shows up when you ask the people doing the work where their week goes.

How the Programme measures recoverable hours, role by role

  1. 1. Interviews, role by role. You pick one team, usually the one where the pressure is highest, and we interview everyone in it in confidence. About an hour per person, at a time that suits them, with no preparation and no forms. We map where each hour goes and what is repeated. It is interviews, not system access, so it needs nothing from your IT team.
  2. 2. A leadership report. Within five working days of the last interview you get a leadership dashboard: hours found by role and by kind of work, and what to stop doing first. Figures sit at the conservative end of what the interviews support, and yearly totals use 46 working weeks at 37.5 hours.
  3. 3. A build programme, if you want one. Whether to build anything is your call once you have the report. If you go ahead, we fix the biggest drains first across the systems you already run, with a person approving wherever judgement matters. Every fix is built to your security and IT requirements, then tested, handed over and signed off.

What a role-by-role view looks like

Illustrative example, with invented figures

A four-role team works 150 hours a week, and 20 of those hours go on admin that can come back. Over a year that is 920 hours, a little over half a working year.

Illustrative example, with invented figures: hours back a year, by role
RoleHours back a year
Finance administrator414
Operations coordinator276
Contracts administrator138
Reporting analyst92

The same report breaks each role down by kind of work. For the finance administrator in this example, 138 hours a year could come back from the weekly reporting pack, and 92 hours a year is work that can stop entirely.

What leaders plan with the findings

  • Grow before you hire. See how much more work the current team can take on before the next role is needed.
  • Fund the fixes with the most hours behind them. Every fix is ranked by the hours behind it.
  • Redesign roles on evidence. Each job description is checked against the work actually done.
  • Give the board one defensible number. Hours found, by role and kind of work, at the conservative end of what the interviews support.

It fits organisations planning growth, living with a hiring freeze or moving to a new operating model.

What the assessments have found

  • About 770 hours a year in a specialist insurer’s finance function, mostly on tools it already paid for.
  • About 870 hours a year across a marine insurance broker’s team: about half a working year.
  • About 780 hours a year in a recruitment team.

That is between about 110 and 290 hours a year for each person interviewed. Every team differs, and these are hours identified in interviews, not a forecast.

Yearly figures use 46 working weeks at 37.5 hours, about 1,700 hours. Results are hours identified in each assessment.

How this compares with what UK owners report: hours UK small businesses spend on admin, every source compared.

Not a headcount review

The hours go back to the team you already have, and it is not a performance review. If staff ask, tell them what it is: a look at where the admin goes, so the team gets time back. Interviews are confidential, role by role.

What it costs

The assessment is a fixed fee, set by the number of people interviewed and agreed before anything starts. Your proposal prices the build programme too, so you see the full cost before you commit. The fee for your team is quoted after a 20-minute call (how the Programme is priced).

Frequently asked questions

What is workforce capacity planning?
Working out how much work a team can take on with the people it has, and when it will need more. For admin-heavy teams, the part most plans miss is the time lost to repeated admin. The Workforce Capacity Programme measures that, role by role, so the plan starts from how the week is actually spent.
What is the difference between workforce capacity planning and a workforce capacity assessment?
The assessment is the measurement; the plan is what you decide with it. A workforce capacity assessment finds where a team’s hours go on repeated admin, through short, confidential interviews with the people doing the work, role by role. The leadership report then gives you hours found by role and kind of work, which you can plan growth, hiring or a new operating model around.
How do you measure recoverable hours role by role?
We interview everyone in the team in confidence, about an hour per person, and map where each hour goes and what is repeated. The report shows hours found by role and by kind of work, at the conservative end of what the interviews support. Yearly totals use 46 working weeks at 37.5 hours, so a working year is about 1,700 hours.
Is this a headcount review?
No. The hours go back to the existing team, and it is not a performance review. Interviews are confidential, role by role.
What does it cost, and what do you need from our IT team?
A fixed fee for the assessment, set by the number of people interviewed and quoted after a 20-minute call. Your proposal also prices the build programme, so you see the full cost of the path before you commit. The assessment needs nothing from your IT team: it is interviews, not system access.

Which team would you start with?

Tell us the team. In 20 minutes we’ll say whether it is the right one to start with, what the first report would show and what it would ask of your people.

Book a 20-minute call →

or email hello@hoursback.co.uk

Running an owner-led business where the hours are mostly yours? Start with the £799 Assessment.