Records how-to
A farm incident register that actually gets used
A farm incident register that gets used is quick to fill in at the scene, records what happened with a photo and a place, and leads to a follow-up action that someone owns. It is about learning, not blame. If reporting a problem feels like getting someone into trouble, nobody reports, and the register stays empty until something serious happens.
Most farms have an incident book somewhere. The question is whether anything goes into it. This article covers what to record, why near misses count, how to follow up, and why emergency numbers belong on every phone.
What to record
A good incident record answers the questions someone will ask a week later, when the people involved are back at work and memories have faded:
| Field | Example |
|---|---|
| What happened | Diesel spilled from a leaking tank fitting at the workshop |
| When | 14 October 2026, about 07:20 |
| Where | Workshop, next to the diesel tank. A GPS point or map pin helps |
| Who reported it | Lerato |
| Who was involved | Workshop team |
| Photos | The spill, the fitting, the area around it |
| Immediate action | Spill kit used, sand put down, tank valve closed |
| Follow-up | Replace the fitting, check the bund, dispose of the contaminated sand |
| Who owns the follow-up | Johan, workshop supervisor, by 21 October |
| Closed | Date and a note of what was done |
Keep it short. A register that asks for two pages per incident gets one line per month.
Report at the scene, with photos
The best time to record an incident is straight away, where it happened. A photo taken at the scene shows what no description can: how big the spill was, which fitting broke, where the drain is. A position tells the follow-up team exactly where to go.
On a fictional 50-hectare macadamia farm near Hazyview, the old system was a book in the office. A worker who saw a fertiliser bag split in the store had to find a supervisor, who had to remember to tell the office, who wrote it up on Friday. By then, nobody could say exactly where the spill had been or how it was cleaned up.
In FieldSafe, anyone on the farm can tap Problem on their phone and choose a picture tile. There are seven kinds: chemical spill, fuel or oil spill, fertiliser spill, storm or property damage, fire, equipment damage, and something else. They can add a photo and the position “from where I’m standing”, and report for someone else if needed. It works with no signal and sends itself later.
Near misses count
A near miss is something that could have hurt someone or caused damage, but did not this time. A ladder that slipped while nobody was on it. A bakkie that nearly reversed into a picker. A spray drifting towards a team in the next Block.
Near misses matter because they are free lessons. The same cause, a bit less luck, and it is an injury. Safety practice in many industries treats near-miss reports as one of the most useful records a workplace keeps, because there are far more of them than injuries, and each one points at something to fix.
To get near misses reported, people have to believe that reporting is safe:
- Thank the person who reports, every time.
- Fix the thing, not the person. Ask “what made this possible?” before “who did this?”
- Show what changed. If a report leads to a new rail or a moved path, tell the team.
- Make it easy. A picture, a few words, done.
FieldSafe does not record injuries or near misses. Its Report a problem screen covers the seven kinds above, about spills, damage and fire. For injuries and near misses, keep a separate paper register. Our free incident report template works for both, with space for what happened, what could have happened, and what will change.
Injuries at work can also carry legal reporting duties, and a register does not replace those. For what you must report and to whom, check with a health-and-safety or labour-law adviser.
Follow-up actions
An incident register is only worth keeping if each entry leads somewhere. Auditors for SIZA Social and other standards often look past the incident itself to what happened next: was the cause found, was something changed, and was it checked? See our page on SIZA Social, and check the current official document at siza.co.za.
A simple follow-up rhythm:
- Acknowledge: someone responsible has seen the report, the same day.
- Contain: stop it getting worse. Close the valve, put down sand, rope off the area.
- Follow up: fix the cause, clean up properly, and dispose of waste correctly.
- Close: note what was done and when, and tell the team.
These steps do not always happen in order. Sometimes the person who reports also contains it before anyone acknowledges anything, and that is fine.
In FieldSafe, a reported problem appears on the manager’s Today screen. Supervisors and managers record the steps (acknowledge, contain, and follow-up work such as spill response or storm cleanup) in any order. A false report can be corrected or removed. If your farm switches audits on, incident records show which audits they count for. Read more on incidents and safety.
Look for patterns
Once a month, read the register from top to bottom. Three diesel spills at the same tank is not three incidents; it is one problem. Patterns are where the real value of a register shows.
Share what you find. A two-minute mention at the next toolbox talk (“we had three spills at the diesel tank, so the fitting has been replaced and there is now a drip tray”) shows people that their reports lead somewhere. That is what keeps the next report coming.
Emergency numbers on every phone
When someone is hurt, nobody should be looking for a number. Every person on the farm should be able to call for help in seconds, wherever they are.
At the least:
- Put the national emergency numbers, 112 from a cell phone and 10177 for an ambulance, where everyone can see them.
- Add the farm’s own numbers: the nearest hospital or clinic, the farm’s first aiders, the manager.
- Make sure every team knows where the first aid box is and who the first aider on their shift is.
Every phone with FieldSafe has a Someone is hurt screen with call buttons for 112 and 10177, up to three of the farm’s own emergency numbers, the team leader and the office. It works offline, and it records nothing, so nobody hesitates to open it. The record comes afterwards, on paper or in your injury register, once the person is cared for.
Learning, not blame
The register that gets used is the one where reporting is quick, safe and leads to something visibly changing. Build that habit first, and the records follow.
Try it on your farm
Download the free incident report template for injuries, near misses and anything else, or join early access to try Report a problem and Someone is hurt on your team’s phones.
FieldSafe helps you prepare; certification is decided by your certification body.