Incident reporting: how to set up reporting and incident management
Incident reporting is how an organisation captures near misses, accidents and security events so it can learn from them and stop them happening again. This guide explains the key terms, what to put in an incident report, how to set up a digital incident management process in four steps, and why most reporting schemes fail.
Key takeaways
- Report near misses too – they are your cheapest warning signs.
- An incident management “system” is a process, not necessarily an IT system.
- Make reporting fast and simple, or people will not report.
- Use one report format per incident type, with only the fields you need for analysis.
- Close the loop: thank the reporter, act on the report and share what changed.
What is incident reporting?
Incident reporting is the act of recording an unplanned event – or a planned event that failed to happen – so it can be handled and analysed. It is the first step of incident management. Accidents rarely happen without warning: most are preceded by near misses that nobody wrote down. The World Health Organization estimates that around one in 10 patients in high-income countries is harmed during hospital care, and that roughly half of that harm is preventable.
Standards and process literature use several related terms:
| Term | Meaning |
|---|---|
| Incident | An unexpected event outside standard operations |
| Near miss | An incident that could have caused harm but did not |
| Deviation | A departure from an approved instruction or standard |
| Non-conformity | A failure to meet a requirement |
| Non-conformance | A defect that makes a product unacceptable |
What is an incident management system?
An incident management system is a structured way to report, prioritise, contain, analyse and prevent incidents. It covers the processes, roles, instructions and tools involved. “System” does not mean IT system: ISO 27001 describes a process approach and does not require any specific software. The process is what deserves attention; an IT tool just makes it easier to run, share and document.
Done well, incident management helps you:
- Stop incidents becoming accidents, where the real costs start.
- Meet legal, regulatory and contractual obligations.
- Restore normal operations quickly.
- Make sure the same incident never happens twice.
- Share what you learn across the whole organisation.
Without it, delays, product failures, data breaches and injuries become more likely – and harder to explain to auditors and customers.

“The improvement ideas that constantly flow from our employees are all reported digitally, picked up by process owners, and some incorporated back into our management system.”
Read case
Hans Jørgen Ebbesen,
CEO, CJ A/S
Which types of incidents should you report?
Most organisations need to handle two very different types of incidents, each with its own ISO standard:
- Health, safety and environment (HSE) – ISO 45001. Events that could cause injury, damage or an accident, such as not wearing a helmet on a construction site. Get ISO 45001
- Information security – ISO 27001. Events that threaten information, even if nothing was compromised. A cyber attack that was repelled is an incident, not a breach. Get ISO 27001
Why does incident reporting fail?
Most reporting schemes fail for the same few reasons:
- A culture of blame. If admitting a mistake makes you look bad, nobody reports – especially when no one was hurt. Management has to treat incidents as chances to learn, not individual failures.
- Reporting is too hard. If reporting takes too long, or people do not know where to report, it does not happen. Balance the data you need against the effort it takes.
- No response. If reports disappear without a reply, people stop reporting. A thank-you and an update on what changed cost nothing.
- Missing data. Without the time, place, sequence of events, photos or log files, analysis is guesswork. A good form and clear instructions fix this.
How do you report an incident?
- Prevent the incident from becoming an accident. Stop the immediate risk if you can do it safely: turn off a machine, clean up a spill, block access to the area – or, for IT incidents, stop a phishing email from spreading or change a compromised password.
- Gather information. Record the date, time, location, people involved and witnesses. Take photos or screenshots if it is safe.
- Report the incident. Fill in the incident form so the formal incident management process starts.
What should an incident report include?
Use one format per incident type and keep it short. These fields cover most needs:
| Field | Basic | Workplace safety | Medical |
|---|---|---|---|
| Date, time and location | Yes | Yes | Yes |
| Description of what happened | Yes | Yes, incl. sequence of events and equipment | Yes, incl. symptoms and treatment |
| People involved and witnesses | Yes | Yes, incl. job title and department | Yes, incl. patient details |
| Injuries or damage | Yes | Yes | Patient condition after the incident |
| Immediate actions taken | Yes | Yes | Medications and dosages |
| Safety equipment used | – | Yes | – |
| Root causes and corrective actions | Recommendations | Yes | Follow-up actions |
| Sign-off | Reporter | Reporter and supervisor | Healthcare provider |
How to set up a digital incident management process in 4 steps
Handling incidents case by case leaves gaps in the documentation – and no trail to prove each case was handled correctly. A digital process fixes that. Here is how, using Gluu as the example.
Step 1: Map the process. Create a process such as “Manage IT security incident” with the outcome “Incident has been logged, analysed and preventive measures taken”. Add a swimlane per role and the activities for reporting, prioritising, containing, analysing and preventing.

Step 2: Add instructions and tasks. Keep instructions short and add tasks to the critical activities so they become measurable. The task for “Register incident” is a form employees fill in from a browser or the mobile app.

Step 3: Prepare variations. Create one overall incident management process and handle each incident type as a variation, so you avoid duplicate instructions.
Step 4: Run and improve. Every report starts a case that is logged automatically and can be exported as a report. Use what you learn to improve the process. Download a sample IT security incident playbook (PDF).
5 incident management best practices
- Make reporting correct and easy – one place, one template per type, available to everyone.
- Recover fast – describe how to stop the damage and get operations back to normal.
- Analyse, learn, mitigate, repeat – find the root cause instead of moving on once the fire is out. See our incident root cause analysis examples.
- Improve how you improve – update training, onboarding, maintenance plans and the incident process itself as you learn (Plan-Do-Check-Act).
- Manage risk without closing the business – reduce risk “as low as reasonably practicable” (ALARP), not at any cost.
If you want to run incident reporting as a digital process, you can try Gluu free for 30 days.
Gluu free 30-day trial. No credit card required. Start from €24 / year.
FAQ – Incident reporting
Incident reporting is recording an unplanned event, near miss or failure so it can be handled, analysed and prevented from happening again. It is the first step in incident management.
An incident is any unexpected event outside normal operations. A near miss is an incident that could have caused harm or damage but did not. Reporting near misses is the cheapest way to prevent accidents.
An incident management system is a structured process for reporting, prioritising, containing, analysing and preventing incidents. It does not have to be an IT system – ISO standards require a process approach, not specific software.
At a minimum: date, time and location, a description of what happened, the people involved and witnesses, injuries or damage, immediate actions taken, and recommendations or corrective actions.
Usually because of a blame culture, because reporting is too slow or complicated, or because earlier reports got no response. Fix all three to get reliable data.
A digital process captures reports in one place from any device, assigns tasks to the right people, leaves an audit trail and makes it easy to analyse trends and follow up on corrective actions.
ISO 45001 covers health and safety incidents and ISO 27001 covers information security incidents. Both describe a process approach to reporting, handling and preventing incidents.