How to write a Discord staff application that actually filters people

Most Discord staff applications fail in the same way: they ask why the person wants to help, how active they are, and whether they have been staff before. Everyone writes a paragraph. You still cannot tell who would recuse a friend in a ticket.

A good staff form is short on motivation and long on judgement. You are hiring for a role that sees reports, member DMs, and sometimes bans. Treat it like that.

Start with gates, not questions

Before anyone types an essay, decide who is even allowed to apply. Discord login lets you see account age and username instead of trusting a typed ID. Requiring that they already belong to the server stops drive-by applications from people who have never read your rules.

• Account age: 30 days for helpers, 90 days for admins is a common split. New accounts are cheap; staff access is not.
• Must be in the server: if they cannot join first, they cannot moderate it.
• One open application at a time: people who spam every form are not mysteriously better at tickets.

Five sections that earn their place

1. Availability — timezone, realistic weekly hours, whether they can take a ping-on-duty shift. “I’m always online” is not an answer.
2. Experience — have they been staff elsewhere, why they left, and a Discord tag you could message. Leaving drama is a signal.
3. Scenarios — what they would do, not what they claim they believe. Spam, friend in a ticket, raid, leaking screenshots.
4. Integrity — bans, blacklists, recusal. The honest version is usable. The clean lie is not.
5. Close — one optional “anything else” box. Do not add a second motivation essay.

Write scenarios like incidents, not quizzes

A useful scenario has a conflict. “A member is spamming. What do you do?” is a quiz. “A moderator you like keeps leaking ticket details in staff chat” is a hiring question. Role-specific banks help: helpers escalate, mods document, admins manage people.

Match depth to the role. A trial mod form can be five questions. An admin form that skips staff-on-staff conflict is theatre.

What not to ask

• Full legal name, address, or phone unless you have a real reason and a retention policy. Most community staff roles do not.
• Age as a vibe check. If the community is 18+, say so and ask only what you will act on.
• “Rate yourself 1–10 as a moderator.” Everyone is an 8.
• Duplicate questions that already exist as Discord data (username, join date) if you already require Discord login.

Tell them how review works

A line of intro copy saves you DMs: who reads the form, that staff see private answers, and that a slow no is still a no. If you run a trial role and probation, say that on the form so people are not surprised when approval is not full perms on day one.

When the questions are stable, stop collecting them in a Google Sheet. A queue with notes, Discord pings, and a bot that assigns the role is the difference between “we meant to hire staff” and actually doing it. The free generator on this site will draft the form; ApplyDesk will run it.