Field service scheduling around a level 4 warning

Field service scheduling software handles a weather stand-down easily: jobs move, customers get told, the week rearranges. The part it usually cannot produce is the record of what was not done and why, and that record is the one that decides an invoice dispute in October. South African operators are about to need it, because a cut-off low arrives on Thursday.

Moving the work is the easy half. Proving what happened to it is the half that pays.

What has been warned, and where

The South African Weather Service has issued yellow level 4 warnings across several districts for Thursday 3 September and into Friday 4 September.

Disruptive rainfall, with flooding of roads and settlements and major disruption of traffic flow, is expected over the Overberg and Garden Route districts on Thursday. Damaging winds are expected over the Namakwa district in the Northern Cape, parts of the Cape Winelands and Central Karoo, and the Little Karoo, from Thursday afternoon into Friday. Damaging winds and waves, which may disrupt ports and harbours, are expected between Alexander Bay and Plettenberg Bay across the same two days, with waves of roughly 4.5 to 5.5 metres in places.

As the system moves east it is expected to bring showers, thundershowers and windy conditions over parts of the Free State, Gauteng, Eastern Cape and KwaZulu-Natal, and the eastern North West, from Friday into Sunday. BusinessTech reports the same warning including the possibility of snow, which SAnews places over the Drakensberg of the Eastern Cape on Friday morning.

Check the warnings again on the morning itself. Levels and districts move daily and the numbers above are dated.

What actually gets lost in a stand-down

A stand-down is not one event. It is four, and most scheduling systems record only the first.

The job moves, and the system records the new date. Good. What it usually does not record is that the original slot existed, that the customer was told, who decided, and on what basis.

Six weeks later the argument is not about the weather. It is about whether a service level was met, whether a penalty applies, and whether the technician was on site on the day the contract says. At that point everybody is working from memory and a WhatsApp thread.

The asymmetry is worth stating plainly. The client has a contract and a diary. You have a rescheduled job with no trace of the original.

The five fields that settle it

None of this needs new software. It needs the cancellation to be a record rather than a deletion.

• The original scheduled date and time, retained, not overwritten.
• The reason code, from a short list. Weather, access denied, customer unavailable, parts, no technician. Free text cannot be counted.
• The authority. Who decided, and at what time.
• The evidence. The warning reference, a photograph, the site contact's name. One line is enough.
• The notification. When the customer was told, through which channel, and by whom.

Five fields, filled in at the moment the decision is made rather than reconstructed afterwards. The reason code is the one that earns its keep, because at the end of a quarter it tells you how many jobs you lost to weather, to access and to your own staffing.

What a South African operator should do this week

Three things, in order, and all of them before Thursday.

Identify the jobs already booked into the warned districts. Contact those customers today rather than on the morning, because a stand-down agreed in advance is a service decision and one announced on the day is a failure.

Decide the rule now, in writing. Which conditions stand a crew down, who has authority to call it, and what happens to a job already in progress. A rule invented at 06:00 in the rain is a rule that gets argued about.

Then look at the following week. Everything moved from Thursday and Friday lands on top of work that was already booked, and the second failure is usually the overloaded Monday rather than the storm.

Where the record has to live

The reason this stays broken is that the schedule lives in one system, the customer conversation in WhatsApp, and the invoice in accounting. The cancellation touches all three and is recorded properly in none.

Joining them so a stand-down writes once and appears everywhere is ordinary integration work, and it is what Zorah builds into the tools a business already runs. The reason code that protects an invoice is the same field that produces a quarterly report on lost capacity, which is why it is worth doing once.

Keep it in job and scheduling records, let the customer-facing half sit with sales and CRM, and expect the reporting layer to be the thing that finally makes the reason codes worth having.

What to do before Thursday

Open your schedule and filter for jobs in the Overberg, the Garden Route, the Cape Winelands, the Central Karoo, the Little Karoo and Namakwa on 3 and 4 September.

For each one, phone the customer today and agree a new date. Then write down, in the job record, that you did it and when. That single line is the thing you will want in October.