Load shedding is a South African business reality. Schedules change, stages escalate, and no matter how good your planning, a Stage 4 afternoon on a busy Wednesday disrupts everything that depends on connectivity or power.
For field service businesses, the disruption goes beyond the office. Your technicians are out in the field during load shedding windows, trying to update job cards, capture photos, clock their time, and communicate with the office — on devices that may have limited charge, on mobile networks that are often congested during blackouts, in buildings where the Wi-Fi access point has gone offline.
This guide is practical. It covers how load shedding affects your operation, what an offline-first app actually does differently from a cloud-based one, and the day-to-day practices that keep a field service team running through any schedule.
How load shedding affects field service businesses
Connectivity drops, but not uniformly
The mobile networks — MTN, Vodacom, Cell C, Telkom — experience significantly higher congestion during load shedding as millions of people simultaneously lose fixed-line internet and fall back on mobile data. Call congestion is common. Data speeds drop. Some cell towers lose backup power during extended outages or in areas with high simultaneous load.
What this means operationally: your technician at a job site in a load shedding zone may have intermittent or no data connectivity for the duration of the outage — typically two to four hours at a time at higher stages.
If your job management app requires a live connection to save data — to update a job status, save a photo, record time entries, or capture a customer signature — the technician's work during that window is either lost, duplicated, or deferred. None of these outcomes are acceptable for a business that bills on the basis of completed, documented work.
Device charging is disrupted
A technician starting their day with a full charge at 7am faces a different situation by 2pm if load shedding has been active for part of the day. Car charging helps but is not reliable on short trips between jobs. Portable battery banks are useful but need to be charged themselves.
For businesses whose technicians spend significant time in buildings without generator power — residential properties during Stage 4, small offices that cannot afford UPS backup — device battery management is a genuine operational concern.
Customer communication becomes harder
Customers whose power and internet are both down may not receive WhatsApp messages, emails, or push notifications during the outage window. ETA notifications that should arrive before a technician shows up may arrive hours late or not at all. Customers waiting for a technician who cannot communicate may assume the job is cancelled.
This is largely out of your control, but building in phone-call fallback for ETA communication during outages is a practical hedge.
Office operations are disrupted
If your dispatcher or office manager loses power, they lose access to cloud-based scheduling, dispatch boards, and job tracking systems that require a browser and internet connection. On a bad load shedding day, your operational centre may be offline at the same time your field team needs coordination.
Laptop batteries give you a couple of hours of fallback. After that, you are on mobile hotspot — which brings you back to the congested mobile network problem.
What "offline-first" actually means
"Works offline" is a claim made by many software vendors. It is important to understand what it actually means, because there is a significant difference between:
- Cached web pages: The app shows you the last screen you viewed but cannot load new data or save anything new. Useful for reading; useless for working.
- Progressive Web Apps with partial offline: Some data is cached. Some actions can be queued. But the app was designed for online use and offline is a degraded mode, not a design priority.
- Offline-first native apps: The app was designed from the ground up with the assumption that connectivity is not always available. Data is stored locally on the device in a full database. Every action — reading, writing, updating, capturing photos — works against the local database. When connectivity returns, the local data syncs to the server in the background.
The difference between partial offline and offline-first is not a marketing distinction. It is the difference between a technician losing 90 minutes of work when connectivity drops, and a technician completing a full shift during load shedding with zero data loss.
How WorkOrderPro handles offline jobs
WorkOrderPro's mobile app is built on WatermelonDB — an offline-first database architecture specifically designed for React Native mobile applications. This is not a workaround or a fallback mode. It is the foundation of how the app stores and retrieves data.
Here is what that means in practice:
All job data is available without connectivity
When a technician opens the WorkOrderPro app, their job list for the day is stored on their device. They do not need a connection to see their jobs, view job details, check the customer's address, or read the problem description. The data was synced to their device the last time they had connectivity and is available in full offline.
Every action works offline
Status updates, photo captures, clock in and clock out, time entries, parts added to a job, notes written, customer signatures — all of these work on the local database. The technician performs the same actions they would perform online. The data is written locally and queued for sync.
Photos are stored locally and uploaded on reconnect
Photos taken through the app are stored in the device's application sandbox immediately at capture. They are not dependent on connectivity to be saved. When connectivity returns, photos are uploaded in the background — the technician does not have to do anything to trigger the upload. The GPS coordinates and timestamp that were recorded at capture are preserved through the upload process.
Background sync on reconnect
When connectivity returns — whether that is because the load shedding window ended, the technician drove to a different area, or connectivity otherwise restored — the app syncs all queued data to the server in the background. No manual action is required. The dispatcher sees the updates arrive as connectivity restores.
Conflicts are handled correctly
If a job is updated by a technician while offline and simultaneously updated by the dispatcher in the web app, the sync process handles the conflict. For dispatch-related updates, an optimistic concurrency system prevents overwriting legitimate changes — if a conflict is detected, the dispatcher is notified rather than data being silently lost.
Practical tips for managing your team during load shedding
Pre-download the day's jobs before the outage window
If you know load shedding is scheduled for the afternoon, make sure your technicians open their app and load their job list during the morning before the outage. WatermelonDB caches all job data at sync time. A technician who has synced their device before the outage has their full job list, customer details, and job notes available for the rest of the day regardless of connectivity.
Check the Eskom schedule the evening before
EskomSePush and similar apps give you the load shedding schedule for the following day by area. If your technicians cover specific areas and you know those areas have morning outages, adjust dispatch timing accordingly. There is no point dispatching a technician to a job site in a known outage zone at a time when the customer is also likely to be without power.
Carry portable battery banks
A 20 000mAh battery bank costs less than R300 and can charge a phone from 0 to 100% twice. For a small team, equipping every technician with a charged battery bank is a modest cost that eliminates the "my phone died" problem entirely. Charge the battery banks at the office overnight.
Have a phone-call fallback for ETAs
When WhatsApp and push notifications are unreliable due to network congestion, a phone call is your fallback. Brief your technicians that if they are in a load shedding zone and heading to a job, they should call the customer directly rather than relying on an ETA notification that may not arrive.
Keep device storage available for photos
Photos require storage. A technician whose phone is full cannot capture job photos — which creates compliance gaps in the photo record and means important documentation is missed. Have a policy: delete unnecessary apps and media, and keep at least 2GB of free storage available. Structured job photos in an offline-first app are typically 1-3MB each, so 2GB handles several hundred photos even without connectivity for upload.
Plan for office downtime
If your dispatcher works from a laptop at the office, a load shedding window kills their access to the web-based dispatch board. Options: a UPS that keeps the router and laptop running through a two-hour outage; a 4G router on a separate power bank; or a mobile phone hotspot. Plan this in advance and test it before you need it.
Load shedding and software selection
The offline-first requirement is one of the most important differentiators when evaluating job management software for a South African service business. Ask these questions of any vendor:
- Does the mobile app work fully offline — job updates, photo capture, signatures, time tracking — or is offline limited to read-only access?
- How is data synced when connectivity returns? Is it automatic, or does the technician have to trigger it manually?
- Are photos stored locally and uploaded on reconnect, or do they require connectivity at capture?
- What happens to data entered offline if the app is closed or the device restarts before syncing? Is the data preserved?
If the answers to any of these questions are vague or hedged, the product is not genuinely offline-first. For South African field service businesses, a product that degrades during load shedding is a product that degrades regularly.
WorkOrderPro works the same offline as it does online. Your technicians keep working during load shedding, and everything syncs when connectivity returns. Start your free 14-day trial. Start your free trial
Frequently asked questions
Q: Does WorkOrderPro work during load shedding if the technician has no signal at all? A: Yes. The WatermelonDB offline-first database stores all job data locally on the device. If the technician has no signal — no mobile data, no Wi-Fi — the app continues to work normally. Status updates, photos, time entries, and notes are written to the local database and synced when connectivity returns.
Q: How does the dispatcher manage jobs during a load shedding window if the office has no power? A: The web-based dispatch board requires connectivity and power at the office. For planned load shedding windows, the practical options are a UPS (uninterruptible power supply) keeping the router and computer running, a 4G mobile hotspot, or brief dispatch preparation before the window — assigning jobs to technicians before the outage so they know their schedule for the window.
Q: What happens if a technician's phone runs out of battery mid-job? A: WatermelonDB writes data to the local database on every action — there is no unsaved work at any point. If the phone dies mid-job, all data entered up to that point is preserved on the device's local storage. When the phone is charged and restarted, the data is still there and will sync when connectivity returns.
Q: Are load shedding schedules integrated into the app? A: No, WorkOrderPro does not integrate directly with load shedding schedule data. Load shedding schedule management is best handled through dedicated tools like EskomSePush, which are updated in real time. The job management app's role is to keep working regardless of what the schedule does.
Q: My area gets Stage 6 regularly. Is the app reliable enough for that? A: Stage 6 involves four-and-a-half hours of load shedding twice a day — a significantly disruptive pattern. An offline-first app handles this without data loss. The challenge at Stage 6 is device charging and network congestion rather than the app itself. Battery banks, car chargers, and phone-call fallback for ETA communication are the practical tools for Stage 6 conditions.
Title variations
- "Managing your field service business during load shedding" (57 characters)
- "Load shedding and field service management: the SA operations guide" (67 characters)
- "How SA service businesses keep running during load shedding" (58 characters)
- "Offline-first field service apps: why they matter for SA businesses" (66 characters)
- "Load shedding field service guide: what offline-first actually means" (67 characters)
Meta description
Load shedding disrupts connectivity and charging across SA. This guide shows how offline-first apps and practical preparation keep field teams running. (150 characters)
Key takeaways
- Mobile networks are congested during load shedding, making cloud-only apps unreliable — offline-first is not a nice-to-have for SA, it is a requirement
- Offline-first means all data is stored locally on the device and synced to the server when connectivity returns — photos, time entries, job updates, and signatures all work without signal
- WatermelonDB, the database underlying WorkOrderPro's mobile app, was designed for offline-first operation in React Native applications
- Practical preparation (pre-downloading job lists, battery banks, phone-call ETA fallback) reduces load shedding disruption significantly
- Ask software vendors direct questions about offline capabilities — "works offline" can mean anything from read-only cached pages to full offline operation
Internal linking suggestions
- "mobile app" → /features/mobile-app — The offline-first architecture is detailed on the mobile app feature page
- "why offline-first apps matter for SA" → /blog/offline-field-service-app-south-africa — Related blog post going deeper on the technical offline-first question
- "job photos" → /features/job-photos — Offline photo storage is a key part of the offline-first capability
- "HVAC industry page" → /industries/hvac — HVAC technicians work in commercial buildings with frequent connectivity issues; strong cross-link
- "paper vs digital job cards" → /guides/paper-vs-digital-job-cards — Offline capability is a key differentiator between digital options; natural link in the digital evaluation section