Badge data, calendar bookings, and Wi-Fi logs each give a clue about who's in your office. But on their own, none show what actually happened after people walked in. You end up with three partial views that don’t line up. Decisions about open hours, security, and café staffing turn into guesswork.
There’s a fix: layer these sources together. Add an office occupancy sensor as the real-use layer. Now, you get intent, entry, device presence, and real occupancy - all in one place. Arrival curves stop being estimates. They start being insights you can act on.
An arrival curve isn’t just a headcount. It shows exactly how load builds from opening, when it peaks, and how fast it tapers off. That shape matters for day-to-day operations. But each data source probably just captures one slice.
Badge systems record swipe-ins. Booking platforms measure which rooms and desks people planned to use. Wi-Fi analytics spot where devices show up. None of them truly tell you if a space was actually occupied, for how long, or what real load looked like hour by hour in each zone.
The gap between raw data and reality leads planning astray.
Most workplace teams already have access to four key data streams, or could. Each one answers a different question. Don’t treat any single source as the full answer.
Bookings reveal planned demand. For example, someone reserved a conference room for eight at 10 a.m. That’s good context, but it’s only intention. Industry no-show rates are 18% to 25%. Many reserved spaces sit empty while the system still shows them as used. Microsoft Places gets this right - it says room analytics reflect intended use, not actual use. Bookings show what people meant to do, not what they did.
Booking data is also where you’ll find ghost bookings. Recurring meetings nobody attends. Speculative room holds. These inflate demand on paper and hide where space is really needed.
Badge logs answer who entered and when. That helps you measure entry timing. But after the door, the trail ends.
Badge data can overstate occupancy by 15% to 20%. Tailgating, shared cards, and the simple fact that a swipe doesn’t show where someone went or for how long - it all adds up. Someone who badges in, grabs coffee, and leaves after 45 minutes looks the same as someone who spends eight hours. That’s the coffee badging problem. It skews your planning.
Wi-Fi access points spot device activity throughout the building. That makes them useful for big-picture trends. You can see when a floor gets busy, how long devices linger, and how traffic ebbs and flows through the week.
But Wi-Fi analytics track devices, not people. One person with a phone and a laptop shows up as two. If someone’s phone uses MAC randomization - a privacy default now - they might not show up at all. Even Cisco admits MAC randomization throws off headcount accuracy. Wi-Fi is great for floor trends, but not precise enough for room accuracy or dwell.
This is where things lock into place. An office occupancy sensor measures what happens inside a space - after entry. Occuspace sensors scan for Wi-Fi and Bluetooth signals from phones and laptops to count real-time crowd density. They don’t use cameras and never see faces. It’s anonymous, always.
In lobbies, sensors show real-time people flow, which entrances get jammed, and when traffic peaks. In meeting rooms and open areas, sensors measure true occupancy and dwell. Not just a booking, but real use. This is the layer that turns guesswork into clear arrival curves.
Weekly averages hide the reality of hybrid offices. CBRE’s 2025 Office Occupier Sentiment Survey says 73% of organizations hit capacity on peak days, but only 34% say the average reaches capacity. So averages lie. Plan off the average and you’re short on staff Tuesday and Wednesday, but overstaffed Monday and Friday.
Occuspace data shows it too: Tuesdays run at 80% capacity, Fridays drop to 30%. A portfolio might average 40%, then spike to 75% midweek. That’s normal for hybrid work. Arrival curves let you see it with clarity.
With arrival curves by hour and day, you can:
The goal isn’t to crown just one data source. You need to sync them all in one place so everyone sees the same story. Occuspace calls this a truth model. Bookings show the plan. Badge logs show who came in. Occupancy sensors show real use.
This works if you have a common space hierarchy: site, building, floor, zone, room. Add a shared time model, so an 8:47 a.m. badge-swipe matches a sensor reading and a booking. Otherwise, you’re comparing apples and oranges.
Aggregate the data by space and time - not by person. The question becomes, “What happened here between 9 and 11 a.m. Tuesday?” Not, “What did this person do?”
Use a layered model. Each source adds something:
The best approach maps all four to the same space layout and time blocks, then puts them into one dashboard. Definitions matter. No-show = booked, but no sensor activity. Dwell = time in space, confirmed by sensor. Peak occupancy = top sensor count in a window - not the highest booking.
Here’s what each data source gives you:
First, align times and locations. Every data stream needs the same room ID, floor, and timestamp. Build a dashboard that shows for any space and time window:
This gives you simple patterns:
Combining badge and sensor data lets you see what share of users stay less than two hours and which days that’s most common (spoiler: Mondays and Fridays). You get patterns, not personal tracking.
Microsoft Places even supports auto-release when no one checks in. Teams Panels can use occupancy data to show real-time usage. Bookings and live presence work together to automatically clean up ghost meetings.
Yes. You just need the right level of detail. For building-wide load, entry counts and Wi-Fi data show surges and occupancy patterns. For more detail by room or event, use occupancy sensors. They show what’s happening in the space, not just who came in.
Live occupancy feeds stream counts, capacity, and busyness into dashboards, APIs, or digital signage. One large tech company uses Occuspace data to optimize food service, reduce waste, and staff based on what’s happening right now.
Once you have real arrival curves by day and hour, midweek operations get much easier. You’ll see the actual Tuesday rush lasts three hours in the morning. The cafeteria peaks at 11 a.m., not noon. The lobby clears by 2 p.m.
Act on these facts:
Facilities teams using live data have been able to adjust hours, shift staffing, and tweak HVAC on the fly. That’s the value of a real arrival curve over a weekly average.
A smart office isn’t just booking software plus badge readers. It’s an operating model that blends access, occupancy, environmental data, and analytics. And it only works if people trust the system.
Badge systems need to be identity-linked for access. Occupancy sensors don’t. Anonymous, aggregate occupancy data answers “Is someone here?” - not “Who is here?” That’s key for trust and compliance. Anonymous counts usually fall outside GDPR and similar privacy laws, so deploying them is easier.
Wi-Fi analytics sit in the middle. Device identifiers plus MAC randomization mean more care is needed. Treat Wi-Fi presence as carefully as badge data. Keep it aggregate, limit retention, and never link to HR records.
Bottom line: measure spaces, not people. Aggregate by room or zone. Use 5 to 15 minute time blocks. Suppress counts under three. Arrival curves help you plan - they’re not surveillance.
Consistent metrics bring it all together. Here’s what matters:
Peak occupancy, average occupancy, and dwell time are the three biggies for cleaning, energy, and space planning. Track by weekday and hour. That’s when you get actionable patterns.
Layering data isn’t theory - it’s what works. Badge data alone misses the in-room story. Booking data alone plans for people who never show. But add occupancy sensing, and you get the real-use layer that makes everything else better.
The stacked approach with sensors, bookings, and badges creates one source of truth: what was booked, who showed up, what actually happened, and where the gaps are. That’s how you decide when to open, where to staff security, and how to plan for midweek café peaks. Weekly averages won’t show you the real picture.
If your data is all over the place, start by adding occupancy sensors to your trickiest spaces. Occuspace sensors go live fast - one or two days, no cabling, no cameras. Data starts flowing within minutes. Arrival curves follow right after.
What’s the best way to consolidate badge, Wi-Fi, and booking data to understand space usage? Use a layered model. Bookings show plans. Badges show entry timing. Wi-Fi catches broad presence. Occupancy sensors deliver real use and dwell. Map all sources to a common space and time model, and view results in a single dashboard with clear metrics.
How do you combine badge, sensor, and booking data for a single view? Align every stream to the same room ID and time. Build a dashboard that shows bookings, entry volume, occupancy, dwell, no-shows, and peaks for any space and time. The unified view reveals the gaps and what really happened.
Can you track event attendance and building load in real time? Yes. Entry counts and Wi-Fi show surges at the building level. Occupancy sensors tell the precise story for rooms and zones. Live dashboards or APIs display count, capacity, and busyness so you can adjust staffing and services on the fly.
