Service Level Agreement

Service Level Agreement: complete guide

Introduction

A Service Level Agreement, usually called an SLA, is a contract that sets out the standard of service a provider promises to deliver and what happens if that standard is not met. Where a general services contract says what will be done, an SLA says how well, how fast and how reliably it will be done. It turns expectations such as "quick support" or "high uptime" into measurable commitments: a response time in hours, a resolution time for each severity level, an availability percentage measured over a month, or an accuracy rate for processed transactions.

SLAs are common in information technology, software as a service, cloud hosting, managed IT support, business process outsourcing, logistics, facility management, housekeeping and security services, payroll processing and customer support outsourcing. They can be signed as a standalone agreement, as a schedule to a Master Service Agreement, or as an annexure to a specific statement of work. In India, an SLA is a contract governed by the Indian Contract Act, 1872, and it must meet the usual requirements of a valid contract: free consent, lawful object, lawful consideration and parties who are competent to contract.

A weak SLA causes more disputes than having no SLA at all. Metrics that are not defined clearly, measurement methods that each side reads differently, service credits that look like penalties, and exclusions that swallow the commitments are among the most frequent reasons that service relationships end up in arbitration. Indian courts also look closely at clauses that fix a sum payable on breach, because under section 74 of the Contract Act a party can recover only reasonable compensation up to the stated amount, not an automatic penalty. Drafting service credits, caps and termination triggers with this in mind matters.

Our team drafts SLAs that match the way your service actually works. We take time to understand your service, your systems for measuring performance and the commercial balance between you and the other side, and then prepare a document that is clear to the operations team as well as to lawyers. This page explains who needs an SLA, what it should contain, the legal points to consider, our process, the information we need, timelines, our fee and what to do once the agreement is signed.

Who Needs It

An SLA is useful for any business that provides or buys a service where performance can be measured over time. Typical users include:

• Software and cloud service providers who promise platform availability, support response times, data backup frequency and recovery time objectives to their customers.
• Managed IT and technical support companies that handle helpdesk tickets, network monitoring, device management or cybersecurity monitoring for clients.
• Business process outsourcing and call centre operators that commit to call answer rates, average handling time, first-call resolution or data entry accuracy.
• Logistics, courier and warehousing businesses that promise pickup windows, delivery timelines, damage rates and inventory accuracy.
• Facility management, housekeeping and security agencies that provide manpower on site and commit to attendance, replacement of absent staff and cleanliness or patrol standards.
• Enterprises and startups buying critical services, who want clear remedies if a vendor's service falls short, rather than relying on general promises.
• Internal shared service centres within a group of companies, which use SLAs to set expectations between group entities and support transfer pricing documentation.
• Government and public sector contractors, where tender documents often require a defined SLA with service credits and reporting.

If you already have a services agreement but it does not contain measurable standards, an SLA can be added as a schedule without rewriting the whole contract. If you do not yet have a main contract, we can advise whether a combined agreement or a Master Service Agreement with a separate SLA schedule suits your business.

Key Benefits

• Clear and measurable expectations. Each service is tied to a defined metric, a target level and a measurement method, so both sides know exactly what good performance looks like.
• Fewer disputes. When metrics, reporting and remedies are agreed upfront, disagreements are resolved by looking at the numbers instead of arguing about intentions.
• Fair and enforceable remedies. Service credits, fee reductions and step-in or termination rights are structured so that they reflect a genuine pre-estimate of loss and can stand up under Indian contract law.
• Better vendor management. Customers get regular performance reports, review meetings and an escalation path, which make it easier to manage a vendor and to decide on renewals.
• Protection for the provider. A well-drafted SLA also protects the service provider through exclusions for scheduled maintenance, customer-caused issues and events beyond its control, and through an overall cap on service credits.
• Support for pricing. Different service tiers, such as standard and premium support, can be priced against different service levels, which helps providers sell upgraded plans.
• Continuous improvement. Review clauses allow targets to be reset as the service matures, technology changes or volumes grow.

