STEWARDS
ROOM
INDEPENDENT
RACING STEWARDSHIP
Orange and white GT race cars on a dark circuit
THE INDEPENDENT STEWARDS ROOMPOST-RACE / ON RECORD

LESS ADMIN.
BETTER REPORTS.
CLEARER DECISIONS.

Built to reduce steward hours, from report to ruling.
Keep clips, accounts and rules together. Spend less time assembling cases and explaining decisions again.

Try with a clipSee a real reviewFree to use · No league setup required · Unsaved cases expire after 14 days
EVIDENCE · REASONS · DECISIONS
EVIDENCE IN. REASONED VERDICT OUT.
SEE THE RESULT BEFORE YOU START

A CLEAR REPORT.
A REASONED RULING.

Get from incident to decision with less chasing, a consistent review and a report that shows how the ruling was reached.

  1. Bring the evidence.
  2. Review it against your rules.
  3. Record the decision and reasons.
Read the real review
REAL REVIEW / SVR 438

Chicane-entry contact.

lyly / SenorDude · 22 September 2026

Incident
lyly closed from behind during braking and made contact with SenorDude’s rear.
Evidence
Evidence reviewed: both drivers’ replays and the replay damage displays.
Finding
Recorded finding: avoidable rear contact by lyly, supported by the replay evidence.
Recommendation
10-second time penalty + 2 licence points for lyly.
01 — LESS WORKKEEP THE CASE TOGETHER.

LESS WORK.
BETTER REPORTS.

Less chasing. Less assembling. Less explaining the same ruling twice.

Evidence, accounts, rule references and reasoning stay together. A consistent report structure helps your stewards record a clear decision without rebuilding the case each time.

Less admin

Keep evidence and accounts in one case.

Less assembling

Reduce the work around each review.

Traceable findings

Report the sources, limits and reasons.

Less repeat work

Revisit the report instead of rebuilding the explanation.

02 / FROM CLIP TO CASELESS WORK AT EVERY STEP

FROM INCIDENT
TO DECISION.

One place for the evidence.
A clear record of the outcome.

  1. 01

    Submit.

    Start with the incident.

    Add clips, name the drivers and give your account. For league cases, the evidence window runs from the original submission time using the league’s chosen duration.

  2. 02

    Collect.

    Build the evidence before the deadline.

    Invite the other drivers to add their viewpoints. Participants can see the uploaded evidence; each driver’s statements stay private to that driver and the stewards.

  3. 03

    Prepare.

    Racecraft Engine.

    Request a review of accounts, rules and selected images or sampled frames. Findings link back to evidence, with missing information and replay uncertainty visible for the steward to check.

  4. 04

    Decide.

    The evidence drives the verdict.

    Once all drivers are ready or the evidence window closes, AI checks the imagery and runs the selected rule tree. A supported path delivers the verdict and reasons; unresolved facts request evidence or exception review.

THE EVIDENCE. THE REASONS. THE RECORD.See the real review
03 — EVIDENCE FIRSTFAIRNESS STARTS WITH THE FACTS.

FOLLOW THE DATA.
CHECK THE EVIDENCE.

EVIDENCE BEFORE CONCLUSIONS.

Compare independent views, keep driver claims separate from findings, and apply the relevant rules consistently.

Record missing angles, conflicting accounts and connection discrepancies so uncertainty stays visible.

WHEN A RELIABLE FINDING ISN’T POSSIBLE:INSUFFICIENT
EVIDENCE.

A fast review still needs a supported conclusion.

04 — THE REPORTTHE REASONS ON RECORD.

THE FINDING.
AND ITS REASONS.

Know what supports the decision—and what the evidence cannot establish.

  • Traceable sources and visible limitations.
  • Facts distinguished from driver claims.
  • The rule breached and the evidence supporting the finding.
  • A clear explanation of the verdict and any penalty.

Keep the explanation with the case so your team can revisit it without rebuilding the discussion.

05 — THE VERDICTEVIDENCE BEFORE CLAIMS.

EVIDENCE REVIEWED.
VERDICT DELIVERED.

The AI establishes supported facts and runs the selected rule tree.

Drivers submit their evidence and accounts. When everyone is ready or the response window closes, the case proceeds to AI review. Missing evidence prompts a request; supported paths deliver a reasoned verdict. Exceptions and appeals stay on record.

EVIDENCE FIRST.VISIBLE REASONING.
06 — YOUR LEAGUEFITS AROUND YOUR WORKFLOW.

FROM A DRIVER’S
CLIP TO A
REASONED VERDICT.

Start with a private incident case. Save it to your account, then invite your organiser to bring it into a league for formal review. The selected rule profile stays with the case and its appeals.

League admins

Cut the chasing and assembling. Bring evidence, people and review deadlines into one case.

Stewards

Handle exceptions and disputes with the evidence and reasons already assembled.

Drivers

Submit evidence and your account, then see how the decision was reached.

FREE TO USE · NO LEAGUE SETUP REQUIRED · UNSAVED CASES EXPIRE AFTER 14 DAYS

LESS WORK. BETTER REPORTS.

Try a clearer way to handle your next incident.

Try with a clip