Commissioning, Snagging, and Client Sign-Off Discipline for AV Systems Integrators

Every AV systems integrator knows the moment: installation is complete, the rack looks clean, and the crew is packing up. But installed is not the same as working. The commissioning phase is where a built system is energized, tested against its design, and proven to perform before the client takes ownership. It is also where the final payment is unlocked - and for most integrators, that final milestone represents the largest single invoice on the project. When commissioning is treated as an afterthought, or compressed by programme pressure at the end of a job, punch list items multiply, sign-off stalls, and the team absorbs rework hours that were never in the quote. This resource sets out the operational disciplines that protect delivery quality, payment timing, and client relationships through the commissioning, snagging, and sign-off process.

Preparing for Commissioning: What Needs to Be in Place First

Commissioning is not a one-day sprint at the end of a project. It is a phase that must be planned, staffed, and protected in the programme from the point of contract award. When commissioning is treated as whatever time remains after delays elsewhere, it becomes the phase that absorbs everything that slipped.

The preparation work before a single device is powered up directly determines how efficient the process will be. Before testing begins, the project manager and lead engineer should confirm three things: the physical installation is complete and matches the design drawings; the network infrastructure is ready and configured to the agreed VLAN and IP plan; and the client's IT team has given the AV contractor access to the systems it needs - conference platform credentials, room booking integrations, and relevant network ports.

When AV is brought in late on a construction or fit-out project, the constraints multiply. Cable routes are already fixed, ceiling voids are full, and power positions are set. Each of those gaps creates extra work during commissioning. Coordinating early with the principal contractor, M&E sub-contractor, and the structured cabling team prevents the kind of integration-point failures that derail commissioning days before sign-off. The display bracket is fitted but the socket is in the wrong position. The cabling is pulled but the network port is not patched. These are not technology failures - they are coordination failures that show up as technology failures on commissioning day.

A commissioning programme should be built into the project plan from the start, showing which systems will be tested in which order, who is responsible for each phase, and what the pass criteria are for each element. The commissioning plan is derived from the design documents - the signal flow diagram, the cable schedule, the IP schedule - so that every path tested maps to a document that can be handed back to the client.

Running the Commissioning Process by Layer

Effective commissioning works from the physical layer up, trusting each layer only after the one below it has been verified. Working out of sequence - chasing an audio problem before confirming a device even has an IP address - wastes hours on symptoms rather than causes.

Pre-power inspection. Before energizing anything, the installation is walked against the drawings. Every device is confirmed in the position the drawings show, with model and quantity matching the equipment list. Cables carry the ID from the cable schedule on both ends. Connectors are seated. Rack grounding, cable dressing, and airflow clearances are checked. Every discrepancy is noted on a marked-up drawing - that redline is the first page of the as-built record.

Power-up and network. Devices are energized in order: infrastructure first, then sources and destinations. As each device comes up, it is confirmed to hold its assigned address with no duplicates or stray DHCP leases. VLAN membership, PoE budgets, and control processor connectivity are all verified before testing moves to signal paths.

Signal path verification. Every connection on the signal flow diagram represents a claim that signal can travel that route. Verification proves it, one path at a time: a known test signal is injected at the source and confirmed clean at the destination. Format transitions - HDMI to SDI, analog to Dante, resolution changes - are explicitly tested, because these are where paths silently fail. Return and monitoring paths are included, not just program feeds.

Performance verification. A path that passes signal is not a path that performs. Audio levels are set and confirmed, gain structure is checked, and echo cancellation is tested on a real call rather than on the bench. Video displays show the correct source at the correct resolution. Lip sync across the path is confirmed. Every result is recorded against the target it was tested against. A pass with no number is a note to self, not a commissioning record.

Control, presets, and failover. Every preset and scene is exercised: source selection, room combine, volume, mute, camera recalls. The system is driven from the real user interface - the touch panel, button panel, or app - not from a back-end configuration tool. Failover scenarios are tested deliberately: the primary feed is pulled, a network link is dropped, and the system's response is confirmed and documented.

Snagging: Managing the Punch List to Closure

The snag list is the honest gap between commissioned and complete. Every AV project generates one. The discipline is in how that list is managed, not in whether it exists.

A punch list that lives in someone's email thread or a shared notebook loses accountability the moment the commissioning engineer leaves site. Items need owners, due dates, and a status that the project manager can track without making a phone call. Each open item should identify the fault, the system it affects, the person responsible for resolution, and the agreed completion date.

