.png)
Capacity forecasting mistakes usually come from treating a workplace scenario as a fixed headcount exercise instead of a set of assumptions that must be tested. The corrective action is to model demand, attendance patterns, space types, operating constraints, and uncertainty separately before making a portfolio decision.
A capacity model can look precise while still producing a weak recommendation. The problem is rarely the arithmetic alone. It is usually the connection between the question being asked, the data selected, and the assumptions made about how people use space.
Workplace teams often need to answer questions such as whether a floor can support a planned team, whether a lease can be reduced, or whether a new neighborhood mix will meet employee needs. Those questions require more than counting seats. They require a clear definition of demand, usable capacity, service levels, and the conditions under which the scenario should hold.
The mistake: Treating current assigned seating as a reliable proxy for future space demand. Assigned seats may reflect historical policy, legacy team structures, or an earlier attendance model. They do not necessarily show how often people are present, whether they need individual desks, or whether they need collaboration space.
The corrective action: Separate the population being modeled from the demand it creates. A scenario should identify expected attendance by day or work pattern, then translate that attendance into demand for desks, meeting rooms, focus areas, project space, support areas, and other relevant resources.
Use a range rather than a single attendance assumption when the organization is still learning how hybrid work is changing. A low, central, and high case can reveal whether a decision is resilient or only works under one optimistic forecast.
The mistake: Applying one utilization percentage across desks, conference rooms, phone rooms, training areas, and collaboration zones. Different resources serve different purposes and have different booking, attendance, and turnover patterns.
The corrective action: Model space types independently before reviewing the portfolio as a whole. A surplus of open desks does not solve a shortage of rooms with the right capacity, technology, acoustics, or location. Likewise, a room that appears underused in aggregate may be difficult to access during the periods that matter most.
Capacity planning should distinguish between physical capacity and usable capacity. Circulation, accessibility requirements, building constraints, furniture standards, safety considerations, and operational support can all reduce the amount of space that is practically available.
The mistake: Treating reservations as proof that a desk or room was occupied. Bookings show intent, but cancellations, no-shows, informal seat changes, and unrecorded use can all create a gap between planned and actual utilization.
The corrective action: Label each input according to what it measures. Booking data can help estimate demand and reservation behavior. Other signals, such as access data, occupancy observations, employee feedback, or workplace requests, may provide context about actual use. None should automatically be treated as a complete picture.
Where signals disagree, do not hide the disagreement by averaging them immediately. Investigate whether the difference reflects poor booking hygiene, unreliable sensors, access patterns that do not represent work time, or a genuine mismatch between planned and actual behavior. Tactic’s guidance on why office utilization data is often wrong is useful background for evaluating these gaps.
The mistake: Forecasting from weekly averages. An office may have comfortable average capacity while becoming difficult to use on particular days, during team gatherings, or when several groups need rooms at the same time.
The corrective action: Examine demand at the interval that matches the decision. Daily peaks may matter for desk supply. Hourly peaks may matter for meeting rooms. Seasonal peaks may matter for training, onboarding, project work, or workplace events.
Peak analysis does not mean designing every square foot for the most extreme possible day. It means making the tradeoff visible. A team can then decide whether to add capacity, improve scheduling, create overflow options, adjust attendance expectations, or accept a defined level of friction.
The mistake: Placing a future team into available capacity without testing who needs to sit near whom. A mathematically adequate floor can still fail if related teams are separated, shared resources are distant, or confidential work is placed in an unsuitable area.
The corrective action: Add workplace relationships to the scenario. Identify team neighborhoods, collaboration needs, visitor requirements, specialty equipment, accessibility needs, and areas that must remain flexible. Capacity is not only a quantity. It is also a question of location and suitability.
This is where a scenario model should connect to a current space record and map, rather than remain a spreadsheet of totals. Tactic’s space management, scenario planning, and forecasting capabilities are designed around that broader planning context, subject to the configuration and data available to each organization.
| Decision point | What to evaluate |
|---|---|
| Demand assumptions | Attendance patterns, peaks, and uncertainty are visible rather than reduced to one average. |
| Resource fit | Desks, rooms, specialty areas, and collaboration spaces are modeled according to their distinct purposes. |
| Workplace suitability | Team adjacency, location, accessibility, and operating constraints shape the scenario. |
| Evidence quality | Bookings are compared with other relevant signals and their limitations are documented. |
| Scenario resilience | The recommendation is tested against changed assumptions and has a defined review trigger. |
A useful scenario should make its assumptions easy to inspect. The following checks help distinguish a robust model from a precise-looking guess.
The mistake: Selecting a preferred scenario before testing how the recommendation changes when attendance, hiring, team mix, or room demand moves.
The corrective action: Vary the assumptions that could materially change the decision. Test different attendance patterns, growth rates, seat-sharing ratios, room demand levels, and timing assumptions. Record which variables have the greatest effect on the result.
Sensitivity testing is especially important when a decision is expensive or difficult to reverse. It can show that a small change in a high-impact assumption deserves more attention than a large change in a low-impact one.
The mistake: Publishing a scenario, approving a move or lease decision, and then allowing the model to age without a review point.
The corrective action: Define the signals that will trigger a refresh. These might include a material change in headcount, a recurring peak-day shortage, a change in attendance policy, a new business unit, or repeated workplace requests for a particular resource.
A forecast is more useful when it has an owner, a review cadence, and a record of assumptions. The goal is not to predict the future perfectly. It is to make decisions easier to revisit when evidence changes.
The mistake: Treating scenario planning as a facilities-only exercise. A capacity decision affects employees looking for a desk, managers coordinating attendance, facilities teams preparing space, and operations teams handling exceptions.
The corrective action: Connect the scenario to the workflows that reveal whether the plan works. Desk reservations, room bookings, employee feedback, visitor needs, and workplace requests can expose issues that a high-level capacity ratio misses. For example, repeated requests for a particular team area may indicate a planning problem even when total capacity appears sufficient.
A connected workplace management platform can help keep planning inputs and operational signals closer together. The Tactic workplace management platform brings together space planning with related workplace operations, while teams should still validate the quality and relevance of their own data.
A capacity forecast is ready when its purpose is explicit, its inputs are traceable, and its limitations are visible. Decision-makers should be able to see not only the recommended scenario, but also the assumptions that support it, the constraints that shape it, and the conditions that would make it worth revisiting.
The strongest model is not necessarily the most detailed one. It is the one that helps workplace, facilities, operations, and people leaders compare credible alternatives without confusing theoretical capacity with an effective employee experience.
Update it when material assumptions change, such as headcount, attendance patterns, organizational structure, space standards, or resource demand. A regular review cadence can help, but an event-based review is also important when a major change occurs.
No. Booking data can indicate demand and intent, but it may not represent attendance or actual use. Compare it with other relevant signals and document the limitations of each input.
Capacity is the theoretical amount of people or activity a space can support. Usable capacity accounts for location, furniture, accessibility, safety, room suitability, circulation, technology, operating rules, and the timing of demand.
