What a good FiveM whitelist rubric actually does
A whitelist rubric is a written scoring system your reviewers use to evaluate every application the same way. Without one, two admins on your team will accept and reject the same player within an hour of each other — and retention suffers in the gap. A good rubric does three things: it removes ambiguity for reviewers, it sets honest expectations for applicants, and it gives you a paper trail when an appeal lands six months later.
Most servers fail the whitelist step not because their questions are wrong, but because their scoring is invisible. The rubric is the system. The questions are just the input.
What the generator above gives you
- Application flow as an ASCII flowchart — discovery → submission → review → verdict.
- 5–8 application questions tuned to your server's RP style. Serious RP gets backstory + CK acknowledgement; semi-serious gets shorter prompts; PD-heavy gets department-fit questions.
- Scoring rubric table — typically 5 criteria × 0–2 points each = 10-point scale, with concrete examples of what 0, 1, and 2 look like for each.
- Score thresholds: e.g. 8–10 auto-accept, 7 accept, 5–6 panel vote, <5 deny.
- Reviewer rules: minimum reviewers per application, what to do on disagreement, how to keep scoring consistent across staff.
- Copy-paste DM templates for approval (with next steps for your specific server) and denial (with specific feedback areas).
Best practices we encode
Calibrate before you launch
Run any new rubric on 5–10 fake applications first, scored independently by 3 reviewers. If scores diverge by more than 2 points on a 10-point scale, your criteria are still subjective — refine the "what 0/1/2 looks like" examples before you go live.
Keep questions answerable in 15–25 minutes
Long applications filter for patient applicants but also for unemployed teens with too much time. Short applications miss low-effort ban-evaders. The sweet spot most successful RP servers land on is 5–8 substantive questions plus a free-text scenario.
One scenario question, always
At least one question should describe a specific in-character situation and ask the applicant what they'd do. This catches metagamers, powergamers, and people who memorized RP-glossary without playing. Generic Q&A like "define NVL" can be Googled in 10 seconds.
Auto-accept threshold matters more than you think
Most servers under-set their auto-accept threshold and end up with a backlog of borderline applications that staff dread reviewing. If your top-scored applicants have a 95%+ post-WL retention, you can safely auto-accept anything ≥ 8/10. Track this for 30 days, then tune.
Always log denials with reason
When the same person re-applies (and they will), reviewers should see whythey were denied last time without re-reading the application. Even a single-tag like "low effort" or "metagame red flags" saves 10 minutes per re-review.
Common mistakes to avoid
- No clear panel-vote rule. When two reviewers disagree, the application sits in limbo for days. Always document who breaks ties (Head Admin, Owner, or majority-of-3).
- Generic copy-paste denials. "Application denied" without specifics breeds resentment and re-applications. Cite the exact rubric criteria the application failed.
- Asking for IRL info. Real age, real name, real Discord activity — none of these belong in an RP whitelist. They're creepy and Discord ToS-adjacent.
- Mixing whitelist and rule-test. If you want to gate on rule knowledge, use a separate quiz; the whitelist itself should test RP fit, not memorization.
- Hidden "vibe checks". If you reject for "feel", write that criterion into the rubric explicitly. Otherwise reviewers just bias by username and you can't defend it on appeal.
FAQ
How long should the whitelist take to review?
Healthy RP servers post a public SLA — typically a response within 24 hours. Below 24h is hard to maintain at scale; above 72h causes drop-off. The generator pairs a rubric with a Staff SLA template so this gets formalized.
Should staff be able to whitelist their friends instantly?
No. Write that into your staff handbook explicitly. "Staff can vouch but not approve" is the standard rule. Otherwise the whitelist becomes a friends-and-family thing, which destroys the trust new players have in the system.
Can I run this rubric without a Discord bot?
Yes. The output is plain text plus tables — paste into Notion, Google Docs, or Discord pinned messages. KeepGrid's Launch OS installer integrates the rubric with Ticket Tool or Carl-bot automatically, but it is optional.
Does the AI know about my specific server's factions?
If you list factions and free-text context in the form above, the rubric gets tuned — PD-heavy servers get LEO-fit questions, gang-heavy servers get conflict-maturity scenarios, whitelist-only servers get tighter intake. The more context you give, the less generic the output.
How is this different from asking ChatGPT directly?
Same model family, different prompt. The generator runs on a system prompt loaded with FiveM/RedM-specific terminology (NVL, RDM, CK, RPSL, fail-RP), real RP-server pain points, and an enforcement format that maps to actual Discord channels and roles. ChatGPT gives a generic application; this gives you something you can paste into your server.
Related tools
- RP Server Rules Generator — pair your rubric with concrete rules so reviewers can cite specific violations.
- Staff SOP Generator — formalize who reviews what, with response SLAs.
- Ticket Routing Generator — set up Ticket Tool / Carl-bot to route whitelist applications to
#wl-review. - Launch Checklist — make sure your whitelist is calibrated before opening to public.
Want all 13 docs + Launch OS install?
The whitelist rubric is one of 13 documents in the full KeepGrid pack. The full pack also installs the Discord channels (#whitelist-apply, #wl-review), creates the Whitelisted/Pending roles, and pins the rubric for your reviewers. See all plans — from Docs Pack $19 to Launch OS + Pro $59 + $19/mo.