How it works
The idea borrows from computing: an operating system is the layer other tasks run on. In the workplace, that layer holds the records every tool needs: people and teams from the directory, buildings, floors and spaces, bookings, check-ins, and the plans that change them.
It runs as a loop. The operational side captures demand as a byproduct of people coordinating their week: bookings, check-ins, presence and visitors. The planning side turns that demand into stack plans, space plans and scenarios. When a plan is approved, the new neighborhoods and assignments go live in the same system people book from, and the next round of data measures the result.
Compared with a set of separate tools, nothing needs to be exported and re-keyed between steps. Compared with a traditional IWMS, the starting point differs: a workplace operating system starts from observed employee demand rather than from leases and drawings, and it connects to the IWMS, HR system and identity provider rather than replacing them.
Point solutions vs IWMS vs workplace operating system vs Work OS
The label is used loosely. These are the four things people usually mean, and how they differ.
| Approach | What it covers | Where the data lives | Watch for |
|---|---|---|---|
| Point solutions | One tool per job: desk booking, visitors, sensors, floor plans | In each tool, joined by exports | Data does not flow, so planning starts from spreadsheets |
| IWMS | Leases, space records, maintenance and assets | One system of record for supply | Weak on daily demand: who comes in, and when |
| Workplace operating system | Daily operations and space planning on shared people, space and presence data | One set of workplace data | Check that data really flows between modules, not just a shared login |
| Work OS | Project, task and workflow management for teams | Tasks, projects and workflows | A different category: it shares the name, not the purpose |
How to measure it
- Map each workplace decision (a restack, a lease renewal, a new team) to the data it needs, and check whether that data lives in one place.
- Count the manual handoffs between booking, analytics, planning and move execution.
- Check how long it takes for an approved plan to appear in the booking system people use every day.
Examples
- A company plans to merge two floors: it reads several weeks of attendance, models the stack in the same platform, and publishes the new neighborhoods to the booking app for the move date.
- A new team joins: HR data creates the people, the planner finds adjacent seats, and the employees book those seats on their first day.
Common mistakes
- Calling a bundle of separate apps an operating system when the data does not flow between them.
- Planning from headcount and org charts while booking and check-in data sits unused in another tool.
- Treating the platform as a replacement for the IWMS or HR system instead of connecting to them.
How Kadence helps
Kadence runs as two connected products. WorkOps runs the day to day: desk and room booking, visitors, team coordination, automatic check-in through Kadence Sense, and Workplace Insights. SpaceOps plans change on that data with stack planning, scenario planning, space planning to seat level and an AI planning agent. Approved plans are published back to WorkOps as live neighborhoods and assignments.
Workplace management software · WorkOps · SpaceOps · Kadence platform guide
Frequently asked questions
What is a workplace OS?
Workplace OS is short for workplace operating system: one platform that holds the shared data of the workplace (people, spaces, bookings, presence and plans) and runs both daily operations and space planning on it. The term signals that the tools are connected, not a set of separate apps.
What is the difference between a workplace operating system and an IWMS?
An IWMS is the system of record for leases, space, maintenance and assets. A workplace operating system starts from how people use the space, through bookings, check-ins and attendance, and uses that demand to plan and carry out change. Many enterprises run both and connect them.
Is a workplace operating system the same as hybrid work software?
Hybrid work software usually means booking and coordination tools for employees. A workplace operating system includes those and connects them to the planning side, so attendance and booking data feed stack plans, scenarios and moves, and approved plans flow back into the booking system.
Who uses a workplace operating system?
Employees use it to plan office days and book space. Workplace and facilities teams use it to run buildings and handle moves. Real estate and finance leaders use its data to decide which floors to keep, consolidate or change. IT connects it to identity, HR and calendar systems.
Related terms
- Workplace management system (WMS) Software that runs daily office use (desk and room booking, visitors, check-in, attendance) and reports how space is used.
- Integrated Workplace Management System (IWMS) Enterprise software that runs real estate, leases, space, maintenance and assets from one shared database.
- Agentic workplace A workplace where AI agents carry out tasks, such as booking space and drafting plans, with people approving decisions.
- Workplace operations (WorkOps) The day-to-day running of an office for the people in it: space, bookings, visitors, services, policies and the data they produce.
Kadence editorial team · Last reviewed