Workplace Scenario Modeling: An Implementation Playbook

Workplace scenario modeling helps teams compare possible space decisions before committing money, time, or disruption. Instead of asking whether an office is “full,” operations leaders can test alternatives such as consolidating a floor, changing team neighborhoods, increasing shared seating, or adding collaboration space. The most reliable approach is to define a decision, build a baseline from trusted data, model a small set of realistic scenarios, and evaluate each one against capacity, cost, experience, and operational risk.

What workplace scenario modeling is designed to answer

Scenario modeling is a structured way to explore how a workplace might perform under different assumptions. It is not a prediction of exactly what employees will do. It is a decision tool that shows the likely effects of changing inputs such as attendance patterns, seat ratios, team assignments, room types, or usable area.

A useful model can help answer questions such as:

• How much space is needed if attendance varies by day or department?
• What happens if two teams need to work together more often?
• Can a floor be consolidated without creating peak-day shortages?
• Which areas should become assigned seating, shared desks, focus rooms, or meeting space?
• What capacity buffer is appropriate for visitors, growth, accessibility needs, and operational exceptions?

The goal is not to select the scenario with the most seats. It is to identify an option that supports the organization’s work patterns while remaining practical to operate.

Start with a decision, not a spreadsheet

Begin by writing the decision the model must support. A broad question such as “Do we have enough space?” usually produces an unfocused analysis. A stronger question defines the choice, time horizon, and constraints.

For example: “Can we consolidate two neighborhoods into one floor over the next 12 months while maintaining access to suitable desks, meeting rooms, and accessible work points on expected peak days?”

Document the following before collecting data:

• Decision: What will the model help leaders approve, reject, or investigate?
• Planning horizon: Is the scenario for the next quarter, lease cycle, or several years?
• Population: Which employees, contractors, visitors, or teams are included?
• Constraints: What cannot change, such as lease boundaries, accessibility requirements, security zones, or construction limits?
• Success measures: Which outcomes matter most, such as peak-day availability, adjacency, cost, or employee experience?

Build a trustworthy baseline

A scenario is only as useful as its baseline. Establish a shared starting point for people, space, demand, and operating rules. Avoid treating a single occupancy reading or a booking count as a complete picture.

Inventory the population

Separate employees by relevant attributes rather than using one company-wide headcount. Useful categories may include department, location, work pattern, role, shift, accessibility requirement, and collaboration needs. Record whether each figure is current headcount, planned hiring, or an assumption.

Describe the available space

Map usable areas and classify them consistently. Include assigned desks, shared desks, meeting rooms, focus areas, collaboration zones, support areas, circulation, amenities, and spaces that are unavailable or restricted. Confirm that the map reflects current conditions, not only the original plan.

For teams that need reliable spatial records, space management and scenario planning tools can provide a more maintainable foundation than disconnected floor plans and spreadsheets.

Measure demand from multiple signals

Combine booking activity, observed occupancy where appropriate, employee schedules, visitor patterns, meeting requirements, and qualitative feedback. Each source answers a different question. Bookings show intended use, observations show presence at a particular time, and feedback can reveal why an area is avoided or difficult to use.

Label data by date, source, and confidence. If a number is estimated, keep it visibly separate from a measured value. This prevents false precision from driving a high-cost decision.

Define assumptions and capacity rules

Capacity is not simply the number of desks divided by the number of employees. Define how the model treats peak demand, shared seating, meeting rooms, special-purpose spaces, and exceptions.

Common assumptions include:

• Expected attendance by day, team, or location
• Maximum practical desk-sharing ratio for different work types
• Minimum number of accessible and adjustable work points
• Required team adjacency or neighborhood boundaries
• Meeting-room demand by room size and technology requirement
• Space reserved for visitors, growth, facilities work, or temporary projects
• Rules for employees who require assigned seating or specialized equipment

Use ranges where uncertainty is material. A low, expected, and high demand case is often more useful than one supposedly exact attendance percentage. Record who owns each assumption and when it should be reviewed.