Commissioning is complete at 100 percent, not 93. The three open runs on a cable test are not a rounding error - they are the punch list, and they stay open until resolved and re-tested. Treating a small number of open items as acceptable at handover sets a precedent the client will remember every time the room has a problem.

Snagging items fall into two categories: those the integrator can resolve without client access or external coordination - programming fixes, configuration corrections, labeling - and those that require a return visit, client IT involvement, or third-party contractor coordination. Separating them immediately makes the resolution path clearer and prevents the whole punch list from stalling behind a single item waiting on someone else.

The most common snagging sources on AV projects are control system programming edge cases, network integration points where the client's IT configuration does not match the assumptions in the design, and physical installation details - a camera not centred on the bracket, a cable not fully dressed - that the client notices even when the system performs correctly. Tracking these in a structured list and assigning resolution owners stops them from accumulating into a client complaint.

Client Demonstrations, User Training, and Formal Sign-Off

The sign-off meeting is the event that triggers the final invoice. Preparing for it properly determines whether that invoice is paid on the agreed date or delayed while the client works through concerns that could have been addressed beforehand.

A client demonstration should walk the system from the user interface, not from a technical configuration view. The client's representative - facilities manager, IT lead, or end user - needs to see the system working the way they will operate it. Preset switching, video conferencing join flows, camera controls, and room combine functions are demonstrated in use, not described in a summary.

User training should cover the tasks the client's team will actually perform: starting a meeting, joining a video call, sharing content from a laptop, adjusting audio levels, and shutting down at the end of the day. A system can be well designed and properly commissioned and still be judged a failure because nobody knows how to use it. The interface must be simple enough not to need explaining twice, and the documentation left behind - quick reference guides, system drawings, firmware version records, warranty information, and service contact details - should be handed over at the sign-off meeting, not emailed weeks later.

The formal sign-off document records what was demonstrated, what the client confirmed as working, and any items agreed as remaining open with a completion date. A signed acceptance is the commissioning report in commercial terms. It is also the proof an integrator needs if the client later disputes the condition of the system at handover.

Protecting the Final Invoice Through Commissioning Discipline

The final payment on an AV project is tied to commissioning sign-off. For projects with stage payment structures, the commissioning milestone typically holds back 10 to 20 percent of the contract value - on a project worth £150,000, that is £15,000 to £30,000 sitting at risk until acceptance is obtained (illustrative example based on typical AV project payment structures). As explored in Where AV System Integrators Lose Margin, that final payment is the one most exposed to delay: it depends on site readiness, third-party IT infrastructure, client availability, and resolution of snagging items that all sit partly outside the integrator's control.

The integrators who collect that final payment on time are not the ones who got lucky with a smooth site. They are the ones who managed commissioning with the same discipline they applied to procurement and installation. That means protecting commissioning time in the programme from the point of contract award. It means building and managing a punch list actively rather than waiting for the client to compile their own. It means scheduling the sign-off meeting before the client's diary fills up, and arriving at it with every test documented, the punch list closed, and the handover pack ready.

When commissioning is compressed by programme pressure, faults that would have been caught during structured testing get discovered instead during a live meeting in front of the client's stakeholders. AV commissioning specialists report that more than 35 percent of AV system issues are traced to configuration errors present at the point of installation but not caught before handover. A structured commissioning process eliminates most of that category before the client encounters it.

Managing Commissioning Across Multiple Live Projects

AV integrators running four or more concurrent projects struggle to maintain commissioning oversight when each job is in a different phase at the same time. A project manager tracking commissioning status by email and memory misses the jobs where a sign-off meeting has not been scheduled, a punch list has grown without being reviewed, or a final invoice has not been issued because no one has confirmed the client is satisfied.

Zigaflow's project tracking gives project managers a real-time view of where each job sits against its programme, including commissioning milestones, without relying on engineers to report upward. Stage payments can be tied to job milestones so the invoicing trigger is a status update, not a reminder that comes too late. For AV businesses growing their project pipeline, the operational discipline that lives in a good process needs to be the discipline that lives in the system - not in one person's awareness of which jobs are approaching sign-off.

Closing

Commissioning is the phase where the gap between a competent installation and a delivered project is closed. The integrators who handle it well do not treat it as a hurried end-of-job checklist. They plan it as a distinct operational phase with its own programme, staffing, and documentation requirements. Snagging is managed to zero, sign-off is obtained with a formal record, and user training is delivered as part of the handover rather than as an afterthought. The result is a client who understands what they have received, a final invoice that is paid without dispute, and a record that protects the integrator if anything is later called into question.