How to Model Workplace Capacity Scenarios Before Making Space Decisions

Scenario modeling helps workplace teams test space decisions before committing money, construction time, or policy changes. Start by defining the decision, then establish a reliable baseline, create a small set of realistic scenarios, test each against demand and constraints, and document the assumptions behind the recommendation. The goal is not to predict the future perfectly. It is to understand how different attendance patterns, team requirements, and capacity choices perform under plausible conditions.

1. Define the workplace decision you need to make

A useful model begins with a decision, not a spreadsheet. Be specific about what leadership needs to choose and by when.

• How many workpoints should each location support?
• Should a team remain in assigned seating, move to shared seating, or use a hybrid model?
• Can an office support projected hiring without adding space?
• Which rooms, neighborhoods, or specialized areas are likely to become constraints?
• Would changing attendance policies improve service without requiring a footprint change?

Define the decision owner, planning horizon, locations in scope, and acceptable level of risk. A six-month seating decision may require a different model from a three-year lease or capital planning decision. Record the questions the model must answer before collecting data.

2. Establish a baseline from connected workplace data

The baseline describes how the workplace operates today. It should combine supply, demand, and actual usage wherever possible. Useful inputs may include workpoint counts, room types, team assignments, scheduled attendance, desk bookings, room reservations, occupancy observations, headcount, hiring plans, and known space restrictions.

Do not treat every available data point as equally reliable. A booking can indicate intent, while a check-in or observation may provide stronger evidence of actual use. Document the source, date range, coverage, and limitations of each input. If data is incomplete, state that clearly rather than presenting a precise-looking result.

Separate the following concepts in the baseline:

• Capacity: the number of people or activities a space can support under defined rules.
• Demand: the number of people or activities that may require the space.
• Utilization: how much of the available capacity is actually used over a specified period.
• Availability: what remains usable after restrictions such as closures, accessibility needs, security zones, or specialized equipment.

Tactic’s space management, scenario planning, and forecasting tools can provide a connected place to organize space records and evaluate planning assumptions. The specific fields and integrations used should still be validated against your operating environment.

3. Segment demand before applying averages

1. Step 1Define the decisionClarify the decision, planning horizon, locations, and risk tolerance.
2. Step 2Build the baselineCombine capacity, demand, utilization, and availability evidence.
3. Step 3Create scenariosModel three to five realistic operating choices with explicit assumptions.
4. Step 4Check constraintsTest peaks, specialized needs, team adjacency, and implementation effort.
5. Step 5Choose and monitorCompare criteria, stress-test the preferred option, and document triggers.

A single attendance average can hide the conditions that create workplace friction. Segment demand by location, day, team, floor, workpoint type, room type, and other factors that affect the decision. For example, a location may have spare desks overall but lack quiet workpoints, accessible seating, collaboration areas, or secure space for a particular team.

Look for patterns such as recurring peak days, team overlap, seasonal changes, onboarding waves, scheduled events, and dependencies between groups. If attendance is optional, distinguish planned presence from realized presence. If employees book desks in advance, examine both booking behavior and actual use when that evidence is available.

Segmentation should support a decision, not create unnecessary complexity. Include a variable only when it changes how a scenario should be evaluated or implemented.

4. Create a small set of plausible scenarios

Build scenarios that represent decisions the organization could realistically take. Avoid producing dozens of variations that make comparison difficult. Three to five scenarios are often enough for a focused decision, provided each has a clear operating model.

Examples include:

• Maintain the current footprint while improving allocation and booking rules.
• Increase shared workpoints for teams with compatible attendance patterns.
• Protect assigned or specialized areas while sharing general-purpose space.
• Consolidate underused areas and move affected teams into denser neighborhoods.
• Support planned growth within the existing footprint through phased changes.

For each scenario, define the assumptions that make it different. These may include expected attendance, hiring, team co-location, workpoint ratios, room demand, operating hours, policy changes, or the timing of a move. Keep assumptions explicit so stakeholders can challenge the model without confusing an input with a conclusion.

