← Driver Toolbox

Safety Rating Methodology Beta

How the Rush SR safety board turns clean running and incident rulings into one transparent rating.

Safety Rating is in beta for 2026. The formula, the session weights, the incident matrix, and the advisory bands are all expected to change during the season as we see how the numbers behave over a full calendar. Ratings are recomputed from the incident log every time, so a tuning change moves every driver’s number at once, including past weekends. Treat a rating as the current reading of a system still being calibrated, not a settled result.

What it measures

Safety Rating measures conduct in the Rush SR field. It does not reward pace, finishing position, or championship points.

The rating is recomputed from the published incident log. It is never entered by hand and never stored as a separate driver field. Each eligible weekend contributes green-flag exposure and the incident points attached to steward rulings. Clean running lifts the rating gradually; incidents reduce it.

Test days are not counted. The current intake includes only official days under the Rush National Series sanctioning bodies, currently the GridLife rounds; practice and warmup sessions carry 0.25 weight, while qualifying and race sessions carry 1.00.

The same replay is used on driver profiles, the public board, and the steward tools. This page displays the live values currently used by the replay.

The field today

Every rated driver, binned by rating. Select a band to see who is in it.

118
Drivers rated
2.33
Field median
95 of 118
Above the 2.00 opening

Select a band to see the drivers in it.

0.00 to 0.25 1 driver

0.25 to 0.50 1 driver

0.75 to 1.00 2 drivers

1.00 to 1.25 1 driver

1.25 to 1.50 2 drivers

1.50 to 1.75 6 drivers

2.50 to 2.75 13 drivers

2.75 to 3.00 13 drivers

3.25 to 3.50 6 drivers

3.50 to 3.75 1 driver

Each driver opens at 2.00, so the bands below that line hold drivers whose incidents have outweighed their green-flag running so far, and the bands above hold drivers who have run more clean minutes than they have given back. A driver with one weekend sits close to 2.00 either way: the rating moves slowly until there is enough running behind it to move.

Published driver profiles show a letter grade instead of the raw number. A is 3.00 and above, B runs from 2.00 to 3.00, C runs from 1.00 to 2.00, and D is anything below 1.00. The letter is advisory, like the rest of the rating. The band breakdown above still prints the exact two-decimal value for every rated driver, and stewards work from the full-precision number behind the letter.

The live rules

The table and formula below are rendered from the live raw_sr_rating_settings option and the deployed Safety Rating matrix.

The live formula

New rating = 5.00 − (5.00 − previous rating) × e−0.5 × E ÷ 500 − (P ÷ 12)

  • E is green-flag exposure, weighted by session type.
  • P is incident points, weighted by session type. A flagged full-course-yellow incident multiplies shared and at-fault points by 2; not-at-fault grades are exempt.
  • 500 is the fixed season anchor. It is a tuning constant, not a measurement.

Session weights

SessionLive weight
Race1
Qualifying1
Practice0.25

Damage/DNF grades that are shared or at fault, and reckless grades, score at full session weight. This prevents serious outcomes from becoming cheaper in practice.

Live incident points

IncidentNot at faultSharedAt fault
Solo off, spin, or 4-off——2
Rule infraction (PUY, jump start, blend line)——4
Blocking or impeding——4
Mechanical failure——1
Contact or squeeze, no consequence124
Costing a position, a spin, or an off136
Causing damage or a DNF2510
Reckless or wholly avoidable——40

The row is the worst consequence caused by the incident. Mechanical failures are the lowest chargeable row, solo offs are next, and damage/DNF uses the live matrix above. An infraction escalates to the consequence row when it caused contact or impeded safety trucks.

Advisory status

Driver under review is an advisory recommendation based on the full-precision rating and appeal state. The sanctioning body retains final discretion over entry and sanctions.

Ratings are cumulative and do not decay. Appeals keep affected weekends provisional until their review windows close.

What-if simulator

Build a season one weekend at a time. Each box is a whole weekend: practice, qualifying, and race combined using the live session weights. This is a read-only projection using the live matrix and formula above.

New drivers start at 2.00. Published drivers use their current live rating.

Weekend 1

Weekend type

Per-session minutes; this weekend aggregates practice + qualifying + race.

Add up to 24 weekends. Delete a weekend with the x in its top-right corner; at least one box remains.

Projected final rating

2.00

Choose a driver and a weekend to project a rating.

Season trajectory

    The simulator never saves a rating or incident. Display values are rounded to two decimals; calculations keep full precision.

    How incidents are graded

    Each involved driver receives a separate grade. The row records the worst consequence caused by the incident, not simply what happened to that driver’s own car. The column records the steward’s responsibility ruling: not at fault, shared, or at fault.

    A solo off, a rule infraction, blocking or impeding, a mechanical failure, contact, a lost position, damage or a DNF, and reckless conduct are distinct rows. A mechanical failure is not treated as driver fault unless the steward assigns that row and responsibility. A rule infraction escalates to the consequence row when it caused contact or impeded safety workers. Blocking escalates the same way: when the blocking caused contact, cost a position, or caused damage, the steward grades that consequence instead. Blocking is graded at fault only, because the driver who was blocked is graded on whatever consequence followed.

    Damage and reckless outcomes are not discounted by session type when the grade is shared or at fault. Serious consequences should not be cheaper because they happened during practice.

    Reporting an incident we missed

    Drivers can report an incident the stewards did not catch through the report form in the Driver Toolbox. A report is logged like any other incident and graded like any other incident — with one exception. If a steward confirms that nobody had already told us about it (it was not already in the incident log, no other driver had reported it, and there was no steward or corner-worker note), the reporter’s grade on that incident is granted immunity: the incident stays on the record with its full audit trail, but its points stop charging the reporter’s rating. Immunity applies regardless of fault — a driver who caused something and told us before we knew still pays nothing for it.

    The grant is a human decision, recorded with who granted it and when. Reporting alone grants nothing: a report of an incident that was already logged, already reported, or already in an official’s notes is an admission, and it is graded normally.

    A granted immunity stands unless the report itself was dishonest. If the “nobody else had it” finding turns out to have been wrong, the grant is not clawed back — the steward who granted it judged the information available at the time. A steward can revoke an immunity, and a revocation must state its reason and is recorded with it in the same audit trail.

    Full-course yellow escalation

    A steward can mark the incident that caused a full-course yellow. The live multiplier applies only to shared and at-fault grades. Drivers who were not at fault are not escalated for being collected in someone else’s caution-causing incident.

    Exposure counts green-flag minutes. Formation, pace, out-lap, in-lap, double-yellow, and red-flag time do not count as green running.

    Advisory status

    “Driver under review” is an advisory recommendation, not an automatic suspension. The rating uses full-precision values and settled appeal state to determine its recommendation band. The sanctioning body retains final discretion over entry and sanctions.

    Ratings are cumulative and do not decay. Appeals keep affected weekends provisional until the applicable review windows close.

    See the drivers

    Review the current Safety Rating summary on each published driver profile.

    ⚡ Cached with atec Page Cache