What is the difference between an SLA and a contract?

A contract is the overarching legal agreement that governs the relationship between the parties - covering scope, payment, liability, termination, and intellectual property. An SLA is typically an annexure or schedule to that contract that defines specific, measurable performance standards the service provider must meet. The SLA does not stand alone; it derives its enforceability from the underlying contract.

What is a reasonable uptime SLA?

It depends on the criticality of the service. For mission-critical systems (payment processing, emergency services), 99.99% uptime (52.6 minutes downtime per year) is standard. For general business applications, 99.9% (8.76 hours per year) is common. For non-critical internal tools, 99.5% may be acceptable. Always clarify whether uptime is measured monthly or annually, and whether planned maintenance is excluded.

Are SLA penalties enforceable in South Africa?

Yes, provided they constitute a genuine pre-estimate of the loss the client would suffer from non-performance. South African courts distinguish between enforceable "penalty clauses" (which may be reduced under the Conventional Penalties Act 15 of 1962 if deemed disproportionate) and "liquidated damages" (agreed compensation). Service credits, being a reduction in fees rather than a punitive amount, are generally enforceable without difficulty.

How often should SLAs be reviewed?

At minimum, SLAs should be reviewed annually. Best practice is quarterly operational reviews with monthly performance reporting. Review triggers should also include significant changes: new service components, major incidents, regulatory changes, or business growth that changes usage patterns. The review clause should specify who participates, what data is examined, and how amendments are approved.

Can I terminate a contract for SLA breaches?

Termination for SLA breaches depends on the contract terms. Most well-drafted agreements allow termination only for "material" or "persistent" SLA breaches - for example, missing the same target three consecutive months, or a single failure exceeding a defined severity threshold. The contract should specify a cure period (typically 30 days) before termination rights arise.

What should happen when an SLA is not met?

The SLA should define a clear consequence chain: immediate notification to the client, root cause analysis within a stated period (e.g., 5 business days), a corrective action plan, service credits or penalty application, and escalation if the failure recurs. The goal is remediation, not punishment - credits compensate for diminished service value while the provider works to restore performance.

Do SLAs apply to internal departments?

Yes. Internal SLAs (sometimes called Operational Level Agreements or OLAs) are increasingly common between IT and business units, shared services centres and operating divisions, or head office and regional branches. While not externally enforceable contracts, they create accountability, align expectations, and improve service delivery within the organisation.

How do I measure SLA compliance?

SLA compliance requires objective measurement tools: monitoring dashboards for uptime and response times, ticketing systems for incident tracking, automated reporting for throughput metrics, and periodic surveys for satisfaction scores. The SLA should specify the measurement methodology, reporting frequency (typically monthly), data sources, and dispute resolution for contested measurements.

GuideBusiness

Service Level Agreements (SLAs) Explained for South African Businesses

How to draft SLAs that protect both parties. Covers performance metrics, penalties, escalation procedures, and compliance with South African law.

Read the Guide Back to Resources

By My-Contracts Legal Team, Legal Content|7 March 2026|12 min read

Definition

What Is a Service Level Agreement?

A Service Level Agreement (SLA) is a formal document that defines the expected level of service between a service provider and a client. It establishes measurable performance standards - such as uptime, response times, and quality thresholds - against which the provider's performance is objectively assessed.

In South African business practice, an SLA is rarely a standalone document. It typically forms an annexure or schedule to a broader agreement - a Master Services Agreement (MSA), a Professional Services Agreement, or a standard service contract. The SLA inherits its legal force from the parent agreement while providing the operational detail that the parent agreement deliberately omits.

The purpose of an SLA is threefold. First, it aligns expectations: both parties agree in advance on what "good service" looks like, eliminating ambiguity. Second, it creates accountability: with defined metrics and consequences, providers are incentivised to maintain standards. Third, it enables business continuity: by specifying recovery procedures and escalation paths, the SLA ensures disruptions are managed systematically rather than ad hoc.

Without an SLA, disputes about service quality become subjective arguments with no agreed benchmark. With one, both parties have a shared reference point that protects the client's operational needs and the provider's commercial interests.

Key Differences

SLA vs Service Agreement vs MSA

Three documents that work together but serve different purposes.

Service Agreement

