Facility Management Insights

You're probably seeing the same contradiction most facility teams see. Employees say they can't find meeting space. The booking system shows rooms fully reserved. Then you walk the floor and find half those rooms empty, workstations untouched, and a few overcrowded collaboration zones carrying the whole office.

That gap is where space utilization analysis earns its keep.

My first real utilization study wasn't about producing a polished dashboard. It was about ending circular debates. Leadership wanted to know whether the office was too big, too small, or just poorly configured. Department heads wanted more rooms. Finance wanted a reason to approve changes. Operations needed something more reliable than hallway opinions and screenshots from the booking platform.

A good utilization study gives you that. It shows how space is used over time, not just who happened to be sitting somewhere when someone looked. Beyond that, it helps turn raw observations into actions you can defend in a budget meeting, a lease discussion, or a workplace redesign conversation.

If you're still sorting through seating mix, collaboration demand, and hybrid attendance patterns, it also helps to learn office design and budgeting in parallel. The physical layout and the financial case always end up tied together.

From Anecdotes to Action with Space Utilization Analysis

Anecdotes create urgency, but they don't support capital requests or portfolio decisions. “We're always out of rooms” might be true for one team on one day. It doesn't tell you whether the issue is shortage, timing, room size, booking behavior, or bad rules in the reservation system.

That's why I treat space utilization analysis as an operations exercise first. It answers practical questions.

• Is the space in use: Not just booked, assigned, or theoretically available.
• Which settings carry the most demand: Open desks, enclosed offices, small rooms, training areas, touchdown spaces.
• Where are we paying for capacity we don't need: A large footprint can still feel constrained if the mix is wrong.
• What change would improve both cost and experience: Consolidation, repurposing, policy changes, or layout adjustments.

What the study usually reveals

The first surprise is often that the loudest complaint isn't the largest problem. Teams may complain about not finding a room, but the data often shows a more specific issue, such as too many oversized conference rooms and not enough small focus rooms.

The second surprise is that booking data alone can mislead you. Reservation systems show intent. They don't show whether a room was occupied, whether the room size matched the group, or whether people stayed for the full reservation.

Practical rule: If your utilization study can't lead to a staffing, budget, or layout decision, you're collecting interesting data instead of useful data.

That distinction matters. Executives rarely approve changes because a dashboard looks impressive. They approve changes when you connect utilization patterns to operating cost, employee friction, and space planning risk.

Defining Your Analysis Goals and KPIs

Most weak studies start with a vague brief. “We want to understand usage” sounds reasonable, but it creates messy data collection and even messier reporting. A better start is to decide what decision the analysis needs to support.

If you're refining broader workplace strategy at the same time, this companion guide to office space planning is useful because it connects utilization findings to layout choices.

Start with the decision, not the metric

I like to ask three questions before any data collection starts:

1. What business decision is pending
2. What would leadership approve if the evidence were clear
3. What would operations change immediately if the pattern were proven

Those questions usually place the study into one of three buckets.

Cost and footprint decisions

If finance is asking whether the portfolio is oversized, your KPIs should focus on efficiency and carrying cost. In practice, that means looking at whether occupied seats justify the amount of space being operated, cleaned, conditioned, and maintained.

Useful KPI themes include:

• Space utilization rate: Whether areas are used enough over time to justify keeping them as-is.
• Cost per occupied seat: Whether empty capacity is driving avoidable operating cost.
• Square feet per occupant: Whether the layout is oversized for actual attendance.

Employee experience decisions

If the problem is friction on the floor, the KPIs should show where the mismatch exists between demand and space type. A low overall utilization number can hide a very real shortage of the spaces people need.

Good experience-focused KPIs often include:

• Meeting-room occupancy: Are rooms used when reserved, and are the right room sizes available.
• Desk use by zone: Which neighborhoods support work well and which ones people avoid.
• Peak demand by time period: Where crowding or competition appears during the week.

Define success in operational terms

A KPI should lead directly to an action. If it doesn't, rewrite it.

Bad KPI: “Improve space efficiency.”

Better KPI framing:

• Reduce ghost bookings in shared rooms
• Identify underused areas for repurposing
• Validate whether current desk supply fits attendance patterns
• Support a right-sizing recommendation with before-and-after comparisons

