Building a strong moderation team: hire, train, and keep them human

Two community staff members reviewing a printed roster and shift notes at a shared desk

11 July 2026

14 min read

AuthorEditorial

A moderation team is not a longer permission grid. It is a small number of people who will still open the queue on a Tuesday when the founder is travelling, who know the difference between a bad take and a ban, and who will not use the nuclear badge to win an argument in Off-topic.

This is the people article. The large XenForo queue already walked node moderators, approval, warning points, soft-delete, and IP tools. Discourse trust levels and the review queue are a different essay. Do not reread either as a hiring plan. You can have perfect tools and a team that ghosts, or a messy stack and three adults who talk to each other. Hire the adults. Then give them a ladder, a shift, a personal account, and a way out.

Community sources for this piece are specific where they exist and silent where they do not. XenForo community practice is sharp on identity: do not post casually as the root Admin; use a personal unbadged profile; on large boards, Moderator Panel by Andrew can keep a Protected Users list so junior mods cannot ban admin profiles. The same notebook does not document hiring interviews, training syllabi, shift rotas, or burnout protocols. Discourse Meta mentions paid moderators in some professional rooms and TL4 as a manual “inner circle,” not an auto-prize. Treat everything below that is not one of those facts as operational practice — the kind you write on a staff page and revise after the first fight.

What you are hiring for

Write the job before you DM a regular.

A moderator is not “someone who posts a lot.” Volume is how you find candidates. It is not the job. The job is four verbs:

Verb	They do	They do not
See	Open the report / flag / first-post list on a schedule	Wait until someone pings them on Discord
Sort	Spam, rule break, interpersonal, “I don’t like this”	Treat every flag as a trial
Act	The smallest tool that stops the harm	Perform the punishment in public for the audience
Write	One sentence the next mod can continue	A novel in the public thread and nothing in the staff log

If a candidate is excellent at volume and terrible at “write,” they will create work. If they are excellent at “act” and terrible at “sort,” they will ban the brilliant jerk’s victim because the victim used a shorter sentence. Train sort and write. Anyone can learn where the button is.

Decide scope on paper:

Room mod — one game, one product, one language. They know the lore. They do not need global ban.
Site mod — every public room, the report list, the obvious alts. Still not billing, still not the root Admin.
Admin — software, legal holds, staff discipline, the account that can destroy the board.

Most communities need more of the first than the third. A twelve-person global-mod group is how you get no one on duty and everyone in the staff thread arguing about tone.

Recruit from people who already do the work

The cheapest interview is last month’s public record.

Look for regulars who:

already move threads, quote the rules without sneering, and leave a path back (“here is how to repost this”)
already absorb heat without escalating
already disappear for a week without drama, then come back — you need to know they have a life
are not the loudest account in every fight

Do not recruit:

the person who applies by listing everyone they want banned
the person whose only energy is “the mods are asleep”
the founder’s friend who has never opened a report
a brand-new account you “have a good feeling about”
someone whose main identity on the board is an argument with a specific other member

Ask in private. A public “we’re hiring mods, reply here” thread selects for people who want a badge. A quiet conversation selects for people who have already been doing the job.

Questions that actually sort:

Here is a real, anonymised report from last month. What do you do in the first ten minutes, and what do you write down?
When was the last time you were wrong in public here? What did you do?
Which room will you not moderate, and why?
How many hours, on which days, can you actually open the list? “Whenever” is a no.
What happens when a friend of yours is the problem?

You are not required to run a corporate interview. You are required to hear them think. If they jump to “ban” on a messy but on-topic fight, they are a deputy, not a moderator.

For professional / vendor communities, Meta notes that some rooms pay moderators to handle escalations and user management rather than relying only on volunteers. That is a budget decision. It does not replace the character test. A paid person with a badge and no judgement is a more expensive problem.

Identity: the Admin account is not a person

This is the rule the XenForo community notebook actually states, and it is the one founders violate for fun.

Administrators should not use the root administrative account — or a profile that is loudly badged Admin — for jokes, debates, or casual chat. When the account that can suspend you is also posting memes, regulars hesitate to disagree. Discussion chills. The root Admin profile is a neutral, system-like actor: announcements, upgrade notes, structured warnings. Staff participate in the room as themselves, on a personal profile that does not carry the nuclear badge.

That split does three jobs:

It keeps official speech searchable and boring.
It lets staff be wrong in public without the badge winning the argument.
It gives you a place to stand when you have to discipline a staff member’s personal account.

