Incident Register Log

An educational library of workplace documents — purpose, who completes them, when they are used, typical fields, common mistakes and how they connect. Linked to workplace safety, workplace training, occupations, industries and employment documents. Informational only — template examples, not legal advice or official documents; employers remain responsible and using a document does not guarantee compliance.

What an incident register log is

An incident register log is the summary layer above individual reports — one line per event, showing what happened, when, its type and whether it is open or closed. It lets an employer see the whole picture and track that actions are being completed.

This is an educational overview with a simplified example. It is not an official template, and the register summarises events; it does not replace the detailed reports or any required external reporting.

Purpose

• Provide a single overview of incidents across the workplace.
• Track each event’s status from open to closed.
• Reveal trends by type, area and time.
• Help ensure no incident or action is forgotten.

Who completes it

• A coordinator, manager or safety lead maintains it.
• Entries are drawn from individual incident reports.
• The employer decides who has access and how it is reviewed.
• Personal detail is kept minimal in the summary view.

When it is used

• Updated each time an incident is reported.
• Reviewed regularly to track open actions and trends.
• When management or a safety committee reviews performance.
• When patterns need to be examined across many events.

Typical columns

• A reference number and the date of the event.
• The type of event and a brief summary.
• The area or task involved.
• The status — open, in progress or closed.
• The action owner and a link to the detailed report.
• Example columns only — adapt to your process and the applicable law.

Common mistakes

• Holding excessive personal detail in a shared summary.
• Letting the register fall out of date with the actual reports.
• Marking events closed without checking actions were completed.
• Never analysing the trends the register reveals.

Document workflow

An incident register log sits above accident reports, near miss reports, dangerous occurrence reports and investigations, summarising each and tracking corrective actions to completion. Trends it reveals feed a review of the relevant risk assessments and instruction.

See the related documents below for what is commonly used with and completed after entries in an incident register log.

Retention (high level)

The register and the records it links to are kept for a period set by the applicable law and the employer’s data-protection duties. This page does not state a period — confirm with the applicable law and the official authority.

Completing and sharing as a PDF

Incident registers are commonly maintained digitally and exported, or summarised and stored as PDFs for review. Exporting to PDF supports the record; it does not replace the detailed reports or guarantee compliance.

Employer checklist

• Keep the summary minimal on personal detail and control access.
• Keep the register aligned with the underlying reports.
• Only close events when actions are genuinely complete.
• Review the trends and act on them.

Worker notes

• Reporting incidents keeps the register accurate and useful.
• Ask where an action you own stands in the register.
• Trust that the summary keeps personal detail to a minimum.

Country considerations

Expectations around recording incidents and handling the data vary by country, and the official authority differs. This page is general and high-level — not a statement of any country’s law and not legal advice.

Confirm requirements with the official authority for your country and a qualified professional.

Who is responsible

The employer is responsible for keeping incident records, tracking actions, protecting the data and compliance. This page is an educational overview with a template example; it does not replace detailed reports or external reporting and does not transfer responsibility.