Service Level Agreement (India)

A Service Level Agreement in India records the bargain between the parties, fixing their respective rights, duties and remedies.

India's IT and technology services sector generated approximately USD 245 billion in revenues in FY 2023-24, making SLAs a commercially significant instrument across thousands of outsourcing, managed services, cloud, and SaaS contracts. Major Indian IT service providers including Tata Consultancy Services (TCS), Infosys, Wipro, HCL Technologies, and Tech Mahindra routinely incorporate detailed SLAs into their contracts with domestic and international customers.

The legal enforceability of service credit and penalty clauses in Indian SLAs is governed by Section 74 of the Indian Contract Act 1872, which provides that where a contract stipulates a sum to be paid in the event of breach, the party suffering the breach is entitled to receive reasonable compensation — not exceeding the stipulated sum — regardless of whether actual damage is proved. The Supreme Court of India in ONGC v SAW Pipes Ltd (2003) 5 SCC 705 clarified that Section 74 permits enforcement of pre-agreed liquidated damages clauses where the stipulated amount is a genuine pre-estimate of loss and not a penalty in terrorem. Service credits structured as a reasonable pre-estimate of the damage caused by SLA non-performance are enforceable under Section 74.

An SLA is typically structured in layers corresponding to different service components. Availability SLAs cover infrastructure uptime — servers, networks, databases, and application platforms. Performance SLAs cover response time, throughput, and transaction processing rates. Support SLAs cover incident response and resolution times, differentiated by severity. Scheduled maintenance SLAs define maintenance windows during which downtime is excluded from uptime calculations.

India-specific SLA considerations include the use of Indian Standard Time (IST, UTC+5:30) as the reference timezone for all SLA calculations, the definition of Indian national holidays (three mandatory national holidays — Republic Day on 26 January, Independence Day on 15 August, and Gandhi Jayanti on 2 October — plus regional holidays) for business-hours SLA calculations, and GST treatment of service credits (which are typically treated as a reduction in the taxable value of the services rather than a separate payment, with implications for GST invoicing under the CGST Act 2017).

Dispute resolution under Indian SLAs typically provides for arbitration under the Arbitration and Conciliation Act 1996, with the arbitral seat in a major Indian commercial city. For SLA disputes involving MSME vendors, the MSME Facilitation Council established under the Micro, Small and Medium Enterprises Development Act 2006 (MSMED Act) provides an alternative dispute resolution mechanism with mandatory conciliation before arbitration.

A Service Level Agreement for India is required whenever an Indian business engages an IT service provider, managed services vendor, cloud provider, or SaaS company under a contract where the quality and continuity of services are critical to business operations and regulatory compliance.

The Service Level Agreement infrastructure outsourcing — where a company hands over management of its servers, network, storage, and end-user computing to a managed services provider — requires a detailed SLA specifying uptime commitments for each infrastructure component, patching and maintenance windows, backup and recovery objectives (Recovery Time Objective and Recovery Point Objective), and security incident response times. Downtime in managed infrastructure can halt business operations, making SLA enforcement critical.

Cloud services contracts with Indian cloud providers such as Tata Communications, Airtel Business, NTT Data India, and Reliance Jio Cloud, and with international providers' India-region deployments (AWS ap-south-1 Mumbai, Google Cloud asia-south1 Mumbai, Azure Central India), require SLAs with Indian-law governance to provide an enforceable remedy framework for Indian customers when availability commitments are missed.

Banking and financial services companies regulated by the Reserve Bank of India, insurance companies regulated by IRDAI, and capital markets intermediaries regulated by SEBI must include IT service SLAs in their vendor contracts to comply with technology risk management guidelines. The RBI's Master Direction on IT Governance, Risk, Controls and Assurance Practices (2023) requires regulated entities to have formal SLAs with IT vendors specifying availability, performance, and security requirements, with escalation procedures and service credit mechanisms.

Healthcare organisations implementing hospital information systems (HIS), electronic medical record (EMR) systems, diagnostic laboratory information systems (LIS), or health data platforms must include SLAs with availability and data integrity commitments that meet the requirements of the Digital Health Mission (NHA) standards and the National Health Data Management Policy.