Moderators need the same split in spirit even if they only have one login. When they are off duty, they are members. When they are on duty, they sign the action. A staff signature in a warning is not a personality. A personality in a warning is how you get “mod abuse” threads that are actually about tone.

Protected Users. Community large-board practice: Moderator Panel by Andrew includes a Protected Users list so junior moderators cannot ban administrative profiles. That is an add-on, not a moral requirement. The stock version of the same idea: do not hand global ban to room mods, do not leave the Admin account logged in on a shared machine, and do not make the founder’s only account the one that argues in Off-topic. Official XenForo already password-prompts when you edit anyone in the Administrative group. That is the last chance to notice you have the wrong profile open.

Discourse’s notebook did not document a personal-versus-staff account policy. It does document that staff is an automatic group of all moderators and admins, and that TL4 is never auto-awarded — an administrator grants it, or SSO maps it. Do not use TL4 as a public loyalty prize. It is a key. The reward design article already said that.

A ladder, not a pile of global badges

Promote the scope, not the colour of the name.

Member who already sorts
        ↓
Room / node / category moderator   (see, sort, limited act)
        ↓
Site moderator                     (queue, alts, warnings)
        ↓
Admin                              (staff, software, legal holds)

Room first. On XenForo, official scale is node-specific moderators: add the username on the node, pick permissions for that branch, inherit downward. That is how game staff moderate play/ and never see billing. On Discourse, a category’s moderation plus a custom group is the same idea; do not confuse it with “give them TL4 so they can garden everywhere.”

Site second. These people see every report. They get the warning ladder, silence/suspend, and the spam tools. They still should not have the root Admin password.

Admin last. Software, backups, payment, the ability to destroy another staff account. Two people is a quorum. One person is a bus factor.

Do not skip rungs because you are tired. A room regular who has never written a staff note will invent policy in public the first week you give them global delete.

XenForo community performance practice is a constraint on the ladder, not a culture opinion: per-node permission overrides are expensive (rebuild cost grows with groups × nodes). That is an argument for broad rooms and a small number of roles, not for making everyone a global mod “to keep the cache happy.” Culture still wants room specialists. Give them the moderator slot on the branch, not a unique group per person.

Train the judgement, then the buttons

The first two weeks are apprenticeship, not a badge drop.

Week 0 — read-only. They watch the queue with a mentor. They draft what they would do in the staff channel. They do not click. You are training sort and write.

Week 1 — paired actions. They take the action. The mentor countersigns or undoes, in the log, the same day. Public corrections of a new mod are how you lose them and educate the mob.

Week 2 — solo on a written slice. “You own first posts in Introductions and spam in the report list. You do not own bans. You escalate X.” Write X. If you cannot write X, you are not ready to hire.

The playbook they train against is a staff page, not a Discord pin:

What a warning is for (the public reason members will read).
What is a move, what is a soft-delete, what is a silence, what is a ticket to admin.
How to talk when they are the target of the thread.
When to wait eight hours (heat) versus eight minutes (spam, illegal, doxxing).
How to hand off a shift: three bullets, links, what is waiting.

The toxic-user playbook owns the behaviour ladder. This page owns who may climb which rung.

Role-play two cases in staff chat before they go live:

A high-value contributor is cruel to a newcomer.
A newcomer is wrong and loud, and veterans want blood.

If the trainee cannot hold both without picking a favourite caste, they are not ready. “Brilliant jerk” is a culture test, not a tools test.

Do not train on production with the Admin account. Do not train by letting them ban a friend “as a joke.” The Protected Users idea exists because that joke happens.

Shifts are how you stop heroics

A team without a roster is two insomniacs and a graveyard.

Write a boring rota:

Slot	Covers	Escalates to
Weekday late afternoon	First posts, obvious spam	Site mod after 30 minutes on anything else
Evening overlap	Reports that need a sentence	Admin if it is staff or legal
Weekend morning	The overnight pile	Same

Coverage means the list is opened, not “someone is online playing the game.” A moderator in Discord voice is not on shift unless they said they are.

Rules that keep rotas human:

No empty slots you pretend are covered. An honest gap (“Sunday 00:00–08:00, spam sits”) is better than a ghost name.
Two people can take a slot. One will flake. That is not a moral event.
Swap in the staff channel, not in DMs only. The next person needs the log.
Founders take a slot. If the only person who ever empties the queue is unpaid and unnamed, you do not have a team. You have a hostage.

For game and RP communities the clock follows the server, not the office. The server-culture article owns patch night. Here: patch night is a scheduled extra slot, not “everyone panic-moderates in the Discord.”

