# Review facility data before an import
More time on the field. Less time in the office.

Audience: administrators
Status: practical assisted mapping guide, not a universal connector or automatic migration.
Your existing facility and club systems remain the official records.

## Outcome and inputs
Outcome: reviewed column mapping, facility/field reconciliation and an exception report.
Inputs: permitted source export, existing destination snapshot, current destination template,
required columns/allowed values, stable source references, parent relationships and staff owner.
Importing or updating records requires a separate authorized process.

## Version and scope
- Source export/version/date:
- Destination snapshot/date:
- Destination template/version:
- Required columns and allowed-value source:
- Review owner:
- Proposed file version:
- Recovery copy reference (private):
Never put private internal references into public copy.

## Column mapping
| Destination column | Source column | Proposed transformation | Required rule/source | Unresolved? |
|---|---|---|---|---|
| | | | | |
Keep original values beside proposed values. Do not invent missing addresses, dimensions,
units or surface types. Verify each rule against the actual supplied destination template.

## Facility and field identity
| Source venue ref | Source field ref | Original label | Candidate destination ID | Evidence for match | Create/update decision by staff |
|---|---|---|---|---|---|
| DEMO-V1 | DEMO-F1 | Field 1 | Unknown | Parent venue required | Hold |
| DEMO-V2 | DEMO-F2 | Field 1 | Unknown | Different parent venue | Hold |
The two fields are distinct in this fictional example even though their labels match.

## Five-step review
1. Freeze sources and define facility versus field. Preserve source IDs and parent links.
2. Write an explicit column map with source, transformation and destination rule.
3. Compare with destination records. Similar names are candidate matches, not proof of identity.
   Keep source and destination IDs separate. Staff decide uncertain creates/updates.
4. Check required values, parent relationships and supplied allowed lists. Do not default
   unknown surface values to grass or infer capacity, booking permission or availability.
5. Resolve exceptions, reconcile counts/relationships and validate the current template.
   Keep a recovery copy. Import/update/delete is a separate authorized action, not performed here.
   After an authorized import, reconcile destination results separately.

## Synthetic value exception
DEMO-F2 surface = mixed. The illustrative supplied allowed list does not contain mixed.
Action: HOLD for staff clarification; do not invent an equivalence or silently use grass.
This is not a statement about the actual allowed values of any platform.

## Exception log
| Source ref | Original value | Proposed value or unknown | Rule/source | Staff question | Owner | Decision evidence |
|---|---|---|---|---|---|---|
| | | | | | | |

## Optional sanitized AI prompt
Organize mapping exceptions using only this approved anonymous/synthetic facility data.
Preserve original values, source IDs, parent venue links and destination IDs separately.
Use only supplied template rules and allowed values. Do not infer missing data or merge
same-named fields across venues. Flag uncertain matches and unsupported surface mappings.
Do not create, update, delete or import records, contact staff or claim venue access.
Return: source ref | rule/evidence | proposed mapping | exception/question for staff.
Source data/version: [paste approved data]
Destination snapshot/template rules: [paste]
Known staff-approved mappings: [paste or none]

## Approval and privacy checkpoint
- Reviewed version/date:
- Staff decisions and remaining holds:
- Counts and parent relationships reconciled:
- Separate import authorization and recovery plan:
Keep access codes, private contacts, booking notes and credentials out of AI prompts.
A mapping review is not proof of scheduling permission or a successful import.