What should an AV support agreement actually cover?

The test of a support agreement is not the day you sign it. It is a Tuesday in week forty, when a room that matters stops working and everyone turns to see who picks up.

A warranty is not support

When the defects liability period ends, the builder’s obligations end with it - and a manufacturer’s warranty covers the box, not the room. Support is the layer that covers the room: the configuration, the integration between systems, the documentation, and the person who knows why it was built that way.

What belongs in the agreement

Scheduled maintenance that lands before your busy season, not during it. A portal where faults are logged, visible and tracked to resolution - not an inbox. Agreed priorities, so both sides know what happens next when something fails. Documentation kept current as the room changes, because a support file that describes last year’s system is a liability wearing a lanyard. And spares thinking: knowing which component fails first, and where its replacement is sitting.

Who should hold it

There is a strong argument that the team that installed the system should support it - they hold the documentation, they know the decisions behind the design, and nothing gets rediscovered at your expense. It is why the City of Rockingham runs more than thirty facilities against one known standard, and why the venues at Baillie Hill run on one platform with us on the tools under an ongoing support agreement. Our version of this is TA CONNECT.

Questions to ask any provider

Who keeps our documentation current, and where does it live? What happens when the technician who knows our room moves on? How do faults get logged, and can we see the queue? And the quiet one that matters most: who commissioned this system, and will the person supporting it ever have to guess?