A standalone SLA as a schedule to a Master Service Agreement (MSA) is used when the parties have an ongoing services relationship covering multiple service lines — the MSA sets out the general terms and the SLA schedule specifies the operational commitments for each service. Updating the SLA schedule without amending the MSA allows parties to adjust service commitments as the scope of services evolves.

An India Service Level Agreement governed by the Indian Contract Act 1872 must contain specific provisions to create an enforceable performance framework and provide meaningful remedies for SLA failures under Indian law.

Service description and scope defines each service component covered by the SLA — specifying system names, service identifiers, geographic scope (data centre locations, city presence), and any exclusions. Clear scope prevents disputes about whether a particular outage falls within the SLA's coverage. The scope must align with the services described in the parent Master Service Agreement or SaaS Agreement.

Availability and uptime commitment specifies the minimum percentage availability for each covered service component during each measurement period (typically calendar month). The definition of 'availability' must be precise — distinguishing between full outage (service completely unavailable) and degraded performance (service available but below performance thresholds). Scheduled maintenance windows during which downtime is excluded from availability calculations must be defined, with the maintenance window announced minimum 48–72 hours in advance.

Incident severity classification and response/resolution times categorises incidents by business impact — Critical (P1), High (P2), Medium (P3), and Low (P4) — and assigns specific response time targets (time to first substantive acknowledgement) and resolution time targets (time to restore service or provide an acceptable workaround) to each severity level. P1/Critical incidents affecting production systems must have the most aggressive targets (response within 15–30 minutes, IST, 24x7).

Service credit formula and calculation specifies the service credits payable for SLA failures — typically as a percentage of the monthly service fee for the affected service component, escalating as the shortfall increases. The formula must specify: the measurement period, the credit percentage per tier of shortfall, the maximum monthly credit cap (typically 25–50% of monthly fee), and whether credits are applied to future invoices or paid in cash. Section 74 of the Indian Contract Act 1872 requires service credits to be a genuine pre-estimate of loss to be enforceable.

Escalation matrix lists the named contacts at each escalation level — from front-line support to senior management — with direct contact numbers (mobile, IST-available hours), email addresses, and the trigger conditions for escalating to each level. Both the vendor's and the customer's escalation contacts should be specified.

Measurement methodology and reporting specifies how each metric is measured (third-party monitoring tool, vendor internal monitoring, or jointly agreed tool), the authoritative data source for SLA calculations, the format and frequency of SLA performance reports (monthly report within 5–10 business days after month end), and the customer's right to audit performance data.

Exclusions and force majeure lists events excluded from SLA coverage — scheduled maintenance, force majeure events, Internet/ISP outages beyond the vendor's control, customer-caused failures (incorrect configurations, authorised changes that cause outages), and events beyond the mutually agreed service boundary. Exclusions must be narrowly and precisely defined to prevent vendors from inappropriately invoking them.

Termination for persistent SLA failure provides the customer with the right to terminate the agreement without penalty if the vendor fails to meet the SLA in a specified number of months within a rolling period (typically 3 months in a 6-month window), or if availability falls below a floor (e.g., 95%) in any single month. This termination right, enforceable under Sections 39 and 73 of the Indian Contract Act 1872, is the customer's ultimate commercial remedy for sustained service failures.

Under Indian law, the Indian Contract Act 1872 governs contractual obligations, with Section 10 setting essential requirements for valid agreements. The Companies Act 2013 regulates corporate entities through the Registrar of Companies (ROC) and Ministry of Corporate Affairs (MCA). The Industrial Disputes Act 1947 and state labour commissioners govern employment disputes. The Information Technology Act 2000 and IT (Reasonable Security Practices) Rules 2011 protect personal data. The Income Tax Act 1961 and Goods and Services Tax Act 2017 govern tax obligations through the Central Board of Direct Taxes (CBDT) and GST Council. The forms-legal.com Service Level Agreement (India) template covers the mandatory elements under Indian Contract Act, 1872.