The pipeline
A prospect applies
/tryout apply — no form to chase, no DMs to collate.Staff work the queue
/tryout queue shows what’s open. /tryout schedule sets a time.Each evaluator scores
/tryout evaluate — independently, without seeing anyone else’s numbers
first.A decision gets made
/tryout decide passes, waitlists, or declines — once enough evaluations
are in.A pass starts a trial
They land on the trial tier and the clock starts.
A human closes it out
On the review date,
/tryout trial passes, extends, or ends it.Scoring
/tryout evaluate opens a form asking for one score per criterion, plus a
recommendation and private notes.
The default rubric is mechanical skill, communication, game sense, adaptability,
chemistry, and reliability — each out of 10.
Every evaluator’s scores are kept separately. Averages are worked out when
you look, so you can always see who said what rather than a number nobody can
trace back.Re-running the command replaces your own scores and touches nobody else’s.
Trials
A trial has a review date. When it arrives, the bot posts a reminder in the staff channel. That is all it does.pass
Promotes them to the division’s configured destination tier.
extend
Pushes the review date out. Say how many days.
fail
Ends the trial. Profile and history are preserved.
Tuning it per division
/tryout config sets how many evaluations a decision needs, how long a trial
runs, which tier trials sit on, and which tier a passing trial graduates into.
What applicants can see
/tryout mine shows a prospect their status and, eventually, their outcome —
passed, waitlisted, or declined.Scores, notes, and the reasoning behind a decline stay in staff channels. That
means evaluators can be blunt in writing without it ever becoming a
conversation.