Ready for the agreed tests
The tested equipment is installed, the required source files and access are available, and both local and remote participants can attend. Use the agreed room modes and acceptance criteria to carry out the scheduled checks.
Wirewolf / Remote AV support / Commissioning checklist
For a scoped session with the site team
Remote AV commissioning checklist
Prepare the people, system and evidence needed to test a room remotely. Wirewolf helps coordinate the session, test the agreed workflows and document the results.
Wirewolf Installations · September 11, 2026 · Call or email to plan your session
Before the session
Define what this visit can prove
Remote commissioning combines configuration work with checks made by someone in the room. A connected processor or a moving audio meter proves only part of the path. Testing the user experience needs the actual source, destination, control interface and the people who can observe the result.
This guide is for an agreed scope approaching site testing. If you are requesting an initial estimate, send us a short project description. You can identify readiness gaps before every detail of the installation is complete.
Readiness decision
Choose the right kind of session
Ready for a limited session
Some dependencies are missing, but a defined subset can still be checked. For example, review control feedback and display routing while conferencing tests wait for the room PC. Name the excluded tests before starting and retain their Not tested status.
Resolve the access or installation gap
If the required equipment cannot be reached, a physical fault prevents the test, or nobody can observe the in-room result, assign the missing action and its owner. Reschedule the affected checks instead of reporting full room acceptance.
Keep the decision in the record
Note the room, planned test scope, current drawing and software revisions, date and timezone, participants and known exceptions. The readiness record is a shared planning tool, not proof that the system has passed.
Preparation
Six things to settle before connecting
The installed equipment and drawing agree
Confirm device models, port assignments and cable labels for the paths under test. Mark substitutions and missing equipment on the current drawing. For retained amplifiers and speakers, obtain the details needed to review the output configuration before changing it.
There is a usable starting configuration
Record the software and firmware versions, editable project files and configuration backups. Identify the current deployed revision and how the responsible technician would restore it. Do not treat an unverified old file as a tested recovery package.
IT has agreed the access and change window
Confirm the approved remote-access method, permitted actions and who can authorize interruptions. Check access to the specific systems in scope. Include the site timezone and a route to reach the local technician if the remote session drops. Share credentials only through the access method agreed with customer IT.
The right people can see and hear the result
Have a technician in the room for cable, display, listening and camera checks. Arrange a separate far-end caller for conferencing tests. Identify which participant records each observation. The programmer's screen share cannot confirm what every speaker zone or remote participant is hearing.
Test sources match the requested workflows
Bring the room PC, representative guest laptop, relevant adapters and the agreed conferencing application. Test the room-PC and guest-laptop paths separately when both are in scope. Prepare suitable presentation content and the camera positions needed for the agreed checks.
The room is available for a realistic test
Confirm physical access and the time available. Record conditions that affect the result, such as building work or unusual background noise. Define the participant positions and operating levels used for speech tests. Agree any disruptive recovery tests in advance, with a local recovery path.
During the session
Test the complete path in each direction
Conferencing audio
Test room speech reaching the far end and far-end speech reaching the room as separate observations. Then check a natural conversation with both sides speaking. Record who hears echo, clipped words, noise or distortion, at which seats and settings.
AEC and local microphone reinforcement solve different problems. Biamp notes that conferencing AEC does not correct local acoustic feedback or poor room acoustics. Use the Biamp commissioning guide for platform-specific setup.
Video and USB paths
For every required host and room mode, confirm the selected camera, microphone and speaker devices in the actual application. Check the intended display destination and image, then the return to the normal room state. A successful presentation does not automatically verify guest-laptop conferencing.
Local speech and playback
Check local microphones and playback in the agreed speaker zones. Record the selected source, volume and mute state. If different displays show different sources, explicitly verify which source is heard. Keep local reinforcement results separate from the far-end call results.
Control and recovery
Compare panel indication with the actual device state. Verify the scoped startup, shutdown and room-mode transitions. Carry out approved recovery scenarios only when the team can restore the system, then repeat the affected user workflow. Unsupported or postponed scenarios stay open.
A symptom is not its cause. For example, Q-SYS lists multiple possible paths behind far-end echo in its AEC troubleshooting guidance. Record the observation before selecting a corrective change. This checklist does not prescribe a universal gain, limiter or AEC setting.
Clear results
Know what passed and what needs attention
Wirewolf documents the agreed checks, observations and open items as part of the scoped commissioning work. Each result identifies the room and signal path, so the next step is clear. Checks that could not be completed remain marked as not tested.
Close the session clearly
Leave the next team a usable record
Summarize the tests completed, exceptions, configuration changes and open items with owners. Identify the delivered file revisions and any later retest. A partial session can still be useful when its limits are documented.
Wirewolf provides scheduled remote AV support and design and commissioning support across Canada and worldwide by agreement. Call or email with a short description of the room and your preferred schedule. We will identify what is needed to plan the session.
The session report records the tests completed. It does not replace project-specific acceptance criteria or establish compliance with a certification standard.