Most of the answers you've gotten so far have been from large regions who
have large events, for whom it is really necessary to have a structured,
formal system if they just want to get an event done before running out of
daylight.
If yours is a small club, with event turnout usually less than 100 or so,
then you can be much more casual about it. Casual is nice, IMHO, as long as
by doing so you aren't letting the event drag.
Our Salina Region events are usually small ones. We run heats of about 8
cars at a time, usually 4, maybe 5, runs. (And our first heat gets an extra
run to entice people to sign up for it).
We let people sign up whatever heat they want to run. Classes don't matter.
Then they also sign up for one worker heat, again their choice. Out here in
the wide open spaces, people seldom can make two events in one day (the next
nearest event, if scheduled, is 90 to 120 miles away) so that is not a
consideration. People can control their own schedule, pretty much. If they
have to leave early, they sign up for early heats -- worker and driver. If
not, the tendency is to work early, run late. Actually, our heat size is
usually predicated on the number of workers needed, so if a heat has eight
drivers, there are slots for eight workers.
The biggest problem that causes us is that often we find ourselves begging
and pleading for workers for the last heat. There are always several drivers
who do not work a heat because they are working all day (event chair, safety
chief, registrar, tech chief, etc.), but with sufficient whining and
wheedling, workers happen. Autocrossers are often quite generous if their
generosity is appreciated.
There are really any number of ways to run an event -- none a wrong way, but
some that work better for YOU than others might. I've run events where
everyone makes their first run, then everyone makes their second. etc. One
variant of that was that everyone got assigned a worker heat, one of four on
the day, and you ran one run in each of the other three.
My impression is that most drivers would rather make all of their runs in a
fairly short timespan. Not back-to-back, or any system that requires them to
hurry their preparation (or go out too soon when the car is too hot), but
enough that they do not have to do full warmups on the car for each run or
spend a couple of hours downtime between each run.
One thing that always bugs me is the "that's not how WE do it" intolerance.
Anyone who goes to an event somewhere else should expect the system to be
different. The visitor must adapt to the local system, and do so graciously
and in a sportsmanlike manner.
--Rocky Entriken
-----Original Message-----
From: Larry Steckel <lorenzoscribe@hotmail.com>
To: autox@autox.team.net <autox@autox.team.net>
Date: Tuesday, April 10, 2001 10:02 AM
Subject: Event organization question.
>My local club, North Hills Sports Car Club, has always ran events in
>numerical order. Car #1 thru #100 and then start over for the second run.
>Steel Cities uses a heat system where you work a heat, sit out a heat and
>run a heat. The net result is you are at the event all day, and can have
>time to socialize and watch the other competitors. And I see that as a
>positive side of autocross.
>
>However, I know from the discussion here at Team.Net and from chatting with
>fellow cone crunchers I have met along the way that some clubs use a system
>where you come in, register, do your three or four runs and can then leave.
>So, in effect, the club is running two or three small events within the
>framework of a one day event at their lot. The competitor has some choice I
>assume as to when they come out and run.
>
>My multiple part question to y'all is; if your club runs in this fashion,
>how do you organize this type of autocross? By that I mean, do you put
stock
>cars in the morning and mods etc. in the afternoon session? Or is it a
>certain number of cars per session on a first come first served basis? Is
>Registration and Tech open all day? How do you get enough workers to
>adequately cover the stations all day? I am interested in learning the
>techniques you have found to make this type of multiple session autocross
>format work.
>
>As usual, thanks in advance for the collective wisdom of all you
>Team.Netters.
>
>Larry Steckel
>
>
>_________________________________________________________________
|