IT is called in to solve the problems. Not to prevent them
The hybrid meeting is won or lost on what IT owns: the network, the platform, identity management. Yet IT is the discipline that is routinely brought in last in the meeting room project, and engaged to fix problems that arose months earlier. This article explains what IT actually owns in a modern meeting room, what it costs when IT isn't involved at the right stage, and what IT needs to demand from the project in order to do its job.
The support cases start the day the room opens
The pattern is familiar. The room is delivered. The next day, IT's ticketing system is running: cables not connected, systems that won't come online, meetings that won't start. IT investigates and finds infrastructure problems built into the installation and furniture. Decisions about cable routes, outlets, and conduit were made months before IT even knew the project existed.
This isn't an accident. It's the normal result of a common setup. IT's role is defined retrospectively by what went wrong, not by what was planned correctly. Increased friction in meetings, late meeting starts, technology perceived as an obstacle. Operational disruptions that take time away from everything else.
And every compromise built into the installation phase is visible in the room, and in IT's ticketing system, for the next ten years.
What IT actually owns in a meeting room
The screen, camera, microphone — that is what the visitor sees. IT delivers what lies beneath the surface, and that is where the hybrid meeting is actually won or lost.
IT's ownership concerns four layers that must all be decided early:
Platform and standards determine which system controls the room: primary platform per room type, driver choice, and identity solution. The three are interconnected — one decision affects the others. If they are made separately, in the wrong order, or by the wrong person, rebuilding is a likely outcome.
Network and infrastructure means wired connection to every room unit and bandwidth planned for future needs — not just for today's systems, but for 4K cameras, AI tracking, and more connected devices per room.
Identity and access concerns how users are authenticated in the room. SSO in the room unit means that personal authentication occurs automatically. Without SSO, it is handled manually: 45–60 seconds per instance, every time it is required. Guest access needs to be defined and predictable, not an improvisation handled on-site.
Operations and lifecycle means that the room is monitored at the device level. "The room is offline" should generate an alarm, not a support ticket. The replacement cycle for AV equipment is typically four to six years — it needs to be planned from day one, not become a budget discussion when the equipment has already failed.
What it costs when IT isn't involved at the right stage — three concrete scenarios
Abstract risks are hard to argue against internally. These three are not abstract.
Scenario 1: Wrong platform locked in ten rooms
The interior architect specified Teams Rooms. IT runs Zoom. No one asked IT. The result is ten rooms with the wrong platform — and a renovation that wasn't in the budget. Platform choice, drive choice, and identity solution must be decided by IT in the program phase. Everything decided without IT at that stage risks needing to be redone.
Scenario 2: SSO missing — every meeting starts 45 seconds lat
In organisations where personal sign-in is required on the room unit, for security or compliance reasons, every user logs in manually without SSO. That takes 45–60 seconds per meeting. Multiplied by the number of rooms and the number of meetings per day, it adds up quickly — every day, in every room that lacks it. IT knew how to solve it. IT wasn't brought in.
Scenario 3: Bandwidth planned for today, not for four years from now
The next technology shift in four to six years requires more bandwidth: 4K video, AI tracking, more devices per room. No reserve was planned in the installation. Adding capacity afterward is not a software update, it means opening walls that have been closed.
IT's four decisions — and when they can be made at the latest las
It's not just about being involved early. It's about being involved at the right stage, with the right decisions on the table.
| Project phase | What IT needs to decide | What happens if IT misses it |
|---|---|---|
| Programme phase | Room types, platform choice, power and conduit requirements | No additional cost |
| System documentation | Infrastructure is integrated, platform choice is locked | Possible but costly |
| Construction documentation | Last chance for conduit and electrical | Possible but costly |
| Installation | Dead Zone 1 — changes require demolition | Very expensive |
| Move-in | Dead Zone 2 — visible and permanent compromises | Very expensive |
The most common mistake is to accept an invitation to a "status meeting" in the system- or construction document phase and call it IT involvement. By that time, most infrastructure decisions have already been made. IT's role at that stage is to confirm others people's decisions — not to make its own.
What IT should require from the project
It's reasonable to demand more than a late invitation. Here is what IT needs to have decided in the program phase — formulated as minimum requirements to bring to the next project meeting:
- Number of rooms and sizes
- Power requirements per room
- Data points and bandwidth — planned for future needs, not just today's
- Conduits to tables
- Cooling requirements for active equipment
- Reserve for future upgrades
IT should also require that each room type is defined against a network matrix before the specification is locked. Huddle rooms, meeting rooms, and boardrooms have different requirements — a one-size-fits-all solution is rarely correct.
One warning sign to react to immediately: if infrastructure is treated as a separate appendix outside the interior design documentation, that is a sign that IT's requirements aren't integrated into the project.
Bring the list to the first project meeting. Ask the questions. If the project cannot answer them in the program phase, that is the answer IT needs to hear.
When early IT involvement is actually not critical
It's reasonable to ask wether this always applies. The answer is no.
A small office with two standard rooms, an already approved platform, and a simple network solution without special requirements often manages with a late IT input. Provided that the installation follows a proven standard and nothing needs to be customized. In those cases, the risk is manageable.
What this article describes is a different kind of project: multiple rooms, mixed room types, SSO or compliance requirements, new infrastructure or a platform change. In those projects, early IT involvement is not a preference, it is a prerequisite.
If you are unsure about which category your project falls into, that in itself is a reason to be involved early.
The role of IT begins in the programme phase — not the installation phase
The role of IT in a meeting room project isn't to save the situation when the installation is complete. It's to be involved when decisions can still be made as a natural part of the project — in the programme phase, before the architect and interior design have locked in what then becomes impossible to change without intervention.
It doesn't require a larger mandate. It requires an earlier mandate.
Frequently asked questions
How early does IT need to be involved in a meeting room project?
In the programme phase — the only point in the project where IT's requirements can be integrated into the drawings without additional cost. That is when power, conduit, and future bandwidth needs must be specified. Everything decided without IT at that stage can still be corrected, but it will cost.
What does it cost to correct network infrastructure after moving in?
More than just doing it right from the start. A cable path that costs 2,000 kronor to lay during the construction phase can cost 15,000–25,000 kronor to fix after the walls have been closed — and that is before downtime, repainting, and re-inspection are factored in. IT's infrastructure decisions are not expensive to make in the programme phase. They are expensive to make in retrospect.
What does SSO mean for meeting rooms?
Single Sign-On (SSO) means the room unit recognises the user through the organisation's identity solution — Teams, Entra ID, Okta, or similar. Without SSO, every user logs in manually at every meeting. With SSO, the meeting starts immediately. The difference is 5 versus 45–60 seconds per meeting, multiplied across all meetings in all rooms every day.
What questions should IT ask a meeting room provider?
Three questions that reveal whether the provider understands IT's role: How do you handle platform choice and driver compatibility? How is conduit and wired connection resolved? What does IT need to provide for operations and lifecycle management?
Pendax Meeting Room Guide 2026 contains a 39-point checklist that covers the entire project timeline — including the specific IT decision points per project phase. If you are in an active project right now, the question is simple: which phase are you in, and does IT still have room to maneuver?
Are you in the middle of an active project and want to discuss where in the process IT still has room to maneuver? Contact us via email or phone.