Key Takeaways
- Facilities teams are already stretched before a single new system gets added. SFG20's State of Facilities Management 2026 report found that 51% of organisations report a shortage of FM staff, with teams becoming increasingly overstretched.
- IT is under comparable pressure. SysAid's State of Service Management 2026 survey found that 43% of IT professionals are currently dealing with burnout tied directly to workload.
- The fix isn't a vague principle about "clear ownership." It's a specific breakdown of which tasks belong to which team, written down and checked regularly.
Ask an IT director, a facilities manager, and an HR lead who should own a new meeting room booking system, and the honest answer from each of them is often some version of "not entirely me." Every one of these teams is already carrying more than their headcount was built for, which makes taking on full responsibility for a system that spans security, hardware, and employee experience a genuinely heavy ask.
Most advice on this stops at "define clear ownership" without saying what that actually looks like day to day. This article goes further: a specific breakdown of which tasks belong to IT, which belong to Facilities, and which belong to HR when the company wants to acquire workplace management tools.
Why Does No One Want to Own Workplace Technology Alone?
No one wants to own workplace technology alone because full ownership means absorbing tasks that stretch well outside a single team's expertise, on top of a workload that's already full. A hot desk booking app going down during peak hours is a good example of the problem: is that an IT support ticket, a Facilities hardware fault, or an HR complaint about staff being unable to work? In most companies, the honest answer is whichever team happens to pick up the phone first.
That default pattern is hard to sustain given how stretched every team already is. SFG20's State of Facilities Management 2026 report found that 51% of organisations report a shortage of FM staff, and SysAid's 2026 survey found that 43% of IT professionals are dealing with burnout tied to workload. Adding an unscoped system on top of either number is a significant ask.
What Role Should IT Play in Managing Workspace Technology?
IT should own the technical layer: the parts of a system that touch the network, security, and data. In practice, for something like a room booking or hot desking platform, that means:
- Setting up single sign-on so employees log in with existing company credentials
- Pushing firmware and software updates on a set schedule
- Deactivating access the day an employee leaves
- Integrating the solution with the company’s calendar
It does not mean IT decides the hot desk booking policy or approves the welcome message on a tablet's screen. Those decisions sit outside what IT is equipped, or has time, to weigh in on.
What Role Should Facilities Play in Managing Workspace Technology?
Facilities should own the physical layer: everything that involves the hardware itself and the space it sits in. For a room booking or desk system, that typically covers:
- Mounting the tablet or sensor and running power to it
- Negotiating the vendor's repair and replacement turnaround
- Keeping spare hardware on hand for a cracked screen or dead battery
- Folding the system into space planning when desk counts or floor layouts change
- Technical Support for employees
It does not mean Facilities decides what data the booking system collects, or which network segment it sits on. Those are IT's calls to make.
What Role Should HR Play in Managing Workspace Technology?
HR should own the experience layer: how the system feels to use and whether it's fair. For booking technology, that usually means:
- Writing the actual policy, such as how long someone can hold a desk and what happens after a no-show
- Covering the system in new hire onboarding
- Checking the booking app works for employees using screen readers or other assistive technology
- Handling complaints when a policy needs adjusting because it isn't working for part of the team
It does not mean HR owns server uptime or vendor contract terms. Gartner's finding that 75% of managers feel overwhelmed by the growth in their responsibilities is worth keeping in mind here: HR's list is already long enough without adding those two on top.
How Do You Divide Ownership So No Single Team Carries It All?
You divide ownership by working through four concrete steps, not by agreeing to a vague principle and hoping it holds. Here's what that looks like in practice.
Step 1: List every workplace system you currently run. Room booking, hot desking, badge access, digital signage, whatever exists today.
Step 2: Split each system's tasks into the three functions below, not by department instinct.
| Function |
Typical tasks |
Usual owner |
| Security & integration |
Login setup, network segmentation, firmware updates, access deactivation |
IT |
| Hardware & vendors |
Installation, repairs, spare stock, space planning, technical support |
Facilities |
| Experience & policy |
Usage rules, onboarding, accessibility, complaint handling |
HR |
Step 3: Assign one named person per function per system, not a team name. "Facilities" is not an owner. A specific person on that team is.
Step 4: Put the whole list on one page everyone can see, and review it every quarter. A shared spreadsheet or dashboard is enough. The point is that anyone can check who owns what without asking around.
How the right vendors can help divide ownership across teams
Teams can log in to the Door Tablet Admin Console using the credentials they already have, so IT doesn’t need to build a separate access system for one tool. All three teams then work from a single console, with role-based permissions giving each department control over its own area without full administrative access.
- IT manages the technical side: calendar integrations (Microsoft 365, Google Workspace, Exchange), device management, software updates and system configuration.
- Facilities sets room profiles and booking rules, and uses real-time utilisation, active meetings and check-in status to catch ghost or no-show bookings before they waste a room.
- HR and Internal Communications manage employee-facing content, including display branding, welcome messages and slideshows, for a consistent workplace experience.
What Happens When No One Wants to Own Workplace Technology?
When no one owns workplace technology, small maintenance tasks get skipped until they turn into real problems. A tablet that never gets a firmware update for a year is a common example: it keeps working day to day, until a security review flags it as an unpatched device on the network, and by then it's a bigger fix than a routine update would have been.
This is the practical cost of the staffing pressures already mentioned. A facilities team short-staffed by half, or an IT team already near burnout, has little spare capacity to notice a slow-building problem on a system nobody formally owns. The fix usually lands on whoever happens to be free when it finally breaks, rather than on whoever was best placed to prevent it.
FAQ's
How often should technology ownership be reviewed?
A quarterly review works well for most companies, matching the same cadence as the four-column ownership list described above. Faster growing companies, or those adding new systems frequently, may benefit from reviewing more often.
What's the first step if our company has never formally divided ownership?
Start with Step 1 from this article: list every workplace system you currently run, then work through the table to see which tasks have no named owner at all. That gap list is usually the clearest place to start.
Can one department own workplace technology alone?
It's technically possible, but it usually means asking one already-stretched team to absorb a workload it doesn't have the capacity for. Dividing ownership by function, using the table above, is what keeps a single department from quietly bearing all of it.
What's the biggest sign that ownership isn't working?
A rise in neglect is usually the clearest signal: a system nobody's checked on in months because every team assumed someone else was handling it. That pattern almost always points back to a missing name in the owner column, not a difficult team to work with.