Documentation

Glossary

The vocabulary the application uses, defined in one place. These are the same definitions behind every hint icon in the product, so nothing here can drift from what you see on screen.

Results & standings

Provisional results: When a race is uploaded the app generates a provisional finishing order straight from the telemetry. Stewards may then apply penalties (time, points, or disqualification) and recompute. Provisional results are not the final word — they become final only when an admin explicitly makes them permanent.
Final results: Final results are the classified order after all penalties have been applied and an admin has made them permanent. Championship standings are built from final results, not from the provisional telemetry order.
Standings: Standings aggregate championship points from each round's final results. They deliberately exclude provisional, pre-penalty telemetry order so the table only ever reflects classified, permanent results.

Stewarding

Penalty: A penalty is a steward's ruling applied to a driver in a session: added race time, a grid-position drop, a points deduction, or disqualification (DSQ). Applying or editing a penalty recomputes the affected results.
Penalty points: Penalty points are licence-style points recorded against a driver for on-track incidents, tracked on the driver profile. They are separate from championship points and do not change the standings directly.
Protest: If you raced in a session, you can file a protest about an on-track incident from its race page — for as long as the result is still provisional. Stewards review it, and the outcome may become a penalty. Once the session is finalized, protests for it are closed. You can track the status of protests you filed on “My Protests”. A league may also set a shorter filing window after the session ends; if it does, the report button shows a countdown until protests close.
Anomaly flag: Anomaly detection flags telemetry that looks unusual (implausible speeds, corner-cutting patterns, etc.). Flags are advisory: they surface things worth a steward's attention and are never an automatic penalty or a final determination.

Driver ratings

OVR (Overall rating): OVR is the headline driver rating, shown on a roughly 60–99 scale. It's a field-relative rating built from Speed, Racecraft and Competence — not a simple average of the five components shown below it — and Consistency affects how quickly it reacts to new results. Safety is fully computed and displayed on its own, but doesn't currently feed into Overall, so a high Safety score next to a lower Overall isn't a data error. "Field-relative" above is the load-bearing word, and it bounds what OVR can be compared with: every race is scored only against the grid that actually ran it, so two tiers that never meet each settle around the same baseline independently. Absolute pace barely shows up — two fields with identical skill spread but 4.0s a lap between them produced a best-driver OVR gap of 0.05. A driver who dominates the slowest tier and one who dominates the fastest therefore read almost the same, and the number should not be used to rank one tier against another.
SPD (Speed): Raw pace — how fast the driver's representative lap times are.
RAC (Racecraft): Wheel-to-wheel skill — overtaking, defending and position gained.
SAF (Safety): Clean-driving score — fewer incidents, collisions and penalties raise it.
CMP (Competence): Competence measures race execution, not raw speed. Half of it is lap consistency: how tightly your representative green-flag laps cluster together, with pit, safety-car and traffic laps filtered out. The other half is pace retention — whether your lap times held up over the race compared with how the rest of the field's moved that day, so managing tyres and fuel to hold your pace while others fade scores well. It is deliberately independent of Speed, which measures how fast you were rather than how well you executed: a quick driver can have a modest Competence, and a steady midfielder a high one.
CON (Consistency): How consistent this driver's race results are, round to round — steadier performances score higher and make the driver's Overall rating respond faster to new results; volatile results are weighted more cautiously.

Championship structure

Tier: Tiers are skill divisions inside a league (e.g. Pro / Am). Drivers are assigned to a tier, and races, results and standings are organised per tier.
Weekend type: A weekend type defines the sessions that make up a race weekend and their order, so each round on the calendar can reuse a consistent structure.
Format: A format captures how a round is run and scored — the session layout and any special rules such as sprint or reverse-grid — so rounds can share a consistent shape.
Point system: A point system maps finishing positions to championship points, including any bonuses (e.g. fastest lap, pole). Each season/format references a point system to score its results.
Driver of the Day: Driver of the Day recognises a standout performance each race weekend. There is one poll per event and it runs on the feature race, so a sprint weekend still has a single vote. Depending on the league it's decided by member votes or an automated tally over the session.
Pace band: A signpost from fastest to slowest, built from classified green-flag lap times — never a driver rating: it says how quick a tier's racing is, not how good the league is. A slower-band league with a happy, reliable field can be a better league to join than a faster one that folds. Bands stay dark until an operator publishes them from a real distribution; until then they read as unavailable everywhere.

Access & platform

Roles & permissions: Access is permission-based. A role bundles permission keys (league.manage, stewarding.manage, members.manage, roles.manage, billing.manage, activity.view). Built-in roles can't be edited; custom roles let you tailor access per league.
Activity log: The activity log records every privileged change (penalties, results, member/role changes, settings) with a snapshot of who made it. It's per-tenant, retention-bounded, and viewable by admins with the activity.view permission.
Plan-locked feature: A lock badge means the feature isn't part of your league's current plan. It stays visible so you can see what's available; upgrading the plan unlocks it. Access is otherwise unchanged.
Data retention & export: Retention controls how long uploaded telemetry and derived data are kept. The Data & Export tools let an admin export a league's data. Retention windows depend on the plan.

Keep reading

The rest of the documentation, and the product it describes.

All documentation Demo Pricing