Race morning checklist

Print this page and keep it with you. It assumes the event, the schedule, and the entry list already exist.

It is written for a club that grids one day at a time. If your club prints the whole weekend at once, the blocks below still apply; you run the grid block once instead of each morning. Which grids to publish covers the choice.

Before the first session

1. Open Event → Overview. Read what it says is missing.
2. Check every race has classes. Fix on Event → Races.
3. Check every class has entries. Fix on Event → Entries.
4. Check every race points at its qualifying session. Fix on Event → Races.
5. Open Event → Entries and choose Update Registrations.
6. Print the schedule and post it.

After each qualifying session

1. Upload the timing file against that session, on Event → Schedule.
2. Open the stored classification and check the rider count looks right.
3. Fix any rider sitting in no class, on Event → Entries.

Before the first race

1. Open Event → Grids and choose Review Ready Grids.
2. Choose Today Only or Select All. See below.
3. Read the before and after for every race. Look at who moved.
4. Leave any waiting race unselected. It names the session it is missing.
5. Publish.
6. Print all grids from the event page and post them.

Which grids to publish

Clubs do this two ways, and Race Control supports both from the same screen. The review header carries Select All, Today Only, and Clear, with a running count of how many races are selected.

One day at a time. Publish only today races each morning. Choose Today Only. This is what WMRRA and CVMA do.

The whole weekend at once. Qualify on Saturday morning, publish everything, print it all. Choose Select All. A club that runs no qualifying works this way too, gridding from championship points or registration order. There is nothing to wait for.

After each race

1. Upload the race timing against its race session.
2. Check the finishing order on the public page.
3. Record any protest ruling on Event → Races, with its reason.

A late registration arrives

Expect this. Riders enter on the day, and they keep entering after the day has started. What to do depends only on what has already run.

Before that rider qualifying session. Choose Update Registrations on Event → Entries. Carry on as normal. They qualify with everyone else.

After qualifying, before their race. Choose Update Registrations. The new rider has no qualifying lap, so the grid places them by the next criterion, behind every rider who set one. That is correct, and it is the same rule that places a rider who crashed in qualifying.

Then open Event → Grids, read the before and after for the affected races, and publish. Print the new grid and post it. Say the revision number out loud, because every printed copy already on the board is now out of date.

After their race has already run. Nothing you do changes that race. Results are a separate record from the grid, and a rider who was not entered did not start. Update the entry so their remaining races are right.

When something is wrong

A grid is missing riders. Those riders have no entry in a class this race runs. Fix on Event → Entries, then review the update on Event → Grids.

A grid put the wrong rider on pole. Check the race points at the right qualifying session. Then check the qualifying groupA label that says which classes one bike can plausibly race. A rider's qualifying lap carries to their other entries in the same qualifying group. labels on those classes.

A rider has no lap time on the grid. They set no lap in the qualifying session that feeds this class. The next criterion placed them. This is normal for a rider who crashed.

A published grid needs changing. Change the data, then review the update and publish a new revision. Tell the riders the revision number.

What Race Control will not do

It will not regrid a published race on its own. It will not add a rider to a race because they appeared in timing. It will not decide a protest.