MotorsportReg.com : click to return home
 

Contents

Double Race With Enduro, PDX, Worker Reg, And Banquet

This event recipe is designed for a full-boat style competitive event with many options.

Secret Sauce

The Double Race With Enduro, PDX, Worker Reg, And Banquet has a selection of segments to reflect the different combinations of participants, a wide range of race classes, and a selection of order form items, often grouped, to choose from.

Configuration

This event is based on the Double Race recipe. Changes to the basic setup are listed below.

Club Profile

Classes should be created that reflect all race classes, all enduro classes, and any PDX run groups needed. Worker specialties should also be created in the Classes list. These classes can be enabled/disabled on a per-segment basis as necessary.

General

  • Basic Settings - set the event beginning and end dates as appropriate.

Segments

This event requires a segment for every individual entry option, typically:

  • Saturday Race
  • Sunday Race
  • PDX/HPDE
  • Enduro
  • Workers

Classes should be enabled/disabled for each segment as appropriate. If Permanent Numbers are to be used for the race segments, choose a Number Pool for each as appropriate. You may map classes to groups to reflect race groups as appropriate. A Banquet segment is optional and only useful if you want to publish a list of banquet attendees.

Registration Form

  • Packages/Inventory - You will need a Race Entry package for the main races, each with associated inventory items, as well as packages for the Enduro and the PDX. The Worker signup will require a $0 package as well. You may opt for additional variants of these packages to handle non-member pricing, early bird pricing, etc. You may want to consider a package for each banquet menu option, each with its own inventory item, to make it easy to get caterer counts for each menu option.
    • The separate Enduro package is important, as racers may be signing up to race the Enduro as part of another entry (i.e. they are a second driver). You should probably create a Primary Driver Name question to nest under the Enduro entry so you can match secondary drivers with their teams.
    • Since the Enduro is usually an additional race on top of the main race, you probably don't want to put those packages in a Group as that would make them mutually exclusive.
  • Assigners - You will need an assigner for each race entry that requests car/class/group/number information. Each assigner should be nested under the appropriate entry package. The PDX assigner is similar. The Worker assigner should ask for Class only, to allow workers to select a specialty.
    • Generally you would not create a specific assigner for a Race+Enduro entry package that creates assignments in both the race and enduro segments, as people may not be running the same car in both events.
    • If you would like to publish an attendee list for the banquet, create a Banquet assigner that collects no information (i.e. is invisible) and place it somewhere on the order form where it will be triggered by selecting a banquet option.