How to Onboard New Raiders Without Killing Morale

Recruit a new raider, invite them to Discord, link them the guild rules doc, and hope for the best. That's the standard onboarding flow in most Classic guilds, and it's why so many recruits ghost after their first or second raid. Not because your guild is bad. Because the first two weeks are confusing, lonely, and full of small moments where the new raider is silently deciding whether this is worth it.

Onboarding is the part of guild management with the highest return on attention and the lowest amount of attention paid. A recruit who feels grounded by the end of week one will carry your roster for months. One who feels lost will quietly drop out, and you'll never get a clear answer about why.

Why New Raiders Quit

Before you fix anything, it helps to be honest about why recruits leave in the first two weeks. It's almost never the reason they give in a goodbye message. Here are the real ones.

They don't know anyone

A new raider joins a Discord full of inside jokes and long conversations about an officer drama they have no context for. Nobody greets them. Nobody pings them into a group. They sit in a voice channel on raid night listening to people call each other names they don't recognize. It's not hostile. It's just that everyone else already has their people.

They don't understand how loot works

You sent them the rules doc. They read it. They still don't know what it means in practice. When the first item drops, they have no idea whether they're supposed to roll, reserve, wait, speak up, or stay quiet. They pick wrong, get corrected, and now they feel stupid in front of strangers.

They can't see their progress

Your guild has a trial period. They don't know how long it is, what counts, or whether they're doing well. Is their parse good enough? Is their attendance being tracked? Are the officers even paying attention? When the feedback loop is invisible, raiders assume the worst.

Their first raid felt like an audition

Being benched on your first raid night tells a recruit they were brought in to fill a slot, not to be part of a team. So does sitting in voice while officers talk over them, or having their mistakes called out publicly while veterans get a pass for the same thing. Recruits notice. They don't always say anything. They just stop logging in.

What Onboarding Is Actually For

The goal of onboarding isn't to test whether a recruit is good enough. You already decided that when you invited them. The goal is to give them enough context, social footing, and confidence that they can be themselves by the end of week two.

That means three things have to happen:

• They learn how your guild operates. Not just the rules, but the rhythm. When raids start, how pulls are called, how loot is distributed, what the loot chat shorthand means. The rules doc doesn't convey any of this.
• They meet actual people. Not the officer who interviewed them. Other raiders. Ideally a few, by name, in context. If they can ping one person the day after their first raid and ask a dumb question, you've won.
• They can see where they stand. How long is the trial, what are officers watching, what's the bar for going full member. Raiders who can see the finish line tend to actually reach it.

A Week-One Playbook That Works

Here's what a good onboarding process looks like in practice. You don't have to do all of this, but the more of it you do, the better your retention gets.

Day zero: a real welcome

Before the recruit joins Discord, post a short message in your general channel: name, class, what they're known for, when they start. When they join, someone who isn't an officer should greet them. A recruit who hears from a regular raider in the first 24 hours treats the guild differently from one who only hears from officers.

Pin a short onboarding message in a dedicated channel with the five things they actually need for their first raid: invite time, summon location, addons required, loot system in one sentence, and who to ping if they're stuck. Nothing more. Save the philosophy for later.

Before the first raid

Have them submit their loot list before they show up. This is the single highest-leverage thing you can do in their first week. Ranking their items forces them to think about what they actually want, which makes the first raid feel like a game plan instead of a lottery. It also gives officers something to react to, which is a much better first interaction than "please read the rules doc."

If you use a tool like LootList+, the new raider can set up their list themselves and see exactly how the scoring works before they ever pull a boss. The system does the explaining so an officer doesn't have to.

First raid: seat them, don't test them

Unless your roster physically cannot fit them, put the new raider in for the first pull. Sitting a recruit on night one sends a clear message: you're not one of us yet. The progression cost of one questionable DPS on a farm boss is basically zero. The morale cost of benching a new raider is enormous.

Assign a buddy. An existing raider, not an officer, whose job is to answer questions in whispers during the raid and keep an eye on whether the new person looks lost. This is a low-effort ask for a veteran and a massive quality-of-life upgrade for the recruit.

Call out one positive thing publicly after the raid. Not flattery. Something specific: a clean interrupt, a good positioning call, a correct defensive cooldown. Recruits remember the first time an officer said something nice about their play. It signals that they're being watched in a good way, not just being graded.

The first loot moment

The first time a new raider gets an item, or doesn't, shapes their entire relationship with your loot system. If they can see why they didn't win it, they accept it. If the decision looks arbitrary, they assume the system is rigged.

This is why transparency matters more for new raiders than for anyone else. Veterans have trust banked up. Recruits don't. Any loot system that can't explain itself clearly to a new raider will produce churn. If the raider can pull up a score breakdown and see why the item went where it did, the drama never starts.

Trial Periods Done Right

Most guilds have a trial period. Most trial periods are vague, which defeats the point. A good trial is a contract: here's what we're looking for, here's how long you have to demonstrate it, here's what happens at the end.

Three things a trial period needs:

1. A fixed length. Two weeks, three weeks, a full tier. Whatever you pick, say it out loud on day one. Trial periods that quietly extend for months are a guild culture red flag.
2. A specific bar. "Good attitude and solid performance" is not a bar. "80% attendance in the trial window, keeping up on damage on your assigned role, and showing willingness to take feedback" is a bar. The more specific, the less it feels like a popularity contest.
3. A real decision at the end. Promote them, extend them with a clear reason, or cut them. What kills trust is trials that never end. Raiders who feel permanently on probation start looking for the exit.

If your scoring system supports it, trial raiders should be able to see their own progress. Knowing their attendance is at 6 of 7 raids and their trial window ends in one week is much better than guessing whether anyone is paying attention.

The Small Things That Add Up

A lot of onboarding is just the default behavior an officer builds into the first two weeks without having to think about it. Some things worth building in:

• Ping the new raider by name in voice once per raid. A simple "hey, great kick there" is worth more than any written welcome message.
• Include them in post-raid chat. If your guild hangs out for 15 minutes after clearing, the new raider should be invited, not awkwardly waiting for the summon that isn't coming.
• Send a quick check-in on day three. Something like, "Hey, how's week one feeling? Anything confusing?" The answers will tell you more about your guild than any exit survey.
• Don't schedule meetings. Recruits hate "hop in voice so we can chat" messages from officers. If you need to talk to them, do it in writing first.

When Onboarding Fails

If a recruit drops out in the first two weeks, the instinct is to assume they weren't a fit. Sometimes that's true. More often, something in the first week felt off to them and they couldn't articulate it. A short message to anyone who leaves early, asking what they would change about the first two weeks, will teach you more about your guild than a year of officer meetings.

You don't need a full exit interview. Just: "Hey, no hard feelings, would love any honest feedback on what didn't land." A surprising number of people will tell you.

The Bottom Line

Onboarding isn't a checklist. It's the set of small choices your officers make during a new raider's first week that decide whether they stay. Most of those choices cost nothing. Greet them by name, seat them in the first pull, give them a buddy, make the trial specific, and let them see where they stand.

The guilds with the best retention aren't the ones with the strictest standards. They're the ones where a recruit feels grounded by day four and stops being a recruit, in their head, before the trial period is even over.

Want to make the first week easier? LootList+ handles trial tracking, visible scores, and transparent loot decisions, so new raiders can see exactly where they stand from day one. The system answers the hard questions so your officers don't have to.