ModWatch

• 

  sceduler

• 

  Home page

• 

  stats and Live chat

ModWatch — Full Project Story

Where it started Reddit has over 100,000 actively moderated communities. Behind every one of them is a team of unpaid volunteers — moderators who remove spam, handle ban appeals, manage conflicts, and keep communities safe. They do this with zero coordination infrastructure. No scheduling tools. No shift handovers. No shared memory. No visibility into who is doing what. They coordinate through DMs, random wiki posts, and word of mouth. The system works until it doesn't — and it breaks in the same five ways, in every subreddit, every single day.

The five problems Problem 1 — No coverage Mod teams have no shift system. Everyone shows up when they feel like it. Busy hours get triple coverage. Nights get nothing. Spam runs free for hours until someone happens to log in. Like a hospital where five doctors all show up Monday morning and nobody covers the emergency room at night. Problem 2 — No handover When one mod finishes and another logs in, there is zero context transfer. Was there a troll attack? Are there open appeals? Did someone get a warning that is about to escalate? The incoming mod reads the entire queue from scratch with no memory of the last eight hours. Like a nurse arriving for a shift with no patient notes. Every session starts blind. Problem 3 — No coordination Two mods online at the same time have no awareness of each other. Alex removes a post. Priya re-approves it ten minutes later thinking AutoMod did it. A user gets banned by Sam, then unbanned by Zara who never saw the reason. Inconsistent moderation is one of the top complaints users have about Reddit communities — and it is entirely caused by mods having no coordination layer. Problem 4 — No visibility The head mod has no dashboard. No data. No way to see who is actually working. They only find out a mod is burned out when that mod quits. They cannot have a fair workload conversation because there is nothing to point to. Like a manager trying to run a performance review with no attendance records and no output data. Problem 5 — No memory Every team has a veteran mod who has been there for years and just knows things. Every Friday night there is a raid from a rival community. This spam pattern means that account type. Do not remove posts with this flair. When that mod leaves, every piece of that knowledge disappears. There is nowhere to store it that the whole team can see, build on, and pass forward.

The insight These five problems are not separate. They are a chain. No schedule causes no coverage. No coverage causes no handover. No handover causes no coordination. No coordination causes no visibility. No visibility causes no memory. Fix the chain and you fix mod team dysfunction entirely. Every other team coordination tool in the world — Slack, Notion, Linear, Jira — exists because teams need this infrastructure. Mod teams have never had it because they operate inside Reddit, and nothing has been built inside Reddit to give it to them. Until Devvit.

Why Devvit makes this possible now Reddit launched Devvit — their native developer platform — to let developers build tools that live entirely inside Reddit. Devvit gives developers Redis for persistent storage, a scheduler for background jobs, real-time presence, and full access to Reddit's mod API. No external servers. No OAuth setup for users. No leaving Reddit to use a third-party tool. ModWatch is only possible because Devvit exists. And Devvit was built specifically for problems like this.

What ModWatch builds Shift Scheduler — Mods claim half-hour slots from a 48-slot daily grid. The queue auto-advances as time passes. Uncovered slots trigger automatic modmail alerts to the team before gaps happen. Live Presence — Every online mod is shown at the top of the dashboard in real time with their name, current shift status, and session duration. No more invisible teammates. Live Mod Chat — When multiple mods are online simultaneously, a live chat panel activates so they can coordinate in real time without leaving Reddit or switching to DMs. Handover System — When a mod's shift ends, a mandatory popup appears. They write what happened, who to watch, what is unresolved, and what is urgent. The next mod reads this the moment they open the dashboard. No session ever starts blind again. Action Lock — When a mod actions a post, a 30-second Redis lock prevents any other mod from actioning the same thing simultaneously. Duplicate decisions become technically impossible. Incident Tracker — A shared live board for active moderation events. Troll waves, ban appeal escalations, coordinated spam attacks — all tracked with severity levels, open and resolved states, and full history. Mod Stats — A head mod dashboard showing weekly action counts per mod. Removes, approvals, bans, warnings, handovers. Real data for real conversations about workload and contribution. Warning History — Every warning issued to every user is logged with reason, mod, timestamp, and linked post. Any mod can see the full history of any user before deciding whether to warn, escalate, or ban. Playbook — A permanent, editable team knowledge base. Recurring raid patterns, spam signatures, escalation procedures, seasonal protocols. Institutional memory that survives when mods leave.

What it delivers One Devvit app. One click install. Works immediately on any subreddit with no setup beyond installation. All five pain points solved end to end. Built in three days by one developer on Reddit's own infrastructure. ModWatch does not make moderation easier by doing it for you. It makes mod teams function — by giving them the coordination infrastructure that every other team on earth already takes for granted.

Built With

• devvit
• devvitblocks
• devvitreddis
• redditmodapi
• typescript