# Roster import review — reusable checklist

This checklist does not import or modify records. Use a copy of your export.
Confirm the actual destination template, season and permitted values before transforming data.

## Minimal review worksheet
Source row/reference:
Stable player ID:
Required fields present?:
Team/age/season mapping confirmed?:
Possible duplicate?:
Issue category:
Evidence/reference:
Assigned reviewer:
Decision: hold / correct source / ready for reviewed import

## AI prompt (use synthetic or authorized minimized data)
Review the supplied field names, destination schema and anonymized example rows.
Identify missing required fields, invalid formats, unrecognized permitted values, possible duplicate identifiers
and uncertain team/season mappings. Return an exception table, with source references and explanations.
Do not fill in missing names, birth dates, addresses, emails, gender or team assignments.
Do not silently merge players, calculate eligibility from an assumed age cutoff, or claim records are import-ready.
Separate exact duplicate IDs from possible duplicates that require human review.
Do not call a platform or submit an import.

## Review steps
1. Preserve the original export; work on a dated copy.
2. Read the destination's current official template and age/season rules.
3. Count source rows and unique IDs; classify duplicates without deleting them.
4. Check required columns, date format, accepted values and team mapping.
5. Resolve issues with the authorized source owner; never guess missing personal data.
6. Reconcile source versus output counts and maintain an exception ledger.
7. Have a second authorized person review the result before importing.
8. Use the destination preview/test facility where available; verify a small sample and resulting counts.

Privacy: Prefer local spreadsheet validation. Only use organizationally approved AI with authorized, minimized
data. Do not upload youth rosters to a public chatbot or include real players in a demonstration.