5. Test each scenario against constraints

A scenario is not viable simply because its total capacity exceeds projected headcount. Test it against the constraints that affect employee experience and operational delivery.

• Peak demand: Can the workplace support high-demand days, not just average days?
• Team adjacency: Can groups that need to collaborate work near one another?
• Specialized requirements: Are labs, secure areas, ergonomic setups, or equipment-heavy spaces protected?
• Accessibility and inclusion: Can employees access appropriate spaces without relying on informal exceptions?
• Meeting demand: Do room types, capacities, and booking patterns match how teams work?
• Operational effort: Can facilities and workplace teams administer the model consistently?
• Change impact: What moves, communications, technology updates, or policy changes are required?

Use both quantitative tests and operational review. A model can show sufficient seats while revealing an impractical daily experience, such as excessive desk hunting or repeated competition for a small number of rooms.

6. Compare scenarios using decision criteria

Choose comparison criteria before reviewing the results. This reduces the risk that stakeholders select the scenario with the most attractive single metric. Criteria may include capacity resilience, employee experience, cost exposure, implementation complexity, flexibility, team connectivity, and reversibility.

Not every criterion needs a numerical score. A qualitative rating such as low, medium, or high can be useful when the underlying evidence does not justify false precision. Explain what each rating means and identify which constraints are non-negotiable.

Separate model output from management judgment. The model may show that two scenarios fit within the same footprint. Leadership still needs to decide whether the additional change effort, employee impact, or risk is worthwhile.

7. Stress-test the preferred option

Before approving a scenario, test how it behaves when assumptions change. Increase or decrease expected attendance, delay hiring, add a team, remove a floor, or shift a high-demand day. The purpose is to find the point at which the plan becomes unacceptable.

Useful stress-test questions include:

• What happens if attendance concentrates on fewer days?
• How much growth can the plan absorb before service quality declines?
• Which space becomes constrained first?
• What temporary measure would protect operations if demand exceeds the forecast?
• Which assumptions should trigger a formal review?

Stress testing turns a recommendation into a management plan. It identifies leading indicators and gives the workplace team options before a capacity problem becomes an urgent disruption.

8. Convert the scenario into an operating plan

A scenario only creates value when people can operate it. Translate the selected model into clear actions, ownership, and timing. This may include updating space records, changing assignments, configuring booking rules, communicating team expectations, coordinating moves, and establishing a process for exceptions.

Define what will be measured after implementation. Depending on the decision, that could include peak utilization, booking-to-use patterns, room availability, request volume, employee feedback, or the frequency of exceptions. A connected workplace platform can help link these operational signals. For example, desk and resource booking can support visibility into planned use, while other sources may be needed to validate actual occupancy.

9. Set a review cycle and decision triggers

Forecasting is not a one-time approval exercise. Set a review date and define the evidence that would cause the plan to change. Triggers might include sustained peak-day pressure, a material headcount change, repeated requests for a scarce space type, a new business unit, or a shift in attendance behavior.

Keep a record of the original assumptions, the chosen scenario, the implementation date, and the evidence reviewed afterward. When actual conditions differ from the forecast, update the model rather than treating the variance as a failure. Over time, this creates a more useful planning history and improves the quality of future decisions.

Common questions about workplace scenario modeling

How far ahead should a workplace capacity model look?

Use a horizon that matches the decision. Near-term operating changes may require a few months of detail, while lease, construction, and portfolio decisions may require multiple years. If uncertainty grows with time, use scenarios rather than one long-range forecast.

What if utilization data is incomplete?

Start with the best available evidence, label its limitations, and combine sources where appropriate. Use the model to identify what information would most improve the decision. Do not imply that estimates are observed facts.

Who should review the scenarios?

Include workplace or facilities leaders, people or employee experience partners, finance, IT when technology dependencies matter, and representatives from affected teams. The right group depends on the decision, but operational feasibility should be reviewed alongside financial and space metrics.