An annual maintenance contract is a one-year, fixed-scope agreement to keep your IT equipment working.
AMC stands for Annual Maintenance Contract. In IT, it is a written agreement where a service provider maintains your hardware and infrastructure for twelve months: preventive maintenance on a schedule, repairs when something fails, and a response SLA that says how fast help arrives. This page explains what a proper AMC contains, the three coverage models, and how to evaluate a quote before you sign. If you are ready to buy rather than research, see our IT AMC services in India page.
- 9Contract components
- 3Coverage models
- 10Clauses to check
- P1-P4SLA priorities
The short answer, before the detail.
AMC full form: Annual Maintenance Contract. It is a yearly agreement between your business and an IT service provider under which the provider keeps listed equipment operational for a fixed fee. It bundles two kinds of work: preventive maintenance on a published calendar (health checks, patching, backup verification) and corrective maintenance when something breaks, delivered against a written response SLA. It differs from a warranty (a manufacturer promise about one product) and from managed services (full operational ownership of your IT). The rest of this page unpacks the contract itself: what a complete one contains, the three coverage models, and the clauses that decide whether the document protects you or the vendor.
The nine parts every serious AMC contract contains.
Scope schedule
The list of services the provider will perform: preventive visits, break-fix repairs, remote support, patching, backup checks. Each service should be named with a frequency (monthly, quarterly) and a delivery mode (on-site or remote). "General IT maintenance" is not a scope, it is an argument waiting to happen.
Asset register
An itemized annexure listing every device under contract: make, model, serial number, location, warranty status. The register is what makes coverage disputes impossible. If a device is on the list, it is covered. Providers who skip the register can later claim any failed device was "not part of the contract".
SLA matrix
A table of priority levels (usually P1 to P4) with a response time and a resolution target for each. Response means an engineer starts working, not an auto-reply email. Without a written matrix, "we respond quickly" means whatever the provider needs it to mean that day.
Exclusions list
What the contract does not cover, stated explicitly: consumables like toner and batteries, physical damage, power-surge failures, software licensing, end-of-life hardware. A short, honest exclusions list is a good sign. A vague one that excludes "misuse" without defining it is a claim-denial machine.
Parts and repair clause
Who pays for replacement parts. In a comprehensive AMC, parts are included. In a non-comprehensive AMC, labour is included and parts are billed separately at agreed rates. The clause should also state repair turnaround and what happens when a part is no longer manufactured.
Escalation matrix
Named roles and time triggers for when a ticket is not resolved: engineer to service manager to account director, each with a contact and a clock. Escalation that depends on you personally knowing someone senior at the vendor is not a process, it is a favour.
Preventive maintenance calendar
The planned-visit schedule: health checks, firmware updates, backup verification, capacity reviews, with a defined cadence per equipment class. Preventive work is the half of an AMC that break-fix contracts do not have, and the half that actually reduces downtime over the year.
Reporting cadence
What gets reported and how often: ticket volumes, SLA performance against target, asset health, upcoming warranty expiries. Monthly written reports are standard. A provider unwilling to report SLA performance is telling you how they expect to perform against it.
Exit and handover terms
Notice period, final-invoice treatment, and the handover obligations: asset register, admin credentials, network documentation, runbooks. Good exit terms are the clearest signal of provider confidence. A contract that is easy to leave is usually one you will not want to.
Industries where AMC contracts are the norm in India.
Manufacturing
Plant floors run weighbridges, barcode stations, industrial PCs, and ERP terminals that stop production when they fail. AMCs here emphasize on-site response windows, standby units for critical stations, and preventive visits timed to maintenance shutdowns.
Healthcare
Hospitals and diagnostic chains contract AMCs for clinical workstations, PACS connectivity, and nurse-station hardware. Contracts add data-handling clauses for patient records and priority SLAs for equipment that clinical work depends on.
Banking and financial services
Branches, NBFCs, and broking offices run AMCs across branch networks because auditors ask who maintains the infrastructure and on what SLA. Contracts here carry the strictest sub-contracting and confidentiality clauses.
Education
Schools and colleges maintain computer labs, smart classrooms, and admin offices on annual contracts aligned to the academic year, with heavy preventive work scheduled in vacation windows and per-device pricing that scales with lab size.
Retail chains
POS terminals, billing counters, and store networks across dozens of locations make per-incident support unmanageable. Multi-site AMCs with a single SLA matrix and consolidated monthly reporting are the standard answer.
Logistics and warehousing
Scanner fleets, dispatch terminals, and warehouse WiFi stop revenue when they stop. AMCs in this sector are built around equipment availability targets and spare-unit clauses rather than repair timelines alone.
Comprehensive vs non-comprehensive vs on-call: what each model covers.
| Feature | On-call Pay per visit, no contract | Non-comprehensive Labour included, parts billed | Comprehensive Labour and parts included |
|---|---|---|---|
Repair labour covered | Billed per incident | ||
Replacement parts covered Consumables are excluded in every model. | Billed at agreed rates | ||
Preventive maintenance visits | On the contract calendar | On the contract calendar | |
Written response SLA | Best effort | ||
Asset register maintained | |||
Budget predictability How close the year-end total lands to the signed figure. | None, spikes with failures | Moderate, parts vary | High, fixed for the term |
Hardware failure risk sits with | You | Shared | Provider |
Best suited for | Very small setups, rare issues | Newer fleets still under OEM warranty | Mixed-age fleets, downtime-sensitive operations |
Three different promises. Know which one you are buying.
Warranty
A manufacturer’s promise that one product is free of defects for a stated period. It is about the product, not your operations.
- Covers manufacturing defects on that single device
- Repair or replacement, often at a service centre, on OEM timelines
- No response SLA, no preventive maintenance, no site visits
- Ends with the warranty period, typically 1 to 3 years
- The gap: nobody is responsible for your environment as a whole
Annual maintenance contract
A service agreement to keep your listed equipment operational for a year: preventive plus corrective maintenance against a written SLA.
- Covers the whole asset register, in and out of warranty
- Preventive calendar plus break-fix with response targets
- Routes in-warranty repairs to the OEM, handles everything around them
- Renewable yearly, scope adjusts as your fleet changes
- The gap: maintains what exists, does not own outcomes or strategy
Managed IT services
Full operational ownership of your IT: monitoring, security management, user support, vendor management, and planning, not just equipment upkeep.
- Covers operations end to end: infrastructure, cloud, users, security
- 24/7 monitoring that catches issues before tickets exist
- Owns outcomes: uptime, security posture, and an IT roadmap
- Includes maintenance, so it supersedes rather than complements an AMC
- The step up when you want an IT department, not a maintenance vendor
Which promise answers which question.
| Your question | Warranty | AMC | Managed services | |
|---|---|---|---|---|
| Who fixes a failed device? | The OEM, on their timeline | The provider, on a written SLA | The provider, often before you notice | |
| Who prevents failures? | Nobody | Preventive visits on a calendar | Continuous monitoring plus preventive work | |
| Who tracks your assets? | Nobody | Asset register, kept current | Full lifecycle management with refresh planning | |
| Who answers user how-to questions? | Nobody | Usually in scope as low-priority tickets | A staffed helpdesk | |
| Who owns security and strategy? | Nobody | Not in scope beyond agreed baselines | The provider, with reviews and a roadmap | |
| What does the cost curve look like? | Free until it expires, then unbudgeted | Fixed for the term, itemized by device | Fixed monthly fee for the whole operation |
What a good AMC SLA matrix looks like.
Resolution target
Within 4 hours
Example incidents
- Server, firewall, or core switch down
- Site-wide network or internet outage
- Ransomware or active security incident
- Billing or dispatch system down company-wide
Resolution target
Within 1 business day
Example incidents
- Department printer or shared drive down
- One branch offline, others working
- Backup job failed overnight
- Email failing for a group of users
Resolution target
Within 3 business days
Example incidents
- Single workstation running slow
- New user setup or device request
- Software install or configuration change
- Peripheral or accessory issues
Resolution target
Within 24 hours
Example incidents
- Cosmetic or minor display issues
- Documentation update requests
- Scheduled non-urgent maintenance
- How-to and training questions
Two tests for any SLA matrix you are offered: it must define response as engineer action, not acknowledgment, and it must commit to reporting performance against these targets in writing every month. A matrix nobody measures is decoration.
The 10 clauses to check in any AMC before signing.
Commercial clauses
- 1. Renewal termsRenewal must require written notice 30 to 60 days before term end, with your explicit consent. Silent auto-renewal that binds another full year is the single most common AMC trap.
- 2. Price-revision clauseIf the contract allows mid-term or renewal-time revisions, the trigger and the cap must be written down (a defined percentage or index, applied at renewal only). An uncapped "rates subject to revision" line makes the fixed fee fiction.
- 3. Liability capCheck what the provider is liable for when their work causes damage or data loss, and what the cap is. A liability cap of one month of fees on a contract guarding your servers deserves a negotiation, not a signature.
- 4. Scope-change mechanismHow devices get added or retired mid-term, at what notice, and how the fee adjusts. Without this clause, every new hire becomes a commercial negotiation.
- 5. Exit and handoverNotice period, refund or settlement of the unexpired term, and a listed handover pack: asset register, credentials, network documentation, runbooks. Silence on handover means your documentation leaves with the vendor.
Operational clauses
- 6. Standby equipmentWhen a covered device needs bench repair, does the provider supply a temporary unit, for which equipment classes, and within what time? For billing counters and critical workstations this clause is worth more than a faster repair promise.
- 7. Reporting cadenceMonthly written reports covering tickets, SLA performance against target, and asset health must be a contractual obligation, not a brochure feature. What gets reported gets honoured.
- 8. Sub-contractingMay the provider send third-party engineers to your site, and does the SLA still bind them? If sub-contracting is allowed, the prime contractor must remain fully responsible for performance and conduct.
- 9. Data handling and confidentialityEngineers touch machines holding your financials and customer records. The contract needs a confidentiality clause, a data-handling commitment covering repairs and disk disposal, and named handling for devices leaving your premises.
- 10. Working hours and after-hours termsWhich hours the SLA clocks run in, what happens to tickets raised outside them, and how after-hours or holiday visits are treated. An SLA that quietly pauses at 6 pm should say so in the contract, not in the dispute.
Six warning signs in an AMC quote.
Vague scope language
The quote says "complete IT maintenance" or "all IT support" without a scope schedule naming services, frequencies, and delivery modes. Vague scope always resolves in the vendor’s favour, because they decide later what was included.
- Ask: which services, at what frequency, on-site or remote?
- Ask: is the scope schedule part of the signed contract?
- A one-page quote for a 100-device fleet is a red flag by length alone
No asset register
The provider quoted without asking for, or building, an itemized device list. Without a register, every claim starts with an argument about whether the failed device was covered at all.
- Ask: will the signed contract annex a serial-numbered asset list?
- Ask: how are devices added and retired during the term?
- A provider who audits before quoting is showing you their discipline
No written SLA matrix
Response commitments exist only as verbal assurances or a marketing line like "fast response guaranteed". If the priority definitions and targets are not a table in the contract, they do not exist.
- Ask: what are the P1 to P4 definitions, response and resolution targets?
- Ask: does response mean engineer action or an automated acknowledgment?
- Ask: is SLA performance reported to us monthly in writing?
Silent automatic renewal
A renewal clause that extends the contract for another full term unless you object within a narrow window, with no obligation on the provider to remind you. It converts your forgetfulness into their revenue.
- Ask: does renewal require our written consent?
- Ask: how many days before term end must the provider notify us?
- Strike any clause renewing more than the original term length
Exclusions doing the real work
A generous-sounding scope followed by fine print excluding "misuse", "environmental factors", or "pre-existing conditions" without definitions. Broad undefined exclusions let the provider reclassify any expensive failure as out of scope.
- Ask for a definition of every exclusion term in writing
- Ask: who decides whether a failure falls under an exclusion, and how is it appealed?
- Compare the exclusions list length against the scope schedule length
No reporting, no reviews
The contract commits to no monthly report and no periodic review meeting. You will have no data on whether SLAs were met, what failed, or what is ageing, which means renewal time arrives with the vendor holding all the information.
- Ask: what does the monthly report contain, and can we see a sample?
- Ask: is there a quarterly review where misses are discussed?
- A sample report from an existing client tells you more than any brochure
How to compare two AMC quotes in five steps.
- 1
Normalize the asset list
Step 1
Confirm both quotes cover the identical device list, from the same asset register you supplied. A quote covering 60 devices is not cheaper than one covering 75. If either provider did not ask for an inventory before quoting, that itself is the finding.
- 2
Line up the scope schedules
Step 2
Put both scope schedules side by side, service by service: preventive visit frequency, remote support hours, patching, backup verification. Mark every service present in one and absent in the other. The gaps are where the price difference lives.
- 3
Compare the SLA matrices
Step 3
Compare priority definitions, response targets, and resolution targets line by line, and check whether response means engineer action or acknowledgment. A 30-minute acknowledgment SLA and a 30-minute engineer-response SLA are entirely different products.
- 4
Read exclusions and the parts clause
Step 4
This is where quotes actually diverge. Confirm which model each quote is (comprehensive or non-comprehensive), what the exclusions list contains, and how parts are priced when billed. An attractive base figure with an open-ended parts clause is not a fixed cost.
- 5
Score both against the 10 clauses
Step 5
Run both contracts through the clause checklist on this page: renewal, price revision, liability, standby equipment, reporting, sub-contracting, data handling, and exit. Then ask each provider for two references running a similar environment for over a year.
Why organizations keep renewing the contract model itself.
Annual maintenance contracts, frequently asked.
From research to a working contract.
IT AMC services in India
What our own AMC contracts contain: coverage tiers, the SLA matrix we sign, preventive calendars, and monthly reporting, for businesses anywhere in India.
Learn moreIT AMC Hyderabad
AMC with on-site coverage across Hyderabad: 2-hour on-site arrival, brand-agnostic hardware support, and 150+ active contracts under management.
Learn moreManaged IT Services India
When maintenance is not enough: full operational ownership of your IT, with monitoring, security management, and roadmap planning beyond the AMC model.
Learn moreSee what a properly written AMC looks like in practice.
Our India AMC page shows the contract structure described here as an actual service: the scope schedules, the SLA matrix, and the reporting cadence we sign our name to. Or send us your environment details and get a written, itemized quote to compare against anything else on your desk.
Related Services
Explore more solutions that work great with this service