Nobody likes hearing it.
You show up on time, your consumables are ready, your addons are updated, and the raid plan has been reviewed. You’ve been grinding this tier for 10 weeks. And then five minutes before the first pull, you get the message.
“Hey, sitting you for this one. We’ll get you in later.”
It stings. Even if you’ve been raiding at a high level for years, even if you’ve made this call yourself a hundred times, being on the receiving end never stops being uncomfortable.
I’ve been on both sides of it. In Death Jesters, I’m sometimes the second or third choice to come in, and it’s usually when one of our primary players is away. In Last Call, I have to handle the roster responsibility from boss to boss. The honest truth is that making the call is often harder than getting it. Not because the decision is unclear, but because I know exactly how it feels to read that message and wonder what it means about where you stand.
Here’s a glimpse of what actually goes into it, from someone who’s been working through a roster every week for a long time.
There Is No Formula
The first thing to understand is that I don’t have a spreadsheet that automatically sorts the roster and spits out who’s sitting next. There’s no universal ranking where the bottom person gets benched, and everyone moves up a slot. It doesn’t work that way. There were times when I wished I had some type of grading tool akin to Fantasy Football rankings, where it would help make that lineup setting and decision-making easier, so that I didn’t have to think about it.
Every boss asks for something different. Every week has a different context. Roster decisions are almost always a blend of several factors at once, and the weight of each one shifts depending on where we are in the tier.
If you’re trying to reverse-engineer why you sat by comparing your logs to someone else’s, you’re probably looking at the wrong thing entirely.
On Progression, the Boss Decides
When we’re actively progressing on a new boss, my first question isn’t “who’s performing best?” It’s simpler than that: what does this encounter actually need?
That question has many answers, depending on the boss. Sometimes it’s about raw class or spec composition — we need another ranged, or we’re running too much melee, and people are tripping over each other. Sometimes it’s specific utility: a Warlock gateway, a Death Knight grip, a Paladin immunity, a Druid knockback. Sometimes it’s survivability — I need players who can reliably handle a specific mechanic without needing a rez every other pull.
I ran into this exact problem just last week on Crown of the Cosmos. I’d committed to a comp that ended up being short on mobility tools, and I spent an entire night patching around it with awkward grip assignments that only worked as long as nobody died in the wrong order. It was my mistake on the comp, and it cost us time. The players weren’t wrong — the setup was.
Some bosses make the requirements even harder to negotiate around. Midnight Falls, for example, has a minimum floor: you need at least two Death Knights for grips, at least two classes that can do knockbacks, a Priest for friendly crystal grips, and an Evoker for the mobility. That’s not a preference list. That’s the encounter telling you exactly who has to be in the room. If you don’t have those pieces, you’re not progressing that boss. Someone who doesn’t fit that checklist isn’t sitting because of anything they did. They’re sitting because the encounter is making the decision for me.
That’s the thing about progression sits: they usually aren’t about you. A very good player can sit a progression boss because the encounter favors a setup that doesn’t include their class. That’s not a judgment on their value. It’s the boss asking for something specific, and we’re trying to give it what it wants.
But hey, that’s the demands of Mythic raiding. I know some of my players have lamented the requirement of certain class compositions, but that is part of the difficulty at this echelon of playing.
On Farm, Loot Becomes Part of the Equation
Once a boss is on farm, priorities shift.
We’re not solving the encounter anymore. That means I start looking at loot wishlists, Droptimizer recommendations, who still needs tier, who’s missing a key trinket or weapon, much more closely. If two players are equally viable for a slot and one of them has a meaningful upgrade on this boss while the other doesn’t, that becomes a real factor.
Farm nights aren’t easy breezy runs. I still want clean kills with a full team that knows what it’s doing. But farm is also how you build the raid for the next tier. Getting the right gear onto the right players now is part of the investment.
It’s also the time to consider the future and work in any alts or main switches for the following season.
Fairness Matters More Than People Think
Beyond composition and loot, I’m keeping a mental ledger of who’s been sat and how often.
A roster dies slowly when the same people keep getting the short end of the rotation. Even if the decisions are all individually defensible, if you look up three weeks in and the same two or three players have been sitting more than everyone else, something’s wrong. People start to feel like permanent backups. That quiet resentment builds into attendance issues, then recruiting drama, then players quietly finding another guild.
I try to catch it before it gets there. If someone has been sat multiple times in a row, that weighs on the next decision even if the current boss could theoretically work without them. Long-term engagement matters more than optimizing a single pull.
Trials Need Real Reps (And So Do Some Veterans)
If I’m recruiting a trial and they never actually play, I can’t evaluate them.
Logs tell me a fraction of what I need to know. I can see throughput and mechanical awareness from a log, but I can’t see how someone communicates under pressure, how they respond after a bad pull, whether they ask smart questions or mentally shut down when things go sideways. Farm bosses are where I find out who someone actually is as a raider.
Our roster has a real range of experience. Some players have multiple Cutting Edge achievements and have seen versions of these situations before, such as Fyrakk seeds and the crystals in Midnight Falls. Others (and there’s no shame in this) are in their first serious Mythic environment. Those players need reps too, maybe more than anyone. It’s one thing to read a strategy guide or watch a Taktyks video. It’s another to be mid-pull, realizing a mechanic is about to overlap with your cooldown window, and having to think through it on the fly. That kind of decision-making isn’t something you can shortcut. You have to earn it through repetitions.
I’ll rotate someone into a farm boss because they need the practice planning their movement, managing their cooldowns around boss events, or adjusting their rotation when something unexpected happens. It’s not supposed to be filler. It’s meant for development. And that development pays off weeks later when we’re deep into a progression boss, and I need everyone thinking, not just reacting.
Scheduling is part of this too. If a raider is heading out on vacation for a few weeks, it doesn’t make much sense to bring them in on a new progression boss we’re expecting to kill while they’re gone. They’d be investing pulls into learning a fight they won’t be there to finish. Better to give those reps to someone who’ll be present for the kill and needs the experience.
If you’re a veteran sitting a farm boss for any of these reasons, I know that’s frustrating. But it’s also how the guild builds depth for when you actually need it.
Reliability Counts, Even When It’s Invisible
Here’s one factor people underestimate: I notice who makes the night easier to run.
Showing up on time. Having consumes. Knowing the plan without needing it re-explained (but confirming their position or interrupt order). Having addons sorted for the mechanic we just talked about in Discord. Keeping a character properly maintained. None of these things show up in a log, but they all add up. When two players are genuinely close in value, the one who creates less friction usually wins the spot.
Raid leaders remember who makes the night smoother. It’s not glamorous, but it matters.
The Call Isn’t About You, Even When It Feels Like It
The most common things I hear after a sit decision are some version of:
“But my numbers were better than his.”
“I must’ve done something wrong.”
Almost none of that is true. Most sit decisions are strategic, logistical, or developmental. They’re made with the team in mind, not against any individual. The fact that I’m rotating you doesn’t mean I’m sending a message. It usually just means the context of this particular boss, on this particular week, is pointed elsewhere.
What I’ll always try to do is be direct about it and give you enough context to understand the call. Not a lengthy justification, but enough to keep you from guessing. If you’re sitting because of comp, I’ll tell you it’s comp. If it’s loot, I’ll say that. Vague non-answers are where resentment grows.
Raid Leaders Get It Wrong Too
This goes both ways. I’d be doing you a disservice if I framed every sit decision as perfectly calculated and correct, because that’s not always true.
Sometimes the wrong person starts. Sometimes I overvalue a class that ends up not mattering as much as I thought it would. Sometimes I build a comp around what the top guilds were running in Warcraft Logs during the first week of the tier, only for Blizzard to patch the encounter and change the math entirely. The Paladins fight is a good example since early on, the dispel quantity was high enough that two Mistweaver Monks felt close to mandatory. Then the nerf hit, the number of dispels dropped significantly, and suddenly you only needed one. Any comp decisions made around that original requirement had to be revisited.
That’s just the reality of a live game. Bosses change. Tuning shifts. What was a hard requirement in week two can become a preference by week four. When that happens, I try to catch it and adjust, but I don’t always catch it immediately, and sometimes players pay the price for a call that looked right at the time and turned out to be wrong.
If you genuinely think a sit decision was a mistake, I’d rather you say something directly than let it fester. I’m not infallible, and I don’t expect to be treated like I am. What I ask is that you bring it to me directly, as opposed to working its way through half the guild before it reaches my ears.
Nobody’s Happy Every Week, and That’s Fine
Every week I’m balancing progression needs, composition, loot, fairness, development, attendance realities, and morale. Sometimes all at the same time, all pulling in slightly different directions. There is no decision that satisfies all of them simultaneously.
If everyone in the raid is mildly annoyed from time to time, that’s honestly a decent sign. It means the rotations are being spread around honestly instead of a permanent hierarchy forming at the bottom.
Being sat sucks. Making the call usually isn’t great either. But if it gives the team a better chance on this boss, or keeps someone engaged who would otherwise start checking out, or gets a trial the reps they need to become a real contributor — it’s the right call, even when it doesn’t feel like it.
One week is not the whole tier. There’ll always be opportunities to shine.