The Site Change AV Integrators Keep Agreeing To (Without Billing For It)
Commercial AV integration projects regularly absorb site changes that were agreed verbally but never documented. From installation week requests to commissioning overruns, undocumented changes are one of the primary drivers of margin erosion on jobs that looked profitable at the halfway point.
A client contact walks the floor during installation week and asks an AV technician: can we add a display to the boardroom breakout? The tech says yes. A conversation happens, an agreement is reached, the work gets done. Nobody sends a confirming email. Nobody raises a change order. Three weeks later the job closes, the invoice goes out, and the display, the extra cable run, and four hours of labor are nowhere in it. This scenario plays out constantly in commercial AV integration - not because integrators are unaware of the problem, but because the gap between what gets agreed on site and what gets captured in the job record is where margin quietly disappears.
Why Site Changes Don't Make It Into the Job Record
The problem is not that AV integrators do extra work for free deliberately. It is that the workflow for capturing site changes is almost always informal. On a multi-room corporate installation, the project manager might be coordinating several client contacts, multiple trade teams, and a commissioning schedule that is already running tight. When a client walks the floor and requests an addition - an extra display here, a different microphone position there - the path of least resistance is to agree and sort out the paperwork later.
Later often does not happen. This pattern is especially common during the second half of a project, when the relationship with the client has moved into a collaborative rhythm. The formal change order process that existed in week one starts to feel bureaucratic by week five or six. Requests get agreed verbally, in a group chat message, or in a brief on-site conversation that nobody ties back to the job record. By the time the project closes, the list of undocumented additions can run to a dozen or more items.
The cause is structural. Without a single system connecting the original quote to the live job record, site changes exist in a parallel space - agreed in one conversation, absorbed into the work, never formalized. The project manager who could reconcile them is managing the next milestone. The admin team invoicing at close-out has no visibility into what changed.
Industry context
PMI's Pulse of the Profession research found that 43% of projects across sectors exceed their original budget, with an average overrun of 27%. For AV integrators managing complex multi-phase installations, undocumented site changes are one of the primary drivers of that variance.
What Each Undocumented Change Actually Costs
The individual amounts seem modest in isolation. A single informal change - one additional display, one revised cable route, one extra panel configuration - might represent three hours of labor and a few hundred pounds in materials. Easy to absorb in the moment, especially when the project margin still looks comfortable on paper.
The issue is how quickly the individual items add up. A typical commercial AV integration project can generate four to eight undocumented changes across its life. At three hours of labor and £300 in materials each, that is 12 to 24 hours of unrecovered labor and up to £2,400 in materials that never reach the invoice. Labor already represents 30 to 40 percent of a typical AV project's total cost, according to AVIXA's AV Industry Outlook and Trends Analysis. When those informal changes pile into that already-compressed margin, the job that looked profitable at the halfway point closes at break-even or below.
One case example in the industry describes a hotel ballroom AV retrofit where technicians logged hours informally throughout the project. By close-out, the job had absorbed a 40 percent labor overrun - $18,000 in unrecovered costs - because nobody compared actual hours against the estimate until the project was complete. The decision point to intervene had passed weeks earlier. The margin was gone before anyone knew to look.
Why Commissioning Week Is Particularly Vulnerable
Most informal changes accumulate steadily during installation. Commissioning week - when systems are tested, integrated, and tuned as a complete environment - is where they cluster. This is the stage where a client sees the full system working for the first time, and where adjustment requests are most frequent and most natural. Button labels need updating. Room control routing needs revision. A system that performed correctly when tested in isolation behaves differently when the wider network is live.
Many of these adjustments are included in the original scope. But some are not. When a client asks for a fundamental routing change, an additional room to be added to the system, or a control interface to be redesigned based on how staff are actually using it - those requests carry real cost implications. Commissioning week's time pressure makes it harder, not easier, to pause and raise a formal request for the record. The team is focused on getting the system live and accepted. The paperwork feels like an obstacle.
The result is that commissioning frequently runs longer than estimated, with additional costs that are never captured. AVIXA's research consistently identifies labor planning and project cost control as top operational challenges for integrators globally. Without a live record of what was agreed, what changed, and when, the conversation about billing for that extra commissioning time becomes difficult - sometimes impossible.
The last-day problem
Changes agreed on the final day of commissioning are the least likely to be documented. The system is signed off, the team is packing down, and raising a change order feels like it would sour the handover. That reluctance is understandable - and it is exactly where unrecovered costs are highest.
Closing the Gap Between Agreed and Invoiced
The fix does not require a new process so much as a consistent habit. Every change request - regardless of how minor it appears - needs one formal step before work starts: a brief written confirmation to the client contact that states what is being added, the estimated cost, and that proceeding constitutes approval. This does not need to be a lengthy document. It can be a two-line email. What matters is that it exists, and that it is attached to the job record.
The other change is moving from retrospective labor reconciliation to real-time tracking. When technicians log hours against specific tasks as they work, the variance between estimate and actual becomes visible while there is still something to do about it. A project manager who can see mid-commissioning that labor is already 10 hours over estimate has options: flag the overrun with the client, formally document the additional scope, or adjust resourcing. A project manager who sees the same figure at invoice stage has none of those options.
One practical step
Create a standing item on the weekly project review agenda called "changes agreed this week." Even if the answer is often none, the discipline of asking the question each week means informal changes are less likely to slip through unrecorded.
Job management software that connects the original quote to purchase orders, site activity, and the final invoice gives AV integrators the visibility to catch these gaps. Changes that start as a verbal agreement on the installation floor need to end up as a documented line on the invoice. That journey only happens reliably when there is a single place that everyone - from the site technician to the project manager to the person raising the invoice - is working from.
The informal site change is not going to stop happening. Clients will always have adjustments once they see the system live. The question is whether those adjustments appear on the invoice or disappear into the job's cost without a trace.
- AV Project Budget Tracking: Prevent Overruns & Protect MarginXTEN-AV · accessed 2026-07-03
- Where Did Our Margins Go?AVNetwork · accessed 2026-07-03
Related pages
Ready to run your business
on one platform?
Book a free demo and see how Zigaflow fits your team.