# Read the score with its context.

Source: https://sector4labs.com/imsa-alpha/methodology

Public methodology

IMSA Alpha presents relative driver-performance views from public timing. The approach groups observations by the available driver rating and vehicle class, then uses representative lap-time comparisons. A score is a summary of supplied timing, not a measurement of driving ability independent of the car and session.

Archival public sample. Data through January 2026. This page explains interpretation; it is not a new validation of the scoring implementation.

## What goes into the comparison?

Public session reports identify the event, session, class, driver, and available timing. Alpha groups comparable records using the rating/class information present in the source. A rating category is not proof that two drivers have equal experience or that their cars ran in identical conditions.

The published method uses percentile-based lap-time summaries rather than relying only on one fastest lap or an unqualified average. Unusual laps can affect either approach. Timing alone cannot determine whether an unusual lap involved traffic, an incident, a cooldown, fuel load, or another cause.

## How should a score be read?

Alpha presents a relative score from 0 to 100 for the selected cohort and session. Inspect the actual report, available peer group, and source coverage before drawing a conclusion. Do not treat an arbitrary threshold as a certified talent, reliability, or safety rating.

Cross-session or cross-event comparisons need context. Weather, flags, tires, fuel, driver allocation, car specification, missing laps, and the peer group can change. A change in the score is not, by itself, proof of improvement, a setup problem, fatigue, or driver error.

## What the source cannot establish.

-   Public timing does not contain a rival's throttle, brake, tire temperatures, setup, or private radio.
-   Relative lap-time observations do not prove why a car lost time or who caused a result.
-   Missing or delayed source data limits the comparison. An absent value is not a known zero.
-   These archival views are not live race authority, an eligibility decision, or a performance guarantee.

[Understand timing versus telemetry](https://sector4labs.com/rules/timing-vs-telemetry).

## Inspect the actual evidence.

[Open IMSA Alpha](https://sector4labs.com/imsa-alpha/), inspect the [data catalog](https://sector4labs.com/data), or read the [dataset manifest](https://sector4labs.com/imsa-alpha/data/manifest.md). Available report, timeline, and insight files are separate distributions. An absent optional file is not supplied by a view label.

For your own team's permitted exports, [inspect a scoped session-reporting engagement](https://sector4labs.com/session-reporting). It adds agreed source context and a handover, not automatic causation.

BoxNext step

## Need a report from your own sources?

Describe the workflow and available exports. Do not send private files through the site.

[Book a 15-minute call](https://sector4labs.com/contact?source=alpha&topic=session-reporting#book)[Send a short brief](https://sector4labs.com/contact?source=alpha&topic=session-reporting#brief)
