Recruiting and training Discord moderators
A moderation team rarely breaks on an incident. It breaks on a disagreement between moderators that nothing had anticipated — and that disagreement almost always comes from recruitment, not moderation.
Updated 12 September 2026
When to recruit
The signal is not member count, it is hour coverage. While you are present when your server is alive, you need nobody. As soon as things happen while you sleep, you do — whether the server has 200 members or 5,000.
Two or three moderators across different hours beat five available at the same time. It is the only criterion that matters at first: an excellent moderator present when you already are solves nothing.
Recruiting too early is a real risk: a team with no work invents subjects, and that is where internal conflicts over non-existent questions are born.
Where to look: at home
Recruit from your active members, not outside. Someone who already knows the server’s culture will make better calls than a seasoned moderator parachuted in, who will apply another server’s habits.
Good candidates stand out without an advert: they answer newcomers’ questions unprompted, they defuse rather than inflame, and they report instead of commenting in public.
Beware the opposite signal: someone who asks to be a moderator often wants the role more than the work. Not disqualifying, but worth checking.
The questions that actually help
Classic application questions — age, experience, availability — predict nothing. Three scenarios teach you more, because they show reasoning rather than a CV.
- “Two members are arguing, neither broke a rule. What do you do?” — the right answer is rarely a sanction.
- “A friend of yours breaks a rule. What do you do?” — the answer that counts is “I raise it with the team rather than decide alone”.
- “You disagree with a team decision, made in public. What do you do?” — the right answer is “I discuss it in private”, not “I say so in front of everyone”.
The third is the most discriminating. A team that contradicts itself in public loses its authority in one go, and does not get it back.
Grant rights gradually
A moderator on trial does not need the ban. They need to delete a message, time someone out, and talk to the team.
Splitting rights is not suspicion: it lets someone learn without a mistake being irreversible. A misplaced mute can be lifted; a misplaced ban leaves a public trace and a grudge.
- Weeks 1-2: access to the staff channel, reading reports, no sanction power. They observe and ask questions.
- Then: message deletion and short timeouts.
- Once trust is there: long timeouts, then kick and ban.
- Never:
AdministratororManage Roles. Both bypass everything else, including granting themselves more rights — they have no business on a moderation role.
Write down what is not up for debate
Three moderators with no shared sanction ladder produce three different case laws. Members notice fast, and the favouritism accusation follows — it destroys a team more reliably than any troll.
A two-page internal document is enough: the sanction ladder by offence type, what is decided alone and what is decided together, and the rule on public disagreement. Nothing more, but nothing less.
What makes moderators leave
- No recognition. It is volunteer work, invisible when done well and criticised when done badly.
- Decisions overruled in public. Correcting a moderator publicly strips their authority for everything after. Do it privately, always.
- The load carried by one person. Often invisible until they leave all at once — look at the real distribution of work, not the team list.
- Vagueness. Not knowing what you are allowed to do is more exhausting than doing a lot.
How Kuratos helps
The Moderation module keeps a sanction history with each one’s reason and author. That makes a team decision arguable from the record rather than from memory — and lets you observe a difference in treatment instead of debating it.
The Tickets module shows how many tickets each staff member handled. It is the figure that reveals one person is carrying all the support, long before they complain about it.
The Reports module lets members escalate abuse without a public ping, with predefined sanctions: two moderators facing the same facts then apply the same thing, without consulting each other.
Key points
- The recruitment signal is hour coverage, not member count.
- Recruit from your active members: server culture cannot be imported.
- The most discriminating question: what do you do when you disagree in public?
- Never
AdministratororManage Roleson a moderation role. - Correcting a moderator in public strips their authority for good.
Frequently asked questions
How many moderators does a Discord server need?
What matters is hour coverage, not headcount. Two or three people across different time zones are enough for most servers of a few thousand members.
Do you need an application form?
It helps to filter, but predicts nothing on its own. Three scenarios teach more than ten questions about experience, because they show reasoning.
What rights should a new moderator get?
Deleting messages and short timeouts. Kick and ban come later. Never Administrator or Manage Roles: those bypass every restriction and allow granting further rights.
How do you handle a disagreement between moderators?
Privately, every time. A team that contradicts itself in public loses its authority in one go. The rule must be written before the case arises.
Put this guide into practice
Kuratos sets up in minutes what this guide describes, and is configured from a web interface rather than through commands.
