Skip to content
Let ideas be heard and improvements last.
Gemy

What is a near miss, how is it reported and why does it matter?

In brief

A near miss is an event that could have caused harm but did not. The law asks for it to be recorded; a good reporting routine shows the accident before it happens. Definition, reporting steps and the investigation sequence.

4 November 2026 · 7 min read

Sample company · demo dataOHS incident record: incident details, official notification warning and investigator
OHS incident record

Türkiye's Occupational Health and Safety Law No. 6331 defines a near miss as an event at the workplace that had the potential to cause harm but did not, and obliges the employer to investigate and record such events. A near miss is therefore not an option but a record the law names. On the floor it is usually either never discussed or told in the corridor and forgotten.

Near miss versus hazard report

The two records are often confused. A hazard report describes a condition before any event: a platform with a missing guardrail, an oily floor, an open panel door. A near miss describes an event that did happen: a foot slipped on the platform but the person held on, a forklift stopped just short of a pallet. Both are valuable, but the near miss has higher priority because it shows the hazard actually in motion.

  • Hazard: a condition that could cause harm; no event yet.
  • Near miss: an event happened, no harm.
  • Accident: an event happened, with injury or damage.

Why it matters

The US Occupational Safety and Health Administration (OSHA) lists investigating near misses and incidents as its own heading among hazard identification steps, and its incident investigation page explains the aim as finding the root cause and preventing recurrence rather than assigning fault. A near miss is the warning the same root cause gives before it ends in an accident next time. Repeated near misses in one area are the cheapest data on where an accident is waiting.

How to report

A good report answers three questions and takes no more than five minutes. The longer the form, the fewer the reports; so the first record is kept short and detail is gathered during the investigation.

  • What happened: the event in one sentence; the question “what would the outcome have been if it had become an accident?” sets the weight of the report.
  • Where and when: unit, machine or area; the time.
  • What you saw: a photo if there is one; otherwise a short description.

Whether the reporter writes their name should be left to them. OSHA's worker participation page states plainly that workers who raise a concern should not face retaliation. If a name is mandatory, the number of reports drops; a falling count does not mean the floor is safe, it means the floor has gone quiet.

No blame, but no cover for negligence (just culture)

EUROCONTROL's definition of just culture strikes the balance: front-line operators are not punished for actions, omissions or decisions commensurate with their experience and training, while gross negligence, wilful violations and destructive acts are not tolerated. A blame-free culture does not mean “everything is forgiven”; it means “honest mistakes are separated from intent”. A company that makes this distinction both protects reporting and takes safety seriously.

  • Honest mistake: the system is fixed, the person is trained, the reporter is thanked.
  • Risky behaviour: conditions are examined, the standard and the audits are reviewed.
  • Wilful violation: discipline applies, but it targets the violation, not the report.

What happens after the report

  • Thanks the same day: the reporter is told the report was received.
  • Investigation: the OHS officer responsible for the unit goes to the scene; what happened, how and in which order is written down.
  • Root cause: a 5 Whys study that questions the condition, not the person; “carelessness” is not a root cause.
  • Action: owner, due date and evidence; the highest feasible level of the hierarchy of controls is chosen.
  • Feedback: the measure taken is told to the reporter and the team; the event is used as an example in the meeting, and the reporter's name is mentioned only if they wish. If similar reports cluster in one area, the problem is in the area, not the people.

Common mistakes

The first mistake is turning the report into a disciplinary file; after that nobody reports. The second is reducing reporting to a number and setting a target of ten reports a month; the target fills the count and empties the content. The third is investigating at a desk; an investigation that does not visit the scene writes a guess, not a root cause. The fourth is closing the measure with “training given” alone; training may be necessary, but on its own it does not change the condition.

What to do in the first month

  • Explain the difference between a near miss and a hazard report to the team with an example; without it, reports either never come or all land in the same box.
  • Show the reporting path on one page: where it is written, who receives it, when an answer comes.
  • Give the fastest answer to the first reports; the three reports of the first week are the seed of the hundred that will come a year later.
  • Describe one report anonymously in the meeting and show the measure taken; the team does not trust the system before seeing it work.
  • Managers report too: if the first report comes from the manager, the floor follows.
  • Offer an anonymous option, but say clearly that the outcome of an anonymous report cannot be returned to the reporter.
  • Track the number of closed actions and the closing time rather than the number of reports; a count target lowers the quality of reports.

The question at the end of the month is not “how many reports came in” but “how many reports got a measure, and in how many days”. A near miss culture starts not with a campaign but with one month of regular answers.

An example from the floor (fictional)

A warehouse worker reported a spot between racks where the forklift's mirror had no view on the turn; nobody was hurt. The investigation found that the same thing had happened three times in two years at the same spot and none had been recorded. The fix was a mirror and a floor line. The reporter was thanked at the weekly meeting; the next month the number of reports from that warehouse rose. More reports do not mean more danger; they mean less silence.

Sample company · demo dataOHS report on a phone: incident type on the first of three steps
OHS report, phone

How it is done in Gemy

  • An OHS report from a phone takes three steps: what happened, where and when, photo and send. The photo is optional; the reporter is asked what the outcome would have been had it become an accident.
  • If “do not record my name” is chosen, the reporter is stored nowhere (including who attached the photo, the file name and the change history); for that reason the reporter cannot open the event later. An accident cannot be reported anonymously.
  • The report goes to the OHS officers responsible for the event's unit; the investigation, root-cause study and actions are done in the event record. Actions land on the central list with the evidence rule.
  • Employees follow their own reports on the OHS page. The OHS board shows accident-free days and events; the accident-free day count is explained with real dates.
  • Health data is protected by a separate permission; only the authorised health role sees it.

The system receives the report and shows its path; the thanks and the measure still come from a person.

In short

A near miss is an event that could have caused harm but did not, and the law asks for it to be recorded. A good report is short, answers three questions and protects the reporter. After the report come thanks, an investigation at the scene, a root cause that questions the condition rather than the person, and an action closed with evidence. A rise in reports shows a rise in trust, not in danger. This article is general information, not legal advice.

Sources

You may copy and share this article with attribution (Gemy, https://www.gemydigital.com/en/blog/ramak-kala-nedir-nasil-bildirilir-neden-onemlidir).

Related posts

Cookies

Essential cookies are needed for the site to work. Analytics cookies load only if you allow them; declining is as easy as accepting. You can change your choice at any time via the footer link.

Cookie policyPrivacy notice