Recruiting, without
the spreadsheet.
Build the form once, put a button in your server, and review what comes back as a team — with a decision that actually does something at the end of it.
Included free Applications are free on every plan, including paths, reviewer roles and acceptance roles.
One form, or one form with paths
Most servers start with a single set of questions. When you need to recruit for two things at once, add paths — shared questions first, then the ones that only apply to the route somebody picked.
Cascade RP — Staff Application Open
Shared questions — everybody answers these.
- Short answerWhat should we call you in character?
- ParagraphTell us about your roleplay experience.
- Short answerRoughly what hours are you around?
Application paths Optional
- Patrol 3 extra questions · reviewed in #patrol-review Open
- Dispatch 2 extra questions · reviewed in #dispatch-review Open
- Fire & Rescue 4 extra questions Closed for now
Paths are optional
A form with no paths behaves exactly as it always did. Nothing is converted, and there is no structure to migrate to.
Preview before you publish
See exactly what an applicant would see, path by path, before anybody can submit. The preview is built from the same answer the submission path uses, so the two cannot disagree.
History stays readable
A submission keeps the questions as they were worded when it was answered. Rewording a question later never rewrites what somebody was actually asked.
Reviewing is not managing
Reading and deciding applications is a different permission from editing the form. Somebody you trust to review does not have to be trusted to rebuild the questions.
The review queue
Submissions arrive where you routed them, with everything the applicant wrote and a decision that does something.
| Applicant | Path | Submitted | Status |
|---|---|---|---|
| Rowan A. | Patrol | 2 hours ago | Awaiting review |
| Priya N. | Dispatch | Yesterday | Accepted |
| Sam O. | Patrol | 2 days ago | Denied |
Rowan A. — Patrol Awaiting review
What should we call you in character?
Rowan Ashby
Tell us about your roleplay experience.
About two years across a couple of servers, mostly patrol and traffic. Happy to start on nights.
On acceptance: adds @Patrol @Staff — checked against your server before it runs.
Who it is for
Servers recruiting staff
Whitelist applications, staff applications, department transfers — anything where somebody answers questions and a team decides.
Servers recruiting for several roles
One panel, one form, several paths — instead of three forms nobody can keep in step and a channel full of duplicate buttons.
Small teams
No external form tool, no copy-pasting answers into a channel, and no second place where the decision has to be written down.
Setting it up
Create a form
Give it a name and the questions everybody should answer. Two question types: a short answer and a paragraph.
Add paths, if you need them
Only if you are recruiting for more than one thing. Each gets its own questions, and can have its own review channel and reviewers.
Choose who reviews
Grant the review permissions to the Discord roles that should read and decide, and the management permissions to whoever edits forms.
Publish the panel
Put the apply button in a channel your members can see. Applications land where you routed them.
What applications do not do yet
There are two question types rather than a wide set, no scheduling or open/close windows on a timer, no cooldown between attempts, and no file uploads. Accepting an application grants the Discord roles you chose — it does not set a rank or create a personnel record on its own.
Ready to open applications?
Free on every plan. Pick a server and build your first form.
Get Started — Pick a Server