1. 01Issue
  2. 02Evidence
  3. 03Private Ticket
  4. 04Staff Review
  5. 05Decision

Purpose and Boundaries

The protest and appeal process gives drivers a structured way to raise serious issues with evidence.

Boundaries

Know what belongs

Use protests for reviewable technical, conduct or administrative issues.

Evidence

Bring facts

Staff needs clear information, not vague frustration.

Process

Keep it private

The correct channel protects the event and everyone involved.

What Can Be Submitted

Use the protest process for issues that can be reviewed with rules, evidence and event context. Judging decisions themselves are final and are not protested; if a driver wants an explanation, they may submit a private post-event clarification request.

Can be submittedExample
Technical concernA car may not match EFVD technical requirements.
Conduct complaintHarassment, threats, retaliation or serious event behavior.
Administrative issueRoster, bracket, result entry or process error.
Disciplinary appealA driver requests review of a conduct or eligibility decision.
Judging explanation requestA private request for explanation after the event, not a live challenge to the call.

What Cannot Be Protested

The protest process is not for every disagreement. Decisions cannot be protested when the issue is a judging call, including disagreement about a judge's objective read of a run. Drivers may still ask for a private explanation after the event if they want to understand a call better.

Not for protestWhy
Personal dislike of a judging callJudges have live authority over run evaluation.
Objective judging disagreementJudge interpretation and live run evaluation remain final for the event.
Public drama threadPublic pressure makes fair review harder.
No evidenceStaff cannot review vague claims or frustration alone.
Closed final decisionRepeated escalation after closure may become a conduct issue.
Live arguing with judges or staffLive event flow must stay clear and controlled.

Submission Deadlines

Deadlines protect event flow and make sure evidence is still available when staff reviews the issue.

Submit quickly

Do not wait

Use the announced deadline for that event or the issue may not be reviewed. If no event-specific deadline is posted, submit within 24 hours after the event ends.

Use the right channel

Keep it private

Submit through the announced ticket or staff process.

Include context

Make review possible

Late reports need clear timestamps, replay references or message context.

Evidence Requirements

Good evidence lets staff review the issue without relying on public pressure or incomplete context.

Replay or video

Show the incident

Use replay files, stream clips or recordings when available. Avoid cropped clips that remove important context.

Timestamps

Point to the moment

Include exact times, run numbers, battle names or message links.

Explanation

State the rule concern

Keep the description short, factual and connected to the rule or issue.

Protest Flow

Protests and appeals are handled privately so staff can review evidence without public pressure or event disruption.

  1. 01

    Submit privately

    Use the announced staff channel or ticket process.

  2. 02

    Provide evidence

    Include replay, screenshots, timestamps or relevant context.

  3. 03

    Staff review

    Authorized staff reviews the issue and applicable rule.

  4. 04

    Outcome

    Staff communicates the result and closes the matter when final.

Review Authority

Only authorized EFVD staff can decide how a protest is reviewed, who is involved and what information is shared.

Reviewer

Assigned by EFVD

Drivers do not choose the reviewer or pressure specific staff members.

Scope

Evidence-based

Staff may limit the review to the submitted issue and available evidence.

Privacy

Controlled process

Private reports, internal discussion and sensitive evidence may remain confidential.

Possible Outcomes

A review can confirm the original decision, correct an administrative issue where staff chooses to do so or create a separate conduct or technical action. EFVD staff reserve the right to edit results, brackets or standings, but there is no obligation or guarantee.

OutcomeMeaning
No changeThe original decision or result stands.
CorrectionA clerical, roster, bracket or technical process issue may be corrected at staff discretion.
Penalty or restrictionA conduct, technical or procedure issue creates an event action.
Further reviewStaff needs more evidence or leadership review before closure.

Anti-Drama Rules

The protest system exists to solve issues, not to create public pressure campaigns.

Private

Use official channels

Do not turn a protest into a public argument.

Respectful

Stay factual

Insults, threats or harassment can create conduct action.

Final

Accept closure

Once staff closes a review, continued escalation may be treated separately.

Policy Changes

EFVD may modify this guide when needed to support sustainability, fairness and the continued growth of the championship.

Read next.

These pages fill in the rest of the EFVD process without repeating the same explanation here.