Record
Incident and near-miss reporting software
The report a driver can finish in the cab.
- Works offline
- Seven-step report
- Photo, video and PDF evidence
- RIDDOR triage built in
- CSV export

What the screenshot shows
jobsafe incident register: a context strip for reports in view, open and investigating, awaiting sign-off and RIDDOR notifications due, a toolbar with search, date range, Filters, Saved views and New report, and a table of reports with mono numbers like 26-035, category, site, reporter, reported time, High, Medium or Low severity, Open, Investigating, Awaiting sign-off or Closed status and RIDDOR flags.
The problem, then the record
Three things that go wrong on paper
- 01On paper
Near misses go unreported because the form lives in the office.
With jobsafeA near miss is one of four report categories and the form is on every phone, offline included, so it gets written down where it happened.
- 02On paper
By the time the investigator reads it, the photo is on someone else’s phone and the plate is wrong.
With jobsafeEvidence is captured into the report from the camera, and the vehicle step takes the registration, model, mileage and last inspection at the time.
- 03On paper
Nobody can say which reports are open, waiting for sign-off or heading for RIDDOR.
With jobsafeFour saved views on the register answer that in one click, and every report carries a status gated by role.
The report
Seven steps, and the draft saves itself
Details, site and location with GPS capture, people involved, vehicle or asset, evidence, RIDDOR triage, review. Each step is short enough for a phone in a yard; the draft autosaves on the device as you go.
- Site and locationThe site from your list, the spot from the phone’s GPS.
- People involvedInjured, witness, first aider or involved, with the employee ID.
- Evidence from the cameraPhoto, video or PDF up to 50 MB each, straight from the phone.

The register
A register that already knows what you want to see
Search, a date range and filters, plus four saved views: “My open”, “Awaiting my sign-off”, “RIDDOR pending” and “This week’s high-severity”. Bulk assign, start an investigation, close, or export the lot to CSV.
- Four categories, three severitiesHSSE, near miss, incident or other; high, medium or low; numbered like 26-014.
- Bulk actionsAssign, start an investigation or close several reports at once.
- CSV exportEvery register exports; nothing you record is locked in.

What the screenshot shows
jobsafe incident register: a context strip for reports in view, open and investigating, awaiting sign-off and RIDDOR notifications due, a toolbar with search, date range, Filters, Saved views and New report, and a table of reports with mono numbers like 26-035, category, site, reporter, reported time, High, Medium or Low severity, Open, Investigating, Awaiting sign-off or Closed status and RIDDOR flags.
The investigation
The detail page is the investigation
The evidence gallery, the people, the vehicle card with its UK number plate, a four-level ICAM root cause, the linked actions, similar past reports, a timeline and comments, all on the one record. Open → Investigating → Awaiting sign-off → Closed, each step gated by role.
- Four-level ICAMAbsent or failed defences, individual and team actions, task and environmental conditions, organisational factors.
- Linked actionsActions raised from the findings sit on the report and on the board.
- Timeline and commentsWho did what, when, with the discussion beside it.

What the screenshot shows
jobsafe report detail for an unsecured-load near miss awaiting sign-off: three evidence tiles (two photos and a witness statement PDF), the vehicle card with the UK number plate YJ68 WCD and a Cartwright curtainsider, the site and location card for the Leeds depot gatehouse, and the ICAM four-level root-cause analysis, with similar past reports and the activity timeline on the right.
Connected to
Where this record goes next
Every module writes to the same record, so what happens here shows up in these.
UK regulation
What the law asks of an incident record
The Reporting of Injuries, Diseases and Dangerous Occurrences Regulations 2013 require certain incidents to be reported to HSE and records to be kept for three years. The Social Security (Claims and Payments) Regulations 1979 require an accident book (BI 510) where ten or more people are employed.
jobsafe keeps the record: what happened, where, to whom, the evidence and the investigation, with the RIDDOR triage on the report. It does not submit anything to HSE; the RIDDOR module tells you whether and by when, and you submit.
jobsafe holds no certification and claims none. The records are yours; so is the judgement in them.
FAQ
Frequently asked questions
Straight answers about incident & near-miss reporting in jobsafe.
One that is on the phone of the person who saw it, works without signal, captures the evidence at the time and puts the report in front of the person who has to act. A paper form or an office spreadsheet fails the first three. jobsafe’s seven-step report is built for exactly that, and the register and investigation are on the same record.
Read more
The guides behind this module
Near-miss reporting: the cheapest safety win you’re probably ignoring
Why near-miss reporting matters, what the safety triangle really tells us, and how to build a reporting culture your field teams will actually use.
Read the guide Safety CultureHow to investigate a workplace accident: finding the root cause, not the blame
A practical guide to accident investigation the HSE way: the four steps of HSG245, immediate, underlying and root causes, the 5 Whys, and preventing a repeat.
Read the guide Free toolkitThe site incident and near-miss reporting toolkit
A seven-page PDF: the report template, the RIDDOR flowchart and near-miss triage.
Read the guideSee incident & near-miss reporting on your own setup.
A 30-minute walkthrough with someone who knows the product, on a UK haulier’s data.


