The outcome
A reviewed team-to-division worksheet and a clear list of unresolved entries before bracket generation. This is a practical guide and template, not an automatic seeding or eligibility tool.
What you need
- An authorized team-registration export and its export date.
- The tournament’s current division definitions, registration status rules and review deadline.
- Current-season official sources for any league placement or ranking used in seeding.
- A director or authorized reviewer to resolve exceptions.
1. Freeze a review copy—not the live roster
Preserve the original export. Record the tournament identifier, season, export timestamp and source row count in a dated working copy. Confirm which entries are accepted, waitlisted, withdrawn or still pending before counting teams. Do not change registrations during this review.
2. Match the event and season first
Event identifiers and age-group definitions can change between seasons. Verify each source belongs to the intended competition and season before reusing a division lookup. Record the source link, the date checked and what it actually supports. A familiar team name is not proof that last season’s division still applies.
3. Reconcile team identities
Use stable team identifiers when available, plus the current team label and registration reference. Treat an exact repeated identifier as a possible duplicate registration, not permission to delete it. Similar team names with different identifiers stay separate until a reviewer confirms their identities.
4. Separate requested placement from verified evidence
Keep the requested tournament division, current league division and any seeding evidence in separate columns. They are different facts. An unknown lookup, stale source or conflicting registration creates an exception—not an invented assignment.
SYNTHETIC EXAMPLE — NOT REAL TEAMS DEMO-101 · North Example FC · Requested: Division A Current-season source supports Division A → REVIEW READY DEMO-102 · Valley Example SC · Requested: Division B Only last season’s source is available → HOLD: STALE SOURCE DEMO-103 · East Example United · Requested: Division A Two conflicting current-season labels → HOLD: DIRECTOR REVIEW
5. Reconcile every row
Give each registration row exactly one review outcome: ready for director review, held for evidence, or excluded from this bracket build with a recorded reason. Reconcile accepted source rows against all outcomes. Track unique teams separately; row totals and unique-team totals need not be the same.
6. Approve the mapping before generating brackets
Have an authorized director approve the division mapping and configured seeding criteria. Keep unresolved entries out of automated assumptions. After generating a bracket draft, check team counts, missing entries, duplicate placements and the event’s agreed constraints before release.
Optional AI assistance
Use the downloaded prompt to summarize a sanitized exception worksheet. Require the assistant to cite the supplied source reference for each suggested issue and mark unsupported facts unknown. Do not ask a model to “fill in” a team’s division from its name.
Privacy checkpoint
Team identifiers and operational notes can still be sensitive. Use organization-approved tools and minimum necessary information. Player names, birth dates, contact details and card images are not needed for this division review.
Reusable resources
- Download the review checklist and AI prompt.
- Download the synthetic division-review worksheet. Replace demo rows only in your private working copy.