Skip to content
Hardware Buddy IT Solutions logo

IT AMC Contract and SLA: What to Check Before You Sign

By Shubham Dobriyal · 14 November 2026 · 9 min read

IT AMC contract and SLA for remote and onsite IT support

Two IT AMC quotes can look similar and deliver very different service. The difference is in the contract: what is covered, how fast the provider must respond, what is excluded and how you can leave if it is not working. This guide walks through each part of an IT AMC contract and service level agreement (SLA), so you can compare proposals properly.

1. Scope of services

The scope should state exactly what the provider will do. A typical IT AMC scope includes:

  • Preventive maintenance and scheduled health checks
  • Computer and server troubleshooting
  • Operating system support
  • Network troubleshooting
  • Software installation and configuration
  • Remote technical support

Vague wording such as "complete IT support" is a warning sign. Ask for a list. Our article on what is included in an IT AMC explains typical scope in detail.

2. Asset list

The contract should attach a list of covered devices: PCs, laptops, servers, NAS, firewalls, switches, printers and so on, ideally with serial numbers and locations. Check:

  • How new devices are added during the year, and at what cost
  • Whether personal devices (BYOD) are covered
  • Whether cloud services (Microsoft 365, Google Workspace) are included

3. Service levels: response vs resolution

An SLA should distinguish between:

  • Response time: how quickly the provider acknowledges and starts working on the issue
  • Resolution or restoration target: how quickly service is restored, where it can be committed
  • Onsite attendance time: how quickly an engineer arrives when a visit is needed

Resolution times often depend on factors outside the provider's control, such as parts availability or a vendor fault, so they are usually targets rather than guarantees. Response times should be firm.

Priority levels: an example structure

Many SLAs use priority levels. The structure below is an example of how priorities are commonly defined; actual times are agreed in each contract.

PriorityExampleHow it is typically handled
P1 CriticalServer down, internet down for the whole office, ransomwareFastest response, immediate remote work, onsite as soon as needed
P2 HighA department cannot work, key application failingFast response, same-day attention
P3 NormalSingle user issue, printer problemResponse within the agreed working window
P4 RequestNew user, software installation, change requestScheduled

Support hours

Check whether support is office hours only, extended hours or 24/7, and whether urgent work outside hours costs extra. Hardware Buddy's team is available 24/7, with response terms agreed in each contract.

4. Preventive maintenance schedule

The contract should say how often preventive visits or remote health checks happen, and what is checked. Our IT preventive maintenance checklist is a useful reference when reviewing this section.

5. Exclusions and items quoted separately

Every AMC has exclusions. Make sure they are listed clearly. Common items quoted separately:

  • Replacement hardware and spare parts (unless comprehensive; see comprehensive vs non-comprehensive AMC)
  • New software and licences
  • Major upgrades and projects
  • Data recovery
  • Third-party subscriptions

Also check how extra work is approved: written quote, email approval or an hourly rate.

6. Backup and data responsibilities

This is often unclear and leads to disputes after an incident. The contract should state:

  • Who is responsible for checking backups
  • How often restores are tested
  • What happens if a backup fails
  • Responsibility for data recovery and its cost

7. Security and confidentiality

  • A confidentiality clause covering your data and client information
  • How the provider stores your passwords (a password manager, not spreadsheets)
  • How remote access is controlled and logged
  • What happens to your data and credentials when the contract ends

Security frameworks such as the NIST Cybersecurity Framework are a useful reference for what good practice looks like.

8. Reporting and reviews

  • A report after each visit or monthly summary
  • A log of tickets with response times
  • A periodic review meeting: open risks, upcoming renewals, recommended upgrades

9. Price, payment and renewal

  • Fee and what it covers; GST shown on the invoice
  • Payment terms (yearly, half-yearly, quarterly)
  • How the fee changes when devices are added
  • Renewal process and notice

10. Exit terms

A fair contract makes leaving straightforward:

  • Notice period for termination
  • Handover of documentation, passwords and admin access
  • Return or deletion of your data held by the provider

Make sure all admin accounts for your systems belong to your business, not to the provider personally.

Contract checklist

