Ask ten integrators what commissioning means and you'll get two answers. Eight will describe a walkthrough: the owner's rep arrives, somebody plays a YouTube clip on the big display, everyone agrees it looks great, and a sign-off sheet gets initialed in the lobby. Two will hand you a document set.
The difference shows up eighteen months later, when the room stops working and nobody can say what it was supposed to do in the first place.
Commissioning is the measured proof that a system meets the design intent. Closeout is the package that lets somebody other than the installer keep it running. They are separate deliverables, they both belong in the contract, and on most jobs neither one is specified tightly enough to be enforceable. Here's what each should actually contain.
Commissioning Is a Test Plan, Not a Walkthrough
There is an actual standard for this — ANSI/AVIXA 10:2013, Standard for Audiovisual Systems Performance Verification. It isn't a pass/fail checklist handed down from on high; it's a catalog of verification items that the design team selects from and assigns to a phase, so that every item has an owner, a method and a recorded result. Most specifications reference it. Very few projects actually run it.
You don't need the full catalog on a four-room office fit-out. What you do need is a test plan written before install, with a number next to every line — because a result without a number is an opinion.
| What gets tested | Typical target | Evidence in the package |
|---|---|---|
| Copper permanent links | Cat6 to 250 MHz, Cat6A to 500 MHz, 100% pass | Certification tester export, one record per link ID |
| Fiber links | Dual-wavelength insertion loss inside the computed budget | OLTS results plus OTDR traces on backbone runs |
| Loudspeaker coverage | ±3 dB across the defined listener area | Measured SPL grid with mic positions on the plan |
| Speech intelligibility | STIPA per IEC 60268-16; 0.50 design target, 0.45 floor | Per-position STIPA readings, noise floor noted |
| Video chain | Native format end to end, no scaler surprises | EDID map, HDCP version per path, measured bit rate |
| Conferencing audio | AEC converged, no double-talk dropouts, far-end level verified | Recorded far-end call sample, per-mic gain structure |
| Rack thermals | Intake vs. exhaust delta under full load | Logged temperatures after a 60-minute soak |
The mistake: Accepting "we tested everything" with no artifacts. A continuity tester that confirms eight wires land on eight pins tells you a cable exists. It tells you nothing about whether that link will carry 4K60 over HDBaseT at 68 meters on a warm day.
What works instead: Name the instrument in the spec. A Level IIIe-or-better certification tester for copper, with exported results per link ID that match the labels on the patch panel. If the test file's link IDs don't match the as-built, the test file is decoration. We go into the rough-in side of this in more detail in our piece on structured cabling decisions at new-construction rough-in.
The Four Drawings That Have to Be As-Built
Design drawings describe what someone intended in month two. As-builts describe what is behind the wall in month nine. On nearly every project those are different documents, and the gap is where future service calls go to die.
- Signal flow / one-line diagram — every source, every destination, every processor, revised to match what shipped. Substitutions during procurement are normal; undocumented substitutions are not.
- Point-to-point schedule — cable ID, type, origin device and port, destination device and port, length. Labeled per ANSI/TIA-606-C, and the labels in the field match the labels on the sheet.
- Rack elevations — front and rear, actual RU positions, including the two blanks somebody pulled for airflow. ANSI/AVIXA F502.01:2018 covers rack construction practice if you want a reference to point at.
- IP and device schedule — hostname, MAC, static address or DHCP reservation, VLAN, subnet, firmware version at handover, and which switch port it lands on.
That last one is the single most valuable page in the binder and the one most often missing. A networked AV system with no address schedule is a system nobody can troubleshoot remotely, which means every issue becomes a truck roll.
Configuration Backups Are the Deliverable Nobody Asks For
This is where the real leverage sits, and it's worth being blunt about it.
Modern AV is software. The hardware in the rack is close to commodity; the value is in the configuration, and the configuration lives in files that can be handed over or quietly withheld. What belongs in the package:
- The DSP or platform design file — the editable project, not a PDF of it. On the Q-SYS and networked-audio platforms that replaced analog DSP racks, that's the Designer file itself, at the version deployed.
- Control system source code — the project source, not a compiled binary. A compiled program you cannot open is a system you cannot change.
- Firmware versions as deployed, device by device. Six months later, "it worked before the update" needs a baseline to be a useful sentence.
- Switch configuration — VLANs, QoS markings, IGMP settings, port assignments. Networked audio is unforgiving here: clock traffic and media traffic need their own markings, and mixed-generation gear running different PTP versions is where most clock fights start.
- Display and projector settings — calibration targets, lamp or laser hours at handover, any geometry or edge-blend data.
The mistake: Treating source code as the integrator's intellectual property and the owner's configuration as part of it. The programming labor was invoiced and paid; the file describing one specific building is not a trade secret.
What works instead: Put it in the contract at award, not at closeout. One line — "Contractor shall deliver editable source and configuration files for all programmed devices" — costs nothing in month one and is nearly impossible to obtain in month twelve.
Credentials, and Who Actually Owns the Accounts
Every system now has logins: control processors, switches, display management portals, conferencing tenants, signage CMS platforms. The question nobody asks during construction is whose name the account is in.
If a cloud platform is registered to the integrator's company email, the owner doesn't have a system — they have a subscription to that integrator. This bites hardest on signage and room-booking platforms, which is why we spend real time on CMS ownership in our post on digital signage content and CMS workflow.
Closeout should hand over a credential schedule covering every account, with the owner's domain as the registered organization, an administrator seat the owner controls, and installer access documented as a named service account that can be revoked without breaking the system. Default passwords changed and recorded. Any dealer-level portal access noted explicitly so it's a choice rather than a discovery.
Training Is a Deliverable With a Date and a Recording
"Training provided" on a closeout sheet usually means a project manager showed one facilities tech which button starts a meeting, on the afternoon the drywall dust was still settling.
The mistake: Scheduling training for the day of substantial completion, for whoever happens to be in the building, with no recording.
What works instead: Two sessions, split by audience. An end-user session on the rooms as they'll actually be used — recorded, so the person hired next March gets the same briefing. A separate technical session for whoever holds the keys: rack layout, reboot order, where the backups live, how to read the IP schedule, what to try before calling. Then a follow-up visit two to four weeks in, once people have had real meetings and real complaints. That second visit catches more genuine issues than the punch walk does. It's also where most of the small hybrid-meeting room gripes get solved for good.
Warranty, Beneficial Use, and When the Clock Starts
Two warranties run on every AV job and they rarely start on the same day. Manufacturer coverage typically begins at shipment or at registration; the integrator's labor warranty begins at substantial completion or beneficial use. On a project that slips — and they slip — a display can burn four months of its warranty sitting in a crate.
The closeout package should state, in writing: the beneficial-use date, the labor warranty term and what it covers, each major component's manufacturer term with registration confirmations attached, serial numbers tied to room locations, and the actual service path — who to call, which hours, what response time was purchased. "Call the office" is not a service level.
The Punch List Discipline
A punch list is not a wish list. Each item needs the room, the specific failure, the party responsible, and a date. Items get closed by re-test, not by assertion — and a retest of a video path means the path was exercised again, not that someone remembers fixing it.
The practical lever here is retention. Hold a meaningful percentage against closeout documentation specifically, not just against physical punch items. Once the drawings, the test records, the configuration files and the credential schedule are a condition of final payment, they arrive. When they're a courtesy, they arrive in about forty percent of cases, and the ones that don't arrive are always the jobs you later need them for.
Where to Start
If you're writing or reviewing an AV scope right now, three lines do most of the work: name the test instruments and the pass criteria, require editable configuration and source files for every programmed device, and require all platform accounts registered to the owner's domain. Everything else in this article is refinement on those three.
Handsome Group designs, installs and commissions AV and low-voltage systems across Los Angeles and Southern California, and we hand over the whole package — as-builts, test records, configuration files, credentials and a training recording — because a system we can't be fired from is the only kind worth installing. If you're holding a closeout that doesn't look like this one, we're happy to tell you what's missing.