SLA Compliance Guide for SA Insurance Contractors (How to Hit 95%+)

By Renier Smith, Founder of Plan My Crew · March 2026 · 10 min read

Why SLA Breaches Happen (The Real Causes)

Most contractors think SLA breaches happen because their team was too slow. In reality, the most common causes are system failures, not team failures.

Strategy 1: Treat 30 Minutes as Your Target, Not 60

The insurer gives you 60 minutes. Your internal target should be 30 minutes. This gives you a 30-minute buffer for traffic, load shedding, wrong address, GPS issues, or a technician who can't find parking.

On paper this sounds obvious. In practice, most contractors are targeting "get there within the hour" — which means any minor delay becomes a breach. Target 30 minutes and you'll consistently hit 95%+ even when things go wrong.

Strategy 2: The Insurance Email Parser (Eliminates the Biggest Cause)

The single biggest improvement to my SLA compliance came from eliminating manual capture delay. When Santam or OUTsurance sends an assignment email, there's typically a 10–20 minute delay between the email arriving and someone capturing the job details into the dispatch system — finding the address, the trade type, the customer contact, the DAS reference, the priority level. During that 20 minutes, the SLA clock is already running.

PMC's email parser reads the assignment email the moment it arrives and creates the job automatically — address, DAS reference, customer details, trade type, SLA deadline — all populated. My dispatch team sees a new emergency job appear in the system with a live countdown timer. Response time from email to team assignment: under 2 minutes.

That 18-minute improvement alone was worth several percentage points of SLA compliance.

Strategy 3: GPS-Based Team Assignment

When an emergency comes in, you have 60 minutes (or 30 minutes if you're targeting correctly). Assigning based on "which team do I think is nearby?" wastes critical minutes. Assigning based on live GPS location data means you're dispatching the closest available team in under 60 seconds.

In PMC, the dispatcher sees all team locations on a live map. When a new claim arrives, available teams within range are immediately visible. The right team is assigned in under a minute. No phone calls to find out where teams are. No guessing.

Strategy 4: Pre-Stocked Vans for Common Jobs

SLA is about arrival, not completion — but a team that arrives without common materials will be back on the same job, affecting your comeback rate. Pre-stocking vans with the most common insurance claim items eliminates the "I need to get a part first" excuse.

Common emergency items to pre-stock:

• Geyser pressure relief valves (most common emergency call)
• Circuit breakers (common DB board failures)
• Gate motor backup batteries
• Basic plumbing fittings and washers
• Earth leakage units

The stock cost is lower than you think. The comeback prevention value is significant — each comeback costs R3,550 and risks your panel status.

Strategy 5: Multi-Team Coverage (No Single Points of Failure)

If you have one team in an area and they're on a job when an emergency comes in, you're going to breach. Insurance panel operations need geographic redundancy — at least 2 teams in each service area, ideally 3.

This feels expensive. It's not optional. One SLA breach per week on a panel that allows 5% failures means you're at 87% compliance within a month. A formal warning follows. Two months of that and you're on probation.

Calculate how many teams you need per area based on your job volume, not your cost appetite. Then plan towards that number.

Strategy 6: Automated SLA Monitoring With Alerts

Manual SLA tracking in Excel is where breaches happen. By the time you notice a job is approaching its SLA deadline in a spreadsheet, you've often already missed it. Automated monitoring changes this:

• Job created → SLA timer starts automatically
• 45 minutes remaining: manager alert fires
• 15 minutes remaining: urgent alert, all relevant parties notified
• SLA breached: automatically logged, no manual recording required

In PMC, this is built in for every insurance job. Before PMC, I was logging SLA performance weekly in a spreadsheet. I would find out about a breach 3 days after it happened. Now I find out with 15 minutes to potentially still prevent it.

Handling Load Shedding Without SLA Breaches

Load shedding adds a layer of complexity that international software completely ignores. A team that can't access their job management app during a Stage 4 outage is a team that can't confirm addresses, can't check in GPS, can't upload photos.

PMC has full offline mode — all job data is available without internet connection. GPS check-in works offline (coordinates are queued and synced when connection resumes). Photos upload when connectivity returns. The job flow doesn't stop because the lights went out.

If you're on a platform that requires internet connectivity for job management, load shedding is directly costing you SLA compliance points.

When You Get a Warning Letter — What to Do

Don't panic. Don't respond emotionally. Do this:

1. Pull your SLA data for the period — identify which jobs breached and why
2. Categorise: team speed issues vs system delays vs wrong team assignment vs traffic
3. Fix the systemic causes first (manual tracking, wrong assignment, stock issues)
4. Respond to the insurer with a written improvement plan — specific actions, measurable targets, timeline
5. Implement automated monitoring so you can demonstrate improvement with data

Insurers don't want to remove contractors — replacing a panel contractor is disruptive for them too. A clear, credible improvement plan buys you time. Data showing improvement keeps you on the panel.

Read next: Full insurance panel requirements guide → | Comeback prevention — save R298K/year →