How Do You Get Retail Associates to Report Incidents and Near-Misses?

By awareretailgroup.com Editorial· Edited by Tom Walsh· Published 2026-10-10

Associates report incidents and near misses when they see a report produce a visible result, so fixing that feedback loop first is the step that gets them reporting again. Federal law protects injury and illness reports under 29 CFR 1904.35, and protects a broader right to raise safety concerns under Section 11(c). Theft reports depend mainly on store policy and state law, while a safety near miss falls under 11(c)’s protection for raising a safety concern, not under 1904.35.

Why Associates Stop Reporting Incidents

OSHA groups “close calls/near misses” together with hazards as safety concerns to report (OSHA). This article uses “near miss” only in that safety sense, and incident for theft and workplace violence, which is the vocabulary retail LP sources use.

Blame keeps some people from filing at all. OSHA’s worker-participation guidance states that reporting falls when workers fear retaliation or discrimination for speaking up, particularly when an investigation focuses on blaming the individual rather than the condition that caused the problem (OSHA).

The later silence is worse: the associate already filed, then never heard whether the case went anywhere. Stefanie Hoover, writing in LP Magazine, points to low morale and a feeling that “nothing will come of it” once an employee reports theft to a retailer or to local police. The longer an associate carries the direct burden of theft or violence without seeing a result, the less willing they are to report the next one (LP Magazine).

Hoover’s starting point is blunt: retailers have spent years investing in incident-reporting technology, and store employees still do not report theft when it happens (LP Magazine). The channels exist. In the LPRC’s late-2020 survey of 22 retailers, every respondent offered an anonymous telephone hotline, 81.8 percent took in-person reports, and 72.7 percent accepted electronic messages (LP Magazine). Silence after the last filing is what kills the next one, not the lack of a hotline or an app.

A wet floor can be mopped on the same shift. A theft case waits on police, so the associate may never see it close. The outcome associates are waiting for after a theft report, an arrest or a prosecution, depends on police and a district attorney. NRF’s 2026 study found 63% of retailers report fewer than half of their store theft incidents to law enforcement, and 54% cited concerns about lack of law enforcement response and follow-through (NRF). OSHA still expects employers to report back to workers routinely about action taken on their safety concerns (OSHA).

What Federal Law Protects, and What It Does Not

29 CFR 1904.35 is the narrowest piece of federal protection, and it covers one thing: injury and illness reports. The rule requires employers to “establish a reasonable procedure for employees to report work-related injuries and illnesses promptly and accurately,” and specifies that “a procedure is not reasonable if it would deter or discourage a reasonable employee from accurately reporting a workplace injury or illness” (eCFR). The same section bars discharging or discriminating against an employee “for reporting a work-related injury or illness” (eCFR). That protection does not reach a theft report or a safety near miss that never becomes an injury.

OSHA’s Section 11(c) provision goes wider. OSHA describes it as prohibiting retaliation for a range of protected acts, including “raising a health and safety concern with their employers” and reporting a work-related injury or illness (OSHA). That is the closest federal hook for a near miss that never becomes a recordable injury, though it still runs through a safety framing, not a theft or workplace-violence one.

OSHA’s October 2018 memo is the current word on incentive programs and post-incident testing, and it states that it “supersedes” any earlier interpretive document that conflicts with it (OSHA). Under that memo, an incentive program that rewards near-miss and hazard reporting is “always permissible.” A rate-based incentive program carries more risk, but the memo says its deterrent effect “would likely be counterbalanced” if the employer adds other safeguards. The memo also warns that telling employees they will not face retaliation “may not, by itself, be adequate,” especially when reporting costs them a reward they would otherwise get (OSHA).

OSHA’s own position is not fully settled. The 2018 memo discusses how the rule applies to post-incident drug testing, while OSHA’s live Recommended Practices for worker participation separately warn that “mandatory drug testing following injuries can also suppress reporting” (OSHA). A chain that tests every associate after every reported incident is following one OSHA document and working against another. None of this is legal advice. A store running a multi-state footprint should route any incentive or testing policy through counsel before rollout.

