T&L raid scheduling for guilds: a complete officer's guide

T&L raid scheduling looks easy until you've actually run a guild for a season. Members miss raids. Officers ping the same five people every week. Loot goes to whoever showed up last time because nobody's tracking attendance fairly. Here's how to actually run T&L raid scheduling so the system carries the guild instead of the guild carrying the system.

What you're scheduling for in T&L

T&L's raid content sits in a few buckets, each needing different scheduling treatment:

• Boco / Tevent / contested world bosses — high-value, high-attendance. Schedule weekly minimum.
• Open-world contested events — PvP-focused, time-sensitive. Schedule with shotcaller assigned.
• Faction-tied content — depends on your faction politics. Schedule alongside faction allies.
• Guild-internal training raids — for newer members learning mechanics. Schedule weekly, lower stakes.

Each gets a different cadence. Don't lump them all into one weekly "raid night."

Time slots that actually work

T&L's playerbase skews global. NA-EU mixed guilds are common. The mistake guilds make: scheduling at one time and assuming everyone "should be able to make it." Members in time zones the schedule doesn't serve quietly leave.

Two patterns that work:

Pattern A: Two scheduled time blocks per week. One slot at 8PM EST (works for NA + early EU), one at 2PM EST (works for EU evenings + late Asia). Members commit to whichever fits.

Pattern B: One main slot with a backup. Tuesday 9PM EST is "main raid" — most members. Saturday 1PM EST is "EU friendly" — same content, different shift. Members can attend either or both.

Avoid: "9PM Tuesday only" with the assumption that EU members will rearrange their lives. They won't. They'll find another guild.

Signup systems

A signup system that works for T&L raids:

• Posted at least 72 hours in advance. Members need lead time to commit.
• Discord-based signup with role tags. Members react / click a button to commit.
• Auto-reminder 24h before to everyone signed up.
• Auto-reminder 1h before to anyone who hasn't acknowledged.
• Public attendance count so members see who else is coming.

The 1h reminder is the lever that moves attendance numbers. People say they'll come and forget. The reminder catches them.

Attendance tracking

If you're running DKP or anything attendance-tied, accurate tracking is non-negotiable:

• Voice channel snapshot at raid start time. Whoever is in voice is counted.
• Mid-raid snapshot for late joiners.
• Public list posted within 24h with who attended vs who signed up.

Manual roll calls are how you lose officers. Automate the snapshot.

Common scheduling failures

Schedule changes mid-week. Members planned around it; they show up to nothing. Don't change a posted raid unless the change is announced 24+ hours in advance.

Officer-only signup channel. Members can't see who's going so they don't bother committing. Make signups visible.

No backup raid leader. Main RL gets sick, raid is canceled. Always have a designated #2 who can call.

Treating EU members as second-class. If your weekly schedule serves NA at the cost of EU, the EU members notice and leave by month 3.

Over-scheduling. Five raids a week sounds great in officer chat. By week 4 attendance is at 40% because nobody can sustain that pace. Schedule less, fill more.

Pre-raid coordination

The 30 minutes before a raid sets the tone. Healthy patterns:

• Voice channel open — members trickle in, social before serious.
• Quick pre-raid call from the RL — comp confirmation, role assignments, special calls for tonight's content.
• Loot system reminder — "tonight is DKP for boss drops, need/greed for trash." Reduces post-raid disputes.
• Tactical refresh for the contested fight if it's new content.

This is more important than the raid itself. Members showing up to organized raids feel like they're in a real guild. Members showing up to chaos feel like they're filling a slot.

Post-raid debrief

The thing most guilds skip:

• Loot distribution posted publicly within 24h. Who won what at what cost.
• Attendance recorded in your tracking system.
• One short note in officer channel: what worked, what didn't, what to adjust next week.

The note is what compounds. Guilds that run debriefs get measurably better at raid execution. Guilds that don't repeat the same mistakes for 6 months.

Tools T&L guilds actually use

• Discord for signups, announcements, voice. Universal.
• Spreadsheets for attendance tracking — works until 30 members, then breaks.
• Specialized guild platforms — what we ship on cogm.app and throney.gg specifically for T&L.

The point at which a guild needs to upgrade from spreadsheets is roughly 40-50 active members. Officers spending 5+ hours/week on coordination is the signal.

How CoGM and throney.gg handle this

CoGM ships event scheduling with role slots, automatic reminders, voice channel attendance snapshots, and DKP-tied tracking — works for any game.

For T&L specifically, our sister site throney.gg has deeper T&L-specific tools: raid templates with T&L's contested content built in, server-merge-aware scheduling, and a DKP system tuned for T&L's loot pool. Same Discord login works on both sites.

Use throney.gg for T&L-specific tooling or start a free CoGM community if you run a multi-game community.