# Tournament manager-notice review

Audience: tournament directors and authorized communications staff.
Type: manual fact sheet, draft and release checklist. No messages are sent by this resource.

## Confirmed fact sheet
Organizer / event reference:
Notice purpose:
Affected registrations/games:
Authorized decision-maker and source:
Source checked at / relevant time zone:
Old value:
Confirmed new value:
What stays unchanged:
Effective date/time:
Required manager action and confirmed deadline:
Approved public information/contact route:
Unknowns to resolve:
Recipient scope (references only; no contact list in AI input):
Approved channel:
Reviewer / release authority:

## Draft template — NOT APPROVED OR SENT
Subject: [Event] — [confirmed purpose/change] — [affected reference]

What changed: [confirmed old -> new]
What is unchanged: [confirmed facts only]
Who is affected: [approved scope]
Action and deadline: [confirmed instruction, date/time and time zone]
Official information: [approved public reference]
Questions: [approved contact route]

Keep missing details in review notes. Do not release a message with unresolved essential fields.

## Release record
Draft version:
Facts and recipient scope checked by:
Approval reference and time:
Sending state: draft / approved / sent / unknown
Actual send reference (only after verification in the approved system):
Delivery state: not checked / confirmed by system / issue / unknown
Acknowledgment state (separate from delivery):
Correction/retry review reference:

## Optional AI draft-review prompt
Use only this sanitized, confirmed event fact sheet to draft a concise manager notice.
Preserve exact confirmed old/new values, dates, time zones, unchanged facts and action scope.
Return the draft plus a separate missing-information checklist.
Do not invent deadlines, refunds, policy exceptions, contact details or official decisions.
Do not choose recipients, access mailboxes, infer facts from old threads or send messages.
Mark the output DRAFT, NOT APPROVED OR SENT.
If an essential fact is missing, flag it for the authorized reviewer rather than completing it.
A translation, if requested, needs human review of critical details before release.

## Synthetic example
DEMO-EVENT / DEMO-GAME-204: field DEMO-A -> DEMO-B.
Kickoff unchanged according to supplied source.
Effective date/time zone and manager action still need confirmation.
Draft only; not approved or sent.

## Checklist and privacy
1. Confirm purpose, authority, facts and affected scope.
2. Verify current recipients in the authorized event list, outside AI.
3. Compare the draft with sources; review critical dates/links and any translation.
4. Obtain authorized approval before using the approved sending process.
5. Keep draft, approved, sent, delivered and acknowledged states distinct.
6. After uncertain outcomes, check records before retrying to avoid duplicates.
Keep player data, contacts, private threads, card images and authenticated links out of AI input.
Public examples stay fictional. This template certifies no eligibility or event policy.