

An annual maintenance contract should make technical support responsibilities clear before a problem occurs. Two proposals with similar prices may cover different equipment, locations, support hours and exclusions. Comparing scope is therefore as important as comparing the annual fee.
List users, computers, servers, switches, firewalls, access points, software and locations that should be included. Clarify whether security systems, printers or third-party applications are part of the agreement.
Specify remote assistance, on-site visits, helpdesk channels and service hours. Agree response targets and escalation paths. A response target is different from a guaranteed resolution time.
Define planned visit frequency, equipment health checks, monitoring, backup-status review and reporting where applicable. Agree maintenance windows and which recommendations require separate approval.
Check whether replacement hardware, subscriptions, upgrades, project work, cabling and support outside normal hours are included. Do not assume every issue is covered simply because a contract exists.
A support arrangement should make it possible to review recurring issues, equipment health, service activity and improvement recommendations. Reassess the scope when users, locations or infrastructure change.
Prepare a list of your locations, users and equipment before requesting a proposal. PROVE can review the environment and discuss a maintenance arrangement with clearly defined responsibilities.