“See Something, Say Something” Isn’t a Policy: Building a Reporting Culture That Actually Protects Kids

Child Abuse Prevention Month — April 2026

The phrase hangs on bulletin boards and appears in staff handbooks across the youth-serving sector: “If you see something, say something.” It sounds empowering. It places responsibility on every member of the organization to serve as a watchdog for child safety. And in practice, it fails—consistently and predictably—because a slogan does not function as a system.

When investigators examine cases of institutional child abuse, a devastating pattern often emerges: multiple staff members noticed something. They felt uneasy about a colleague’s behavior. They observed boundary violations. They heard a child say something that raised concern. And they did nothing—or they did something that went nowhere. The phrase “see something, say something” assumed they would know what “saying something” meant, who to say it to, and what would happen next. They didn’t, because no one had built the system.

Child Abuse Prevention Month demands that organizations move beyond slogans and build reporting infrastructures that function under pressure, protect reporters, and produce action.

WHY PEOPLE DON’T REPORT

Understanding why reporting fails requires recognizing that barriers operate on multiple levels simultaneously.

At the individual level, staff members experience what researchers call “diffusion of responsibility”—the assumption that someone else noticed the same thing and will report it. They fear damaging a colleague’s reputation based on a misinterpretation. They worry about retaliation, social ostracism, or earning the label of troublemaker. And they genuinely like the person whose behavior concerns them, which creates cognitive dissonance that the brain resolves by minimizing the concern.

At the organizational level, reporting fails when the infrastructure doesn’t support it. Staff members who don’t know who to report to, what information to include, or what the organization will do with their report default to inaction. Organizations that have punished or dismissed previous reporters—even inadvertently—teach their workforce that reporting carries more risk than staying silent. And organizations in which leadership responds to concerns with defensiveness, delay, or an instinct to protect the institution’s reputation rather than the child’s safety create a culture in which silence becomes the rational choice.

The Centers for Disease Control and Prevention (CDC) identifies organizational culture—specifically the degree to which employees feel empowered and obligated to report concerns—as a critical factor in child sexual abuse prevention. CDC’s publication emphasizes that prevention strategies must address not only individual behavior but the organizational environments that either enable or obstruct reporting.

WHAT A REPORTING SYSTEM ACTUALLY REQUIRES

A functional reporting system answers every question that a concerned staff member might have at the moment they decide to come forward. It eliminates ambiguity, reduces fear, and creates accountability at every stage.

First, the system must define who receives reports. Organizations should designate at least specific individuals—by role, not by name—to receive child safety reports. Organizations also should ensure that a staff member has an alternative if the person they would normally report to turns out to be the subject of the concern, or if that designated person has a relationship with the subject that might compromise objectivity. The designated recipients should hold sufficient organizational authority to act on reports and have training in handling disclosures.

Second, the system must specify what to report. Staff members should not bear the burden of determining whether their concern rises to the level of “abuse.” Organizations should define reportable concerns clearly: any behavior by an adult that violates the organization’s child safety policies; any behavior that causes a staff member discomfort or concern about a child’s safety; any disclosure by a child—direct or indirect—that suggests abuse or boundary violations; and any pattern of behavior that, while not individually alarming, collectively raises concern. The system should explicitly tell staff that reporting a concern that turns out to lack foundation carries no penalty.

Third, the system must prescribe what happens next. This is where most organizational reporting systems fail entirely. A staff member submits a report and then hears nothing. They don’t know whether anyone took action. They don’t know whether anyone investigated the concern. They don’t know whether the child remains safe. This black hole of information breeds cynicism and discourages future reporting.

A robust response protocol addresses immediate child safety (does the accused person retain access to children during assessment?), mandatory reporting obligations to law enforcement and child protective services (who makes that determination and on what timeline?), internal investigation procedures (who investigates, what standard of evidence applies, how the organization documents its findings), communication with the reporting staff member (at minimum, confirmation that the organization received the report and initiated a response), communication with affected families (what, when, and by whom), and documentation and record-keeping throughout the process.

MANDATORY REPORTING: THE LEGAL FLOOR, NOT THE ORGANIZATIONAL STANDARD

Every state requires certain professionals to report suspected child abuse to designated authorities—law enforcement, child protective services, or both. These mandatory reporting laws establish a legal minimum. Youth-serving organizations should build their reporting expectations well above that floor.

The Child Welfare Information Gateway, a service of the U.S. Department of Health and Human Services, maintains a comprehensive database of state mandatory reporting statutes. Every staff member in a youth-serving organization should know whether they qualify as a mandatory reporter in their state, what triggers a mandatory report, who receives the report, and the timeline within which they must file it.

But organizational reporting should extend well beyond the legal mandate. A staff member who observes a colleague giving one child special attention, communicating privately outside of work, and gradually isolating that child from peers has witnessed a classic grooming pattern—but may not have witnessed conduct that triggers a mandatory report under their state’s statute. An organizational reporting system captures this concern and initiates a response before the behavior escalates to the point of legal reporting.

The CDC’s 2007 publication, Preventing Child Sexual Abuse Within Youth-Serving Organizations: Getting Started on Policies and Procedures, outlined six key components of organizational child sexual abuse prevention, including responding to inappropriate behavior, breaches in policy, and allegations. That framework remains foundational for organizations building reporting infrastructure.

PROTECTING REPORTERS

No reporting system functions if the people it depends on fear using it. Organizations must build explicit protections for reporters that go beyond a statement in the handbook.

Anti-retaliation policies should define retaliation broadly—not just termination, but also schedule changes, reassignment, social exclusion, and hostile supervision. The policy should designate a specific process for reporters to raise retaliation concerns and should establish consequences for anyone who retaliates against a good-faith reporter. Some organizations also provide anonymous reporting options—hotlines, online portals, or designated external contacts—that allow staff to raise concerns without identifying themselves.

Anonymous reporting carries trade-offs. It lowers the barrier to reporting but limits the organization’s ability to follow up, gather additional information, or assess the reporter’s credibility. Organizations that offer anonymous reporting should treat it as a supplement to—not a replacement for—a named reporting system with strong anti-retaliation protections.

BUILDING THE CULTURE

Ultimately, a reporting culture depends less on the written system than on the way leaders respond to it in practice. When a supervisor thanks a staff member for raising a concern—even one that turns out to lack foundation—that supervisor builds a culture in which reporting feels safe. When leadership responds to a report with swift, visible action, the organization demonstrates that reports matter. When the designated recipients communicate with reporters about the process (within the limits of confidentiality), they reinforce the system’s credibility.

Conversely, every time an organization dismisses a concern, delays a response, or signals that reporting creates inconvenience, it teaches staff that the slogan on the bulletin board means nothing.

The gap between “see something, say something” and an actual reporting system mirrors the gap between awareness and prevention that defines so much of Child Abuse Prevention Month. The slogan identifies the goal. The system achieves it.

This April, take down the “see something, say something” poster. Replace it with a flowchart that tells every staff member exactly what to do, who to contact, and what happens next. That’s not a slogan. That’s a system.