CheckYes / No
Written scope of services
Asset list attached
Response times by priority
Support hours stated
Preventive schedule defined
Exclusions listed
Backup responsibilities clear
Confidentiality clause
Reporting defined
Exit and handover terms

How Hardware Buddy sets up an AMC

  1. Audit: we list your devices, servers and network.
  2. Proposal: scope, visit frequency and response terms, with a fixed quote.
  3. Onboarding: we document your setup and fix urgent issues.
  4. Ongoing: you call or WhatsApp us when something breaks, and we handle preventive maintenance.

Onsite support covers Delhi, Noida, Gurgaon, Ghaziabad, Faridabad and all Delhi NCR. Remote support is available across India and internationally.

Red flags in an AMC contract

  • No written scope, or only "complete IT support"
  • No response times, or response times only for "normal" hours with no mention of critical issues
  • Admin passwords held only by the provider
  • No mention of backups, security or confidentiality
  • Automatic renewal with a long notice period and no review
  • Extra work billed without a quote or approval process

How to tell if the SLA is being met

An SLA only helps if you can see whether it is met. Ask for:

  • A ticket log showing when each issue was raised, responded to and closed
  • A monthly or quarterly summary of tickets by priority
  • Records of preventive tasks completed
  • Backup check and restore test records
  • A review meeting to discuss recurring issues and upcoming risks

If the same problems keep returning, the review should lead to a root-cause fix, not just repeated tickets.

Contracts for multiple locations

If you have branches or staff in different cities, check how the contract handles them:

  • Which locations get onsite support and which are remote-only
  • Response terms for each location
  • How branch networks, VPNs and local devices are covered
  • Whether travel for onsite visits outside the main area is charged separately

Hardware Buddy provides onsite support across Delhi NCR and remote support across India and internationally, so multi-location contracts state which sites receive onsite visits.

Starting an AMC on the right foot

The first month sets the tone. Expect an audit, a list of urgent risks, documentation of your setup and agreement on how to raise issues (phone, WhatsApp, email). See what to expect in the first 90 days.

Example scope wording

Clear scope wording avoids disputes. An example of how a scope section might read (to be adapted to each contract):

"The provider will maintain and support the devices listed in Annexure A, including preventive maintenance every quarter, monthly remote health checks of servers and backups, troubleshooting of computers, servers and network issues, operating system support, software installation and configuration of licensed software supplied by the client, and remote technical support. Replacement hardware, new licences, major upgrades, data recovery and third-party subscriptions will be quoted separately and carried out after written approval."

Wording like this makes it clear what is included, how often, and what needs separate approval.

Key takeaways

  • Insist on a written scope and an attached asset list.
  • Response times should be defined by priority, with support hours stated.
  • Exclusions and items quoted separately must be listed clearly.
  • Backup responsibilities and confidentiality need their own clauses.
  • Ask for reports and reviews so you can see whether the SLA is met.
  • Make sure admin accounts belong to your business and exit terms include a full handover.

Products and services for this

Quick answers

What should an IT AMC contract include? +

A written scope, asset list, response times by priority, support hours, preventive maintenance schedule, exclusions, backup responsibilities, confidentiality, reporting and exit terms.

What is the difference between response time and resolution time? +

Response time is how quickly work starts on an issue. Resolution time is how quickly service is restored, which can depend on parts or vendors, so it is often a target.

What is an SLA in IT support? +

A service level agreement defines the support levels the provider commits to, such as response times by priority, support hours and reporting.

What is usually excluded from an IT AMC? +

Replacement hardware (in non-comprehensive AMCs), new licences, major projects, data recovery and third-party subscriptions are common exclusions.

Who should own admin passwords under an AMC? +

Your business. Admin accounts should belong to the company, with credentials stored securely and handed over if the contract ends.

Does Hardware Buddy offer 24/7 support? +

Yes. Our team is available 24/7, with response terms agreed in each AMC contract.

Want an AMC with a clear scope and response terms? We audit first, then propose a fixed quote.

Tell us what you need. Get a clear quote.

Call or WhatsApp +91-8287980829, 24 hours a day, 7 days a week. Or send your requirement and we will get back to you.

Call WhatsApp Get Quote