Hiring an AV programmer: what to ask before you sign
Certifications, source code, version control and commissioning. A buyer's checklist for control and DSP programming work.
Published September 28, 2026. 2 minute read.
A control system can be installed perfectly and still fail its users every morning. The difference is usually the programmer. Here's what to check before you hire one, whether it's an integrator's in-house team or a programming-only freelancer.
1. Platform and depth
"We do Crestron" can mean they sell it, install it, program it, or all three. Ask specifically who writes the code and on which platforms. On AVCleared, firms list each ecosystem with depth (sells, installs, programs, services), so you can filter for "Programs Q-SYS" directly.
2. Certifications held by the person doing the work
Company-level claims don't help if the certified programmer isn't on your job. Ask who will program your rooms and what they hold:
| Platform | Certifications to look for |
|---|---|
| Crestron | Crestron Certified Programmer; Masters Silver, Gold, Platinum |
| Q-SYS | Level One and Two; Control 101 and 201 (201 requires 101) |
| Extron | Control Specialist (ECS), Control Professional (ECP), Authorized Programmer |
| Audio / DSP | Q-SYS Level Two, Biamp Tesira, Dante Levels 1-3 |
| Design | AVIXA CTS-D |
On AVCleared, every certification belongs to a named person and shows Claimed until proof is verified.
3. Source code and file handover
This is the question buyers most often forget. Agree in writing:
- Will you receive the source code and compiled files, or only the compiled program?
- Will touch-panel and UCI project files be included?
- What happens to the code if you change integrators?
Many owners now require source-code turnover at closeout. You can make it a hard rule in an AVCleared requirement profile.
4. Version control and standards
Ask whether the programmer uses version control, follows written code standards, and documents IP schedules and signal flow. These are what make the next service call fast.
5. Commissioning and verification
Ask how they test before handover: a written commissioning checklist, an AVIXA performance verification report, a punch list, and user training. Reviews on AVCleared score commissioning thoroughness and programming stability separately, which is often more telling than the overall stars.
6. Remote access practices
Remote programming and support are normal now. Ask how they secure remote access, who holds credentials, and how access is removed at the end of the engagement. Your IT team will ask too.
Put it in the requirement profile
Every item above can be a rule: required ecosystem and depth, a named certification held by someone on the crew, source-code turnover, a performance verification report at closeout. Contractors who don't meet a hard rule show as Not approved with the missing items listed, so you can see the gap before the first site walk.