How to Choose a Managed IT Support Agreement
A good IT support agreement provides more than a telephone number to call when something breaks. It brings user support, infrastructure monitoring, security, backup and change management into a measurable service plan. When comparing proposals, assess the following decisions rather than relying on package names.
Key takeaways
- ✓Use a written inventory to identify the devices, users, locations and applications covered by the agreement.
- ✓Review priorities, service hours, resolution targets and escalation alongside the SLA response time.
- ✓Ask for more than confirmation that a backup ran: define restore testing, responsibilities and reporting.
- ✓Monthly service reports should show recurring problems, risks and planned improvements.
1. Establish an accurate picture of your infrastructure
A reliable proposal starts with discovery and an inventory. User numbers alone are insufficient: servers, virtual machines, network devices, firewalls, access points, business applications, Microsoft 365, branches and remote workers must be considered together.
An incomplete inventory can lead to disagreements over scope after the contract begins. The agreement should also identify who maintains the inventory and how new devices are added to the service.
- Device, licence and warranty inventory
- Critical services and business applications
- Locations, connections and boundaries of responsibility
- Existing issues, technical debt and priority risks
2. Define measurable service levels
An SLA does not mean that every request will be resolved at the same speed. A business outage, an issue affecting one user and a planned change should have different priorities. Response time should describe the period between logging a request and a specialist starting work; the resolution target should describe restoring the service to a usable state.
- Definitions of critical, high, normal and low priority
- Conditions for remote and on-site response
- Service hours during and outside normal working hours
- Escalation to the vendor or a senior specialist when the issue cannot be resolved
3. Include security and backup in service oversight
Resolving a user request and managing infrastructure risk involve different activities, but both require consistent oversight. Update status, administrator permissions, MFA, firewall changes, endpoint protection and backup failures should form part of a regular review plan.
Backup success means more than a job displaying a successful status. Selected samples must be restored, RPO and RTO targets established for critical systems, and test results recorded.
4. What should a monthly report contain?
A report should support decisions as well as list activities. A management overview should explain the business impact of technical details, while a technical appendix preserves a record of changes.
- Opened, closed and outstanding requests, including priority and resolution times
- Recurring problems and root cause investigations
- Server, disk, backup and security checks
- Licence, warranty and capacity alerts
- The maintenance and improvement plan for the following month
5. Which factors determine the price?
The cost of an IT support agreement depends on user and device numbers, locations, critical systems, required service hours, the frequency of on-site work, security and backup scope, and existing technical debt. Compare the work and responsibilities included alongside the monthly total.
- Whether initial setup and documentation are charged separately
- Whether project work, licences and hardware are included
- Conditions for on-site visits, travel and out-of-hours work
- The handover of information and access when the agreement ends
Eight questions to ask before requesting a proposal
- Which devices, locations and services are covered?
- How are request priorities and response targets measured?
- Under what conditions and how frequently is on-site work provided?
- How often are backup restores tested?
- How are firewall and administrator access changes approved?
- Which measures appear in the monthly report?
- Which activities are outside the agreement and incur additional fees?
- How are documentation, the password vault and configurations handed over at the end of the agreement?
Related guides
Sources
This guide provides general information. Define implementation requirements around your business risks and infrastructure.