AV Acceptance Test Sheet: Pass Criteria by Signal Path

An AV acceptance test proves that every signal path, control action and failure behaviour in the contract works as specified, with a measurable pass criterion and a recorded result. A walk-through where someone presses a few buttons is a demonstration, not an acceptance test, and it leaves the operator to find the faults.

This sheet is written by Singapore-based AV and IPTV integrator Prestige Solutions for AV consultants and technical managers who sign off AV control and signal routing in multi-purpose venues. It lists what to test, how to pass it, what evidence to keep and which failures should block handover. Thresholds are planning values as of 2026; where a device data sheet or the project specification sets a stricter figure, that figure wins.

What does an acceptance test need before it starts?

It needs a frozen configuration, a signed test list and the right instruments. Testing against a system that is still being tuned produces results nobody can compare later.

• Frozen configuration: export the routing, DSP and control programme versions and note the firmware of every endpoint, switch and processor. Any change after testing starts means the affected tests are repeated.
• Test list from the specification: each line cites the clause it proves. A test without a clause either belongs in the specification or does not belong in the sheet.
• Instruments: a signal generator or test-pattern source, an SPL meter, a multimeter, a laptop with the control system's diagnostic tools, and a timer. Record instrument model and calibration date in the sheet.
• Witnesses: the integrator runs the test, the consultant or client representative witnesses and initials each line.

Which video tests prove the signal paths?

Test every source to every destination that the routing matrix allows, plus the combinations that matter most to the operator. A matrix with 8 sources and 6 displays has 48 crosspoints; testing only the ones used on the demonstration day leaves most of the system untested.

For AV-over-IP systems, add the network side: confirm multicast group membership on the switch, check that the bandwidth per stream matches the design and that no switch port shows discards while all streams run. A path that works on an idle network and fails when the full set of streams runs is a common handover surprise.

How do you pass the audio tests?

Audio passes when levels, polarity, coverage and noise all meet the sheet's figures at the listening positions, not at the rack. A meter reading in the equipment room tells you nothing about what the audience hears.

The level plan these tests check against is described in the multi-zone gain structure note. If that sheet does not exist, the audio tests have nothing to prove against, and the consultant should hold the audio line open.

What control tests catch the faults operators actually meet?

Control tests should replay the operator's real day: start-up, source selection, volume, room combining and shutdown, with the wrong button pressed as often as the right one. Faults in control logic show up in sequences and in states, rarely in a single button press.

• Start-up and shutdown: from a cold, powered-off room, one press brings up displays, DSP and sources in the specified order and time. Shutdown leaves nothing powered that should be off.
• Feedback accuracy: the panel's reported state (input, volume, mute, power) matches the real device after each action, including after someone changes the device by hand.
• Third-party device control: every device driven over RS-232, IP or vendor API reports a response to each command; test with the network cable pulled and confirm the panel shows a fault rather than a false "on" state.
• Room combining: open and close each partition state, confirm the preset recalls and the combined room takes the correct source and level. The sensor logic is covered in more detail in the touch panel integration note.
• Wrong-order use: press source select during start-up, mute during switching, and power off while a source is playing. The system should settle in a valid state without a reboot.
• Access levels: an operator login cannot reach installer pages, and the installer password is changed from the default and recorded in the handover pack through the client's own process.

Which failure tests should be done before handover?

Test the failures that the design claims to survive. If the specification promises a fallback, an uninterrupted feed or a clean recovery, then pulling the plug is the only honest way to confirm it.

What should block handover?

Block handover when any test that proves a contract requirement fails, and agree a short written list of minor items that can be completed after handover. Everything else turns into an argument six months later.

1. Blocking: any path that fails the crosspoint sweep, any control sequence that needs a reboot to recover, uncorrected feedback or hum, and any failure test that does not meet the specified behaviour.
2. Minor with a date: label corrections, cosmetic panel text and documentation gaps, each with an owner and a completion date.
3. Handover pack: signed test sheet, as-built drawings, configuration exports and the version list, the gain sheet, the control programme source or escrow arrangement as per the contract, equipment list with serial numbers and the operator quick guide.
4. Operator training record: names, date and the tasks each person has performed themselves, not only watched.

FAQ

How long should an acceptance test take for a typical meeting room?

Plan roughly half a day for a standard room with a single matrix, a DSP and one control panel, and more for divisible or networked venues where every combination needs repeating. Compressing the schedule is the usual reason tests get skipped, so it is better to book the time in the project programme than to squeeze it into the last hour.

Who should hold the signed sheet?

Both parties. The client keeps the original with the handover pack, and the integrator keeps a copy with the project record. A later fault can then be compared against what the system did on the day it was accepted.

Can part of the test be repeated remotely after handover?

Control and network checks can often be repeated through the control system's diagnostics, which is useful after firmware updates. Audio coverage, display quality and physical failure tests still need someone in the room with the instruments.

Visit Prestige Solutions for the wider AV and IPTV service range.

Recommended next step

Contact Prestige Solutions to review your site drawings and current operating pattern. Call +65 8010 2337 or +65 9825 8218, message us on WhatsApp (+65 8010 2337), or email sales@prestigesolutions.com.sg. You can also browse the full product range before the site walk.