Discourse and XenForo both let you see who handled a flag. Use that in the Monday note, not as a public scoreboard. A leaderboard of “actions taken” is how you get over-moderation.

Culture: consistency is the product

Members can live with a strict room. They cannot live with a random one.

One policy, many voices. The staff page is the policy. The personal account is the voice. If two mods would do different things with the same report, the page is unfinished. Finish the page. Do not “use your judgement” as a substitute for writing the easy 80 percent.

Appeal exists. A site mod’s warning can be reviewed by another site mod or an admin, in private, on a timer. “The decision is final” is for spam and illegal content. For interpersonal messes, a 48-hour appeal window saves you from 48-day grudges.

Staff disagreement is staff-only. The fastest way to destroy a team is to argue about a call in the public thread. Undo, explain, move on. The member sees one institution.

Off-duty means off-duty. A room mod who is playing the game may still report. They should not approve their own faction’s appeal. Recuse is a grown-up word. Put it on the page.

The founder is on the policy. If you override a trained mod in public because a donor complained, you taught the team that the page is fiction. Override in staff, with a note, and take the next similar case yourself.

Humour has a place. The badge does not do stand-up. The Admin-account rule is the extreme form. The everyday form is: do not dunk on users you just warned.

Burnout is a staffing problem

Moderation eats people who care. The symptoms are operational, not poetic:

They only log in to punish.
Every report is “obviously” the worst case.
They write novels, then nothing.
They take a “week off” that becomes the rest of the year, with the badge still on.
They start arguing as staff in every off-topic thread.

Fixes that actually work:

A written off-ramp. “You can drop to room-only or to member with 48 hours’ notice and no courtroom.” Leaving must be cheaper than ghosting.
A cap on consecutive weeks on the hard slot (legal, harassment, the same three users). Rotate the ugly work.
A second human on the ugly work. Two people reading a harassment report is slower and saner.
No hero channel. A 24/7 Discord @mod is how you train members to skip the forum tools and how you train mods to never sleep.
Take the badge off people who have already left. A ghost with delete permission is not a courtesy. It is an incident waiting.

If you cannot staff the rota with the people you have, you do not need a motivational thread. You need a smaller public surface: fewer rooms, slower first-post promises, a temporary freeze on the channel that generates 80 percent of reports. The active-users article already told you an unanswered first post is a museum. An unstaffed fight room is a fire.

Paid hours, if you have them, buy coverage, not loyalty. Write the hours. Pay the hours. Do not pay “passion.”

Tools only as far as the team needs them

You do not need another suite to start.

XenForo stock that matters to a team: Registered stays primary; Moderating and Administrative are secondary. Node mods for rooms. Soft-delete as the default public action. Warning points that feed a stripped group (the queue article owns the ladder). The Admin password prompt on Administrative edits. Community: Protected Users if junior mods have ban.

Discourse stock that matters to a team: TL1+ flags into a review queue. Flags from higher trust weigh more. Diverse TL3 flags on a TL0 post can auto-silence and hide — staff can still override. Silence (cannot post/flag/PM-start; can read and reply to staff PMs) versus suspend (cannot log in). Watched words are a moderator tool. Staff is an automatic group. TL4 is manual. Do not retrain the whole team on trust-level theory in the hiring week; give them the queue and the two verbs silence/suspend.

Shared hygiene:

Staff notes on the user, not only in Discord.
Same reason codes everyone can search later.
No shared Admin password in a pin.
Two-factor on every account that can ban.
A monthly “who still has the badge” review.

If the team cannot find last month’s note on a user, you do not have institutional memory. You have folklore.

The first 30 days of a new team

Treat a new roster like a launch, not like a permission checkbox.

Day 1. Publish the public version of the rules and the private staff page. They will disagree. That is the point. Fix the disagreement before the first shift.

Day 2. Every new mod posts once as their personal account in a thread that is not a moderation action, so the room remembers they are a person. Then they stop using the badge as a personality.

Day 3–7. Paired queue. Daily 10-minute staff standup in text: waiting, done, one judgement call.

Day 8–14. Solo slice. First appeal happens. Admin reviews it in private with the mod present. The goal is calibration, not a courtroom.

Day 15–30. First scheduled week off for someone. If the board dies, the rota was a lie. Fix the rota, not the person who slept.

At day 30, ask each mod — in private — whether they want the badge. Make leaving easy. The people who stay after that question are the team.

Checklist

A strong moderation team is a habit you can point at on a calendar: someone will open the list, use the smallest tool, write one sentence, and go back to being a person. The software will not do that. The badge will not do that. The people you chose — and the identity you refused to let them perform — will.