Draft a schedule for six teams playing a single round robin on two pitches. Matches last [minutes], changeovers [minutes], venue hours [times] and minimum team rest [minutes]. First calculate the 15 fixtures and available pitch slots, then check whether the constraints fit. Output fixture times and pitches, and independently check no simultaneous team appearances, every pair once and rest intervals. Flag infeasibility rather than breaking a rule. Keep umpire assignment separate until I provide availability and conflict constraints. This is a draft for organiser validation.
Make it yours: Provide organiser-approved rules and rest requirements, not assumed federation rules.
A useful follow-up
Here is umpire availability and team affiliation. Assign officials and list every conflict check and unfilled slot.
02
Text
Check whether the tournament fits before scheduling
Assess a [format] tournament with [teams], [pitches], [match length], [turnaround], [opening hours] and minimum rest [rule]. Calculate required fixtures and available pitch slots. Show assumptions and capacity arithmetic. If infeasible, explain the constraint conflict before proposing any timetable.
Make it yours: Provide actual competition rules; AI must not invent them.
A useful follow-up
Which single approved change would restore feasibility?
03
Text
Draft round-robin fixtures with explicit byes
Draft fixtures for these teams [IDs] under [competition rules]. State whether each pairing occurs once or twice. Include byes where required, then verify expected match count, no self-matches, no missing pairs and no duplicates. Do not assign times until the fixture list passes these checks.
Make it yours: Use stable IDs rather than similar team names.
A useful follow-up
Return the unordered pair list so I can validate coverage independently.
04
Files
Assign pitches and times without hidden violations
Use these validated fixtures and availability windows to draft a timetable. Hard constraints: [pitch, team, rest and travel rules]. Preferences: [preferences]. Return match ID, start, end, pitch and teams, then a violation report. If no valid solution is found, say so; do not silently relax a hard rule.
Make it yours: Include transition time and time zone.
A useful follow-up
Check every team's consecutive matches against the minimum rest rule.
05
Files
Assign umpires within qualification and availability
Assign officials to these scheduled matches using [official IDs, eligibility, availability, conflicts, workload limits]. Each match needs [number and roles]. Treat qualifications, overlapping duties and declared conflicts as hard constraints. Return assignments and uncovered matches. Do not invent availability or fill gaps with ineligible people.
Make it yours: Share IDs and necessary eligibility, not sensitive personal information.
A useful follow-up
Show each official's assignments, breaks and unresolved conflicts.
06
Files
Audit an umpire rota independently
Audit this umpire rota against the supplied match schedule and eligibility table. Check overlapping matches, travel buffers, qualifications, declared team conflicts, maximum duties and required breaks. Reference offending match IDs and time intervals. Separate hard violations from fairness preferences; do not assume the draft is valid.
Make it yours: An organiser must approve the final rota.
A useful follow-up
Propose the smallest swaps that fix confirmed violations, then recheck all constraints.
07
Files
Repair a schedule after a late withdrawal
Given this approved schedule and [withdrawal or delay], propose a minimal-change repair. Keep [locked matches] fixed, preserve all hard constraints and show before/after rows by match ID. List who must be informed. If a valid repair cannot be found, present options for the organiser instead of breaking a rule.
Make it yours: State which changes need competition approval.
A useful follow-up
Check that each repair has not created a new umpire or pitch clash.
08
Text
Define fairness without disguising it as a rule
For this tournament [format and constraints], propose measurable fairness preferences for rest, early starts, pitch distribution and official workload. Separate them from mandatory competition rules. Explain trade-offs and ask the organiser to rank conflicting preferences before optimising.
Make it yours: Fairness depends on the event; do not assume one universal score.
A useful follow-up
Compare two schedules using the approved measures without hiding hard violations.
09
Text
Write a validator specification for sports schedules
Specify a validator for match and umpire CSV files with fields [fields]. Define checks for missing IDs, duplicates, time parsing, pitch/team/official overlaps, eligibility, breaks and expected fixture coverage. Include a tiny valid fixture and separate invalid cases. Do not claim a schedule is validated until the checks actually run.
Make it yours: Use a script or spreadsheet to verify arithmetic and clashes independently.
A useful follow-up
Which test catches an overlap that starts before another match ends?