Model a small set of realistic scenarios

Resist the temptation to model every possible layout. Three to five scenarios are usually easier to explain and compare. Each should represent a real operating choice, not just a different number in a cell.

Useful scenario types include:

• Baseline: Continue operating the current footprint and rules.
• Operational improvement: Keep the footprint but change booking, neighborhood, or allocation rules.
• Consolidation: Reduce the active footprint while protecting critical capacity and adjacencies.
• Reconfiguration: Change the mix of desks, rooms, focus areas, and collaboration space.
• Growth or resilience case: Preserve additional capacity for hiring, demand spikes, or disruption.

Change one major variable at a time where possible. If a scenario reduces space, changes attendance assumptions, and removes assigned seating simultaneously, leaders may not understand which factor produced the result.

Compare scenarios with a decision framework

Do not rank scenarios on utilization alone. A space can appear efficient while creating long searches for suitable desks, poor team coordination, or insufficient meeting capacity. Compare each option using the same criteria and document tradeoffs.

Consider scoring or discussing:

• Capacity fit: Can the scenario support expected and peak demand?
• Team fit: Does it preserve important collaboration patterns and adjacencies?
• Experience: Can employees find suitable spaces without excessive friction?
• Inclusion: Does it support accessibility, privacy, focus, and different work styles?
• Cost and reversibility: What will implementation cost, and how difficult is it to undo?
• Operational complexity: Can workplace teams maintain the rules, maps, assignments, and communications?
• Data confidence: How much of the conclusion depends on uncertain assumptions?

A simple qualitative rating such as strong, acceptable, or weak is often more defensible than a made-up financial precision. If financial analysis is required, give Finance ownership of cost assumptions and clearly separate those figures from workplace demand estimates.

Turn the preferred scenario into an operating plan

Scenario selection is not the end of the work. Translate the preferred option into concrete changes that employees and operators can understand.

1. Define the future state: Confirm neighborhoods, seat types, rooms, capacity limits, and exceptions.
2. Assign ownership: Name owners for space records, employee assignments, booking rules, communications, and measurement.
3. Prepare systems: Update maps, resources, room details, permissions, and booking configurations.
4. Test with affected teams: Walk through representative workdays, including peak demand and accessibility needs.
5. Communicate the change: Explain what is changing, why it was selected, how to book or request space, and where to report problems.
6. Review after launch: Set a check-in date and compare actual demand, friction, and service requests with the scenario assumptions.

Connected workflows matter at this stage. For example, desk and resource booking can help translate a seating scenario into daily reservations, while workplace requests can capture issues that the model did not anticipate.

Use a repeatable review cycle

Workplace scenarios become outdated when hiring, attendance expectations, team structures, or lease conditions change. Establish a review cadence based on the decision’s risk. A major portfolio decision may need quarterly review, while a small neighborhood change may need a post-launch review and an annual refresh.

At each review, ask:

• Which assumptions changed?
• Where did actual demand exceed planned capacity?
• Which spaces were consistently avoided or difficult to access?
• Did employees follow the operating rules?
• Which requests or exceptions indicate a structural problem?
• What should be changed in the next scenario?

Keep prior scenarios and decisions together with their assumptions. This creates an audit trail and helps future teams understand why a choice was made, rather than rebuilding the analysis from memory.

FAQ: workplace scenario modeling

How is scenario modeling different from capacity planning?

Capacity planning establishes how much capacity may be required. Scenario modeling compares different ways to provide it. The two practices work together, but scenario modeling focuses more directly on choices, tradeoffs, and consequences.

How many scenarios should a workplace team create?

Start with three to five credible options, including the current state. Add another scenario only when it represents a meaningful decision or exposes an important risk. Too many options can make stakeholder review slower without improving the decision.

What should teams do when attendance data is incomplete?

Use the best available evidence, label its limitations, and model a range rather than hiding uncertainty. Improve data collection while treating the first model as a decision aid, not a claim of perfect precision.