A reporting channel should reduce risk, not test courage
An LGBTQ+ group may need to receive reports about harassment, threats of outing, discrimination, misuse of images, boundary violations or moderation failures. The channel should let someone ask for help without posting the case to the group, confronting the reported person or explaining their entire identity. Reporting harm must not require a second disclosure before the first one is taken seriously.
Trans, travesti, non-binary, femboy and feminine people are not interchangeable identities, and no one should have to choose a label to access protection. A form can ask what happened and what support is needed, but legal name, body, transition history, orientation and gender markers should remain optional unless a specific detail is genuinely necessary and the reason is explained.
Offer more than one way in
A single inbox controlled by one popular organiser may exclude anyone who has a conflict with that person. Combine at least two routes, such as a private form and direct contact with another trained person. Where practical, accept anonymous or pseudonymous reports and explain the trade-off: without contact details, the team may be unable to ask questions or share an outcome, but it can still identify patterns and reduce risk.
Make the channel easy to find in the rules, pinned message and group entry page. State available languages, accessibility options, approximate review times and alternatives for someone who cannot write a long account. Distinguish an internal report, a request for support and immediate danger. Moderators should not promise emergency response they cannot provide; for urgent risk, offer appropriate local help without simply abandoning the person.
Ask for the minimum needed to begin
An initial report can start with four fields: what happened, where it happened, roughly when and what the person needs now. A profile name, link or witness can be optional. Avoid requesting identification documents, home address, legal name, diagnosis, gender marker or proof of community membership. The more data a channel accumulates, the greater the possible harm from a breach, account takeover or misuse by moderators.
Before submission, explain who will see the information, why, for how long and when it might be shared. Agreement to have a report assessed is not blanket permission to forward it to leadership, read excerpts in a meeting or approach the reported person with identifying details. If a later stage requires wider circulation, ask again and offer a concise or redacted version.
Do not make perfect evidence a condition for listening
An initial account does not need to arrive as a complete case file. Memories may be incomplete, messages may have disappeared and screenshots may increase distress or danger. The team can listen, record the information as a report and explain what is possible with the material available. A missing screenshot does not prove nothing happened; equally, a report should not trigger automatic punishment without careful assessment and a safe opportunity to respond.
When evidence would help, request proportionate items: a URL, approximate date, account name and a screenshot that preserves context. Ask people to hide unrelated contacts, notifications and bystanders. Do not repeatedly forward intimate images or store illegal content. eSafety recommends keeping evidence of abuse in a separate place to reduce repeated exposure; a channel can receive a description first and agree on the safest transfer method later.
Restrict access and manage conflicts of interest
Only a small number of people should access reports, each with a defined role. Use individual accounts, strong authentication, access records and storage separate from ordinary group conversations. Do not forward screenshots into moderator chats for convenience. Anyone with a close friendship, relationship, dispute or dependency involving the people concerned should declare the conflict and leave the review without receiving further details.
Send a simple acknowledgement with a case number or reference and the next realistic deadline. Do not repeat sensitive material in an email subject or a notification visible on a lock screen. If the team must discuss the case, use a minimal summary and remove identifiers that do not affect the decision. An organiser's curiosity is not an operational need, and a moderator title is not unlimited authority.
Respond with process, proportion and a route to repair
Define possible pathways in advance: guidance, a configuration change, content removal, mediation only when wanted and safe, a warning, temporary restriction or removal from the group. Different cases require different responses. The person reporting should know what was received, which limits prevent certain details from being shared and when another update will arrive. Prolonged silence can look like retaliation or informal protection for whoever has more influence.
Maintain a fair procedure for the person named in a report without unnecessarily revealing the source. Share enough of the alleged conduct for a response, not the reporter's biography. Prohibit retaliation, identity hunting and mobilising friends against either side. If a decision is mistaken or incomplete, provide a review by a different person and record the correction without deleting institutional learning.
Close the loop without keeping a permanent archive of vulnerability
After closure, keep only what a clear purpose requires and delete temporary copies, downloads and duplicates. Set different retention periods for contact details, evidence and statistical records. Trends can be tracked through aggregate categories such as incident type and response time without retaining names or intimate text. Regularly review who still has access and revoke permissions when someone leaves the team.
A trustworthy channel can be summarised as discreet entry, anonymity options, minimum data, proportionate evidence, restricted access, honest timelines, protection from retaliation and an informed ending. In the CorvinNoir experience, community safety does not depend on turning anyone's private life into a public document. Listening with a method protects people and makes moderation decisions more consistent, reviewable and humane.
Leave your voice on this page.
Comments are published only after CorvinNoir approves them.
…