SLA versus a general services contract. A general services contract sets out the scope of work, payment terms, intellectual property, confidentiality, liability and termination. An SLA sits on top of that framework and deals only with performance: which metrics apply, how they are measured, how often they are reported, and what follows a shortfall. Many businesses keep the SLA as a separate schedule so it can be updated each year without renegotiating the legal terms.

How service credits work in practice. Suppose a hosting provider commits to monthly availability of a stated percentage. The SLA defines how downtime is counted, excludes scheduled maintenance announced in advance, and sets a table of credits, for example a percentage of the monthly fee for each band of shortfall. The credit is adjusted against the next invoice, there is a monthly cap, and repeated serious failures over a defined period give the customer a right to terminate. Writing this mechanism carefully avoids the argument that the credit is a penalty.

Eligibility and Legal Requirements

There is no registration or licence needed to sign an SLA, but the agreement must meet the requirements of Indian law to be valid and enforceable:

• Valid contract under the Indian Contract Act, 1872. The parties must be competent to contract, consent must be free, and the object and consideration must be lawful. For a company or LLP, the person signing should be authorised by a board resolution, partners' resolution or a power of attorney.
• Reasonable compensation, not penalties. Under sections 73 and 74 of the Contract Act, a party that suffers a breach can recover compensation for loss that arises naturally from the breach. Where a sum is named in the contract, courts award reasonable compensation up to that sum. Service credits should therefore be linked to the value of the service affected.
• Limitation of liability. Clauses that exclude indirect losses and cap overall liability are common and generally enforced between commercial parties, but they must be clearly worded and must not be against public policy.
• Stamp duty. An SLA is an instrument chargeable to stamp duty under the Indian Stamp Act, 1899 or the stamp law of the relevant state. The rate depends on the state and the nature of the agreement. Unstamped or under-stamped agreements cannot be admitted as evidence until the duty and penalty are paid. Government stamp duty is payable at actual.
• Electronic execution. Under the Information Technology Act, 2000, contracts can be formed electronically and signed using electronic signatures, subject to the exceptions listed in that Act. Stamp duty still applies, and many states allow e-stamping.
• Data protection. Where the service involves handling personal data, the Digital Personal Data Protection Act, 2023 and the rules notified under it place obligations on the data fiduciary and require it to have a valid contract with any data processor. SLAs for such services often include security, breach notification and data return clauses.
• Sector-specific rules. Services to regulated entities such as banks, insurers, payment system operators or listed companies may need to meet outsourcing guidelines issued by the relevant regulator, including audit rights, business continuity and regulator access.
• Labour law compliance. Where manpower is deployed, such as in housekeeping or security, the agreement should allocate responsibility for wages, social security contributions and other obligations under the labour codes as they apply in your state.
• Dispute resolution. Arbitration clauses must meet the requirements of the Arbitration and Conciliation Act, 1996, including a clear seat, the number of arbitrators and the method of appointment.

Contract, stamp and data protection rules change from time to time, and state stamp rates differ. We check the current position at the time of drafting.

Step-by-Step Guide

1. Initial consultation. We discuss the service, whether you are the provider or the customer, the commercial relationship, the contract value and duration, and any existing agreements the SLA must fit into.
2. Understanding how the service runs. We review how service requests come in, how tickets or jobs are logged, what tools are used to monitor performance and what reports are already produced. This keeps the SLA tied to data you can actually measure.
3. Defining the services and metrics. We list each service covered and agree on the metrics for each one, such as availability, response time, resolution time, accuracy, turnaround time or attendance.
4. Setting targets and severity levels. Together we fix target levels, priority or severity categories with clear definitions, service hours, and the measurement period, usually monthly or quarterly.
5. Drafting exclusions. We prepare exclusions for scheduled maintenance, emergency maintenance, customer-caused delays, third-party failures and force majeure events, with notice requirements for each.
6. Structuring remedies. We draft the service credit table, monthly and annual caps, the process for claiming credits, the right to terminate for repeated failure and any step-in rights.
7. Reporting and governance. We add reporting formats, frequency, review meetings, an escalation matrix and a procedure for revising service levels.
8. Integrating the legal terms. We align the SLA with the main contract on liability caps, confidentiality, data protection, intellectual property, term, termination and dispute resolution, so that the documents do not contradict each other.
9. Review and revisions. You review the draft with your operations and finance teams. We explain each clause, incorporate your comments and support you during negotiation with the other side.
10. Execution guidance. We advise on stamp duty in the relevant state, e-stamping, physical or electronic signing, and the documents each signatory needs, and share the final version in editable and signed-ready formats.

