Modhandoff

ModHandoff: Auto-runbook, onboarding, and ownership—so every mod team stays consistent when people join or leave.

Comment

ModHandoff

Inspiration

Every subreddit has “tribal knowledge” that lives in DMs, old modmail threads, and a few senior moderators’ memories. When a mod leaves — or a new one joins — teams lose consistency, miss important coverage in queues and modmail, and end up re-litigating the same edge cases repeatedly.

ModHandoff was built to make moderation knowledge durable, structured, and instantly transferable across teams.

What I Built

ModHandoff transforms moderation continuity into a simple, repeatable workflow for Reddit mod teams.

🧠 Living Runbook (Wiki-backed)

Automatically creates a structured moderation runbook that moderators can continuously update and maintain.

  • Stores workflows, escalation paths, and moderation norms
  • Syncs directly with Reddit Wiki pages
  • Keeps institutional knowledge centralized and searchable

👥 Role Ownership Board

Assigns clear ownership for critical moderation responsibilities.

Tracked roles include:

  • Queue Owner
  • Modmail Owner
  • Automod Maintainer
  • Wiki Maintainer
  • Escalation Lead

All ownership changes are automatically synced to:

wiki/modhandoff/roles

✅ New Moderator Onboarding Checklist

Starts onboarding for a new moderator with one action.

Workflow

  1. Senior mod launches onboarding for a username
  2. New moderator receives a PM checklist
  3. Progress is tracked automatically

This ensures every new mod learns:

  • Community rules
  • Queue handling
  • Escalation expectations
  • Internal moderation standards

🔁 Action Replay + Decision Annotations

Captures real moderation actions from the modlog and turns them into reusable training examples.

Moderators can annotate actions with:

  • Rule Applied
  • Outcome
  • Notes / Reasoning

Example

“Rule 2 → Remove → Repeat low-effort repost”

These annotations build a living moderation training archive synced to:

wiki/modhandoff/replay

📦 One-Click Handoff Packet

Generates a complete moderation snapshot instantly.

The handoff packet includes:

  • Current role owners
  • Onboarding progress
  • Recent annotated moderation decisions
  • Operational notes

Outputs

  • Wiki page
  • Shareable Reddit post

This makes leadership transitions dramatically smoother.

🚨 Ops Assistant

A lightweight operational assistant that helps moderation teams stay organized.

Automatically:

  • Pings leads when roles are unassigned
  • Detects stalled onboarding progress
  • Sends scheduled reminders

How I Built It (Devvit)

Built entirely using the Devvit SDK (@devvit/public-api).

Core Devvit Features Used

addMenuItem

Used for:

  • Mod-only workflow actions
  • Launching onboarding
  • Generating handoff packets

createForm

Used for:

  • Role assignments
  • Onboarding setup
  • Replay annotations

addTrigger

Used for:

  • AppInstall
  • ModAction event capture

addSchedulerJob

Used for:

  • Reminder jobs
  • Ops assistant health checks
  • Follow-up notifications

Storage Architecture

Redis / KV Storage

Used for:

  • Ownership state
  • Onboarding checklists
  • Replay feed data

Reddit Wiki

Used for:

  • Durable documentation
  • Team-visible outputs
  • Shareable operational snapshots

This combination keeps the app lightweight while ensuring critical knowledge remains accessible inside Reddit itself.

Challenges & What I Learned

Building for Every Community

Different communities moderate differently, but one challenge was universal:

Moderator continuity during turnover.

Focusing on continuity made the product broadly useful across subreddit sizes and categories.

Designing for Fast Demos

Every feature was designed to produce visible artifacts immediately:

  • PM checklists
  • Wiki pages
  • Snapshot posts
  • Replay logs

This made the app easy to understand and demo in under two minutes.

Working Within Devvit Constraints

Devvit’s native environment shaped the UX heavily.

Instead of external dashboards or services, I leaned into:

  • Menu actions
  • Native forms
  • Wiki synchronization
  • Reddit-native workflows

The result feels lightweight, reliable, and fully integrated into the moderator experience.

Tiny Real Example

A new moderator joins: Correct_Home2611

Step 1 — Onboarding

A senior moderator runs:

Start New Mod Onboarding

The new mod immediately receives a PM checklist.

Step 2 — Role Assignment

The team assigns:

  • Modmail Owner
  • Queue Owner

Assignments sync automatically to:

wiki/modhandoff/roles

Step 3 — Decision Annotation

A moderator handles a tricky case and annotates it:

“Rule 2 → Remove → Low-effort repost”

The action is saved to:

wiki/modhandoff/replay

Step 4 — Generate Handoff Packet

With one click, the team generates a complete operational snapshot so any moderator can instantly understand:

  • Who owns what
  • What standards the team follows
  • How decisions are made
  • Which onboarding tasks are complete

Why ModHandoff Matters

Moderation teams change constantly, but community standards should not.

ModHandoff helps subreddits:

  • Preserve institutional knowledge
  • Reduce onboarding friction
  • Improve moderation consistency
  • Create transparent operational workflows
  • Scale moderation sustainably

It turns moderation from “knowledge in people’s heads” into a durable, collaborative system.

Built With

Share this project:

Updates