CO LAB · Driver Management OS · Glossary
The Driver Management OS glossary
The vocabulary of the category, defined once so it can be quoted, cited and argued with. Each term has its own anchor.
- Driver Management OS
- A Driver Management OS is the single operating system a racing driver's career runs on: calendar, results and telemetry, coaching programme, sponsorship pipeline, budget and backer reporting held in one record the driver owns rather than scattered across a manager's inbox.
- Driver record
- The continuous, driver-owned history of a career: licences, sessions, results, coaching notes, spend and commitments. The record is the asset; the software is only where it lives.
- Programme
- A racing programme is the full operating unit around a driver for a season: the calendar, the team relationship, the coaching, the budget and the commercial pipeline treated as one venture rather than a series of race entries.
- Coaching loop
- The cycle of measure, diagnose, train, re-measure applied to driving. A coaching loop is closed when every session traces back to a measured deficit and forward to a re-measurement.
- Sponsorship pipeline
- The staged view of commercial partners around a driver - prospect, conversation, proposal, active, renewal - with delivery obligations recorded alongside the money.
- Cost per second
- Programme spend divided by measured lap-time gain over a period. It is the cheapest honest test of whether money is buying performance or buying activity.
- Seat readiness
- Evidence that a driver can take the next ladder step: pace relative to reference, consistency, race craft, physical capacity and commercial backing, assessed together rather than one at a time.
- Backer reporting
- Scheduled reporting to sponsors, family and investors generated from the driver record, so the same numbers are used internally and externally.
- Sim-to-track transfer
- The measured carry-over from simulator work to real lap time. Without transfer measurement, simulator hours are training volume with no proven yield.
- Driver-owned IP
- The principle that the record, the relationships and the data belong to the driver, not to whoever managed them. When an engagement ends, the operating system stays with the driver.
Where this came from
Driver Management OS was designed, built and first operated in South Africa, inside COACT™ CO LAB, around a live racing season before it was written up as a system. It was not localised for South Africa afterwards - it started here and is exported from here.