A rain date turns one night's takings into three obligations at once: people who will come to the new date, people who cannot and want their money back, and people who never see the announcement. The policy has to answer all three before the weather makes you answer in public.
Most tracks already have a sound policy, printed on the entry form and the back of the ticket. The gap is rarely the wording. It is carrying it out in one pass, for everybody, in the same way, in the week when the phone starts before the rain does.
What the policy has to decide
- Whether a ticket or an entry moves automatically to the rain date, or the holder must choose
- How long they have to choose, and what the default is when they do not
- Whether a credit against a future night is offered instead of cash, and how long it lasts
- Whether competitors and spectators get the same terms, having paid very different amounts
- What happens to add-ons: paddock space, camping, crew passes, transponder hire, pre-ordered food
- Who carries the card processing cost on a refunded sale, and whether a credit avoids it
- What counts as a cancellation at all, when a programme is shortened rather than lost
That last question causes more argument than a complete washout does. A night that runs half a programme before the rain arrives is neither a cancelled event nor a delivered one, and the policy should say which before anybody has to decide on the spot.
Bulk execution is the whole thing
A blanket cash refund is the most expensive answer available, and often the one a track reaches for because it is the only one it can carry out quickly. A credit against the rain date keeps both the money and the crowd, but only if issuing it to everyone affected is one reviewed action rather than a fortnight of phone calls.
So the requirement is plain. Identify everyone holding anything against that date, spectators, competitors and add-ons alike. Offer each the options your policy allows. Record which option each took. Then show, at any point that week, who is still owed something.
Without that, the work lands on whoever answers the phone and the answers drift between the first caller and the last. Two people who bought the same ticket getting different outcomes is what turns a wet Saturday into a public argument.
The people who never see the announcement
Some find out at the gate, because nothing in a rented ticketing tool reaches a person who bought under a friend's account. Contact details recorded against the ticket, not only against the card that paid, give you a route to them. Where seats went out as a group block, reaching the buyer is not reaching the people coming.
Settle it before the season, not during it
A washed-out night is not an exception in motorsport but an ordinary part of a calendar, so the policy belongs in the system from the first race, tested on a small postponement rather than met for the first time on your biggest night.
What we would not touch
Race control, timing and scoring stay with the equipment and officials you use now. Where a sanctioning body sets the rulebook or holds the licences, that stands. Card processing stays with your processor, and its rules on how far back a refund may be made are a fact your policy lives with.
Working out the cost of the stack around it
Refund handling is rarely a line on an invoice, so start with the fees you can see: gate fees per ticket, entry fees per competitor, memberships and waivers, across a whole season, in our free software bill calculator.
Then read the guide to renting versus owning your software, which is honest about when renting is the better answer. Where it is not, Hiro rebuilds only the parts a track really uses, beside the old system until it is proven. The page on software for motorsports and race tracks sets out the detail.