Load notes
Audit Trail

Audit Trail keeps one record for the set on site, not fragments across calls, WhatsApp images and loose job cards. For generator work, that file should show run hours, fault notes, fuel entries and the name of the plant or branch before anyone books service.
The same avoidable gaps turn up on many South African sites: no photo of the control panel, no listed kVA requirement, or a call-out logged without the plant name. Audit Trail is our note on keeping generator sales, service and breakdown records clear from the first message.
On South African sites, weak records usually show up when a breakdown starts at shift change or after a load shedding run. A useful file includes the unit ID, panel photo, site contact and the last service entry so the next person can see what happened without guessing. Use the contact form if a record needs to be matched to this note.
Details that must appear first
- Plant or branch name recorded
- Clear control panel photo saved
- Correct genset or service path linked
- Site contact name and role listed
Audit Trail works best when the service note and the equipment page point to the same unit. That way, the file shows whether the issue sits with the generator, the ATS panel, fuel supply or access restrictions at the premises.
How the Audit Trail reads across a Sunnyrock genset service week
Audit Trail is about keeping generator records in one usable file instead of spreading them across messages and notebooks. Keep service history, run hours, fuel logs and maintenance sign-off together so the next inspection or breakdown check starts with facts.
Every record should start with the required kVA, the actual load being carried and any site limits that affect operation. Johannesburg dust, Durban salt air and Cape Town delivery access all change what must be checked and how often hours, filters and alarms need to be logged.
The first image set matters more than most teams expect. A photo of the controller, hour meter, breaker position and canopy plate can settle later disputes about runtime, alarm history and which set was attended to when the power supply became unstable.
What the file must contain
A complete trail should leave one readable sequence from first report to sign-off. That includes the fault description, attendance notes, parts used, updated run hours and the person who accepted the work on site.
Before widening the scope, tie Audit Trail to the matching runtime note and the relevant load note so there is one chain of reference.
- Run hours matched to visit date
- Alarm or fault code captured
- Sign-off name added to record
Site conditions that affect records
Older factories around Sunnyrock, busy yards near OR Tambo and retail sites with fixed receiving times all create record gaps if access is not written down early. The file should note gate rules, shutdown windows, escort requirements and whether the generator is the main standby set or a temporary backup unit.
Coastal corrosion can change inspection findings, while inland dust often shows up in filter condition, radiator cleaning and panel sealing. Load shedding also affects how often test runs are done, so runtime entries need actual dates and hours instead of rough estimates.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Audit points worth checking
Audit Trail keeps one record for the set on site, not fragments across calls, WhatsApp images and loose job cards. For generator work, that file should show run hours, fault notes, fuel entries and the name of the plant or branch before anyone books service.
File the ATS panel note on the day of attendance, not after parts or invoices start moving around. That single habit makes it easier to support a buyer, maintenance manager or workshop admin who later needs proof of the visit, the hours and the work completed.
