Workplace capacity • 5 min read
Desk-sharing ratio benchmarks: 1.2:1, 1.5:1 and 2:1
Compare common desk-sharing ratios as capacity scenarios, then size the office from peak-day demand, usable desks, buffers, and team patterns.Quick answer
There is no universal best ratio
At 1.2:1, 120 employees share 100 usable desks; at 1.5:1, 150 share 100; at 2:1, 200 share 100. The higher ratio is safe only when credible peak attendance plus a visible buffer remains below usable capacity.
A practical framework
Work through the decision in a visible order.
Keep the ratio direction visible
For 100 people and 70 usable desks, employees per desk = 100 ÷ 70 = 1.43:1. Desks per employee = 70 ÷ 100 = 0.70, or 70%. Both describe the same inventory; an unlabeled “0.7 ratio” is ambiguous. State the numerator, denominator, location and date in the worksheet.
Then test the busiest day. If 75 people need those 70 desks, the shortage is five even if the weekly attendance average is only 50. Keep usable capacity separate from booked seats and measure walk-ins, no-shows and unavailable workstations before reducing inventory.
1.2:1
A conservative sharing scenario with roughly 83 desks per 100 employees. It can suit teams with frequent office use or uneven arrival patterns, but the peak-day test still matters.
1.5:1
A middle scenario with about 67 desks per 100 employees. Test whether team anchor days, visitors, specialist equipment, accessibility needs, and neighborhood preferences concentrate demand.
2:1
An aggressive scenario with 50 desks per 100 employees. It needs reliable staggering, strong reservation behavior, alternative work settings, and a rapid response when observed peaks exceed the model.
Choose from observed demand
Run a reversible pilot, publish the capacity rule, let people report shortages, and compare reservations with actual use. A ratio is a planning hypothesis, not a workplace promise.
Use reservations as evidence, not demand itself
Compare bookings with check-ins, no-shows, walk-ins, blocked desks, turn-aways, neighborhood switching, meeting-room pressure, and user reports. Reservation behavior can overstate or understate real need.
Worked example: a 2:1 ratio can still fail on Tuesday
A fictional office has 120 assigned people and 60 usable desks: a 2:1 people-to-desk ratio. Average daily attendance is 45, but an observed Tuesday peak is 68. On that day, demand exceeds the usable desks by eight. The ratio and average have not made the peak disappear. These are invented figures, not a recommended density or a measured benchmark.
If the same office plans around 1.5:1, the arithmetic suggests 80 desks. Whether 80 is suitable still depends on usable space, accessibility, team patterns, booking behavior and an agreed allowance for uncertainty. Keep headcount, desks and attendance measured over compatible periods. A ratio alone cannot establish that a workplace is safe, compliant or well designed.
Define usable capacity before dividing headcount
Count desks that can actually be assigned for the relevant work, including equipment and accessibility needs. Exclude unavailable workstations and record any shared rooms separately rather than treating every seat as an interchangeable desk. Name the date and location of the count, because a refurbishment or a broken work area can change the denominator.
Compare proposed team days with credible peak demand, not only with the building-wide average. A desk reservation is an expression of intent; it may differ from actual use. Keep the distinction visible in the planning record. Avoid collecting identifiable worker data merely because it is technically available when a less intrusive aggregate can answer the capacity question.
Write the fallback before reducing desk inventory
Specify what happens if demand exceeds capacity: an agreed overflow area, a different coordinated team day or a reservation process with a clear owner. Test the fallback before making an irreversible space decision. Include how people can raise equipment or access needs without putting private information in a public capacity sheet.
Review the decision after ordinary weeks and known peak events. Record unmet demand, unusable desks and the effect on collaboration rather than reporting only a lower desk count as success. The capacity planner below helps preserve assumptions and a review date. Ratio examples are arithmetic scenarios; use local facilities, accessibility and applicable legal advice for the actual workplace decision.
Action checklist
Before you consider the task complete
- Compare usable desks with credible peak demand and show any deficit explicitly.
- Agree an overflow process and review point before reducing the desk inventory.
- Count usable general-purpose desks, not installed desks.
- Estimate demand by weekday, team and location.
- Add a named operational buffer.
- Pilot reservations and record turn-aways or unused holds.
Common questions
Questions this guide should answer
Is 2:1 a safe desk-sharing benchmark?
It is a ratio, not a guarantee of adequate capacity. In the fictional example, 120 people and 60 desks produce 2:1, yet a 68-person peak exceeds capacity by eight. Assess usable capacity, actual demand and the workplace's other requirements.
Is a 2:1 desk-sharing ratio good?
Only when the busiest credible demand plus buffer fits within usable capacity and the pilot shows acceptable access. The headline ratio alone cannot answer that.
What counts as a usable desk?
A desk that is available to the measured population and fit for the intended task. Remove repairs, reserved specialist stations, inaccessible placements, and other unavailable inventory.
Should ratios be calculated for the whole company?
Usually calculate by location, weekday and population that can genuinely share the same desks. A portfolio average can hide a shortage in one office and surplus in another.
How much capacity buffer is needed?
There is no universal percentage. Choose and publish a buffer from demand variability, data quality, service level, special needs, growth, and the speed at which extra capacity can be restored.
How long should a desk-sharing pilot run?
Long enough to include representative weekdays, team events and normal variation, while remaining reversible. Avoid drawing a permanent conclusion from a launch week or holiday period.
Evidence and review notes
Primary references
Sources support the factual and safety context. The guide keeps interpretation and limitations visible rather than turning a reference into a universal personal rule.