Download institutional Service Level Agreement (SLA) templates in Word (.docx) and PDF, prepared using the statutory framework (review required before execution or filing). Features real-time statutory paper preview, interactive Gemini AI legal drafter (draft clauses with prompts, customize operational metrics, adapt tone, and generate Hindi / bilingual summaries), and Section 74 liquidated damages remedies.
Click an industry framework to instantly update the live contract preview, uptime SLOs, response matrices, and Section 74 damages.
Institutional commercial agreement formatted under Indian Contract Act 1872 (§ 73, 74 liquidated damages), DPDP Act 2023 data processing covenants, and CERT-In 6-hour cybersecurity reporting.
Statutory Enforceability Assured • Indian Contract Act, 1872 & IT Act, 2000Verified Format
This live preview renders a complete, institutional commercial agreement—incorporating the statutory Preamble, Corporate Identity Numbers (CIN), Recitals, 4-tier Incident Severity Matrix, Section 74 liquidated damages covenants, DPDP Act 2023 data processor provisions, and bilateral signature executions. You can edit any party details or metrics in the Interactive Customizer or use Gemini AI Drafter to insert custom clauses.
[Executed under the Indian Contract Act, 1872, Information Technology Act, 2000 & DPDP Act, 2023]
THIS SERVICE LEVEL AGREEMENT ("Agreement" or "SLA") is entered into on this 23 October 2026 ("Effective Date"), by and between:
ALPHA ENTERPRISES PRIVATE LIMITED
CIN: U72900MH2020PTC123456
101, Express Towers, Nariman Point, Mumbai - 400021, Maharashtra, India
Represented by: Rajesh Sharma (Director)
NEXUS CLOUD SOLUTIONS PRIVATE LIMITED
CIN: U72200DL2018PTC654321
Plot 45, Okhla Industrial Area Phase-III, New Delhi - 110020, India
Represented by: Amitabh Sen (Managing Director)
WHEREAS:
A. The Service Provider is engaged in the professional commercial business of providing designated enterprise technical, cloud, software maintenance, and operational workflows.
B. The Client desires to retain the Service Provider, and the Service Provider agrees to deliver the Services strictly in conformance with the service levels, uptime targets, incident resolution matrices, and liquidated damages remedies stipulated herein.
1.1 The Service Provider shall deliver the following designated operational and technology services during the agreed Term of 12 Months from the Effective Date:
2.1 Availability Target: The Service Provider warrants that the contracted services shall achieve a minimum availability of 99.95%, measured 24 hours per day, 7 days per week over each calendar billing month.
2.2 Permitted Maintenance: Uptime excludes pre-scheduled maintenance conducted during agreed windows: “Every second Sunday from 01:00 AM to 04:00 AM IST with 5 days advance notice.”. Any outage outside permitted windows constitutes unscheduled downtime.
3.1 Incidents and defects reported by Client shall be prioritized, acknowledged, and remediated in accordance with the statutory matrix below:
| Severity Tier | Impact Definition | Target Response | Target Resolution |
|---|---|---|---|
| Severity 1 (Critical) | Complete system outage; mission-critical business transactions halted; no workaround available. | 1 Hour | 4 Hours |
| Severity 2 (High) | Core feature severely impaired; business operations impaired but secondary workflows functioning. | 2 Hours | 8 Hours |
| Severity 3 (Medium) | Non-critical defect; acceptable operational workaround available; productivity partially affected. | 8 Hours | 24 Hours |
| Severity 4 (Low) | Cosmetic glitch, documentation inquiry, or general configuration enhancement request. | 24 Hours | 72 Hours |
4.1 Service Credit Formula: In the event of failure to meet contracted availability or resolution timelines, Client shall receive credits calculated at: 5% of monthly fees per 0.05% drop below 99.95%, subject to an aggregate monthly ceiling of 25% of monthly billing.
5.1 The Service Provider acts as a Data Processor under Section 8 of the Digital Personal Data Protection Act, 2023 (DPDP Act) and shall maintain technical safeguards prescribed under Section 43A of the Information Technology Act, 2000. In accordance with CERT-In Cyber Security Directions 2022, any cyber incident or unauthorized breach must be reported to Client within six (6) hours of detection.
6.1 Pursuant to the CERT-In Directions 2022, the Service Provider shall report any information security incident, cyber breach, or unauthorized system compromise to the Client within six (6) hours of detection.
7.1 This Agreement shall be governed by and construed in accordance with the substantive laws of India. Any controversy or dispute arising under this SLA shall be referred to arbitration in accordance with the Arbitration and Conciliation Act, 1996. The seat and venue of arbitration shall be New Delhi, India.
IN WITNESS WHEREOF, THE PARTIES HERETO HAVE DULY EXECUTED THIS SERVICE LEVEL AGREEMENT AS OF THE EFFECTIVE DATE FIRST WRITTEN ABOVE.
Authorized Signatory: Rajesh Sharma
Designation: Director
Entity: ALPHA ENTERPRISES PRIVATE LIMITED
Date: 23 October 2026
Authorized Signatory: Amitabh Sen
Designation: Managing Director
Entity: NEXUS CLOUD SOLUTIONS PRIVATE LIMITED
Date: 23 October 2026
A Service Level Agreement (SLA) is a legally enforceable contract or covenant executed between a service provider and a client that defines quantifiable operational performance standards—such as 99.9% uptime, Severity 1 incident response within 1 hour, and sub-second API latency—along with predetermined financial remedies (Service Credits) if thresholds are breached. Legally, an SLA is classified under the Indian Contract Act, 1872 as an accessory contract governed by Section 74 (liquidated damages) and Section 73. Operationally, SLAs are classified into three models: Customer-based SLAs, Service-based SLAs, and Multi-level SLAs. In modern technology infrastructure, cloud computing SLAs (e.g. AWS or Azure) establish recovery objectives (RPO/RTO) and data durability, while IT services contracts must strictly integrate data processor safeguards under Section 8 of the Digital Personal Data Protection Act, 2023 (DPDP Act).
A Service Level Agreement (SLA) is an enforceable agreement between a service provider (vendor, software developer, cloud provider, or outsourced agency) and a client that defines the quantitative and qualitative performance metrics expected during service delivery.
In commercial jurisprudence and enterprise IT governance, a Service Level Agreement is classified under two distinct dimensions:
Under Indian law, an SLA is classified as an accessory bilateral contract or a conditional performance covenant. Governed by Sections 73 and 74 of the Indian Contract Act, 1872, its financial remedy clauses operate as agreed pre-estimates of liquidated damages.
Under ITIL (Information Technology Infrastructure Library) standards, SLAs are classified into three operational categories:
The foundational purpose of an SLA is to bridge the gap between high-level commercial expectations and day-to-day technical execution. Specifically, an SLA is used for:
Corporate leaders, procurement heads, and legal counsel frequently encounter four related legal instruments. Understanding their distinct boundaries prevents jurisdictional defects and scope ambiguity:
| Instrument | Legal Enforceability | Primary Focus & Scope | Remedy for Breach |
|---|---|---|---|
| Master Services Agreement (MSA) | Legally Binding Contract | High-level legal rights: IP ownership, indemnification, liability caps, warranties, and termination. | Contract damages, specific performance, injunction, or court litigation. |
| Service Agreement | Legally Binding Contract | Commercial scope: specific deliverables, milestones, fee schedule, billing cadence, and payment terms. | Withholding payment, contract termination for breach, interest on overdue sums. |
| Service Level Agreement (SLA) | Legally Binding (Schedule/Annexure) | Technical performance metrics: 99.9% uptime, P1–P4 severity matrix, MTTR, maintenance windows, and DPDP 2023. | Predetermined Service Credits deducted from future invoices (Sec 74 liquidated damages). |
| Memorandum of Understanding (MoU) | Generally Non-Binding (unless formal intent expressed) | Preliminary roadmap expressing mutual intent to collaborate prior to executing definitive contracts. | Reputational/relationship termination; damages rarely enforceable unless binding covenants exist. |
When two corporate entities execute a B2B Service Level Agreement, the document must contain eight structural pillars to ensure operational clarity and judicial enforceability in India:
Defines exact covered software modules, cloud instances, and API endpoints. Explicitly lists out-of-scope tasks (e.g. customized third-party plugins, user network errors) to prevent scope creep.
Guarantees monthly availability percentage (99.9% or 99.95%). Defines the exact measurement formula: [(Total Minutes - Downtime Minutes) / Total Minutes] × 100.
Categorizes incidents into P1 (Critical Outage: 1 hr response / 4 hr fix), P2 (Major Impact: 2 hr response), P3 (Minor Glitch: 8 hr response), and P4 (Support Query: 24 hr response).
Establishes tiered invoice rebates (e.g. 5% credit for <99.9%, 15% for <98.5%) structured as genuine pre-estimated liquidated damages under Indian Contract Act, capped at 15%–25%.
Stipulates the client’s duty to provide timely bug logs, designate authorized IT coordinators, maintain supported client-side hardware, and ensure prompt network connectivity.
Excludes pre-notified scheduled maintenance windows (e.g. Sunday 01:00 AM–04:00 AM IST with 72h advance notice), government internet shutdowns, and Force Majeure events from downtime.
Appoints the vendor as Data Processor under Section 8 of DPDP Act 2023, requiring AES-256 encryption, role-based access, and mandatory 6-hour cybersecurity breach notice under CERT-In rules.
Grants the client immediate penalty-free contract termination rights if chronic breaches occur (e.g. 3 consecutive months of sub-98% uptime), coupled with 60-day data handover support.
In cloud computing (covering Infrastructure-as-a-Service, Platform-as-a-Service, and Software-as-a-Service), SLAs serve as the foundational trust mechanism between hyperscalers/SaaS providers and enterprise clients.
Leading cloud providers like Amazon Web Services (AWS) structure their Service Level Agreements around Monthly Uptime Percentage (MUP) across multi-availability-zone deployments. For instance, in the Amazon EC2 and Amazon S3 SLAs:
| Monthly Uptime Percentage | Permitted Monthly Outage | AWS Service Credit Percentage |
|---|---|---|
| 99.99% or greater | 0 to 4.38 minutes | 0% (SLA Target Met) |
| 99.0% to < 99.99% | 4.38 minutes to 7.3 hours | 10% Service Credit |
| 95.0% to < 99.0% | 7.3 hours to 36.5 hours | 25% Service Credit |
| < 95.0% | Over 36.5 hours | 100% Service Credit |
Service Level Agreements extend far beyond software code and cloud infrastructure. Outsourced business process vendors and staffing firms require domain-tailored Key Performance Indicators (KPIs):
| Outsourcing Vertical | Core Operational Metrics | Standard SLA Target Threshold | Remedy / Penalty Trigger |
|---|---|---|---|
| BPO & Contact Center | First Contact Resolution (FCR), Average Handle Time (AHT), Call Abandonment Rate | FCR ≥ 85%, Abandonment ≤ 3%, CSAT ≥ 90% | 5%–10% invoice discount if monthly CSAT drops below 85%. |
| IT Managed Services & AMC | Mean Time Between Failures (MTBF), Mean Time to Repair (MTTR), Patch Cadence | MTTR ≤ 2 hours, Security Patches deployed within 14 days | Per-hour delay deduction against monthly maintenance retainer. |
| Staffing & Recruitment | Time-to-Shortlist, Candidate Screening Accuracy, Replacement Guarantee | Profiles submitted within 5 business days; 90-day replacement warranty | Free candidate replacement or 100% agency placement fee credit if candidate leaves within 90 days. |
When drafting SLA penalty clauses in India, counsel must navigate the distinction betweenliquidated damages and penalties under Section 74 of the Indian Contract Act, 1872.
In the landmark decisions of Fateh Chand v. Balkishan Dass (AIR 1963 SC 1405),Maula Bux v. Union of India (1969 2 SCC 554), and ONGC v. Saw Pipes Ltd (2003 5 SCC 705), the Supreme Court of India established binding principles:
1. Genuine Pre-Estimate of Loss: If parties agree on a predetermined sum that genuinely reflects the foreseeable loss caused by delayed performance, the court will enforce it without requiring the injured party to prove actual financial loss.
2. Prohibition on Penal Forfeitures: If an SLA clause demands astronomical penalties completely disproportionate to the contract value, Indian courts will strike it down as an unenforceable penal forfeiture and award only reasonable compensation.
3. Best Practice for SLA Drafters: Always label remedies as "Service Credits", explicitly recite that they represent a genuine pre-estimate of loss under Section 74, and cap them at a reasonable ceiling (15% to 25% of monthly billing).
Under Section 8 of the Digital Personal Data Protection Act, 2023 (DPDP Act), whenever a cloud, IT, or BPO vendor processes personal data on behalf of an enterprise client (Data Fiduciary), the vendor acts as a Data Processor.
To maintain statutory compliance, the SLA must incorporate:
Under Section 35 of the Indian Stamp Act, 1899, any agreement that is not duly stamped is inadmissible as evidence in court and cannot be acted upon by an arbitrator until the deficient duty and penalty (up to 10 times) are paid. Standard commercial agreements are stamped under Article 5 (Agreement or Memorandum of Agreement) of the respective state stamp schedule:
| State / Union Territory | Governing Stamp Schedule | Prescribed Stamp Duty (General Commercial SLA) |
|---|---|---|
| Maharashtra | Maharashtra Stamp Act (Article 5(h)) | ₹500 (or 0.1%–0.2% depending on contract value) |
| Delhi (NCT) | Indian Stamp (Delhi Amendment) Act (Article 5(c)) | ₹100 (Non-judicial stamp paper) |
| Karnataka | Karnataka Stamp Act, 1957 (Article 5(j)) | ₹200 to ₹500 |
| Tamil Nadu | Indian Stamp (Tamil Nadu Amendment) Act (Article 5(j)) | ₹100 to ₹300 |
| Uttar Pradesh | Indian Stamp (UP Amendment) Act (Article 5) | ₹100 |
| West Bengal | Indian Stamp (West Bengal Amendment) Act (Article 5) | ₹100 to ₹500 |
"The parties agree that Service Credits constitute genuine pre-estimated liquidated damages under Section 74 of the Indian Contract Act, 1872, and not a penalty."
Statutory and operational answers for founders, company secretaries, and vendor managers.
A Service Level Agreement (SLA) is a legally binding commitment between a service provider and a client that defines the exact quality, availability, response times, and performance standards expected of the service. It is used to align operational expectations, establish objective performance metrics (such as 99.9% uptime), mitigate business risk, and prescribe non-litigious financial remedies (Service Credits) when thresholds are breached.
Legally, an SLA is classified as an accessory contract or conditional covenant governed by the Indian Contract Act, 1872 (specifically Section 74 regarding liquidated damages). Operationally, SLAs are classified into three types: (1) Customer-based SLA (covering all services delivered to a single customer); (2) Service-based SLA (a standardized baseline SLA across all customers using one service, such as AWS or SaaS); and (3) Multi-level SLA (combining Corporate, Customer, and Service level tiers).
The primary purpose of an SLA is fourfold: (1) Setting objective, measurable benchmarks for service delivery; (2) Allocating operational risk between vendor and client; (3) Establishing automated escalation and resolution timelines for system outages; and (4) Providing pre-determined financial compensation (service fee discounts) without the delay and expense of court litigation.
A comprehensive SLA consists of eight core components: (1) Service Description & Scope; (2) Service Availability & Uptime Metrics; (3) 4-Tier Incident Severity Matrix (P1–P4 response and resolution times); (4) Service Credit & Liquidated Damages calculation formulas; (5) Client Dependencies and Responsibilities; (6) Exclusions & Excused Downtime; (7) Data Privacy & Security (DPDP Act 2023 & CERT-In reporting); and (8) Chronic Failure Exit Rights & Arbitration Governance.
A Contract (such as a Master Services Agreement) is the overarching legal foundation establishing legal capacity, intellectual property ownership, indemnities, liability caps, and dispute resolution. An SLA is a specialized operational schedule or annexure attached to that contract that specifically measures performance quality, system uptime, and operational remedies.
A Service Agreement outlines what services will be provided, commercial pricing, payment terms, and duration. A Service Level Agreement (SLA) defines how well those services must be performed—setting quantifiable technical standards (e.g. 99.95% availability, sub-1 hour P1 incident response) and penalties if the provider falls short.
A Memorandum of Understanding (MoU) records mutual intent and preliminary alignment between parties before a definitive commercial agreement is drafted, and is often non-binding. In contrast, an SLA is a legally enforceable, binding contract with defined financial liabilities and service credit penalties executed under the Indian Contract Act, 1872.
In cloud computing (IaaS, PaaS, SaaS), an SLA specifies infrastructure availability (such as 99.9% or 99.99% uptime), network latency thresholds, data durability (e.g. AWS S3 11-nines durability), Recovery Time Objectives (RTO), Recovery Point Objectives (RPO), and tiered service credit rebates for unscheduled cloud downtime or API outages.
AWS SLAs (such as for Amazon EC2 or Amazon S3) calculate Monthly Uptime Percentage (MUP). If MUP drops below 99.99% but remains above 99.0%, AWS provides a 10% service credit; if uptime drops between 99.0% and 95.0%, a 25% credit applies; and if uptime falls below 95.0%, AWS credits 100% of the affected service billing against future invoices.
An SLA between two enterprise companies must clearly define: authorized corporate representatives, explicit in-scope and out-of-scope boundaries, service availability windows, escalation contact matrix, audit rights for SOC 2 / ISO certifications, data processing protocols under Section 8 of the DPDP Act 2023, Section 74 liquidated damages caps (15%–25%), and arbitration seated under the Arbitration and Conciliation Act, 1996.
A BPO (Business Process Outsourcing) SLA governs customer support and back-office operations. It tracks operational metrics including First Contact Resolution (FCR ≥ 85%), Average Handle Time (AHT), Call Abandonment Rate (≤ 3%), Quality Assurance (QA ≥ 92%), and Customer Satisfaction (CSAT ≥ 90%).
You can download professional, legally verified Service Level Agreement templates in editable Microsoft Word (.docx) and printable PDF format directly from this page using the 1-click download buttons above. Formats are fully vetted under Indian contract law for Cloud/IT SaaS, Vendor Management, Software AMC, and Recruitment workflows.
Under Indian law, SLA financial remedies are governed by Section 74 of the Indian Contract Act, 1872. Indian courts enforce "liquidated damages" if they represent a genuine pre-estimate of loss suffered due to service failure. If the clause imposes an arbitrary, exorbitant penalty without relation to actual damage, courts will decline to enforce it as a penal forfeiture. Hence, SLAs typically cap service credits at 15% to 25% of monthly billing.
Standard SLAs categorize incidents into four tiers: Severity 1 (Critical: core system outage, response within 1 hour, resolve within 4 hours); Severity 2 (High: major degradation without workaround, response within 2 hours, resolve within 8 hours); Severity 3 (Medium: partial function bug with workaround, response within 8 hours, resolve within 24 hours); and Severity 4 (Low: minor cosmetic query or documentation request, response within 24 hours, resolve within 72 hours).
Commercial agreements such as SLAs are executed on non-judicial stamp paper under Article 5 of the relevant State Stamp Act. Stamp duty varies by state: in Maharashtra, it is typically ₹500 (or 0.1%–0.2% depending on contract value); in Delhi, ₹100; in Karnataka, ₹200–₹500; and in Uttar Pradesh, ₹100. Unstamped agreements cannot be admitted as evidence in an Indian court under Section 35 of the Indian Stamp Act, 1899 until stamp duty and penalties are paid.
Yes. When an IT, cloud, or SaaS service provider processes personal data belonging to the client or its end-users, the provider acts as a Data Processor under Section 8 of the DPDP Act, 2023. The SLA must stipulate technical security safeguards, data confidentiality, strict breach notification timelines (recommended within 6 hours to align with CERT-In directives), and data erasure protocols upon contract termination.
99.9% uptime ("Three Nines") permits up to 43.8 minutes of unscheduled downtime per month (8.76 hours per year). 99.99% uptime ("Four Nines") permits only 4.38 minutes of unscheduled downtime per month (52.6 minutes per year), requiring high-availability multi-region redundancy.