Current driver-facing guides.

These are the public or driver-facing documents surfaced by the EFVD guides. Use the current version only.

Start here

New Driver Get Started Guide

Intro to EFVD, the application flow, and the first steps for a new driver.

Competition

Competition Guide

Event rules, qualifying, battles, restart procedure, DNF, DQ and judging basics.

Technical

Technical Regulations

Vehicle eligibility, livery rules, file structure, optimization and submission standards.

Conduct

Code of Conduct

Community expectations, staff interaction, sponsor protection and disciplinary process.

Progression

License Program Guide

How the license works, what it unlocks, and how reviews, probation and removal happen.

Applications

Applicant Application Guide

How drivers apply, how selections happen, and what happens after selection.

Judging

Judging Guide

Qualification, battles, collision calls, restarts, OMT and decision standards.

Appeals

Protest and Appeal Guide

Private evidence-based review process for decisions, protests and appeals.

Media

Social Media and Content Guide

How EFVD presents itself, which content pillars to use, and how to keep the brand consistent.

Public info

Public FAQ

Fast answers for new drivers, viewers and returning competitors.

Partners

Sponsor Deck

Partner-facing overview of the series, audience, event model and exposure inventory.

Keep these off the public nav.

Staff operations and forms

The Staff Operations Guide, Forms Package, and Post Event Report Template are operational documents. They support the team, but they do not belong in the public document hub.

Internal review material

License review sheets, internal staff notes, and private event reports stay private by design. That keeps the site clean and protects working process.

Handbook context

The broader Competition Handbook is an internal framework. The public site surfaces the driver-facing guides instead of the full operations stack.

One current version per document.

  • Use the guide pages linked on this page.
  • Do not surface internal staff docs in public navigation.
  • Keep public copy short, direct, and easy to scan.
  • When the season changes, update the hub before the rest of the site.