AV integration and your network: where the in-house team’s job ends and the AV partner’s begins

The room was signed off in a drawing that showed a display, a table and a camera. Nobody wrote down which VLAN the devices would sit on, who would provision them, or what happens to a firmware update six months later.

It works on handover day. The questions arrive afterwards, usually from the person who owns the network and was not in the room when the AV was specified.

In a technology business this matters more than it does elsewhere, because the in-house team already runs a serious environment. They own the network, the Microsoft or Zoom tenancy, the identity setup and the security posture. AV integration has to sit alongside all of it without creating exceptions, and without generating work for people who have plenty already.

This article looks at where the boundary between the two jobs actually falls, the decisions that determine whether AV integration holds up, how hybrid meeting spaces change the requirement, and how one Liverpool studio approached it.

Table of Contents

• Two jobs that overlap in one room
• The decisions that determine whether it holds
• What hybrid working changed
• What this looks like in practice
• Agreeing the boundary before installation
• FAQs

Two jobs that overlap in one room

The clean version of the split is straightforward. The in-house team owns the infrastructure: network, tenancy, identity, security policy, and the standards everything else has to meet. The AV integrator owns the room: displays, audio, control, the physical install, and making the thing behave for the people using it.

The overlap is where the trouble sits. Room devices need addresses, policies and updates. Meeting platforms need accounts and licences. Someone has to own the moment a room fails, and it is rarely obvious from the contract whether that is a network fault or an AV fault.

Most disputes after handover are not technical disagreements. They are gaps where both parties assumed the other had it.

The decisions that determine whether it holds

An AV system integrator worth working with raises these before anything is installed, rather than discovering them on site.

For in-house technical teams, the points worth settling in writing:

• Device provisioning — how room devices are addressed, which network segment they sit on, and who configures them.
• Platform and licensing — which of Teams or Zoom is native to each room, who owns the room accounts and licences, and how meetings on the other platform are joined.
• Security posture — how room devices meet the standards applied to everything else, and what exceptions, if any, are being requested.
• Firmware and updates — who keeps devices current, and whether room health is visible centrally or discovered when someone complains.
• Support boundary — what the in-house team resolves, what the integrator resolves, and the response expectation attached to each.
• Documentation — a written specification and a short user guide, so a colleague can cover a room they have never worked in.

Settled properly, these produce a pattern that can be repeated in the next office. Left open, each room becomes a negotiation.

What hybrid working changed

Hybrid offices raised the standard rather than changing the equipment. When half the participants are remote, audio does most of the work, and a room that sounded acceptable to the people sitting in it can be quietly poor for everyone else.

It also changed the load, and technology offices feel that more than most. Open-plan floors with squads clustered together mean the small rooms get used constantly for stand-ups, pairing and one-to-ones, not just for scheduled calls. Distributed teams push the proportion of remote participants higher than the office headcount suggests. A hybrid workspace where three rooms behave differently produces a steady trickle of interruptions that would not have registered when calls were occasional.

There is also a hardware wrinkle specific to these businesses. Developer laptops are rarely uniform — different machines, different operating systems, different docking arrangements, often personal preference rather than a standard build. A room that only works cleanly with one configuration will fail for a good portion of the people trying to use it.

The practical implication is that audio and consistency deserve more attention than screen size, and that the room needs to work when it is full rather than when it is being demonstrated empty.

What this looks like in practice

Viewpoint’s project team worked with Firesprite, the Sony-owned video game developer, on a collaborative technical environment for its new Liverpool offices. A studio of developers is an unforgiving setting for this kind of work: the people using the rooms build technology themselves, run demanding infrastructure of their own, and notice immediately when something has been compromised to make an install easier.

The full Firesprite case study covers what was delivered.

Agreeing the boundary before installation

The cheapest moment to settle all of this is before anyone orders equipment. A short written agreement covering provisioning, platform ownership, updates, support and escalation removes most of the friction that otherwise surfaces months later.

It also changes how the relationship works. An integrator who expects to work alongside an in-house team, rather than hand over and withdraw, will ask different questions during design and leave better documentation behind. Where responsibility sits afterwards is worth deciding at the same time as the design, which is why the support and maintenance arrangement belongs in the initial conversation rather than the closing one.

Viewpoint AV works alongside in-house technical teams, taking the room without taking over the network — get in touch.

FAQs

What does AV integration actually involve?
Bringing room technology into line with the systems already running — network, meeting platform, identity and security — so that the room behaves as part of the environment rather than as a separate island. The physical install is the visible part; the integration work is mostly decisions about ownership and configuration.

What should an in-house team ask an AV system integrator before work starts?
How room devices will be provisioned and addressed, which platform is native to each room, who owns licences, how firmware is maintained, where the support boundary sits, and what documentation will be handed over.

Who is responsible when a meeting room fails — IT or the AV supplier?
Whichever was agreed in writing. Without that, it defaults to argument. The useful version specifies not just who fixes what, but the expected response time and how a fault gets raised from the room itself.

Do AV integrators need access to the corporate network?
Room devices generally need network connectivity, but the terms are negotiable and should be set by the in-house team’s standards rather than the integrator’s convenience. A supplier asking for broad exceptions is worth questioning.

What makes a hybrid meeting room work well?
Audio, mostly. Remote participants disengage quickly when they cannot hear clearly, so microphone coverage and acoustic treatment matter more than display size. Consistency between rooms comes second, because it determines whether people trust the space enough to book it.