Guild operations guide
How to track guild attendance fairly
Build a guild attendance process with clear eligibility, verification, corrections, privacy boundaries, and useful reporting.
- Author
- ForgeKeep product team
- Published
- Updated
Decide why attendance is being tracked
Attendance data can support raid planning, point awards, rank reviews, or simple recognition. Do not collect it merely because it is measurable.
State the purpose and retention period so members understand how the record will be used.
Define the event and eligibility window
Every attendance entry should refer to a specific event and a clear time window. Decide how late arrivals, early departures, standby members, disconnects, and cross-guild participants are handled.
Apply the same rule to officers and members.
Verify exceptions without public exposure
Automated check-ins and OCR can reduce manual work, but an authorized officer should review uncertain matches and duplicate identities. Keep screenshots and member-level history private.
Public marketing pages should explain the process without exposing real rosters or attendance records to crawlers.
Report trends, not shame lists
Use attendance summaries to plan capacity and identify support needs. A private conversation is usually more useful than a public leaderboard for sensitive participation issues.
Allow corrections for a fixed period, then lock the session and record later changes as adjustments.
- Event identifier
- Check-in window
- Verification owner
- Exception rules
- Correction deadline
- Retention policy