February AIContract Templates

India · Business & partnerships

Service Level Agreement (SLA)
Contract Template for India

Indian B2B SLA for a defined production service, with measurable availability, incident targets, exclusions, service credits and continuity controls.

Governing law: IndiaPublished templateUpdated 2026-10-03
SERVICE LEVEL AGREEMENT (SLA)
SERVICE LEVEL AGREEMENT (SLA) India Date: [date]. Place of execution: [city and State or Union Territory]. Customer: [legal name, entity type, registration number, GSTIN and address] (Customer). Service Provider: [legal name, entity type, registration number, GSTIN and address] (Provider). Covered Service means the production service identified in Schedule 1. Service Month means each calendar month during the Term. Available means the Covered Service can perform the Critical Functions in Schedule 1 from the agreed monitoring point. Unavailable Minute means a minute when it is not Available, excluding Excluded Time. Service Credit means the fee reduction calculated under Schedule 2. Incident means an unplanned interruption or material degradation of the Covered Service. 1. Covered service The Provider must supply the Covered Service throughout the Term in accordance with Schedule 1 and use reasonable skill and care. The SLA applies only to the environment, hours, users, volumes, dependencies and Critical Functions stated there. New scope or a changed dependency requires a written change signed by both parties. The Provider remains responsible for its personnel and approved subcontractors. The Customer must provide the access, information, connectivity, licences and decisions allocated to it in Schedule 1. 2. Availability Monthly Availability Percentage is calculated as: (Eligible Minutes minus Unavailable Minutes) divided by Eligible Minutes, multiplied by 100. Eligible Minutes are the minutes in the Service Month within the coverage window in Schedule 1, less Excluded Time. Measurements must use the monitoring source and time standard in Schedule 2. Excluded Time is only: notified planned maintenance within the agreed window; emergency maintenance reasonably necessary to protect security or service and notified as soon as practicable; Customer-caused outage; a third-party dependency expressly allocated to the Customer; suspension permitted by this SLA; or an event beyond reasonable control that the Provider could not reasonably avoid or overcome. An exclusion applies only to the part and period actually caused by it. 3. Incident response The Customer must report an Incident through the stated channel with the information reasonably available. The Provider must classify it under Schedule 2, acknowledge it within the Response Time, investigate, take reasonable restoration steps and provide updates at the stated interval. Response Time begins when a complete report reaches the channel during the applicable coverage hours. Waiting for necessary Customer access, information or approval suspends the clock and must be recorded. For a Critical Incident the Provider must maintain reasonable continuous restoration efforts during the coverage window, escalate to the named managers and provide a preliminary incident summary within [two] Business Days after restoration. Business Day means a day other than Sunday or a public holiday at the Customer's address. A root-cause report for a Critical Incident is due within [five] Business Days unless the parties agree another date. 4. Maintenance and change Planned maintenance requires at least [five] Business Days' notice and must stay within the Schedule 2 window. The Provider must assess production changes, keep rollback measures and notify changes likely to affect the SLA. Emergency changes must be limited to what is reasonably required and reported promptly. 5. Measurement and reports The Provider must preserve reliable monitoring and Incident records. Within [five] Business Days after each Service Month it must provide Availability, Unavailable Minutes, exclusions, Incidents, response performance and earned Service Credits. The Customer may challenge a report within [ten] Business Days with reasonable particulars; the parties must compare source records in good faith. If monitoring fails, the parties must use the best contemporaneous evidence, including service logs and user reports. The Provider may not treat missing Provider-controlled monitoring as proof of Availability. 6. Service Credits Service Credits accrue according to Schedule 2 and are applied to the next invoice or refunded if no further invoice is due. Credits are calculated against the monthly fee for the affected Covered Service, not unrelated services. The total credit for a Service Month is capped at [percentage] of that fee. A Service Credit is the agreed price adjustment for the measured shortfall. It is not the sole remedy for repeated material failure, repudiation, fraud, wilful misconduct, confidentiality or data breach, death or personal injury, or liability that cannot lawfully be limited. No double recovery is permitted for the same loss. 7. Fees, GST and payment The Customer must pay the fees in Schedule 3. Fees are [inclusive/exclusive] of GST. The Provider must issue a valid tax invoice and the Customer must pay an undisputed amount within [thirty] days. A genuinely disputed amount may be withheld after prompt written reasons. The Provider must disclose its micro or small enterprise status and valid Udyam registration. Mandatory payment periods, interest and remedies under the Micro, Small and Medium Enterprises Development Act 2006 remain unaffected. 8. Security, data and continuity The Provider must apply the security, backup, recovery and continuity measures in Schedule 1, limit privileged access and promptly report actual unauthorised access to Customer systems or data. If it processes personal data, the parties must record legally required processing instructions and safeguards before processing. The Customer must maintain the backups and continuity responsibilities expressly allocated to it. Each party must protect the other's non-public information with reasonable care and use it only for this SLA. Permitted disclosure is limited to bound personnel, advisers and lawful requirements after notice where lawful. 9. Term, suspension and ending This SLA begins on [start date] and ends on [end date]. The Provider may suspend only the affected part for an immediate security threat, unlawful use or an undisputed amount more than [fifteen] days overdue after a further [five]-Business-Day written warning. It must limit the suspension, preserve data and restore promptly when the cause ends. A party may terminate for material breach not cured within [ten] Business Days after notice where cure is possible, or immediately for fraud, insolvency or unlawful performance. Repeated failure means [three] Critical Incidents or Availability below [percentage] in [three] Service Months within a rolling [six]-month period and is a material breach if not remedied under an agreed corrective plan. 10. General The Provider warrants authority and that the Covered Service will materially conform to Schedule 1. Rights that cannot lawfully be excluded remain unaffected. Neither party is liable for indirect or consequential loss or lost profits except where law prohibits exclusion. Aggregate liability is capped at [twelve months' fees/two times those fees], excluding fraud, wilful misconduct, confidentiality or data misuse, infringement, death or personal injury, unpaid fees and non-limitable liability. Changes and waivers must be signed in writing. Notices are effective on proven delivery by hand, registered post or email. This SLA and its schedules are the entire agreement on the stated service levels. Indian law governs. Courts at [city and State or Union Territory] have jurisdiction, subject to mandatory statutory forums. The parties must complete applicable stamping at the place of execution; [party] bears the duty. Counterparts and legally valid electronic signatures may be used. SCHEDULE 1 - SERVICE AND DEPENDENCIES Covered Service, Critical Functions, production environment and coverage window: [details]. Capacity, supported volumes, Customer dependencies and third-party allocations: [details]. Security, backup, recovery objective and continuity responsibilities: [details]. SCHEDULE 2 - TARGETS AND CREDITS Monitoring point, source and time standard: [details]. Availability target and planned-maintenance window: [details]. Incident classes, Response Times, restoration targets, updates and escalation: [details]. Service Credit tiers, calculation and monthly cap: [details]. SCHEDULE 3 - FEES Monthly fee for each Covered Service, GST and invoice schedule: [details]. Provider MSME status and Udyam number: [details or not applicable]. SIGNATURES For the Customer: [authorised signatory, office, signature and date]. For the Provider: [authorised signatory, office, signature and date]. Witnesses if required: [names, addresses, signatures and dates].

Licensed under CC BY 4.0. Attribution is required when you publish or redistribute this Template or an adapted version to the public. Attribution is not required merely because you use or adapt the Template for your own business or legal purposes, including preparing, negotiating, signing, or exchanging an agreement with a counterparty. License details.

More templates for India