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

Purpose and Boundaries

The Live Battle Protest process lets a driver who competed in a disputed battle request review of a specific, evidence-supported claim of a clear and material error.

Standing

You drove the battle

Only a driver who competed in the disputed battle may submit its protest.

Evidence

Bring facts

Staff needs clear information, not vague frustration.

Process

Keep it private

The correct channel protects the event and everyone involved.

Choose the Correct Process

Use the process that matches the outcome you want. A clarification requests an explanation. A protest asks EFVD to review an eligible battle result.

ProcessWhen to use it
Objective live-battle protestA verifiable fact, mandatory procedure or automatic rule, such as the wrong driver advancing, incorrect lead/chase order, wrong run count, confirmed start/server failure or result-entry error.
Subjective live-battle protestA specific, material incident involving application of criteria such as contact responsibility, chaseability, legal passing, mistake severity, line, angle or proximity.
Uncertain live-battle protestThe driver can identify the incident and material effect but is unsure how to classify it. Event Ops may reclassify it.
Competition QuestionA qualifying name, score-entry, calculation or system error reported before qualifying results and the bracket are locked. The run is not rescored.
Judging ClarificationAn explanation of how published judging criteria applied to the driver's own qualifying run or battle. It does not request a result change.
Staff report or disciplinary appealChoose Contact Staff → Conduct or Safety. For an appeal, enter Disciplinary appeal as the subject.
Administrative reviewChoose Contact Staff → EFVD Competition → Competition Question and clearly identify the decision or correction being reviewed.

How to request a Judging Clarification

After the event, choose Contact Staff → EFVD Competition → Competition Question in Discord. Enter Judging clarification as the subject. Identify the event, your run or battle, and the specific call or criterion you want explained.

A clarification is informational. It does not reopen, rescore or rejudge the run or battle, and it cannot change the result. EFVD is not required to review replay or other evidence.

Staff decides whether, when and how to respond. Internal votes, deliberations, notes and private evidence may remain confidential.

A clarification does not replace a Live Battle Protest or pause or extend its deadline. A driver seeking a battle-result correction must use the protest process when eligible.

What Cannot Be Protested

A protest is not a second judge vote or a way to re-argue the whole battle. A subjective submission must identify a specific incident, the relevant judging principle, supporting evidence and a material connection to the result. Event Ops decides admissibility.

Not for protestWhy
Driver did not compete in the battleOnly a driver from the disputed battle has standing to submit its protest.
General disagreement or judging preferenceDissatisfaction without a defined, material incident is inadmissible.
Qualifying score or judge interpretationQualifying is not part of the battle-protest flow. A Competition Question may correct an objective entry or system error. A Judging Clarification may explain the criteria, but neither route rescores the run.
Decision to call OMTAn OMT call itself cannot be protested.
Original runs after an OMTOnly the completed OMT runs may support a protest of the final winner, and subjective review cannot create another OMT.
Locked bracket stage, duplicate or unsupported claimLate, duplicated, incomplete, outside-scope or unsupported submissions may be inadmissible.

Submission Deadlines

Event Ops applies the deadline announced for the event. When no deposit is required, creating the private ticket officially submits the protest. After three prior protests have been resolved as Inadmissible, the next protest remains a draft until its $5 CAD Stripe deposit is verified.

Requesting a Judging Clarification does not pause or extend the Live Battle Protest deadline.

Submit quickly

Use the event deadline

Open the private ticket and complete every structured answer before the announced deadline.

Submission time

Ticket or payment verification

The ticket creation time counts when no deposit is required. When a deposit is required, successful Stripe verification records the official submission time.

Payment failure

Notify Event Ops immediately

If a required payment fails, report it in the open draft ticket. Event Ops records the Discord message timestamp and determines whether the event deadline was met.

Evidence Requirements

The driver must identify the disputed battle and opponent, relevant run, specific incident, rule or judging principle, course location or approximate timestamp, material effect and supporting evidence or a precise reference to official evidence.

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.

Material effect

Connect evidence to the result

Explain how the identified issue affected, or could reasonably have affected, the winner, a mandatory procedure, run validity or bracket advancement.

Protest Flow

Live battle protests are handled privately through the Discord Contact Staff panel. One active protest ticket is permitted per driver, and all grounds from the disputed battle must be included in that ticket.

  1. 01

    Open the private route

    Choose EFVD Competition, then Live Battle Protest in Contact Staff.

  2. 02

    Confirm and classify

    Confirm standing and restrictions, then choose Objective, Subjective or Uncertain.

  3. 03

    Complete and submit

    Answer the structured questions. If you have fewer than three prior Inadmissible outcomes, creating the private ticket officially submits the protest.

  4. 04

    Deposit when required

    After three prior Inadmissible outcomes, use the ticket-bound Stripe link for exactly $5 CAD and select Check Payment. EFVD adds no processing fee.

  5. 05

    Event Ops review

    After the ticket or required payment verification officially submits the protest, Event Ops decides standing, timeliness, scope, admissibility and outcome in the same ticket.

Review Authority

The announced winner remains unless EFVD confirms a clear and material error. Event Ops decides how the protest is reviewed, who is involved, what information is shared and whether a competition correction is required.

A clarification response does not change the announced winner. EFVD may make a separate correction under the authority described in the Competition Guide.

Admissibility

Owned by Event Ops

Event Ops checks standing, deadline, completeness, scope, any required payment and the identified incident.

Review

Assigned by EFVD

Appropriate judges or officials may review the claim. The driver does not participate in deliberations.

After OMT

Final-run boundary

Only completed OMT runs may support a protest of the final winner; original runs stay closed and subjective review cannot create another OMT.

Possible Outcomes

Only protests officially resolved as Inadmissible count toward the deposit threshold. Denied, Partially Upheld, Upheld and Unable to Review outcomes do not count. After three prior Inadmissible outcomes on the driver's Discord account, each later protest requires a refundable $5 CAD deposit before submission. The count carries across events.

The deposit is not a filing fee. When a deposit is required and collected, the official outcome fixes its action as shown below.

Official outcomeCompetition meaningDeposit
InadmissibleThe submission lacks standing, is late, incomplete, unsupported, duplicated, outside scope or otherwise cannot be accepted. This is the only outcome that counts toward the threshold.If collected, retained
DeniedThe reviewed claim does not establish a material error; the announced result stands. This outcome does not count toward the threshold.If collected, retained
Partially UpheldEFVD confirms part of the material claim and records any competition effect.If collected, exactly $5 CAD refunded
UpheldEFVD confirms a material error and records any result, bracket or other competition effect.If collected, exactly $5 CAD refunded
Unable to ReviewAn EFVD system failure makes review impossible.If collected, exactly $5 CAD refunded

If no deposit was required, there is nothing to refund or retain. A confirmed material error receives any collected deposit back even when the winner does not change. A protest withdrawn after review starts retains any collected deposit. Refunds are initiated through Stripe to the original payment method; allow up to 14 business days for an issued refund to appear.

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

Last updated: August 12, 2026. This guide remains effective until EFVD changes it; it does not expire at the end of a season. Staff announce material rule changes through the official EFVD Discord.

Read next.

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