How to manage multiple raid teams in one WoW guild

A guild with one raid team has a schedule. A guild with five has a logistics problem. The same raiders show up on two rosters, officers step on each other's edits, and nobody can say how many healers the guild really has. RaidOps started as the internal tool for the Old Gods, a guild that runs 15 raid teams, so this is a problem we know well. These are the decisions that mattered most.

Decide what each team is for

Teams multiply for different reasons, and the reason should shape the rules.

• A progression team pushes for Mythic bosses and has strict attendance and role needs.
• A clear team farms Heroic or Normal on a relaxed schedule.
• An alt night gives raiders a place to play characters that aren't their main.
• A learning team brings in newer raiders and teaches mechanics.
• A key team runs Mythic+ dungeons together instead of raiding.

Write one sentence per team on what it expects: schedule, difficulty, attendance bar. Raiders choose better when the choice is visible, and officers have something to point to when a conversation gets awkward.

One guild list, many team rosters

Keep two layers of data. The bottom layer is every character in the guild, with class, spec, role, item level and owner. The top layer is team membership: which characters belong to which team, and how each is used there.

Putting them in the same document works at first. Past about three teams it falls apart, because the same character appears in several tabs and each copy goes stale on its own. Treat the character as the single record and let teams point at it.

Two rules help:

1. A character sits on one team. If a player wants to raid with two teams, they bring two characters, or they get moved. This avoids double-counting attendance and role slots.
2. A player has a main team. Even with alts spread around, a main team tells officers where the player's attention is, and where to look first when they go quiet.

Alts should roll up to the main for attendance, as described in the attendance guide.

Permissions: lead the team, not the guild

When every officer can edit every roster, mistakes follow. The officer who runs Tuesday should be able to change Tuesday's roster, mark Tuesday's attendance and review Tuesday's applications, and should not be able to touch Thursday's. Guild-wide views stay readable to all, and write access follows the team.

RaidOps works this way. Officers and team leads manage the teams they lead, admins manage everything, and a team lead can add an existing character they own straight to their team. Raiders see their own team's marks and the guild-wide roster. Mostly it stops accidents.

Recruiting without chaos

With several teams you will usually be short on a role in one place and overstocked in another. Instead of posting a general "we're recruiting" message, record what each team needs: tank, healer, melee, ranged, any DPS or flexible. Show it to members so they can apply to the team that needs them, and let a closed team stop taking applications.

RaidOps keeps that list on each team, lets officers update it from the application review screen, and shows open teams to applicants. Applications are decided by the team's officers, and they can approve, waitlist or deny from a Discord message as well as in the app.

Open teams for casual nights

Some teams don't need a fixed roster. An alt night or a fun run can be open: anyone in the guild signs up, first come first served, and extras go on a waitlist. The pieces you need are limits per role, a waitlist that promotes people when someone withdraws, and a lock a couple of hours before the raid so the roster stops moving. RaidOps has this as an Open team setting. If your teams are all fixed rosters, ignore it.

Discord: one channel and one role per team

Discord gets noisy with several teams. A clean pattern is one channel and one role per team, with the raid post in the team's channel and the role used for pings. Maintaining the role by hand is the part that fails, because someone leaves a team and keeps the role for months.

The RaidOps bot posts each raid in the team's linked channel, and it can sync a Discord role to the team roster, adding it when a character joins and removing it when the player's last active character leaves. Whether you use RaidOps or not, assign the job to something automatic or a named officer, not to whoever remembers.

Repeating schedules

Most teams raid on a fixed weekly night. Creating that raid by hand every week is a small tax that adds up across five teams. Use recurring events, whichever tool you choose. Raid-Helper and Sesh offer them as premium features; RaidOps creates next week's raid from the latest one without a paid tier. Check your tool's rules on what carries over, since you probably want signups cleared and notes kept.

Look at the guild as a whole

Once teams are separate, you still need the guild-level view, because that is where the useful questions are:

• Which roles are we short on across all teams?
• Who is raiding on two nights, and are they burning out?
• Which team has the weakest attendance trend?
• How many characters do we have at an item level that qualifies for Heroic?

If your tool can't answer these without exporting to a sheet, it was probably built around individual raiders, not teams. We covered how popular tools differ in our roundup of WoW raid management tools.

Frequently asked questions

How many raid teams can one guild run?

Nothing in the game limits it. The practical ceiling is how many leads you have and how large your pool of raiders is. RaidOps lets you create as many teams as you need, and the Old Gods run 15 on it.

Can a player be on more than one raid team?

It depends on your rules. The simplest approach is that each character belongs to one team, and a player brings a different character to a second team. In RaidOps, a character belongs to one team, and a raider with several characters can be on several teams and sets one as their main team.

How do I stop officers from editing the wrong roster?

Give permissions per team. Team leads edit their own team, admins edit all of them, and everyone can read the guild-wide views.

How do I handle recruiting across several teams?

Track the roles each team needs and show them to members. Let closed teams stop accepting applications so officers aren't reviewing requests they can't act on.

Does RaidOps support multiple teams?

Yes. You can create as many teams as you need, each with its own roster, raid nights, attendance, progression and Discord channel.