Whitelist rubric anti-patterns

Two reviewers split. The application sits. Days pass. A third reviewer eventually weighs in but they're also unsure. The application sits longer. Eventually the owner gets pinged and decides — but now five days have elapsed and the applicant has lost interest.

Fix: document a tie-break before you have a tie. Default: senior staff (Head Admin / Owner) breaks ties on a 24-hour cooldown. This means even contentious applications resolve within 48 hours, not 5 days.

If your panel is just 2 reviewers, you don't have ties — you have unanimous-or-stop. Document that.

"Quality of writing." "Roleplay potential." "Fits the community." These look like rubric criteria but they're actually personality tests dressed up as scoring. Two reviewers can score the same applicant 0/2 and 2/2 on "fits the community" with equal confidence.

Fix: every criterion needs a behaviorally observable definition. Not "quality of writing" — "applicant uses paragraphs (not single-line walls), shows character voice (the writing sounds like a person, not a checklist), and demonstrates RP awareness (mentions reactions, environment, other characters, not just their own actions)."

If you can't describe what 0 / 1 / 2 points looks like in concrete behaviors, the criterion isn't scorable. Drop it or rewrite it.

Three weeks into your server, two of your reviewers are friends with applicants. Both reviewers approve their friends with high scores. The decisions look fine in isolation. Then a denied applicant compares notes with their friend — "wait, you got in with the same answers I had?" — and posts a thread accusing your staff of favoritism.

It might be true. It might not. Doesn't matter — the trust collapse is real either way.

Fix: mandatory recusal when a reviewer has a personal relationship with the applicant. Discord friend, real-life friend, gaming partner, prior server-mate. The reviewer marks themselves recused on the application thread; another reviewer takes the slot.

This single rule prevents most of the "the staff is corrupt" drama that hits servers in month 2–3.

One person can score 5–10 applications a day comfortably. After that quality drops fast. If your server gets 30 apps a week and you have one whitelist reviewer, you're building a backlog by Wednesday.

Fix: minimum 2 reviewers per app, ideally 3. Distribute load — each reviewer should handle 5–10 apps a week, not all the apps. This forces you to either keep the bar high or expand your reviewer pool, both of which are healthier than a 23-app backlog handled by one tired person.

If you're a small server (1–5 staff), don't fake a panel — explicitly document that you're owner-reviewed and set expectations: "reviews happen Friday evenings, you'll hear back Saturday." Predictability is more important than panel size at small scale.

Generic denial: "Your application was not accepted at this time. You may reapply in 14 days." The applicant has no idea what was wrong. They reapply with the same content. They get denied again. Now they're posting in your community Discord asking why everyone hates them.

Fix: structured denial referencing the rubric. "Your application scored 4/10. The criteria where you fell short: Writing Quality (0/2 — single-line walls, no paragraph structure), RP Awareness (1/2 — focus on your character's actions without acknowledging environment or other characters). Suggested resources before reapplying: [link to your starter guide]. Reapply window opens [date]."

This serves two purposes: (1) honest applicants improve and reapply successfully, (2) low-effort applicants self-select out instead of feeling singled out.

Applicant denied. Same applicant submits again 12 hours later. With identical content. Denied again. Submits again. Each cycle wastes reviewer attention.

Fix: cooldown table by denial reason. 14-day minimum is the floor. 30 days for high-effort denial reasons (rule violations, plagiarism, incoherent character). 90 days for ban-related re-applications. Document this on the application form so applicants see it before submitting.

Edge case: if an applicant's 14-day window expires and they reapply with literally the same content, the rubric should treat that as a low-effort signal worth its own discussion in the rejection feedback. "You reapplied with no changes after 14 days — please address the original feedback before resubmitting."

Healthy whitelist process from a 60-player serious-RP server (anonymized):

• 5-criteria rubric, each 0/1/2, total 0–10. Pass = 7+.
• 2 reviewers per app. Tie at 6/8 → senior breaks tie within 24h.
• Recusal documented and visible in the review thread.
• Median review time: 18 hours. P95: 36 hours.
• Rejection includes per-criterion feedback. Reapplications drop ~80% after this was added.
• 14/30/90 day cooldown table by denial reason. Visible on the application form.

If you want a starting rubric tuned to your RP style, KeepGrid's free /tools/whitelist-rubric generator outputs all of the above. Edit it, debate it with your staff, ship it.