How to get staff to report near misses

Staff skip reports that cost time and return nothing

Reporting costs time and carries some risk, and staff rarely see anything come back. Four barriers matter: staff do not see the event as reportable, reporting takes time, they fear blame, and nothing visibly happens afterward. The evidence below speaks to three.

You can test time yourself.

The best federal data is about harm, not near misses, and about hospitals. In a 2012 study of Medicare patients discharged in October 2008, the HHS Office of Inspector General found hospital incident systems captured an estimated 14 percent of patient harm events.

Administrators said staff did not see 61 percent of events as reportable. Another 25 percent were events staff usually report but did not that time.

Near misses are likely at least as underreported, since nothing went wrong to prompt a report. That is our inference, not a finding. Of 40 reported events in the study, 28 led to an investigation and 5 to policy changes.

AHRQ's PSNet adds two points. No feedback after reporting is a commonly cited barrier. Nurses have repeatedly said their workplaces lack a blame-free environment.

Give staff concrete near-miss examples

A near miss could have caused harm but did not. OSHA's glossary calls it an incident that could have, but did not, result in death, injury or illness, and one that signals hazards are not controlled. See near miss.

Staff often skip reports because the event feels like a non-event. Use examples from their own setting.

Some regulators ask for these reports. CMS says ASCs should find errors that result in near misses. Pennsylvania's law requires facilities to report near misses, which it calls incidents, to a state authority. Check your own state.

Just culture means a predictable response

Staff know in advance how the organization will respond, and it responds the same way each time. AHRQ's PSNet describes three kinds of behavior. Human error is a slip. At-risk behavior is a shortcut. Reckless behavior is ignoring required safety steps.

The response depends on the behavior, not the outcome.

• Human error: console the person and look at the process.
• At-risk behavior: coach, ask why the shortcut made sense, and fix what rewards it.
• Reckless behavior: hold the person accountable.

Write this into policy and say it aloud. OSHA's recordkeeping rule says a reporting procedure is not reasonable if it would deter a reasonable employee, and bars discrimination for reporting. That covers injuries and illnesses, not near misses, but the logic carries over.

Pennsylvania's MCARE Act protects staff who report serious events or incidents from retaliation. See employee reporting and retaliation and just culture.

Design the first report to take 90 seconds

Treat 90 seconds as a design budget and cut anything that does not fit. It is a target to test with a stopwatch on your own form, not a promise from anyone.

1. Put the entry point where the work happensA QR code on the equipment, room or door. Email for inbox people. A web form as fallback.
2. Ask one thing first"What happened?" in a sentence or two, in the reporter's words.
3. Collect the rest by conversationShort follow-ups come after, only the ones that apply. Let the reporter skip any.
4. Pre-fill what you knowLocation from the code, date and time from the clock, reporter from the login if you want names.
5. Accept a thin reportA short report that arrives beats a perfect one that does not.

In IncidentKit these are quick report by QR code, email-to-incident, the web form and text intake with Lauren. Lauren asks the follow-ups, and a person reviews and signs. Voice is rolling out.

A small 2018 pilot of a voice interface for incident reporting found it usable. Participants felt uneasy speaking aloud about sensitive issues in busy clinical areas, so keep text available.

Close the loop: respond fast and show what changed

A reporter who hears nothing concludes nobody read it. Build the loop into the process so it does not depend on one busy manager.

In IncidentKit, each corrective action has an owner, due date, evidence and effectiveness check. Nothing closes until verified. See close corrective actions.

Leaders should say it plainly, early and often

Staff learn what is safe to report from what leaders do with the first few reports, not from a poster. Try lines like these:

• "Report it even if nothing went wrong. That is the report we most want."
• "We look at the process before we look at any person."
• "You will hear back within a business day."
• "When a report leads to a change, we will tell the whole team."
• "Here is a near miss I was part of, and what we changed."

Leaders also need to be seen. PSNet notes that leadership walk rounds are linked to better safety culture scores. AHRQ publishes Surveys on Patient Safety Culture for hospitals, medical offices, nursing homes, community pharmacies and ambulatory surgery centers. See near-miss reporting and safety culture.

Watch three numbers

Track how many reports arrive, how fast each gets a first response, and how many lead to a verified change. OSHA's recommended practices list reported hazards and near misses as a quantitative indicator for a safety program.

Expect the first number to rise when reporting gets easier. That usually means more is being seen, not that work got less safe. Do not set quotas for individuals. A quota produces filler reports and resentment.

If the count rises but the other two numbers do not move, you have built a faster way to ignore problems. Start with the near-miss report template, or see near-miss reporting.

Frequently asked questions

Sources

• HHS OIG: Hospital Incident Reporting Systems Do Not Capture Most Patient Harm (OEI-06-09-00091, January 2012)
• AHRQ PSNet primer: Reporting patient safety events
• AHRQ PSNet primer: Culture of safety
• OSHA 3886: Recommended Practices for Safety & Health Programs in Construction
• 29 CFR 1904.35: Employee involvement
• CMS State Operations Manual, Appendix L: ambulatory surgical centers
• Pennsylvania MCARE Act (Act 13 of 2002), sections 308 and 313
• Sun, Chen and Magrabi (2018): Voice-activated conversational interfaces for reporting patient safety incidents

Reviewed against the sources above on Oct 5, 2026. Rules change: confirm current requirements with the issuing body or your counsel before relying on any summary.