Conference Room AV Diagram: Design and Document a UC Room

What is a conference room AV diagram?

A conference room AV diagram is a signal-flow drawing scoped to one UC space: a huddle room, a mid-size meeting room, or a boardroom. It shows every device that touches audio, video, or control, how each one connects, and which direction signal travels. It is the room-level version of the method in how to create an AV signal-flow diagram, applied to the pattern that repeats across a whole building of rooms.

UC rooms look simple from the doorway (a display, a camera, a table) and are deceptively tangled behind the wall plate. The same signal can leave a laptop as HDMI, cross the room as USB, and reach the far end over the network, all in one meeting. A diagram is how you keep those paths straight before the drywall closes, and how the next tech understands the room without reverse-engineering it live during a board meeting.

The canonical UC room signal chain

Almost every UC room, from a huddle space to a large boardroom, is a variation on one chain. Learn the chain and each room becomes a matter of scale, not a new puzzle:

• Camera, an all-in-one video bar, a single PTZ, or multiple cameras with tracking in larger rooms. Sends video to the codec or room PC.
• Microphones, integrated in the bar for small rooms, or table/ceiling mics through a DSP for larger ones. The single biggest driver of whether a room sounds good to the far end.
• Codec or room PC, the compute at the center: a dedicated UC appliance or a small-form-factor PC running the meeting platform. Everything upstream feeds it; everything downstream hangs off it.
• Display(s), one screen in small rooms, often two in medium and large rooms. Show far-end participants and shared content, and sometimes a local self-view.
• Room audio, the bar's own speakers in a huddle room, or ceiling/wall speakers driven by a DSP or amplifier in larger rooms.
• Control panel, a touch panel (often on the table) to join, share, and adjust the room without teaching anyone the underlying gear.
• Occupancy and network, room/occupancy sensors, plus the wired network that carries the meeting itself and, increasingly, the AV signals between devices.

Draw that chain sources-left to destinations-right, exactly as you would any signal flow: camera and mics on the left, the codec/PC at center, displays and speakers on the right, with control and network as their own lane underneath. See signal-flow best practices for the layout conventions that keep a room readable.

USB, HDMI, or network: which path carries what

The thing that makes modern UC rooms harder than legacy AV is that one room mixes three transport types, and the same signal can hop between them. Keep them distinct on the diagram, because they fail in different ways and get built by different trades:

• USB commonly carries the camera and microphone (and often room audio) between peripherals and the codec/PC. It is the backbone of most small and mid rooms. USB has real, short cable-length limits, so longer runs typically need active cables or extenders, check the peripheral and cable specs for the version you are using.
• HDMI typically handles local video: laptop content into a wall or table input, and the codec/PC out to the display(s). Like USB, passive HDMI has distance limits, and longer or in-wall runs are commonly extended over a balun or category cable, verify against the extender's rating.
• Network increasingly carries the meeting itself, control traffic, and, in larger designs, AV-over-IP or networked audio (for example Dante or AVB) between devices. This is where the room stops being self-contained and becomes part of the building's IT, which is why the network layer gets its own treatment below.

The content path and the camera path are not the same path

This is the single detail that trips people up in UC rooms, and it is worth its own section. A room with two displays and a content input has at least three distinct video paths, and they are easy to conflate on paper until the wall is open and one of them is missing:

• Camera to far end, the room's own camera into the codec/PC and out over the network. This is what the far side sees.
• Content in, a laptop or room source into the codec/PC so it can be shared to the far end and shown locally. This is the wall plate or table input people plug into.
• Codec to display(s), the meeting output to the screens: far-end participants on one display, shared content on the other, with roles that may swap depending on the platform.

The control and network layer

Half of a modern UC room lives on the network, so the network is part of the AV diagram, not a separate IT afterthought. Document it on the same drawing as the signal flow:

• Touch panel and control, the panel that drives the room, plus how it connects (commonly a single network cable that also delivers power over Ethernet). Show its port and its home on the switch.
• PoE, many room devices (touch panels, some cameras and mics, sensors) draw power over the same cable that carries their data. Total that draw against the switch's budget rather than assuming it fits, the method is in PoE budget planning.
• VLAN, UC rooms are usually placed on a dedicated AV or UC segment so meeting traffic and control gear are isolated from general corporate data. Note which VLAN each device lands on, see VLAN planning for AV systems.
• IP assignments, every networked device needs an address, and a room full of them needs a plan so nothing collides across a building of near-identical rooms. Track them in an IP schedule tied to the same project.

