# Tournament document-readiness review

Audience: tournament directors and authorized reviewers.
Type: manual ledger and checklist, not a live check-in integration or eligibility certification.

## Event configuration
Organizer / event / season:
Accepted registration source:
Current roster reference and check time:
Confirmed document requirements and official source:
Relevant event dates/deadlines:
Designated reviewer / escalation contact:
Approved private evidence store and retention process:

## Per-registration / per-entry ledger
Opaque organizer-event-registration reference:
Roster version:
Opaque entry reference (no personal identity in AI input):
Evidence reference (private document stays in approved store):
Receipt status/time:
Readability: readable / unclear / not checked
Matching: matched / missing / ambiguous / not checked
Reviewer decision: pending / decision recorded under event process
Official approval in source system: confirmed / not confirmed / unknown
Actual roster-lock state: confirmed locked / confirmed unlocked / unknown
Communication state: not drafted / draft only / sent with verified delivery reference / unknown
Exception category and minimal description:
Assigned reviewer / required follow-up:
Decision source and audit reference:
Changed-roster re-review required?:
Last verified time:

## Process
1. Confirm current organizer/event rules; do not reuse old requirements without checking.
2. Match accepted registrations and roster version using stable references.
3. Log receipt separately from readable, individually matched evidence.
4. Attachment counts do not prove unique player matching.
5. Keep reviewer decisions, saved official approvals, actual lock state and messages separate.
6. Hold missing/unclear/conflicting records for authorized review.
7. If a roster changes, flag affected decisions for re-review.
8. Use authorized approval/lock procedures and verify the resulting source-system state.
9. Preserve unknown/failed states; do not upgrade a note or dashboard label to confirmed action.
10. This worksheet performs no approvals, locks, mailbox processing or sending.

## Optional sanitized-status AI prompt
Review the supplied event-scoped status ledger for missing fields and contradictory states.
Return a reviewer task list with opaque record/evidence references, issue category and required follow-up.
Use only the supplied event requirements. Leave unclear requirements unresolved for the director.
Do not infer eligibility, certify authenticity, match identity from faces, process player-card images,
approve registrations, lock rosters or send messages.
A received packet is not approval. A review note is not confirmation of a saved system action.
Document matching is not independent verification with an issuer.

## Synthetic example
DEMO-EVENT / DEMO-TEAM-A / DEMO-ROSTER-V2
Packet received; DEMO-P01/P02 reviewed, DEMO-P03 unresolved.
Reviewer decision pending; official approval unknown; roster lock unknown.
Communication is a draft, not sent.

## Privacy
Keep documents, player identities, dates of birth, contacts and authenticated links
in the approved private system. Use minimized opaque references in AI input.
Restrict access and follow organizer retention rules. Public demonstrations stay synthetic.