This article is for informational purposes only and does not constitute legal advice. For specific incidents, consult appropriate legal and PR professionals.
There's a moment that comes up in every long-running event organization: something has happened, you've handled it on the back end, and now you have to decide what — if anything — to say to your community.
Get this wrong and you make the situation substantially worse. Say too little and members feel misled when they find out from another source. Say too much and you re-traumatize the reporter, expose people who shouldn't be exposed, or invite a legal situation you weren't in before. The wrong tone — defensive, evasive, performative — can damage trust more than the incident itself.
This article is about how to make the call and how to write the communication when you do.
First: Do You Communicate at All?
Not every incident requires public communication. The default assumption that "transparency means telling everyone everything" is wrong, and it leads organizers to over-share in ways that hurt the people the communication is supposed to protect.
A working framework: communicate publicly when the community has an ongoing safety stake in knowing. Don't communicate publicly when the situation is contained, the reporter wants privacy, and a public statement would mostly serve your need to look responsive rather than the community's need to stay safe.
Public communication is usually warranted when:
- The subject is still active in the community and members may interact unaware.
- Multiple members are affected and a coordinated response requires coordinated knowledge.
- Information is already circulating informally and silence will be read as concealment.
- A policy is changing as a result and members need to know what's different.
Private handling is usually right when:
- The situation is fully resolved (subject left, suspended, banned) and there's no ongoing risk.
- The reporter has asked for privacy and a public statement would identify them.
- The incident was an isolated misunderstanding addressed directly between the parties.
- A public statement would expose details that legally or ethically shouldn't be public.
When in doubt, lean toward less — you can always say more later.
When You Do Communicate: The Holding Statement
If you decide to communicate, the first statement should go out fast. Crisis communications guidance is consistent: issue an initial statement within the first hour of learning about an incident if it's already public, or within 24 hours of deciding to communicate.1 Speed matters because the information vacuum gets filled by speculation.
A holding statement has three jobs: acknowledge that something happened without speculating; express genuine care for anyone affected; and commit to a process without committing to outcomes you don't yet have facts to support.
A workable template:
We're aware of [a recent incident / a concern raised in our community about X]. We take this seriously and are working through what happened. We'll share more as we have it. If anyone is affected and would like to talk privately, [contact method].
That's it. Don't add details you'll have to walk back. Don't promise specific consequences. Don't name people. Don't speculate about motives.
The "we don't yet know everything" framing isn't weakness — it's accuracy. Trying to sound decisive when you don't have the facts is how organizations end up with statements that contradict their own follow-ups a week later.
What Not to Say
Several common moves quietly damage trust:
Don't minimize. "Just a misunderstanding," "blown out of proportion," or "isolated incident" all read as defensive even when true. Let the facts establish proportion.
Don't make the statement about you. "I'm devastated by this" centers your feelings over the affected members'. Save personal reflection for a separate context.
Don't name the reporter, even by implication. "Someone who's been with us a long time" gives away enough for people to guess. Use neutral phrasing: "concerns have been raised," "we've been made aware."
Don't blame the reporter for reporting late, indirectly, or anonymously. Even oblique framing — "we wish we'd known sooner" — discourages future reports.
Don't promise outcomes you can't deliver. "This person will never be welcome here again" feels strong, but if facts emerge later that complicate the picture, walking it back is much worse than never having said it.
Don't post on social media first. If the community has an internal channel — email list, group chat, Discord — it goes there first. Social media is for what needs to be public after the directly-affected community is informed.
The Follow-Up Statement
After the investigation concludes, a follow-up statement updates the community. Usually a few sentences to a paragraph:
Following our note last week, we've completed our review of [the situation]. [Brief description of outcome in general terms]. We're [any policy or process change]. Thank you to everyone who came forward and to the community for your patience.
Include if applicable: what was found in general terms, what action was taken in general terms, what's changing going forward, an invitation to anyone with additional concerns to come forward.
Leave out: names of anyone other than yourself, operational details that compromise privacy, exhaustive justifications, performative emotional content.
The Question of Apology
If your event's processes contributed to the incident — slow response to earlier warning signs, inadequate code of conduct, a hiring decision that turned out badly — an apology is appropriate. Make it specific. "I should have responded faster when concerns about X were first raised, and going forward we're changing Y" lands very differently from "We're sorry anyone had a bad experience."
If your event's processes didn't contribute, don't apologize for the existence of bad actors. You're not responsible for everything that happens at your venue. You're responsible for how you respond.
The test: would the same incident have happened at a well-run version of your event? If yes, focus on response and prevention. If no, the gap is yours to acknowledge.
When Members Push Back
Whatever you say, some members will push back. Some will think you said too much; some too little. Some will demand details you can't share. Some will challenge the decisions you made.
A few patterns that help:
Acknowledge what you heard before responding. "I hear that you want more details. Here's what I can share, and here's what I can't and why."
Don't relitigate the investigation in public. If someone questions the outcome, you can say "I'm not going to discuss specifics publicly, but I'm available to talk one-on-one if you have ongoing concerns."
Distinguish disagreement from harm. Some pushback is legitimate criticism you should weigh. Some is people uncomfortable with the existence of a safety process at all. The first deserves engagement; the second deserves a clear statement of what your event stands for.
Keep the focus on community standards. "This is the kind of event we want to be" is a stronger anchor than "this specific person did this specific thing." It also makes the conversation about the future.
The Quietest Part
The most important part of communicating about an incident is what happens between statements. The community is watching not just what you say but how the event feels in the weeks after. Are reporting channels still open? Are affected people supported? Are you visibly running your event differently? Or did the statement go out and everything went back to normal?
A statement is the start of credibility-building, not the end of it.
The Tools
TellSafe provides the front-end of this — anonymous reporting via QR code or kiosk mode, a two-way relay so reporters can stay in contact through the investigation without being identified, and a place to keep incident records. It started in the West Coast Swing dance community, and the relay specifically turned out to be useful for keeping reporters informed during the silent stretches between public statements.
The communication side is judgment, not tooling. But having tooling for the back-end means the public statement isn't the only place the affected member hears from you — and that changes how the statement itself lands.
Sources
- Trizcom PR, Sample Crisis Communications Holding Statement (March 2026). trizcom.com