Metric Definition
Used capacity versus available capacity
Track from
Workspace utilisation analysis
Workspace utilisation analysis is the study of how much of a workspace available capacity is actually put to use over a given period, expressed as a percentage. It applies to desks and meeting rooms, to billable hours on a team, and to compute or production capacity. The aim is to find slack you are paying for and bottlenecks you are not.
7 min read
What is workspace utilisation analysis?
Workspace utilisation analysis is the study of how much of a workspace available capacity is actually used over a period, expressed as a percentage of what was on offer. If a team has 40 desks and 24 are occupied on an average day, desk utilisation is 60 per cent. If a consulting team has 1,000 available hours in a week and bills 720 of them, utilisation is 72 per cent. The same logic applies to rooms, equipment and compute.
Utilisation matters because unused capacity is a cost you carry whether or not you use it. Rent, salaries and reserved infrastructure are paid in full regardless of how much gets consumed. Analysis turns a flat percentage into a decision: release space, rebalance work, or invest in more capacity because the slack has run out.
Higher is not always better
Utilisation near 100 per cent looks efficient but leaves no buffer. A team booked solid cannot absorb a spike, and a room always full cannot host an unplanned meeting. Read utilisation alongside the cost of being full at the wrong moment, not as a number to maximise.
How to calculate workspace utilisation analysis
Divide the capacity you actually used by the capacity that was available, then multiply by 100. The art is in defining both terms honestly. Available capacity should reflect realistic availability, not a theoretical maximum that ignores holidays, maintenance or non-working hours. Used capacity should count genuine use, not time merely booked and then left idle.
Worked example: a 12-person delivery team has a 480-hour week at full availability. Two people are on leave, removing 80 hours, so realistic available capacity is 400 hours. The team logs 320 productive hours. Utilisation is 320 divided by 400, which is 80 per cent. Measured against the theoretical 480 it would read 67 per cent, which would understate how stretched the team actually is.
- 1
Define available capacity
Set the realistic maximum for the period, net of leave, maintenance and non-working time.
- 2
Measure capacity used
Capture genuine consumption: occupied desks, billed hours, room minutes in use or compute consumed.
- 3
Choose the period
Fix a consistent window, such as a working week, so peaks and troughs are not hidden by averaging.
- 4
Divide and express as a percentage
Used over available, times 100, computed the same way every period for a comparable trend.
Workspace utilisation analysis in a metric tree
A single utilisation percentage hides why capacity sits idle or runs hot. To act on it you have to break the number into the things that move it: how much capacity exists, how demand arrives, and how well demand is matched to supply. A room at 40 per cent might be unbooked, or booked and abandoned, or simply the wrong size for the meetings people hold. Each cause has a different fix.
KPI Tree decomposes utilisation into these causal drivers so the analysis becomes a set of owned, fixable nodes rather than one figure on a dashboard. When utilisation drifts, the push goes to the accountable owner of the driver that moved, not to a generic facilities or operations inbox. That is the gap between a dashboard that reports a number and a system that turns the number into the next action.
Metric tree insight
Low utilisation rarely has one cause. Decomposing it separates a demand problem from a matching problem. Adding capacity when the real issue is idle gaps between bookings makes the percentage worse, not better.
Workspace utilisation analysis benchmarks
Healthy utilisation depends on what is being used and how costly it is to run short. Billable service teams target high figures because idle hours are lost revenue. Physical space targets lower figures because a buffer protects flexibility. Treat these ranges as starting points and adjust for how expensive a full or empty state is in your context.
| Workspace type | Healthy range | Notes |
|---|---|---|
| Billable team hours | 70 to 85 per cent | Above 85 risks burnout; below 70 erodes margin |
| Office desks | 60 to 80 per cent | Hybrid work pulls steady-state lower than pre-2020 norms |
| Meeting rooms | 40 to 60 per cent | Higher leaves no room for ad hoc or overrunning meetings |
| Compute or production | 65 to 80 per cent | Headroom absorbs spikes without provisioning for the peak |
How to improve workspace utilisation analysis
Improving utilisation means closing the gap between what you pay for and what you use, in whichever direction the analysis points. Sometimes that is lifting a low number by routing demand better. Sometimes it is relieving a number too high by adding capacity before something breaks. Work the driver, then confirm the headline followed.
Right-size capacity
Release desks, rooms or reserved compute that consistently sit idle, and add where the analysis shows sustained strain.
Smooth the demand curve
Shift flexible work off peaks and into troughs so the same capacity carries more without growing.
Cut idle gaps
Reduce no-shows and short unbooked windows between uses; recovered slivers often beat buying more capacity.
Verify the move worked
Re-measure after each change and confirm utilisation shifted toward the healthy range rather than past it.
Common mistakes when tracking workspace utilisation analysis
- 1
Using theoretical capacity
Measuring against a maximum that ignores leave and downtime understates how stretched a workspace really is.
- 2
Counting booked as used
A reserved desk or room that nobody turns up to is idle capacity, not utilisation.
- 3
Chasing 100 per cent
Pushing every workspace to full removes the buffer that absorbs spikes and protects flexibility.
- 4
Averaging away the peaks
A monthly average can read healthy while every Tuesday afternoon is gridlocked; analyse the distribution, not just the mean.
Related metrics
Cycle time
Process speed
Operations MetricsMetric Definition
Cycle Time = Process End Time − Process Start Time
Cycle time measures the total elapsed time from the start to the end of a process. It is a fundamental operations metric used in manufacturing, software development, service delivery, and any context where the speed of a process directly affects throughput, cost, and customer satisfaction.
Sprint velocity
Agile planning metric
Operations MetricsMetric Definition
Sprint Velocity = Sum of Story Points Completed in a Sprint
Sprint velocity measures the amount of work a team completes during a sprint, typically expressed in story points, ideal days, or another unit of estimation. It is a planning tool that helps agile teams forecast how much work they can commit to in future sprints based on their historical completion rate. Velocity is one of the most widely used and most frequently misunderstood metrics in agile software development.
Inventory turnover
Stock efficiency
Operations MetricsMetric Definition
Inventory Turnover = Cost of Goods Sold / Average Inventory
Inventory turnover measures how many times a business sells and replaces its inventory during a given period. It is a critical operations and finance metric that reveals how efficiently capital is being deployed in stock.
Employee turnover rate
Staff attrition
HR & People MetricsMetric Definition
Turnover Rate = (Separations / Average Headcount) × 100
Employee turnover rate measures the percentage of employees who leave an organisation during a given period. It is one of the most closely watched HR metrics because high turnover disrupts productivity, erodes institutional knowledge, and drives up recruitment and training costs.
Metric decomposition
Metric Definition
Workspace utilisation analysis becomes actionable when you decompose used capacity and available capacity into the drivers you can move.
Metric trees for operations teams
Metric Definition
Operations teams own capacity efficiency, so this guide shows where workspace utilisation analysis fits alongside the other levers they manage.
Turn a utilisation number into an action
Model workspace utilisation as a tree in KPI Tree, splitting the headline percentage into available capacity, demand and matching efficiency. Put a RACI owner on each driver so when utilisation drifts the right person is told, and the verified impact loop checks whether the fix moved the number back into a healthy range.