Software Annual Maintenance Contract (AMC) in India: What Should It Cover?
A software Annual Maintenance Contract should clearly define post-go-live support. Explore the essential terms to check, including coverage, response and resolution times, exclusions, reporting and liability.

By Ankit Rawat·Published: November 15, 2026 at 12:35 AM ISTAn Annual Maintenance Contract Should ensure the software functions correctly post Go-live. However in many cases it will be provided as a single page with no details other than the words "support".
What does India data says:
Mantra Identity Devices & System, a business unit of Mantra Softech India provide details of their Annual Maintenance Contract Policy. They provide response times based on the priority of the issue. Priority 1 (critical impact to service): 4 business hours, Priority 2: 1 business day, Priority 3: 3 business days and Priority 4 (general enquiries): 5 business days. Support is provided Monday to Friday 09:00 to 18:00 IST and does not include public holidays. It then goes on to say that the above times "are indicative only and do not guarantee the issue will be resolved, repaired, replaced or restored". Any services not specifically mentioned in the contract shall be deemed to be excluded. Upgrades, enhancements, third party software, data back-up, data restoration, migration and bespoke software development are excluded. There is a maximum liability of the total AMC fees in the last 12 months.
Note: This is just one vendors policy, it has been put in place to protect them and relates to identity devices, firmware and software. There is no date provided and it states that if there is a signed agreement this shall take precedence. This is an example of how the clauses may look.
What should be in the Software AMC?
As seen the above policy shows how important it is to have everything clear.
- Scope: What applications, version and environment are covered. Does it include any bug fixes, security patches or small updates? What is considered a new feature?
- Response/Resolution Times: Just providing a response time does not give any insight into how quickly the issue will be resolved. Provide the target times for restoring the service depending on the priority. Define what each priority means with examples.
- Support Hours & Communication: Define what hours the support will be available, what time zone it is in, any public holidays and how to log the request. If you are paying for faults to occur outside of these hours then you should pay for out of hours cover.
- Exclusions: Define how third party components, data restoration, migration and enhancements will be managed and priced.
- Reporting: Request a monthly report detailing the tickets raised, times to respond and recurring issues. An annual review should also be provided.
- End of Contract: Define what will happen to the documentation and access.
Things to consider when signing a Software AMC
- What applications, versions and environments are covered?
- Will it include patches and small updates? Who will decide what is considered an enhancement?
- What are the response and restore times for each priority?
- What hours will support be available? How much will it cost for out of hours calls?
- What is excluded? How will excluded work be priced?
- How is liability restricted? What service credits will be offered?
How we handle Software AMC
We start by understanding what applications you are using and what level of support you require. This is then added to the scope, with priorities, target times and exclusions. We then agree how you would like reporting to be handled so you can see how the support is performing.
If you are looking to draft or review a Software AMC please get in touch. See more on our services page
Frequently asked questions
Q1. What is a Software Annual Maintenance Contract (AMC)?+
A Software AMC is an agreement that defines the maintenance and support a provider will offer after an application goes live. It should specify the applications covered, support scope, service priorities, response targets, exclusions and reporting arrangements.
Q2. What should a Software AMC include?+
A Software AMC should clearly define the applications and versions covered, bug fixes and updates, response and service-restoration targets, support hours, communication channels, exclusions, reporting requirements and end-of-contract responsibilities.
Q3. What is the difference between response time and resolution time in a Software AMC?+
Response time refers to how quickly the support provider acknowledges an issue. Resolution time refers to how long it takes to fix the issue or restore the affected service. An AMC should define both rather than relying only on response targets.
Q4. What services are commonly excluded from a Software AMC?+
Depending on the agreement, exclusions may include upgrades, feature enhancements, third-party software, data backup and restoration, migration and bespoke software development. These exclusions should be clearly documented and priced separately where applicable.
Q5. Why should a Software AMC include monthly reporting?+
Monthly reporting helps businesses review tickets raised, response performance and recurring issues. It provides visibility into support performance and gives both parties a basis for reviewing the agreement.
Q6. What should businesses check before signing a Software AMC?+
Businesses should check the applications and environments covered, patch and update provisions, response and restoration targets, support hours, out-of-hours charges, exclusions, liability limits and any service credits.
Need clarity on your Software AMC?
Whether you are drafting a new agreement or reviewing an existing one, EICE can help define the support scope, priorities, service targets, exclusions and reporting requirements.