Fair records
How to track LORDNINE attendance and contribution without turning it into a shame list
Use clear attendance rules, correction windows, and private records to support fair guild decisions and better event planning.
- By
- ForgeKeep editorial team
- Published
- Reviewed
- Reading time
- 6 min read
Step 01
Explain what the record is for
Attendance may support capacity planning, a point system, leadership eligibility, or simple recognition. Say which purpose applies before collecting data. A number that is useful for scheduling is not automatically a fair measure of every member’s contribution.
When contribution affects rewards, publish the inputs and the correction process together. Members should not discover a rule only after a contested distribution decision.
Step 02
Define edge cases in advance
Late arrivals, standby assignments, disconnects, alternate characters, and approved absences are ordinary parts of guild play. Decide how each is recorded before the event, then apply the same rule to officers and members.
A short correction window is healthier than permanent debate. It gives people a way to surface an error while the event is still fresh and lets the record become stable afterward.
Step 03
Use private records for private decisions
Public rankings can create pressure without improving accuracy. Keep member-level history behind the guild’s authorization boundary and share only the level of detail needed for the specific decision.
ForgeKeep’s attendance workflow is designed around reviewable event records. The public site explains the method; it does not expose real member rosters, screenshots, or attendance history to search engines.
Continue reading