# Practice-field constraint review

Audience: administrators and authorized schedulers.
Type: manual constraint worksheet + optional AI prompt, not an automated allocation product.

## Planning scope
Season / applicable dates / time zone:
Current permission and venue sources:
Approved priority rules:
Reviewer and approval process:

## Space record
Venue reference:
Field and grid reference:
Applicable dates and operating window:
Confirmed simultaneous capacity:
Shared-space restrictions:
Lighting/operating restrictions and source:
Permission status: confirmed / pending / unknown
Source reference and date checked:
Responsible person / next check:

## Team request
Anonymous team reference:
Requested sessions and duration:
Confirmed unavailable days/times:
Preferred days/venues (not guarantees):
Shared coach reference(s):
Approved travel/changeover constraints:
Conflicting answers to confirm:

## Constraint ledger
Reference | Limit or preference | Confirmed/pending/unknown | Source | Owner | Follow-up
DEMO-GRID-A | one team at a time in confirmed window | confirmed | demo source | reviewer | review assignments
DEMO-GRID-B | capacity/permission unresolved | pending | demo request | reviewer | hold out of confirmed total
DEMO-COACH-1 | simultaneous requests for two teams | confirmed conflict | demo requests | scheduler | seek alternatives

## Checklist
1. Define venue, field and usable grid separately.
2. Confirm capacity and applicable dates; do not reuse a prior season's permission without checking.
3. Separate hard constraints from preferences using approved organizational rules.
4. Keep unknown capacity out of confirmed totals.
5. Check every shared coach, travel/changeover requirement and contradictory answer.
6. Compare confirmed team-slot supply against requested sessions; retain unallocated requests.
7. Check lighting/operating restrictions for the relevant dates.
8. Have authorized staff review every assignment and approve publication.
This worksheet reserves no fields, changes no permits, writes no club-system sessions and sends nothing.

## Optional AI prompt
Organize these authorized, sanitized field/team constraints into confirmed limits, preferences and unknowns.
Preserve source references, date applicability, time zones, capacities and shared-coach dependencies.
Identify contradictions, missing information and questions for the scheduler.
Do not invent permits, assume field-to-grid capacity, relax hard constraints or fill pending slots.
Do not claim a draft is feasible/optimal without a verified constraint model.
Do not book fields, write schedules or send messages.

Privacy: use anonymous references, not child schedules, coach contacts, credentials or private staffing notes.
Use approved tools and synthetic examples for public demonstrations.