A weekly moderation workflow for Jetonomy communities

Most community managers burn out not because their community is too large, but because moderation has no defined stopping point. Every open tab is a potential pending decision. The queue is never empty. Time spent grows with the community whether you want it to or not.

Jetonomy’s trust level system removes the human from the obvious-decision path - spam from trust-0 members, flag resolution by trust-4 members, duplicate closures by trust-3 members. What remains for the community manager is a smaller, bounded set of decisions that genuinely require judgment.

This post is a concrete workflow for spending 20-30 minutes per week on Jetonomy moderation and having it be enough.

The moderation surfaces you have

Jetonomy’s moderation work happens in four places:

Surface	What lives there	How often to check
Moderation queue	Posts/replies pending review from new members	Daily (2-3 minutes)
Flag review panel	Content flagged by trust-2+ members	2x per week
Trust level panel	Members approaching promotion thresholds	Weekly
Reported users	Patterns of rule-breaking across multiple posts	Weekly

The queue is the daily touchpoint. Everything else is the weekly review.

Day-to-day: the moderation queue (2-3 minutes)

The moderation queue (admin - Jetonomy - Moderation) collects posts from members at trust level 0 if your settings require pre-approval for new members. The actions are fast:

1. Approve - post looks fine, goes live.
2. Spam - mark as spam, feeds the Akismet training data.
3. Decline - not spam but not appropriate - remove with a template reply.

Most queues at a small-to-medium community have 3-8 items per day. Clearing them takes under 3 minutes if you are making quick calls. The decisions that slow you down are the borderline ones - usually a real member asking a low-quality question. The right call here is almost always Approve with a note suggesting they improve the question, not Decline. Declines on legitimate members cause churn.

One configuration decision that keeps the queue manageable: set trust-level-0 posts to Pending only for your highest-risk spaces (public-facing, heavily indexed). Internal or gated spaces can be set to Publish immediately - the trust level system handles them.

Twice a week: flag review (5 minutes)

When trust-2+ members flag content, it enters the flag queue. This is different from the moderation queue - flags are typically from legitimate members who spotted something wrong in published content, not pre-publication review.

Flag review procedure:

1. Open admin - Jetonomy - Flags.
2. For each flagged item: read the content, read the flag reason.
3. Resolve as spam / remove: clear and obvious. 10 seconds per item.
4. Dismiss the flag: the content is fine, the flag was wrong or overly cautious. Add a note so the flagger understands.
5. Escalate: it is genuinely contested. Take more time, or consult a second moderator.

The flag queue should move fast. If you are spending 5 minutes per flagged item, either the flags are genuinely contested (which is unavoidable) or your community rules are not clear enough for members to apply them consistently.

A healthy ratio: 80% of flags should be resolve-in-seconds decisions. 20% should require thought.

Weekly review: trust levels (5 minutes)

From admin - Jetonomy - Users, filter by “approaching promotion threshold.” This is the list of members who are close to moving from trust 2 to trust 3, or trust 3 to trust 4.

What to do with this list:

• Check the member’s recent posts. Is the pattern genuinely high-quality? Or are they gaming - posting frequently but with low signal? Jetonomy’s trust calculation weights accepted answers and post survival, which makes gaming hard. But a quick scan confirms the system is tracking what you expect.
• Demote a member if needed. If a trust-3 member has gone inactive for 6 months, consider a manual review. Inactive high-trust members are usually harmless, but a formerly-trusted member who became adversarial after a gap would have outsized permissions. Rare, but worth a glance.
• Look for members who should become moderators. Trust-4 members with a long track record of helping others are candidates for trust-5 (full moderation access). This is a deliberate decision - do not auto-promote to trust-5.

Time: 5 minutes, skip weeks where nothing notable is on the list.

Weekly review: patterns and problem users (5 minutes)

This is the judgment layer that the trust system cannot handle automatically. From admin - Jetonomy - Users - Reported:

• Repeated low-quality posts from the same member. Pattern detection catches what single-post review misses.
• Members who consistently generate flags. Even if individual posts are borderline-acceptable, a member who generates 8 flags per month is consuming disproportionate moderation bandwidth.
• High-quality contributors to acknowledge. Who answered 10 questions this week? A public thank-you or a badge nudge (Pro) costs nothing and keeps contributors engaged.

The standard actions:

Pattern	Action
Repeated spam despite trust-0 pending queue	Suspend the account
Pattern of borderline rule-breaking	Private message with specific examples
Consistent off-topic posting	Reply on the posts, link to the right space
High contributor needing recognition	Public reply or badge (Pro)

The decisions you do not have to make

The goal of the trust level system is to remove the obvious decisions from your plate. Specifically, with trust levels correctly configured:

• Spam from new accounts - trust-0 posts go to pending, Akismet catches the obvious ones, you clear the rest in 3 minutes.
• Typos and formatting in titles - trust-3 members can fix these without your involvement. They do, quietly, every day.
• Spam that slips through - trust-4 members can hide spam posts without involving you. It happens before you check the queue.
• Duplicate questions - trust-3 members can close their own duplicates. They self-clean what they can see.

If you find yourself making decisions the trust system should handle automatically - approving edits from trust-3 members, manually hiding obvious spam - it means the trust level thresholds are too conservative for your community. Adjust them from admin - Jetonomy - Settings - Trust Levels.

The full weekly schedule

When	Task	Time
Every morning	Clear the pending queue	2-3 min
Tuesday, Friday	Flag review	5 min
Friday	Trust level panel, problem-user report	10 min
Friday	Write a short community note or reply to a standout post	5 min

Total: 20-30 minutes per week. The morning queue check is the only daily task and it should stay under 5 minutes. If it is taking longer, either volume is growing (scale the morning check to twice a day) or the threshold for pending is too aggressive (loosen it).

Scaling beyond this workflow

This workflow supports communities up to roughly 1,000-3,000 active members. At that scale, a single community manager can maintain it alone.

When volume outgrows it, the right move is not to hire a full-time moderator immediately - it is to lean harder on the trust-4 and trust-5 layer. Identify your most active trust-4 members and explicitly invite them to act as volunteer moderators. Their existing permissions are already moderator-adjacent; you are just naming the role and giving them a communication channel with you.

Jetonomy’s moderation is designed so the community handles the volume and you handle the exceptions. The workflow above is the minimum structure that makes that design work.