In WireFlow the network documentation (VLANs, IP assignments, PoE, switch and port mapping) lives on the same diagram as the AV signal flow, so the room is one source of truth instead of an AV drawing and a spreadsheet that quietly drift apart.

Room size to device set: a starting point

Room size drives the device set more than any other factor, mostly because acoustics and sightlines scale with the room, not with the budget. The table below is a common starting point for scoping, useful for a first pass and a rough bill of materials. It is not a specification: a hard-surfaced small room can need the mic treatment of a medium one, and platform choice moves everything.

Certified Zoom Rooms and Teams Rooms hardware

Most corporate UC rooms are built to run a specific platform, commonly Zoom Rooms or Microsoft Teams Rooms, and those platforms publish their own certified-hardware and room-design requirements. That certification is what determines whether a given camera, mic, or compute device is supported, and it changes over time.

The diagram is platform-agnostic on purpose: it captures how the room is wired and addressed, which stays true whichever platform runs on the compute. When the certified device list changes, you swap a device on the drawing and the derived documentation updates with it.

How to document the room port-to-port

A UC room diagram earns its keep when it is precise enough to build from without a phone call. Work through it in order:

1. Inventory every device that touches AV or the network: camera, mics, DSP, codec/PC, displays, speakers/amp, touch panel, occupancy sensor, network switch, and every wall plate, floor box, or table input.
2. Lay it out left to right, camera and mics into the codec/PC at center, out to displays and room audio, with control and network on a lane beneath.
3. Draw each connection port-to-port with its transport labeled (USB, HDMI, network, Dante/AVB, analog), never a vague line between two boxes, see connecting devices and ports.
4. Mark the display roles and the content input: which screen carries far-end participants, which carries shared content or self-view, and which plate the room source lands on.
5. Add the network layer: switch port for each device, its VLAN, its PoE draw, and its IP assignment, tied to the room's IP schedule.
6. Label every cable and plate with an ID that matches the physical label, so the drawing and the room agree, see port-to-port documentation.
7. Walk each path end-to-end before you call it done: camera to far end, far-end audio to the room speakers, content-in to the display and out to the far end, and the touch panel to the codec.

Because the documentation derives from the same diagram, the room's gear list and cable schedule stay consistent instead of being retyped into a spreadsheet that ages badly. When the room is one of twenty, that verified drawing becomes the template you stamp across the floor, and it rolls up into the project's AV tech pack for the install crew. You can start a room diagram free or explore the sample project to see a finished room documented end-to-end.

Frequently asked questions

What is the difference between a Zoom Room and a Teams Room diagram?

The AV diagram is nearly identical, because the room hardware (camera, mics, codec/PC, displays, control, network) follows the same signal chain regardless of platform. What differs is the compute device and its certified-hardware requirements, which come from the vendor. Draw the room the same way, then confirm the supported device list with the platform vendor for the deployment.

Do I really need a diagram for a small huddle room?

For one room, maybe not. For a floor of them, absolutely. The value of documenting a huddle room is that it becomes the standard you repeat, so twenty rooms get built identically and a tech who has never seen a specific room can still service it. The small rooms are exactly where undrawn deviations hide.

Where does the network fit on a conference room AV diagram?

On the same drawing, as its own lane. Modern UC rooms carry the meeting, control, and often the AV signals themselves over the network, so VLAN, PoE, switch ports, and IP assignments belong with the signal flow rather than in a separate IT document. Keeping them together is what prevents the AV drawing and the network plan from drifting apart.

How do I document a dual-display room without mixing up the screens?

Give each display an explicit role on the diagram (far-end participants, shared content, or self-view) and label the content-input plate separately from the camera path. The classic failure is two identical lines to two identical boxes labeled "Display," which passes a power-on test and then shows the wrong content on the wrong screen in the first real meeting.

Can one diagram cover a whole building of meeting rooms?

Document each standard room type once, then track per-room deviations (a different wall plate, an extra display, a room on its own VLAN). A project can hold the standard-room templates plus the specific instances, which is how you scope and build a floor of rooms without redrawing the same chain twenty times.

Build this diagram in WireFlow

Port-aware devices, validated connections, and exports your crew can read on site. Free plan includes three editable diagrams, no credit card.

Start a free diagram · Explore the sample show first