California vs. New York: Two Different Reporting Floors

California requires a workplace violence reporting system inside the prevention plan. New York treats that same system as optional.

California’s Labor Code section 6401.9, created by Senate Bill 553 and enforceable since July 1, 2024 (Cal/OSHA), requires every employer to “establish, implement, and maintain an effective workplace violence prevention plan” (FindLaw). That plan must include “procedures on how to respond to actual or potential workplace violence, and how to accept and respond to reports of workplace violence, including procedures to prohibit retaliation against employees for reporting workplace violence” (Cal/OSHA). California also requires a violent incident log “maintained for a minimum of five years” (FindLaw), plus annual training with additional sessions triggered whenever a new hazard emerges or the plan changes (FindLaw).

New York’s Retail Worker Safety Act takes a lighter touch on the reporting mechanism. NYSDOL states plainly that establishing a reporting system is “not required,” calling it instead “a best practice and a recommended component of an effective workplace violence prevention program” (NYSDOL). Record-keeping gets the same treatment: NYSDOL “recommends” retailers maintain incident report records without requiring it (NYSDOL). Retaliation is still illegal, defined as “punishing, disciplining, or terminating an employee for exercising their rights under the law” (NYSDOL). New York requires training once a year for employers with 50 or more retail employees, and every two years for employers with 49 or fewer (NYSDOL).

A chain running stores in both states cannot rely on one policy. Store managers can check the training specifics in what SB 553 requires a manager to train and the rollout dates in the Retail Worker Safety Act timeline.

Just Culture and the Blame-vs-System Test

A four-bucket error model from hospitals applies to register errors. AHRQ’s Patient Safety Network, summarizing David Marx’s 2001 just culture primer, structures the response to an error around four behavior types: human error, negligence, reckless conduct, and knowing violations (AHRQ PSNet).

Take two cases at the same register. One scans the wrong loyalty number during a rush: a human error. Another disables a security tag so a friend can walk out with merchandise: a knowing violation. Treating both the same way, with automatic discipline, teaches the first associate to stop reporting mistakes before a manager ever finds out.

James Reason’s work on organizational accidents offers a practical filter for the gray area between those extremes: the substitution test. Substitute the associate for someone from the same role with comparable qualifications and experience, and ask whether that person would likely have done the same thing (Managing the Risks of Organizational Accidents (p. 228)). If another associate would likely have done the same thing, the system or the training is the problem. A different answer, where the associate knowingly broke a known rule, moves the case toward discipline instead.

A store LP team can turn that test into a working tool when an incident gets reviewed, before memories fade and before this logic bleeds into associate-facing observe-and-report protocols for live situations like customer aggression, where the expectation stays observe and report, never confront.

A policy that defaults every report to the bottom row of that table, regardless of what actually happened, guarantees associates learn to hide the next incident rather than report it.

Zero Tolerance and Just Culture Can Coexist

Zero tolerance applies to the person who threatens or commits violence. An associate whose own good-faith error is part of the incident is reviewed under the error-versus-violation test, and filing the report is never itself what gets reviewed. A 2020 survey of 22 retailers, administered across the LPRC’s Retail Network and covering more than 52,000 stores, found 96 percent had an official policy for responding to workplace violence incidents, and 95 percent of those policies carry a “zero-tolerance clause” (LP Magazine). The same survey found 27 percent of retailers said workplace violence would lead to termination of the employee involved, and 23 percent said discipline would run “up to and including termination” (LP Magazine). Every one of those figures describes the response to the person committing violence. The survey says nothing about the associate who reports it.

Just culture does not ask a store to go soft on violent conduct. Reckless behavior and a knowing violation still draw the hardest response in the framework researchers use to sort incidents. A policy that writes “zero tolerance for workplace violence” without specifying whether it covers the associate who made a good-faith error while trying to de-escalate a situation leaves that distinction to whoever reviews the case that day, which is exactly the inconsistency that drives associates to stay quiet.

