Raid Attendance Tracker for Guilds
Attendance is the quietest source of guild drama. Someone is sure they've made every raid; the officer is sure they haven't; nobody has the records to settle it. Most attendance-based loot systems — DKP, EPGP, or a loot council that weighs reliability — assume a history exists. ReadyRaider records every signup and outcome per raid, so the history is a byproduct of scheduling rather than a spreadsheet someone has to maintain.
What Gets Recorded
Every raid keeps the full picture rather than just a headcount. Each member's signup carries a status — confirmed, tentative, declined, waitlisted, benched, or no-show — along with the role they signed up for and when they responded. That distinction matters: a raider who declined in advance and a raider who confirmed and then didn't appear are not the same thing, and any attendance system that treats them identically will be argued with.
- Confirmed, tentative, and declined signups, with timestamps
- Waitlisted and benched raiders tracked separately from absences
- No-shows recorded distinctly from advance declines
- The role each member signed up for, not just that they attended
- An audit log of roster changes, so edits are traceable
Why Spreadsheets Fail at This
Attendance spreadsheets fail for a predictable reason: they require someone to transcribe the raid after it happens, every week, forever. That person eventually stops, and the record quietly becomes a month out of date before anyone notices. Deriving attendance from the signup sheet instead means the data is captured at the moment people respond, as a side effect of the scheduling they already do. There is no separate step to forget.
- No post-raid transcription step for an officer to abandon
- Data captured when people respond, not reconstructed afterwards
- Survives officer turnover, since nothing depends on one person's file
- Records live with the squad rather than in someone's personal Drive
Using Attendance for Loot and Roster Decisions
Attendance history is mostly useful at two moments: when loot is contested and when a roster spot is. Both are decisions people will push back on, and both go considerably better when the answer is a record rather than a recollection. This is most valuable in the first weeks of a new tier, when patterns are still forming, and at the point a guild has more raiders than raid spots and has to choose.
- Evidence for DKP, EPGP, or attendance-weighted loot council decisions
- A basis for choosing between raiders competing for one spot
- Proof that bench rotation has actually been fair
- Early warning when a reliable raider starts drifting
Attendance Across Games and Raid Sizes
Attendance follows the member rather than the raid, so a guild running several kinds of content sees one history per person. That matters for guilds whose members split across a main raid, an alt night, and dungeon runs — or across games entirely. The same squad can run World of Warcraft, Final Fantasy XIV, Destiny 2, or Guild Wars 2 events, and a member's reliability reads the same way regardless of which one they signed up for.
- One attendance history per member, across every raid they sign up for
- Works for any game, with system templates for several MMOs
- Spans raid sizes, so a 10-man alt night counts alongside the main raid
- Free tier covers 5 active raids and 50 squad members
Frequently Asked Questions
What attendance data does ReadyRaider record?
For every raid, each member's signup status — confirmed, tentative, declined, waitlisted, benched, or no-show — along with the role they signed up for and when they responded. Roster changes are also kept in an audit log.
Does it distinguish a no-show from someone who declined?
Yes, and that distinction is the point. Someone who declined in advance and someone who confirmed and then didn't appear are recorded differently, because any attendance system that treats them the same will be disputed.
Can I use this for DKP or EPGP?
Yes. ReadyRaider doesn't calculate DKP or EPGP points itself, but it provides the per-raid attendance history those systems are built on, which is the part that's normally maintained by hand in a spreadsheet.
Is attendance tracking free?
Yes. Attendance records come with every raid on both tiers. The free tier allows 5 active raids, 3 raid templates, and 50 squad members; premium removes the raid and template limits and raises the member cap to 200.
Do benched raiders show as absent?
No. Bench is its own status, so a raider you benched is recorded as having been available and rotated out rather than as missing. That's what lets you show bench rotation has been fair.
Does attendance carry across different games?
Yes. Attendance follows the member across every raid in the squad, whatever the game or raid size, so a guild running a main raid plus an alt night sees one history per person.
What happens to the records if an officer leaves?
They stay with the squad. Nothing depends on one person's spreadsheet, which is the usual failure mode for guild attendance tracking.
Stop arguing about who showed up
Attendance history as a byproduct of scheduling, not a second job.
Related Resources
Guild Raid Night Scheduler
Lock in a weekly night across timezones
MMO Raid Roster Planner
Plan composition before raid night
WoW Forever Raid Scheduler
Raid scheduling built for Forever
WoW Forever Guild Recruitment
Recruit against real roster data
Discord Raid Organizer Bot
Signups from your Discord server