Estimating moderation workload before membership grows

Base the estimate on the actions people must perform, not membership count alone. List the tasks, estimate their frequency and duration, then model how activity might change. Keep the forecast as a range and allow for difficult cases and interruptions.

Four-step moderation workload estimate

Count the work behind each item

Moderation can include reviewing a report, reading context, deciding on an action, explaining it to a member, documenting it and consulting another owner. Registered accounts do not show how often those tasks arise or how long they take.

Use categories that reflect effort:

Count each incoming item once for volume, then record the actions and time it generates. One report followed by a warning and appeal is still one initial report but several pieces of work.

Moderation work categories to count

Establish a baseline or scenario

For an existing community, sample more than one kind of day. Record arrivals, handling time and unresolved work by category. Read cases behind the counts so a short queue is not mistaken for easy work.

Discourse provides built-in admin dashboard reports covering various community metrics, and notes that only staff can access them. Reddit offers a Mod Insights help page. Definitions differ, and these reports do not provide a complete labour estimate. Include work done outside the platform.

For a proposed community, label inputs as assumptions. State expected posts, reports and other actions, then replace the assumptions when real work can be observed.

Calculate time and uncertainty

Multiply expected items in each category by the time per item, then add scheduled coordination and a separate allowance for unpredictable work. For illustration, 50 routine reviews at two minutes each, five complex cases at 12 minutes each and three hours of coordination total five hours and 40 minutes. This fictional calculation excludes interruptions, follow-up and leave; its inputs are not staffing benchmarks.

Model a normal period and a busier one. Membership, posting, reports and case complexity need not grow at the same rate. Show the assumptions so the team can revise the estimate when the mix changes.

Turn the estimate into a decision

Compare required hours with time trained people can protect for moderation. Check when that time is available and who can act during an absence. Spare time does not clear a queue if the person lacks the relevant authority or access.

Choose a review trigger before expanding: a sustained rise in unresolved items, a longer wait for human review or repeated dependence on one person for complex decisions. Possible responses include training another reviewer, changing unnecessary approval steps, improving routing or narrowing the response promise.

Automation may reduce some repetitive work while creating alerts that need judgement. Discord publishes an AutoMod FAQ. Include the time to review those alerts in the forecast.

Automation trade-offs