Documents Checklist

Information about the parties:

• Legal name, constitution and registered address of each party
• CIN, LLPIN, GSTIN or other registration details, where available
• Name and designation of the authorised signatory for each party
• Board resolution or authority letter for the signatory, if the other side requires it

Information about the service:

• Description of each service to be covered, including service hours and locations
• The main services agreement, Master Service Agreement or statement of work, if one exists
• Existing performance reports, dashboards or ticketing data, if available
• Details of any subcontractors or third-party platforms the service depends on

Commercial details:

• Fee structure, billing cycle and payment terms
• Proposed service levels, targets and service credit expectations
• Term of the agreement, renewal and notice periods
• Preferred dispute resolution method and seat of arbitration or jurisdiction

For regulated or data-heavy services:

• Any outsourcing guidelines or audit requirements that apply to the customer
• Description of personal or confidential data that will be handled
• Information security standards or certifications the provider follows

How Long It Takes

A first draft of a Service Level Agreement is usually ready within three to five working days from the date we receive the complete information. A typical timeline looks like this:

• Consultation and information review: one to two working days.
• First draft: two to three working days after the consultation, depending on the number of services and metrics.
• Revisions: one to two working days for each round of comments.
• Finalisation and execution guidance: one working day once the commercial terms are agreed.

Timelines can stretch when several departments must agree on metrics, when the other side sends extensive comments, or when the SLA must be aligned with a long existing contract. We keep each round moving and highlight the points that need your decision.

Pricing

Our professional fee for Service Level Agreement is ₹ 2,999.

This covers:

• Consultation on the service, metrics and commercial structure
• Drafting of a customised SLA, either standalone or as a schedule to your main contract
• Service credit table, caps, exclusions and termination triggers
• Reporting, governance and escalation clauses
• Two rounds of revisions on the draft
• Guidance on stamp duty, e-stamping and signing

Stamp duty is payable at actual as per the law of the relevant state. Drafting of a full Master Service Agreement, extensive negotiation calls with the other side, or translation into another language are quoted separately where needed.

Common Mistakes to Avoid

• Vague metrics. Phrases such as "prompt response" or "high availability" cannot be measured. Each commitment needs a number, a unit and a measurement period.
• No measurement method. If the SLA does not say which tool or log is the source of truth, the parties will rely on different data and reach different conclusions.
• Credits that look like penalties. Large fixed sums unrelated to the value of the service are at risk under section 74 of the Contract Act. Link credits to fees and cap them.
• Missing exclusions. Providers often forget to exclude scheduled maintenance, customer-caused delays or failures of systems they do not control.
• Exclusions that are too wide. Customers should watch for exclusions so broad that the provider never actually fails a service level.
• Conflict with the main contract. An SLA that has a different liability cap or termination clause from the main agreement creates confusion. Include an order of precedence clause.
• No review mechanism. Service needs change. Without a clause for periodic review, outdated targets stay in force for years.
• Ignoring stamp duty. An unstamped agreement may not be admissible as evidence when you need it most.

What Happens After

Once the SLA is signed, the real work is in running it consistently:

• Pay stamp duty and keep the original safe. Store the stamped and signed copy, and a scanned copy, where both legal and operations teams can find it.
• Set up measurement. Configure ticketing, monitoring or attendance tools to record exactly the metrics defined in the SLA.
• Share the SLA with operations. The people delivering the service should know the targets, severity definitions and escalation contacts.
• Issue and review reports. Produce performance reports at the agreed frequency and hold the review meetings set out in the agreement.
• Apply service credits as agreed. Calculate and adjust credits according to the process in the SLA. Ignoring credits for months can be treated as a waiver.
• Track renewal and notice dates. Diarise the end of the term and notice periods so the agreement does not lapse or auto-renew by accident.
• Revisit targets periodically. Use the review clause to update service levels when volumes, technology or business needs change.
• Seek advice early on disputes. If a serious or repeated failure occurs, follow the notice and cure procedure precisely to preserve your rights.

Our team can also help with related agreements, such as Master Service Agreements, vendor agreements and non-disclosure agreements, and with notices if a dispute arises.

FAQs

What is the difference between an SLA and a Master Service Agreement?

A Master Service Agreement sets out the general legal terms for a relationship, such as payment, liability, intellectual property and termination. An SLA deals with the performance standards for the services. The SLA is often attached as a schedule to the Master Service Agreement.

Is an SLA legally binding in India?

Yes. An SLA that meets the requirements of the Indian Contract Act, 1872 is a binding contract. Its enforceability depends on clear drafting, proper authority of signatories and payment of the applicable stamp duty.

Are service credits enforceable?

Service credits are generally enforceable when they reflect a reasonable estimate of loss and are linked to the fees for the affected service. Under section 74 of the Contract Act, courts award reasonable compensation up to the stated amount, so credits should not be set at arbitrary or excessive levels.

Can service credits be the only remedy for poor performance?

Yes, if both parties agree. Many SLAs state that service credits are the sole financial remedy for missing service levels, while keeping a right to terminate for repeated or serious failures. Customers should consider carefully before agreeing to this.

Does an SLA need to be stamped?

Yes. Agreements are generally chargeable to stamp duty under the stamp law of the state where they are executed or brought into. The rate depends on the state. We guide you on the correct stamp duty, which is payable at actual.

Can an SLA be signed electronically?

Yes. The Information Technology Act, 2000 recognises electronic signatures for most contracts, including SLAs. Stamp duty still applies, and e-stamping is available in many states.

What metrics should a software SLA include?

Common metrics include platform availability, support response and resolution times by severity, data backup frequency, recovery time and recovery point objectives, and security incident notification timelines. The right mix depends on your product.

Who should measure performance under the SLA?

Usually the service provider measures and reports, using agreed tools, and the customer has a right to verify or audit the data. The SLA should name the source of truth to avoid disputes.

Can service levels be changed during the contract?

Yes, if the SLA includes a change or review procedure. Changes should be recorded in writing and signed by both parties, so there is no doubt about which targets apply.

What happens if the provider keeps missing targets?

The SLA usually provides an escalation process, a cure period and, for repeated or serious failures, a right to terminate without penalty. Following the notice steps exactly is important to preserve your rights.

Can a customer-friendly SLA also protect the provider?

Yes. A balanced SLA gives the customer measurable commitments and remedies while protecting the provider through clear exclusions, credit caps and limits on liability. We draft for the side we represent while keeping the document realistic for the other side to accept.

Do I need an SLA for a manpower or housekeeping contract?

It is strongly advisable. An SLA can set attendance levels, replacement timelines for absent staff, quality checks and deductions for shortfalls, and it can make clear who is responsible for wages and statutory contributions.

Can you review an SLA sent by the other party?

Yes. We can review a draft prepared by your vendor or customer, highlight risks, suggest changes and explain which points are usually negotiable. Reviews are part of our documentation services.

How many revisions are included?

Our fee includes two rounds of revisions on the draft. Further rounds or extensive negotiation support can be arranged and are quoted separately.

Related Documentation services

• Shareholders Agreement
• Terms of Service
• Vendor Agreement
• Cheque Bounce Notice