The strongest KPI set is small. If you track everything, no one knows what deserves action.

I've found that four or five measures are usually enough for a first study. More than that, and stakeholders start arguing over methodology instead of confronting the result.

Match stakeholders to KPIs

Different leaders care about different consequences. Finance wants cost exposure. HR and workplace teams care about usability. Department leaders care about access. Real estate wants portfolio implications. Operations wants changes that can be implemented without months of disruption.

A practical setup looks like this:

Stakeholder	What they usually ask	KPI that answers it
Finance	Are we paying for empty capacity?	Cost per occupied seat
HR or workplace	Do people have the right settings for work?	Meeting-room occupancy, desk use by zone
Business leadership	Should we expand, hold, or reconfigure?	Space utilization rate, square feet per occupant
Facilities operations	What should we change first?	Utilization by space type and zone

Once those links are clear, your analysis becomes easier to defend. The study stops being “facilities data” and becomes an operating decision tool.

Choosing Your Data Collection Method

The collection method shapes the quality of the recommendation. I learned that early. Teams often choose tools based on what's easiest to pull, not what the decision requires. That leads to reports full of clean charts and weak conclusions.

For buildings already running integrated controls, a primer on building automation systems can help you spot where occupancy-related signals may already exist.

Industry guidance is clear that space utilization analysis should be built around a utilization rate measuring how much available space is used over time, and that teams should compare sensor data, booking data, and badge data because each source has different blind spots. It also notes that one week is often noise, four weeks starts to show patterns, and a full quarter is better for separating real trends from seasonal effects and team events, according to OfficeSpace's utilization analytics guidance.

Booking data works best for intent

Booking data is usually the easiest place to start. If you use Outlook room calendars, Microsoft Teams Rooms, Robin, Envoy, Condeco, or another reservation layer, you already have a record of what people planned to use.

That makes booking data useful for:

• spotting repeat no-show reservations
• identifying room sizes that are over-requested
• finding long reservations that don't match actual need
• seeing demand by day and time block

Its weakness is obvious on the floor. Booked doesn't mean occupied. It also doesn't tell you whether a room sat empty for most of the reserved period.

Sensors show actual use, but they add complexity

Desk sensors, room occupancy sensors, overhead people-counting systems, and broader IoT platforms give you better evidence of actual use over time. They're strong when you need confidence in room occupancy, peak demand patterns, or cleaning and HVAC alignment.

Their trade-offs are operational, not theoretical:

• you need installation planning
• facilities and IT usually need to coordinate
• someone has to own calibration, maintenance, and data governance
• privacy communication has to be handled carefully

If you can support that, sensors usually settle arguments faster than any manual process.

Sensor projects fail when the technology is sound but the purpose is fuzzy. Buy the measurement method that answers the decision already on the table.

Badge and access data helps with flow

Badge data can tell you when people enter the building or a secure zone. It's good for macro attendance patterns, arrival waves, and comparing daily presence against assigned capacity.

It's less useful for detailed room-level analysis unless your building has fine-grained access control. Even then, a badge swipe at the door doesn't confirm how long someone stayed or how many others joined them.

Manual observation still has a place

For a first study, I'm not against manual surveys. A clipboard, floor plan, and disciplined observation schedule can produce solid baseline insight, especially in a single site or pilot area.

Manual methods work when:

• you need a quick baseline before spending on tools
• the site is small enough to observe consistently
• you want to validate what your booking platform claims
• the budget won't support hardware yet

What doesn't work is pretending a casual walk-through counts as analysis. Manual observation only helps when the times, zones, and categories are defined in advance.

A practical selection guide

Method	Best for	Weak spot
Booking data	Reservation patterns and intent	Doesn't confirm actual occupancy
Sensors	Actual use over time	Requires implementation and governance
Badge data	Building entry and attendance flow	Limited room-level detail
Manual surveys	Baseline studies and validation	Labor-intensive and less continuous

The most reliable first study usually combines methods. Booking data tells you what should have happened. Sensors or observation tell you what did happen. Badge data adds context about attendance pressure at the building level.

Calculating and Benchmarking Key Utilization Metrics

