KwaZulu-Natal summer storms take out camera systems every season. A strike does not need to hit the building — a nearby strike coupled onto a long cable run will do it, and a camera system is mostly long cable runs.

When it happens, the technical question is usually simple: what is dead, and what does it cost to replace. The claim is where it gets complicated, and most of the complications are avoidable if you know what is coming.

The adjuster does not work for you

Worth understanding at the outset, because it explains everything else.

A loss adjuster is appointed by the insurer to establish what happened and what it should reasonably cost. They are generally professional and often helpful, but they are not your representative and not your installer’s. Their questions are aimed at establishing cause, scope and value — not at getting you back up quickly.

That is not adversarial. It just means vagueness works against you, and specificity works for you.

One storm is not necessarily one claim

This is the requirement that surprises people most, and it can delay a claim badly.

If equipment was damaged by two different causes, or on two different dates, expect to be asked for the quotation to be split — itemised so that each set of damage sits against its own cause and its own event.

The obvious case is a property that took a lightning strike in one storm and water ingress in another. It feels like one long bad summer. To an insurer it is potentially two separate incidents, each with its own date, its own excess and its own assessment.

Practically, that means:

  • Record the date each fault appeared, not the date you got round to reporting it. If cameras died on the night of the storm and a recorder failed a fortnight later after water got in, those are different facts.
  • Do not let your installer merge everything into one convenient quote. It reads as tidier and it is much harder to assess. A single blended figure is the fastest route to a query.
  • Itemise by device, with cause against each line where it is known.

Expect an independent assessment

An insurer may appoint a different contractor to assess the damage — not the one who installed the system or quoted the repair.

This is routine and is not an accusation. It is how an insurer avoids relying solely on the estimate of the party who will be paid to do the work.

Two things follow. Nothing should be thrown away before it is inspected — damaged equipment often has to be physically collected for assessment, and disposing of it early can cost you the claim. And your quotation should be legible to a third party: model numbers, quantities and locations, so that somebody unfamiliar with the site can walk it and reconcile.

The part almost nobody thinks about: the configuration

Here is the requirement that catches even experienced people.

An adjuster on a programmed system may ask for the current configuration and interface files — the working setup, not just the hardware list. Because replacing a recorder does not restore a system. What made it your system was the configuration: camera names, recording schedules, retention settings, motion zones, privacy masks, user accounts, notification rules, integrations.

Replace the hardware without that and you have new equipment that records everything to no plan and calls its cameras “Camera 1” through “Camera 24”.

Which raises the question worth acting on today, before any storm:

Who holds a copy of your system’s configuration, and when was it last exported?

If the answer is “the installer has it somewhere”, that is a single point of failure sitting outside your control. If the answer is “nobody, it is only on the recorder”, then the same strike that kills the recorder kills the design work with it — and the replacement is not an equipment cost, it is a re-commissioning.

Ask your installer to export the configuration and give you a copy. On most systems it is a menu item and a file. Store it with the building documents. Refresh it whenever the system changes materially.

What to have ready when you claim

  • Date and description of each incident, separately.
  • Photographs of visible damage, and of device labels showing model and serial.
  • An itemised quotation, by device and location, with cause per line.
  • The original installation documentation if it exists — what was installed, when.
  • A configuration export, if you have one.
  • The damaged equipment, retained until told otherwise.

And the boring prevention that actually works

Surge protection on a distributed camera system is not an upsell, and it is the cheapest line on any KZN specification.

The exposure is not only the mains. A camera system’s vulnerability is its cable runs — long conductors between buildings, up poles, across yards, which couple energy from a nearby strike and deliver it to whatever they are plugged into. That is why a single strike can take out a recorder, a switch and several cameras at once: they are all connected to each other.

Protect the paths, not just the plug — mains, network and any inter-building link — and earth it properly, because a surge device with nowhere to send the energy is decoration.

It will not stop a direct strike. It will change a claim from “the system” to “two cameras”, which is the difference between a season’s inconvenience and a season’s project.

General guidance based on contractor-side experience of storm-damage claims. No specific claim, property, client, insurer or outcome is described. Insurance practice varies by insurer and by policy and changes over time — check your own policy and take advice on your own claim.