Module: Race Guide
The Race Guide module gives participants access to the event’s official race guide directly through chat — no need to search through a PDF or scroll a long document on their phone.
How It Works
The organizer’s race guide is scanned and structured into the chat system in advance. Sabin then answers questions directly from that content — rules, schedule, categories, cut-off times, whatever the guide covers — in the participant’s own language, on demand.
Limitations to Communicate Clearly
| Text only, no images | Sabin reads and answers from the written content of the race guide; diagrams, maps, and photos in the original PDF are not reproduced or shown in chat. If a participant needs a visual (e.g. a course map), they should be directed to the original race guide document. |
| Page limit applies | To keep processing and answer quality reliable, the race guide is limited to a maximum number of pages (upload allowance: e.g. once per week, or up to 20 uploads — per existing spec). Organizers should keep the guide as text-focused and concise as possible for best results. |
Overlap with Venue
Race guides typically already include location-related content — start/finish points, parking, venue access — which naturally overlaps with the separate Venue module (map links, airport/ferry info, points of interest). In practice, a participant’s location question may be answered from either module depending on how it’s phrased.
This isn’t a conflict: Venue adds structured, always-current location data (Google Maps links, transport) that a static race guide text wouldn’t capture, while Race Guide covers whatever the organizer wrote into the official document. Worth deciding whether to keep this overlap as-is (redundant but harmless) or route location questions exclusively through Venue going forward.