Divisible Meeting Rooms: What Must Change When the Wall Opens

Divisible meeting rooms are sold as two rooms when the partition is closed and one room when it opens. The wall can do that by itself. The audio, displays, cameras, controls, and conferencing paths cannot.

A good scope defines each room state before equipment is chosen. A Pueblo training center may need two private remote classes in the morning and one all-hands session after lunch. A Colorado Springs office may use each side as a boardroom until a quarterly meeting fills the entire space. Those are different signal paths, not just different furniture layouts.

Divisible meeting rooms need a real room state

The AV system needs to know whether each partition is open or closed. That input can come from a wall sensor, a deliberate control-panel command, or both. Q-SYS published a September 2026 partition-sensor note showing how an infrared wall sensor can feed room-combine logic.

Automatic sensing removes one step from the user's day, but the state cannot be invisible. Each control panel should show Separate or Combined in plain language. An authorized user also needs a documented way to correct the state if the wall stops halfway, the sensor is blocked, or maintenance leaves it out of alignment.

The state change should drive a tested set of behaviors. It is not enough to turn on more loudspeakers. Source selection, microphone routing, echo-cancellation references, camera choices, display content, volume controls, mute state, USB or room-compute connection, and control-panel authority may all change.

Biamp's room-combine guidance illustrates the same split: separated rooms operate independently, while combined mode can share audio, displays, volume, lighting, and control. The useful planning question is which functions your facility needs to share in each state.

Separated mode is where divisible meeting rooms earn trust

Start the design with the wall closed. Room A and Room B should behave like separate meeting rooms, even if they share a processor, rack, or network.

That means Room A's microphone cannot enter Room B's call. Room B's laptop cannot appear on Room A's display. A camera in one side cannot be selected by the other side. Each room needs its own volume, mute, source, camera, and conferencing controls. A shared technical backbone is fine. Accidental signal sharing is not.

Echo cancellation follows the same boundary. Biamp's multiple-room AEC guidance says each room's reference must contain the signals actually played from that room's loudspeakers. Feeding Room B call audio into Room A's reference when it is not playing in Room A asks the processor to cancel something that is not there.

This is also a privacy acceptance test. With the partition closed, place two different calls at the same time. Speak a distinctive phrase and share a different slide deck in each room. Confirm that neither audio, video, content, chat notification, nor control command crosses the wall through the AV system.

Combined mode needs one clear leader

When the wall opens, the facility needs to decide which side becomes primary. The primary room may own the active call, source selection, camera mode, record control, and master mute. The second panel can mirror approved controls or show a limited page. Two panels should not fight over different sources while everyone watches the displays change back and forth.

Combined volume should feel like one control while preserving the commissioned balance between loudspeaker zones. The far side of a long room may need a different calibrated level than the front. A master control should move those zones together without flattening their offsets.

Specify which displays show the presentation, remote participants, and any separate presenter view in each state.

The partition is only the trigger. The real room combine is a controlled change in who can hear, see, present, and command the system.

Two private calls require two real conferencing paths

If both sides must host independent hybrid meetings while divided, put that sentence in the requirements. Do not assume a divisible audio system automatically provides two laptop or room-compute connections.

Biamp's published two-way divisible-room example includes room-combiner processing but makes its USB conference interface available only in one partition while divided. That design is valid for its stated use. It would fail a facility that expected both sides to host separate USB calls.

Other reference designs use a conferencing path on each side, then select one primary system in combined mode. Zoom's ProAV divisible-space design uses the partition sensor to route audio and video and makes Room A the primary Zoom Room when the wall opens.

When more than one room device joins a combined meeting, audio ownership must be explicit. Microsoft's Coordinated Meetings guidance requires microphone audio to be enabled on only one coordinated Teams Rooms device to avoid echo and feedback. That primary device can receive several physical room microphones through the installed audio system. A second display or whiteboard device can join, but that does not make two active room-audio systems safe.

If either call may be confidential, stop or move the calls before the partition opens. The AV system should also keep electronic routes isolated, warn the user, and require a deliberate choice before one endpoint becomes primary. That interlock prevents signal crossover. It cannot preserve acoustic privacy after the physical wall is open.

Cameras and microphones change with the shape of the room

A camera framed for six seats in Room B may point at the back of an audience when the wall opens. A microphone placed for one furniture layout may miss a presenter standing where the partition was stored. The combined room needs its own camera shots, microphone coverage, and presentation positions.

Crestron's divisible-room example changes camera and microphone resources between independent and combined systems. The exact equipment is vendor-specific. The planning lesson is broader: every supported layout needs a defined view of the presenter, audience, whiteboard, and remote participants.

Mark the approved furniture layouts and test each with people seated or presenting in the actual positions.

Acoustics change too. Opening the wall increases room volume and listening distance, and may expose more reflective surfaces. A conference system that works in two smaller rooms does not automatically provide intelligible local reinforcement in the combined space. Measure and commission that use case rather than promising a microphone or processor will overcome the room.

Controls should explain the current room

A person walking in should be able to answer four questions from the control panel:

• Is the space Separate or Combined?
• Which room or endpoint owns the meeting?
• Which displays and loudspeaker zones will this control affect?
• How do I return to a safe state?

In separated mode, label controls by room. In combined mode, make the primary control obvious and either synchronize or limit the secondary panel. Preserve separate emergency power and life-safety behavior outside the meeting-room logic; a movable wall does not authorize an AV programmer to redefine those systems.

On reboot, the system should recover to a documented state. For facilities where conversations may be confidential, Separate is the safer default until the partition state is confirmed. If the sensor and software disagree, show the fault rather than silently routing signals across rooms.

Acceptance tests for divisible meeting rooms

Use authorized testers, dummy meetings, synthetic slides, and non-sensitive phrases. Do not use real confidential calls. Commission every supported state, including the awkward transitions:

1. Run two private calls with the wall closed and prove there is no audio, video, content, or control crossover.
2. Run two local presentations with different sources, volumes, and display content.
3. Combine from idle and verify the intended primary controller, meeting endpoint, displays, loudspeakers, microphones, and cameras.
4. Combine while one call is active and verify the documented handoff.
5. Open the wall during two dummy test calls and confirm the system does not bridge electronic routes without authorization.
6. Close the wall during a combined session and verify the expected result.
7. Block or fail the partition sensor, exercise the manual override, and clear the fault.
8. Reboot in both states and confirm that routing returns safely.

Include a far-end participant in the call tests. They should confirm speech from the normal seats, camera framing, shared content, and freedom from echo. Record the result by configuration, not as one generic “room passed” line.

Scope the behavior before the hardware

Our commercial AV design and installation service covers flexible spaces as a complete audio, video, control, and network problem. For rooms centered on remote meetings, start with conference room AV. GTZ also builds Q-SYS systems where room-combine logic, conferencing, cameras, audio, and user control need to live on one platform.

GTZ serves businesses and meeting facilities in Pueblo, Colorado Springs, and Fountain. Bring the floor plan and event schedule so the scope can name the room states and calls that must work.