A service agreement is a complete contract between a client and provider covering the full scope of the engagement: services to be delivered, payment terms, intellectual property, liability, confidentiality, termination, and governing law. It is the primary legal instrument. For straightforward, single-service engagements, the service agreement may include SLA-type performance standards directly within its terms. This is common for facilities management, security services, and cleaning contracts in South Africa where the relationship is relatively simple.

Service Level Agreement (SLA)

The SLA is a performance-focused annexure that defines measurable standards, monitoring mechanisms, reporting requirements, and consequences for non-compliance. It answers the question: "How well must the service be delivered?" The SLA does not typically address commercial terms like pricing, liability caps, or termination rights - those belong in the parent agreement. However, service credits and penalty mechanisms in the SLA must align with the liability and payment provisions of the parent contract to avoid inconsistency.

Master Services Agreement (MSA)

An MSA is an umbrella contract designed for ongoing, multi-project relationships. It establishes the common terms that apply to all work: liability, indemnity, IP ownership, confidentiality, dispute resolution, and general obligations. Individual projects are then commissioned through Statements of Work (SOWs) that reference the MSA. Each SOW may have its own SLA tailored to the specific service. This structure is standard for IT outsourcing, consulting engagements, and managed services in South Africa, where the relationship spans multiple workstreams over several years.

When to use which structure

Single service, single provider: A service agreement with embedded SLA terms is sufficient. Multiple services or evolving scope: Use an MSA with separate SOWs and SLA annexures for each workstream. The MSA + SOW + SLA model provides maximum flexibility while maintaining consistent governance terms across all engagements.

Metrics

Key Performance Metrics and KPIs

Every SLA should define metrics that are specific, measurable, achievable, relevant, and time-bound. These are the six categories most commonly used in South African SLAs.

Availability / Uptime

The percentage of time a service is operational and accessible. A 99.9% uptime SLA permits roughly 8.76 hours of downtime per year, while 99.99% allows only 52.6 minutes. Cloud and IT services typically target 99.9% or higher, with planned maintenance windows excluded from calculations.

e.g., 99.9% monthly uptime for hosted ERP

Response Time

The maximum time between a client reporting an issue and the service provider acknowledging it. Response times are typically tiered by severity: critical issues (P1) may require acknowledgement within 15 minutes, while low-priority requests (P4) may allow 8 business hours.

e.g., P1 Critical: 15 min, P2 High: 1 hour

Resolution Time

The maximum time to resolve or provide a workaround for an issue after acknowledgement. Resolution targets are also severity-based and may distinguish between a permanent fix and a temporary workaround. The SLA should clearly define what constitutes "resolved."

e.g., P1: 4 hours to workaround, 24 hours to fix

Throughput / Capacity

Minimum processing capacity the service must sustain, measured in transactions per second, concurrent users, API calls per minute, or data volume. Capacity SLAs prevent degradation during peak periods and provide a basis for scaling discussions.

e.g., 500 concurrent users with sub-2s page load

Quality Metrics

Measurable standards for output quality, including error rates, defect rates, accuracy percentages, and compliance scores. In BPO arrangements, quality metrics might include data entry accuracy of 99.5% or call resolution rates above 85%.

e.g., data entry accuracy >= 99.5%

Customer Satisfaction (CSAT)

Periodic measurement of end-user satisfaction through surveys, Net Promoter Score (NPS), or Customer Effort Score (CES). While subjective, CSAT targets create accountability for the overall service experience beyond raw technical metrics.

e.g., CSAT score >= 4.2/5.0 per quarter

Consequences

Penalty and Credit Structures

SLAs without consequences are aspirational statements, not enforceable commitments.

Service Credits

The most common remedy in commercial SLAs. When service levels are missed, the client receives a credit against future invoices - typically 5-15% of the monthly fee per missed target, capped at 20-30% of the total monthly charge. Service credits are easy to administer, preserve the commercial relationship, and are almost always enforceable because they represent a fee reduction rather than a penalty.

Liquidated Damages

A pre-agreed monetary amount payable for specific breaches. Under South African law, liquidated damages are enforceable if they represent a genuine pre-estimate of the loss that would flow from the breach. The Conventional Penalties Act 15 of 1962 allows courts to reduce liquidated damages amounts that are disproportionate to the actual prejudice suffered.