Once the data is collected, the hard part isn't math. It's choosing calculations that mean something to leadership.

The baseline metric is utilization rate, which measures how much of the available time a space was used. That's different from occupancy, which is only a snapshot of who was present at one moment. A room can look “busy” because the calendar is full while still performing poorly over the course of a week.

A recent benchmark reported that global average utilization reached 53% in 2025, peak utilization averaged 80%, and most organizations target 65% or higher. The same benchmark uses a simple example: a meeting room booked for six hours but occupied for only two hours has a utilization rate of 33%, which is why ghost bookings distort demand if you only look at reservations, according to Skedda's comparison of utilization and occupancy.

The core formulas that matter

You don't need a long list of calculations. You need a short list that supports action.

Here's the set I'd use first:

Metric	Formula	Example
Utilization rate	Occupied time ÷ available time	A room used for part of the day versus all reservable hours
Desk utilization	Desks in use ÷ available desks	A workstation neighborhood compared against total available desks
Square feet per occupant	Total office square footage ÷ average daily occupancy	Total area divided by the people actually using it
Meeting-room occupancy	Occupied room time compared with reservable room time	Shared rooms measured over the analysis period

Sample Utilization Metric Calculations

How to read the numbers correctly

A low metric doesn't always mean failure. It may mean the wrong space type is in the wrong place.

For example, a low utilization rate in large conference rooms often pairs with high pressure on smaller rooms. That tells you the issue isn't a shortage of meeting space overall. It's a size mix problem. That's an easier recommendation to sell because it points toward repurposing rather than expansion.

If you need to support density or layout conversations, it also helps to understand how to measure square footage accurately, because small errors in area assumptions can distort the business case.

Don't benchmark one metric in isolation. A floor can show moderate average use and still suffer from bad peak-time congestion in specific space types.

A simple way to benchmark without overcomplicating it

I like to compare each space type against three questions:

1. Is it used enough over time to justify the footprint
2. Does demand cluster at predictable periods
3. Does the actual use match the intended design

That third question is where many layouts break down. A room designed for a large group may function like a small touchdown space. A bank of desks may be used mainly as bag-drop space while people work elsewhere. The metric is only the start. The interpretation creates the recommendation.

Ghost bookings deserve special attention

Ghost bookings are one of the easiest executive-level findings to explain because everyone has seen them. The room looks unavailable on the calendar. In reality, nobody uses it, or they use it briefly and leave it blocked for the rest of the reservation.

That finding usually supports practical changes such as:

• shorter default room reservations
• release rules for no-show bookings
• room-size guidance in booking tools
• conversion of oversized rooms into smaller, higher-demand settings

That's where utilization analysis stops being abstract. It starts correcting behavior, not just reporting it.

From Data to Decisions Reporting and Recommendations

A utilization study only creates value when the report makes the next move obvious.

I've seen technically solid studies go nowhere because the final deck buried the recommendation under heat maps, floor diagrams, and method notes. Executives usually need three things: what's happening, why it matters, and what action you recommend. If you can't state all three clearly, the work stalls.

A practical benchmark structure is to track space utilization rate, meeting-room occupancy, cost per occupied seat, and square feet per occupant, then rescan quarterly or biannually so before-and-after comparisons stay valid and support right-sizing and layout changes, based on Matterport's guidance on space utilization metrics.

Build the report around decisions

I don't start the executive summary with methodology. I start with mismatches.

Examples of useful findings:

• enclosed focus rooms are full while large conference rooms sit partly idle
• one neighborhood draws consistent use while another stays quiet
• reserved rooms show low actual occupancy compared with calendar demand
• attendance peaks create pressure on specific days, not throughout the week

Those findings become recommendations only when you attach a consequence.

Example recommendation logic

Observation	Operational meaning	Recommendation
Large rooms are lightly used	Room size doesn't match demand	Split one large room into smaller settings
Desk banks remain underused	Layout or location is unattractive	Repurpose part of the zone for alternate use
Peaks are concentrated by day	Capacity issue is timing-specific	Adjust team attendance norms or booking rules
Ghost bookings are common	Calendar demand is overstated	Tighten reservation policies and auto-release rules

Translate findings into budget language

