Documentation
Back to tutorials

Moderation

Using the Verifications Page

Review completed checks, manual-review sessions, checked members, evidence details, exports, and staff actions from one place.

Who uses it

Moderators, managers, assistants

Where it lives

Dashboard > Verifications

Goal

Staff can find the right session, understand why it passed or failed, and take the right next action.

Before You Start

  • Permission to view verifications.
  • At least one completed or queued verification session.
  • A clear staff policy for manual approval or rejection.

Steps

1

Start with the main list

Use filters for member, build, activity, verdict, review state, and evidence source. The main list is best when you know the session or member you are looking for.

2

Use Review Queue for staff decisions

Review Queue is for sessions that need human attention. Open the detail view, inspect score breakdowns and evidence notes, then approve, reject, override, or ask for resubmission based on guild policy.

3

Use Checked Members for roster questions

Checked Members groups sessions by person. Expand a member to see what builds they have checked across activities and roles. This is better for readiness planning than searching one session at a time.

4

Export when staff need spreadsheets

Use CSV exports when a raid lead, officer, or external planning workflow needs the filtered list outside GearCheck. Export the filtered view rather than all sessions when possible.

Launch Checklist

  • The list filter matches the question you are trying to answer.
  • Manual-review decisions include a clear staff reason.
  • Evidence source labels make sense for the session.
  • Thread links and detail links route staff to the right context.

Common Pitfalls

  • Treating Review Queue as the full verification history.
  • Approving a session without checking whether the build source was OCR, Markdown, TONL, or another adapter.
  • Exporting all data when a filtered export would be cleaner.

Related