How to Build Car Show Classes Without Award-Day Arguments

Class names always look obvious to the people who wrote them. Then a restomod Camaro rolls in and one person calls it stock while somebody else sends it to modified.

Build your classes around the cars that are actually likely to show up, and write down what the fuzzy words mean. You don't need a class for every possible vehicle. You need a setup entrants can understand and your staff can explain without making up rules in the parking lot.

Classes should reflect the field

Review prior registrations or the clubs you are inviting. Build the smallest set of classes that separates meaningfully different vehicles while leaving enough entries for real competition. More trophies do not automatically create a better show.

The name is not the definition

“Modified,” “stock,” “classic,” and “truck” mean different things to different owners. Define model years, permitted modifications, vehicle types, and any documentation requirements. Include examples for likely edge cases.

Most arguments are really process problems

Tell entrants whether they select a class, staff confirm it, or a classification team assigns it. Set a deadline for challenges and name the person whose decision is final. Avoid moving a vehicle after judging begins unless the published rules require it.

Trophies put the structure to the test

Before publishing, compare expected class counts with the trophies ordered. Decide what happens to an empty class, a class with one vehicle, or an unexpectedly large class. Write down any merger or split rule.

Driven To Show groups/classes can organize registration, score views, People’s Choice ballots, judging, and trophy eligibility. Configure the groups before registration opens and test a registration in each one. The system can enforce the structure you choose; it cannot make an ambiguous class definition fair.

Reviewed and updated August 2026.