Write both rules into the current violence policy so a night manager is not left to guess which one applies. A workplace violence policy should state, in the same document, that zero tolerance applies to the person who threatens or commits violence, and that an associate’s own good-faith error or near miss gets reviewed under the error-versus-violation test instead. Store managers revising that language this quarter should check it against the zero-tolerance clause and the error-versus-violation test before publishing it.

The Feedback Loop That Keeps Reporting Alive

What keeps people filing is seeing that the last report changed something they can point to on the floor, a repaired sensor or a door that is finally on camera. OSHA’s worker-participation guidance recommends employers “report back to workers routinely and frequently about action taken in response to their concerns and suggestions,” tells them to “provide frequent and regular feedback to show employees that their safety and health concerns are being heard and addressed,” and adds an option for anonymous reporting to reduce fear of reprisal (OSHA). Reason puts it most plainly: apart from a lack of trust, few things stifle incident reporting more than “the perceived absence of any useful outcome” (Managing the Risks of Organizational Accidents (p. 220)). NASA runs the closest working model of that loop outside retail. Its Aviation Safety Reporting System describes itself, in one account, as embodying “a circle of information feedback that begins with pilots, controllers, maintenance technicians, flight attendants, dispatchers and others who voluntarily report their safety experiences” (NASA ASRS). If the person who filed never sees a reply, the next close call stays off the record.

Retail’s version of that loop is thinner. Stefanie Hoover, writing in LP Magazine, argues that the best way to reinforce incident reporting is to make sure action gets taken once an incident is reported (LP Magazine). A corporate review of the violence plan does not reach the associate who filed, so it does not keep that person reporting. In the LPRC survey, nearly 82 percent of retailers reviewed their workplace violence prevention strategy after an incident (LP Magazine); that review happens above the store, and the associate who filed the report rarely hears what it changed.

A store LP team can build its own version of the feedback circle without naming names. Pull the incidents that generated a real change in the last month, strip identifying details about the associate and the suspect, and post the result at the next huddle: a single line naming what got reported and what the store changed. Pair it with the five-minute LP huddle card so it takes a manager minutes, not a meeting, to run. An associate who filed a report six weeks ago and sees it named as resolved learns the report mattered. Three reports of the same problem with no bulletin item teaches the opposite lesson, no matter what the policy manual says about an open-door culture.

Measuring Whether Reporting Is Actually Working

A rising count of reported incidents and near misses is not failure data by itself. One OSHA practices guide lists “the number of reported hazards and near misses” as a quantitative indicator of how a reporting program is performing (OSHA 3885). OSHA’s 2018 memo adds a second measure employers can track directly: a mechanism for “accurately evaluating employees’ willingness to report injuries and illnesses” (OSHA). Do not treat the inbound count as a culture score. Ask at training whether people still think filing is worth it.

A spike in reported incidents can mean associates are reporting more, or it can mean more theft and violence actually happened that month. Volume alone cannot tell those two apart. Track whether the same cashier files again after the first report, because a second filing is the real test of whether reporting still feels safe. Pairing the count with a willingness measure, even a short survey item asked at the next training session, separates a reporting culture that is working from a store that is just getting busier.

What to Do This Week

A manager can run these with the current incident form and the next huddle slot. No new system is required.

• Run every reporting channel, theft, near miss, and workplace violence, through the same test 1904.35 uses for injury reports: would this step deter or discourage a reasonable associate from reporting.
• Build a short “what we fixed” bulletin for the next huddle, using the five-minute LP huddle card, and run it every time an incident report leads to a real change.
• Rewrite the workplace violence policy so the zero-tolerance clause names who it covers, and routes an associate’s own error through a separate review step instead.
• Confirm which state’s reporting and record-keeping floor the policy is actually built to if the chain operates in both California and New York, and apply the stricter one everywhere.
• Add a willingness-to-report question to the next associate training session instead of relying on raw incident counts alone.