Facilities teams often understate their own case by talking only about space. Leadership is deciding between uses of capital and operating dollars. Your recommendation needs to sound like a business decision, not a floor plan preference.

That means framing the output in terms such as:

• Avoided expansion pressure: If the issue is poor mix, don't ask for more square footage.
• Better return on existing space: Repurpose underused areas before requesting renovation elsewhere.
• Improved employee experience: Reduce the friction people feel when the wrong space types dominate the floor.
• Defensible sequencing: Start with policy changes, then low-cost reconfiguration, then capital work if needed.

A recommendation gets approved faster when you show that you've already ruled out the more expensive option.

Keep the visuals simple

For executives, I'd rather show one annotated floor plan and a short findings table than a dense dashboard with every metric you collected. The report should make patterns obvious:

• Use heat maps carefully: They're helpful when the colors highlight real contrast, not when every area looks mildly active.
• Group by space type: Desks, small rooms, large rooms, collaboration areas.
• Show before and after paths: Even if the “after” is still a proposal, map the intended effect clearly.
• Separate evidence from recommendation: Don't make people infer the conclusion.

A format that works in real meetings

A strong utilization presentation usually includes:

1. One-page summary: top findings and proposed actions
2. Evidence page: key metrics by space type or zone
3. Floor plan markup: what changes physically
4. Operational impact: cleaning, maintenance, booking policy, moves
5. Financial framing: where the recommendation protects or improves spend
6. Recheck plan: when you'll measure again and what success will look like

That last point matters. Recommendations land better when you present them as manageable experiments with follow-up measurement, not one-way bets.

Common Pitfalls and Your Analysis Checklist

Most bad studies don't fail because the formulas were wrong. They fail because the scope, timing, or communication was weak.

The most common mistake is collecting too little data and treating it like a trend. Short snapshots are tempting because they're fast, but a few unusual days can distort everything from desk demand to meeting patterns. Another mistake is relying on one source and calling it complete. Booking data alone, badge data alone, or a few walk-throughs alone will each leave blind spots.

Mistakes that create weak recommendations

Some problems show up over and over:

• Unclear purpose: The study collects data before anyone agrees on the decision it should support.
• Technology mismatch: Teams buy sensors when a manual baseline would've answered the immediate question, or they rely on manual counts when they need continuous evidence.
• No employee context: The numbers say a zone is underused, but nobody asks whether acoustics, location, furniture, or etiquette rules are driving avoidance.
• Poor privacy communication: Occupancy tracking triggers resistance when employees don't understand what is and isn't being measured.
• Reporting without action: The final output describes conditions but doesn't recommend changes in policy, layout, or operating practice.

If occupants think the study is about surveillance, cooperation drops fast. If they understand it's about fixing friction and waste, the conversation usually changes.

Use this checklist before you launch

I keep a short checklist for every utilization project. It prevents a lot of rework.

Pre-study checklist

• Decision identified: Lease question, redesign need, policy issue, or cost review.
• KPIs selected: Only the measures needed to support that decision.
• Space categories defined: Desks, rooms, touchdown areas, collaboration zones, support spaces.
• Collection method matched: Booking data, sensors, badge data, manual observation, or a mix.
• Study window set: Long enough to avoid one-off anomalies.

During-study checklist

• Observation rules documented: Same definitions across all observers and systems.
• Blind spots acknowledged: Know what each data source can't tell you.
• Occupant communication issued: Explain purpose, scope, and privacy boundaries.
• Early anomalies flagged: Don't wait until final reporting to notice obvious inconsistencies.

Reporting checklist

• Findings grouped by decision impact: Cost, employee experience, capacity, policy.
• Recommendations are specific: Convert, combine, release, repurpose, consolidate, or reschedule.
• Operational owners assigned: Someone has to implement each change.
• Re-measurement planned: Build in the next review so the study becomes a management cycle, not a one-time project.

A good checklist does more than organize tasks. It protects the credibility of the entire study. When leadership sees a clean line from goal to method to recommendation, the analysis stops looking experimental and starts looking investable.

---

If you want more practical facility guidance like this, follow Facility Management Insights for grounded articles on operations, planning, maintenance, and workplace decision-making.