An AV support renewal arrives with the same room count as last year. Since then, the organization has added two spaces, replaced several conferencing devices and moved its executive meetings to a different floor. The price is easy to find. Whether the agreement still covers the right work takes more effort.
Before signing, compare the agreement with the rooms you use today and the support they needed over the past year. Look at what failed, how long repairs took and which problems keep returning.
Bring these six sets of records to the renewal meeting. Each should help you and the provider decide what to keep, what to change and what needs a price before you renew.
Key Takeaways
- Reconcile covered assets and service hours with current room use.
- Distinguish acknowledgment, diagnosis, workaround and full restoration.
- Review repeat incidents and completed maintenance alongside ticket totals.
- Turn the findings into written scope changes, owners and dates.
1. The Current Coverage List
Begin with the room and equipment schedule attached to the agreement. Check it against the rooms you have now: spaces added or removed, equipment replaced, software changed and locations moved. Identify retained devices that may no longer be supported by their manufacturers.
For each important room, confirm the covered hours and services. A space used for evening public meetings may have different needs from a small room used only during office hours. Record the room’s current business purpose rather than relying solely on its original designation.
Check the boundaries between providers. Who handles a network-related meeting failure, a room-platform account issue or an integration with building systems? Even when another team owns the repair, the support process should explain who coordinates the handoff and communicates with the customer.
Update the coverage list and flag any missing rooms or excluded work before approving the price.
2. The Incident History
Request the incidents for the review period in a form the team can sort by room, symptom, cause and outcome. Ticket counts alone do not reveal impact. A few questions about the touch panel may have little effect on meetings. One long outage in a critical room deserves closer attention, even if it produced only one ticket.
Look for missing context. A ticket marked “resolved” should explain what restored service and whether the underlying cause was addressed. If the record contains only a short closure code, discuss how future reporting can capture a useful explanation without creating excessive administrative work.
Ask room owners about failures that never became tickets. People sometimes move to another space, use a laptop speaker or abandon a feature. Those workarounds can hide reliability problems from the support record. Label user reports separately from confirmed incidents and investigate patterns rather than treating every recollection as a verified outage.
3. A Timeline from Failure to Restoration
Choose a sample of meaningful incidents and reconstruct what happened. Include when the issue was reported, when it was acknowledged, when technical assessment began, when a workaround became available and when the expected room function was fully restored.
A provider may acknowledge a ticket in minutes while the room remains unusable for hours. Record both times. A workaround may let a meeting proceed even though a camera or control function still needs repair.
Compare the timeline with the actual service commitments. Confirm whether clocks run during business hours, what events pause them and how dependencies on customer access or third parties are recorded. Use consistent definitions before drawing conclusions from averages.
Review critical rooms separately. An overall service average can obscure a recurring problem in the one room used for board meetings. Where reliable availability data does not exist, say so and agree on a practical measurement method for the next term. Do not fill the gap with an assumed uptime percentage.
4. Repeat Failures and Corrective Actions
Group repeat incidents by room, device and symptom. Similar symptoms can have different causes, so ask the technical team to distinguish confirmed findings from working theories.
For each meaningful pattern, identify the corrective action and its status. A configuration change, firmware update, cable replacement or user-guide revision should have an owner, completion date and a way to check whether it worked. Repeatedly closing tickets after a reboot does not establish that the underlying issue has been removed.
For repairs still waiting, ask what is holding them up. A technician may need an empty room or approval from another team. Agree on the access or decision needed and who will arrange it.
Give recurring failures that interrupt important meetings priority over routine questions that staff can resolve quickly.
5. Maintenance That Was Actually Completed
Compare the planned maintenance schedule with service records. Identify what was inspected, tested or updated, the date, the technician and any findings that required follow-up. A calendar appointment marked complete is not the same as a record of the work performed.
Review the scope against the installed systems. Does the visit include a representative call, content sharing and remote audio checks, or only a visual inspection? Are configurations backed up where appropriate? Who reviews supported software and firmware levels, and who approves changes?
Updates should follow an agreed process for compatibility, scheduling and recovery. The renewal should make clear which activities are included and which require separately approved work. Resolve any overdue findings and carry outstanding actions into a tracked plan.
VIcom’s Technology Maintenance Program describes scheduled maintenance, support and lifecycle planning among its services. Check your agreement for the rooms, maintenance visits and response commitments it includes.
6. Lifecycle Recommendations with a Reason
Ask for replacement and upgrade recommendations tied to evidence. Each recommendation should identify the affected room, the operational issue or support constraint, the proposed action and the consequence of waiting.
Separate urgent service risks from useful improvements. A device nearing the end of manufacturer support calls for a different discussion from a camera upgrade intended to improve framing. Both can matter, but they should not compete in the budget without an explanation of their purpose.
Check dependencies and timing. A room refresh may require network changes, licensing or a period without room access. Coordinate those needs with the organization’s calendar and budget process. Record what can be maintained through the next term and what needs a planned decision sooner.
Turn the Evidence into a Renewal Agenda
Use one working table to keep the meeting focused. Enter the actual finding and proposed change in the final column; do not leave the discussion at a general request for “better support.”
| Evidence | Question for the Review | Decision to Record |
|---|---|---|
| Current coverage | Are the right rooms, assets and hours included? | Add, remove or clarify scope |
| Incident history | Where did service problems affect users? | Improve reporting or target specific rooms |
| Restoration timelines | Did support meet the agreed commitments? | Clarify measures, escalation or coverage |
| Repeat failures | Which causes remain unresolved? | Assign corrective actions and verification |
| Maintenance records | Was the intended preventive work completed? | Adjust visits, tests or change procedures |
| Lifecycle recommendations | What needs attention during the next term? | Approve a plan, defer with reasons or request more evidence |
For each accepted change, name an owner and date. Confirm the resulting agreement in writing, including exclusions and any work that will be quoted separately. Retain the review record so next year’s discussion can assess whether those decisions improved service.
Related Reading
Managed AV Operations: Monitoring and Analytics
Build a 2027 AV Budget Around a Room Risk Register
Where VIcom Fits
VIcom can help compare your current rooms, repair history and maintenance needs with the proposed support agreement. Bring the current agreement and available incident records to a support discussion so the proposed coverage addresses the rooms and problems that matter to the organization.
Connect with VIcom by filling out the form below.