Why it matters
Without it, mis-entries, poor race selection, and missed declarations risk credibility, ownership value, and regulatory compliance, leading to avoidable losses and welfare impact from ill-suited races.
From design to safety
Design
Design AI-aligned race plan
The AI considers past performance, upcoming race types, and owner preferences to propose an initial race plan and priority declarations. It ingests handicap implications, course profiles, and jockey capacity constraints, and outputs target list with provisional declarations and contingency options.
- Race Programme Ledger
- Entries Register
- Conditions Book
- Ratings Sheet
Build
Build data feeds and rules
Integrate official race entries feeds, course conditions, and handicap data with validation checks on consistency and timeliness. It validates data feeds from official sources and sets schema for time-stamped entries and versioning.
- Race Programme Ledger
- Entries Register
- Conditions Book
- Distances Chart
Operation
Operate live race entries
AI polls real-time ratings, going, and distances; it suggests entries and confident declarations while flagging conflicts. It tracks live market hints, weather forecasts, and course changes, adjusting likelihoods and suggesting dynamic entry windows.
- Entries Register
- Conditions Book
- Ratings Sheet
- Distances Chart
Maintenance
Maintenance of data integrity
Regular vetting of race entries data, updates from racing authority, and recalibration after each meeting or handicap reset. It runs data integrity checks weekly, reconciles updates after handicap resets, and maintains audit trails for regulators.
- Ratings Sheet
- Going Monitor
- Distances Chart
- Conditions Book
Safety
Safety and compliance checks
AI ensures entries comply with withdrawal times, passport checks, and regulatory rules before declarations are made. It cross-checks with vaccination records, anti-doping status, and stable inspections, logging any anomalies.
- Race Programme Ledger
- Entries Register
- Conditions Book
- Ratings Sheet
Part by part
- 1
Race Programme Ledger
- Watch for
- Errors in planned programme entries, mismatched race codes, or outdated race dates.
- AI action
- Flag conflicting entries and propose alternative races for trainer approval.
- 2
Entries Register
- Watch for
- Duplicate declarations, missing owner approvals, or incorrect entry fee status.
- AI action
- Highlight missing signatures and generate updated declaration pack.
- 3
Conditions Book
- Watch for
- Inaccurate course conditions or going data linked to an incorrect race.
- AI action
- Recommend races with matching going and surface based on forecast data.
- 4
Ratings Sheet
- Watch for
- Misaligned ratings versus recent form or handicap updates.
- AI action
- Suggest weight allowances and target races with favorable ratings differential.
- 5
Distances Chart
- Watch for
- Distances not aligned to horse best distances or race type.
- AI action
- Flag unsuitable distances and propose closer match options.
- 6
Going and Weather Monitor
- Watch for
- Going swings, forecast rain, or track drift impacting performance.
- AI action
- Trigger alerts and adjust entry options to suit expected conditions.
Worked example
Strategic Race Entry for Janice Star in 2m4f mile
Illustrative scenario with sample data.
A mid-season plan to place the filly in distances she handles best given current form and forecast conditions.
Signal in
raceProgrammeCode=RPG21; upcomingRaces=[{code:RAC101,dist=2m4f,going=soft,course=left-handed},{code:RAC102,dist=1m6f,going=good,course=straight}]; ratings=[{horseId=JS1,form=3-1-2,handicap=95}]; ownerPreferences=[:prefers targets with exposure]
System out
Declaration pack ready for RAC101, with alternative RAC102 flagged as backup; status=awaiting trainer approval; alert to change due to forecast going.
Human sign-off: Licensed trainer reviews AI suggestions, approves RAC101 as primary and RAC102 as backup, signs declaration pack.
How to roll it out
Phase 1
Weeks 1 to 4
Baseline data integration, feed validation, and initial plan generation from historic form.
Phase 2
Weeks 5 to 8
Live testing with real entries, monitoring alerts, and adjustment of declarations.
Phase 3
Weeks 9 to 12
Full operation with live declarations, regulatory checks, and performance review.
Where people stay in charge
- Every entry decision must be signed off by the licensed trainer or their designate before submission.
- The AI may propose backups, but final declarations require human approval and documented rationale.
- Regulatory checks, withdrawal times, and passport status must be validated by yard compliance personnel prior to submission.
Questions owners and crews ask
What data does the AI need to optimise race entries?
The AI uses race programme data, going, course, distance, ratings, form, and owner preferences to propose optimal entries and backup options.
Who approves the AI-generated entry plan?
The licensed trainer reviews and approves the primary entry and backups, with final sign-off documented in the declaration package.
Can the system account for owner restrictions or syndicate rules?
Yes, it integrates owner preferences and syndicate constraints to tailor target races and declaration timing accordingly.
How is regulatory compliance ensured before declarations?
The system flags withdrawal times, passport status, entry fees, and regulatory checks for human sign-off prior to submission.