How to Review Discord Applications as a Team

One person reading every application works until the first busy week. Then answers sit unread, two moderators reply to the same person in DMs, and nobody remembers who said yes. Reviewing as a team fixes that, but only if the rules are set before the pile starts.

This is how we would set it up, with Mico or without it.

Who should be allowed to decide?

Fewer people than you think. Everyone on staff can read applications and have an opinion. The people who press the button should be the ones who will answer for the decision when the applicant asks why.

In Mico two groups can decide:

A reviewer role is set per panel. That is the useful part: your partnership managers review partner requests, your head moderators review staff applications, and neither sees the other's queue. How many reviewer roles a panel can hold depends on the plan; the pricing page has the numbers.

If you started with /setup, you already have this. It reuses a role that looks like staff (Staff, Moderators, Admin) or makes one called Application Reviewer, and it makes a private #application-reviews channel only reviewers can read. The staff application setup guide walks through it.

Where should applications land?

In a private channel per kind of application. Each panel has its own review channel, so a staff round and a whitelist wave never mix. Keep it private: the review message shows every answer and the AI score, and applicants should never see either.

Each application arrives as one review message:

What is on it:

• the answers, with the full application attached as a text file for long ones
• a quality score and a "Looks AI-written" score, each out of 100, with a short reason (when AI scoring is on and the server has scores left this month)
• how long the applicant took to fill it in
• Accept, Deny, History, Talk to them and a link to the dashboard

On paid plans a panel can also ping roles when a new application arrives. Pick a role your reviewers actually watch, not @everyone on staff. A ping nobody owns becomes noise in a week.

How do you discuss an application before deciding?

In a thread, never in the main channel. Two kinds exist, and they do different jobs.

A habit that saves arguments: whoever opens the discussion closes it with one line, "accepting" or "denying, reason: ...", and then presses the button. The thread stays as the record of why.

Pressing Talk to them a second time reopens the same thread, even after Discord archived it. You never end up with two half-empty threads for one person.

What stops two reviewers deciding the same application?

The first click. When a reviewer presses Accept or Deny, Mico records the decision and every later click on that application is refused with "Someone else decided this application a moment ago." The applicant gets one message, the roles change once and the review message updates to show who decided and when.

So you do not need a claim system for the decision itself. You may still want one for the reading, so two people do not spend ten minutes on the same long answer. A cheap way: react with your own emoji on the review message when you start reading. Mico does not track that; it is a team convention.

Should you check the applicant's history first?

Yes, for anyone who has applied before. The History button shows that person's earlier applications in your server: when they joined, how many they sent, how many were accepted or denied, their average scores, and each past decision with who made it.

It answers the questions that matter in a team. Did someone already deny them last month? Was it for the same panel? Did they withdraw twice before sending? History needs Premium or Pro.

How do you review from Discord without scrolling the channel?

Use /review. It is one menu with everything a reviewer needs:

The dashboard on the website shows the same queue, for reviewers who would rather read long answers on a big screen. A decision made in either place is the same decision.

How do you keep reviewers consistent?

Write down what a yes looks like, in one pinned message in the review channel. Three to five lines:

Then use Reviewer statistics once a month. If one reviewer accepts nine in ten and another accepts one in ten, the standard is not shared yet. That is a conversation, not a reprimand.

The deny reason deserves its own care, because the applicant reads it word for word. How to write a denied message covers that half.

Where does Mico stop?

If your server truly needs a formal vote, run it in the staff thread and let one person record the result. Most teams find that one person deciding with the thread as backup is faster, and the history shows who decided if anyone asks later.

The AI score is advice for the reviewer, not the decision. If you want to know what it reads and what the auto-accept and auto-deny settings do, read what the AI score can and cannot tell you.