Liability Caps and Exclusions

Every SLA penalty structure should operate within the liability framework of the parent agreement. Common provisions include an aggregate annual cap on service credits (typically 100% of one month's fees), exclusion of indirect and consequential damages from SLA remedies, and carve-outs for fraud, wilful misconduct, and breaches of confidentiality. The SLA should also address force majeure events that suspend SLA obligations - such as load shedding (a uniquely South African consideration), natural disasters, or third-party infrastructure failures outside the provider's control.

Best practice for penalty structures

Structure your penalty regime as a graduated consequence model: first breach triggers reporting and root cause analysis; repeated breaches trigger service credits; persistent failure triggers escalation and remediation plans; chronic non-compliance triggers termination rights. This approach incentivises improvement rather than simply punishing failure, and is more likely to be upheld by South African courts as reasonable.

Escalation

Escalation Procedures

A structured escalation model ensures issues reach the right decision-makers at the right time.

Operations / Service Desk

Immediate to 4 hours

First-line support handles the issue using standard operating procedures. Most routine incidents are resolved here without escalation.

Management

4-24 hours

If Level 1 cannot resolve or the issue persists beyond agreed response times, it escalates to the service delivery manager and the client account manager for joint resolution.

Executive / Senior Leadership

24-72 hours

Persistent or high-impact issues escalate to executive sponsors on both sides. This level typically involves C-suite or director-level attention and may trigger emergency resource allocation.

Legal / Termination

72+ hours or chronic failure

If the issue remains unresolved or represents a material breach, the client may invoke contractual remedies: formal dispute resolution, service credits, penalty enforcement, or termination for cause.

The SLA should specify named contacts at each escalation level, required response times per level, mandatory documentation (incident logs, root cause analyses), and automatic escalation triggers when response or resolution timeframes are exceeded. Both parties should maintain an up-to-date escalation matrix as a living document reviewed at each quarterly service review.

Governance

SLA Review and Amendment

SLAs are living documents that must evolve with the business relationship.

Monthly performance reporting against all SLA metrics with trend analysis

Quarterly operational reviews with both parties' service delivery managers

Annual strategic reviews to benchmark SLAs against industry standards and evolving business needs

Triggered reviews after major incidents, significant scope changes, or regulatory updates (e.g., new POPIA requirements)

Formal amendment procedures requiring written agreement from authorised representatives on both sides

Performance baselines recalculated after significant service changes or infrastructure upgrades

The amendment clause should specify who has authority to approve SLA changes, the minimum notice period for proposed amendments (typically 30 days), and whether changes require a formal variation agreement or can be approved via the governance forum. Changes to financial terms (service credits, penalty rates) should always require formal written amendment to the parent agreement.

By Industry

Industry-Specific SLA Considerations

SLA structures and metrics vary significantly by industry. Here are the key considerations for the most common sectors in South African outsourcing.

IT and Cloud Services

Cloud SLAs focus on availability (99.9-99.99%), Recovery Point Objective (RPO) defining maximum data loss, and Recovery Time Objective (RTO) defining maximum downtime after disaster. Include planned maintenance windows, geographic redundancy requirements, and data sovereignty obligations under POPIA. Major providers like AWS and Azure offer standardised SLAs - but these are provider-favourable and should be supplemented with contractual commitments.

Facilities Management

Facilities SLAs cover emergency response times (e.g., lift entrapment within 30 minutes), preventive maintenance schedules, HVAC comfort ranges, cleaning quality audits, and statutory compliance (OHS Act, fire regulations). Include lifecycle replacement plans, energy efficiency targets, and penalty structures for repeat failures of the same equipment or system.

Business Process Outsourcing (BPO)

BPO SLAs measure processing accuracy, turnaround times, abandonment rates, first-call resolution, and agent utilisation. Include transition SLAs for onboarding (knowledge transfer milestones, parallel running periods) and exit SLAs for disengagement (data handover, staff transition). Measure against agreed baselines established during the first 90 days of service.

Professional Services

Professional services SLAs focus on deliverable quality, milestone adherence, resource allocation (named personnel, minimum seniority), and change request turnaround times. Include acceptance criteria for each deliverable, maximum revision cycles, and escalation paths for scope disputes. Milestone-based payment triggers should align directly with SLA achievement.

FAQ