Module: Course Management
Course Management is the most comprehensive module in the Sabin platform. Where other modules answer questions, Course Management actively manages the physical event course itself — its locations, its timing, its condition, and the coordination between the event team, the authorities, and the people working the course on the ground.
Location Tracking
The module tracks every physically relevant point along the course, organized into distinct location types:
| Crossroads | Intersections where the course crosses public roads, requiring traffic management or marshal presence. |
| Route segments | The course itself, broken into manageable sections for timing and monitoring. |
| Signs | Every directional or warning sign that needs to be physically placed along the course. |
| Road closures | Points where roads are fully or partially closed for the event. |
| Control points | Checkpoints where riders or runners are tracked as they pass, feeding into timing and safety monitoring. |
| Aid stations | Water, food, and medical support points along the course. |
| Locations of attention | Hazards, technical sections, or anything requiring extra caution from participants or extra oversight from the team. |
| Road damage | Potholes, surface issues, or other physical problems affecting the course. |
Every one of these locations is geographically anchored, meaning any team member — whether event staff, police, or ambulance crew — can reach any point with a single tap through Google Navigation. There’s no need to describe a location verbally or share coordinates manually; the location itself carries its own navigable reference.
Timing and Cut-off Calculation
Course Management doesn’t just record where things are — it calculates when they matter. For every location along the route, the module estimates:
| Expected arrival time | When the field of participants is expected to reach that point. |
| Cut-off time | The latest time a participant can pass that point and still continue in the race. |
These calculations are built from minimum and maximum expected speed inputs — the slowest and fastest realistic pace for the field on that section of course. From these speed bounds, Course Management generates a full timetable covering the entire route, and from that timetable, cut-off times can be derived for different distances or route variants (useful when an event offers multiple distances that share parts of the same course).
This turns what is often a rough, manually-estimated schedule into a data-driven timetable that updates consistently as course details change.
The Buku — PDF Export for Authorities
Once the timetable exists, Course Management can generate a formatted PDF document — referred to internally as the Buku — built directly from the calculated timing data. This document is intended for police, ambulance services, and other supporting authorities, giving them:
| Exact expected timing per location |
| Cut-off times per location and per route |
| A clear, official reference they can carry or distribute internally |
This removes the need to manually compile timing information into a separate document each time an event’s course or schedule changes — the Buku is generated from the same live data Course Management already tracks.
Road Closure Status
For every road closure point, Course Management tracks and displays a live status — whether it’s currently open, closed, or pending closure. This gives the event team, and anyone with access to the module, an always-current picture of the course’s closure state without needing to physically check or radio each point individually.
Road Damage Reporting
Team members can log road damage directly at the relevant location, attaching photographs as evidence. Over time, this builds a structured list showing exactly:
| Where damage exists |
| What kind of damage it is (via the photo and any notes) |
| Which locations need repair before the event |
This list can be handed directly to the responsible local authorities as an actionable report — replacing informal notes, scattered photos, or verbal reports with a single, organized, location-tagged record.
Signage Placement Workflow
Placing signage along a long course is one of the most logistically demanding tasks in event setup, and Course Management turns it into a guided, self-checking workflow:
| 1 | The person responsible for placing signs is navigated via Google Navigation to the first location requiring a sign. |
| 2 | Once there, Sabin asks whether the sign has been placed. |
| 3 | If confirmed yes, Sabin automatically starts navigation to the next location in the sequence. |
| 4 | This repeats until all signage locations are covered. |
Every placement is timestamped and logged, producing a complete record of when each sign was placed and by whom — useful both for verifying setup is complete before race day, and for accountability if a sign is later reported missing or misplaced.
Why This Module Matters
Course Management is what turns Sabin from a participant-facing information tool into an operational backbone for the event itself. It’s the one module genuinely useful to people who aren’t racing at all — police coordinating road closures, ambulance crews needing cut-off timing, road crews placing signage, and local authorities receiving repair reports. This is also why the module deserves a name that reflects its scope: it doesn’t just display signs, it manages the course.