Priority routing must reward credible urgency without treating repeated reports as proof.
Fast investigation protects members, while broad escalation protects reviewers from a queue shaped by crowd behavior.
Who you’d be doing this for
“By the time I find the report that mattered, I’ve already dug through twenty copies of the same argument.”
Bianca Konstantinou · Volunteer Moderator
Runs moderation for a large gaming server where members use reports to flag harmful content between moderator shifts.
What is at stake
Urgent reports are getting lost among repeated submissions in large servers. You must weigh faster routing against unfairly deprioritizing harm that arrives with little context.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- urgent-case recall vs queue noise
- learned signals vs controllable rules
- faster routing vs reviewer trust
- historical labels vs emerging harm patterns
Why Discord
Reported-content review sits between community members asking for help and the enforcement systems that act across servers.
Written with these in mind
Not your kind of problem? 16 more at Discord, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.