1. Understand the two parts

RaceControl is a separate subscription from the private SCP setup workspace. New tracks currently receive guided assignment and activation. Arrange that setup before depending on the application for an event.

2. Download, install and verify your track

1. Sign in to My Account using the account assigned to the subscribed track. If no download is offered, ask support to check your track assignment and subscription.
2. Download the Windows subscriber ZIP. Extract the entire ZIP to a folder you can keep; do not run it inside the compressed ZIP.
3. Open Start Race Control.cmd. On first launch, choose Laptop only or Enable Wi-Fi. Follow any Windows administrator prompt for optional direct Wi-Fi access. If permission is cancelled, use Laptop only and retry Wi-Fi setup later.
4. Set up the local organizer and track credentials as prompted. The organizer password unlocks local management; the website account verifies subscription access. These are separate sign-ins.
5. Open Local Home from RaceControl settings. Under Backups & publishing → Offline licence import, find this laptop’s installation ID.
6. In your website account, select your track and use that installation ID to download its signed licence. Return to the laptop and choose Import licence.
7. With support during initial activation, configure the website connection for that same track. Keep the private track publishing token private. Save the connection and use Refresh licence while online.

Two activated laptops are supported per subscribed track. Each track has its own connection, licence and publication receipt. Select the correct saved track connection before publishing. If your subscription lapses, renew and refresh the licence before running new events; keep backups and use the retained event/export access for recovery.

Do this rehearsal before race day: launch the app, unlock Organizer, verify the licence, create a practice event locally, publish its information and scan the website QR codes from a phone. Do not overwrite a real event for testing.

3. Prepare your event

1. Open the main RaceControl application and sign in to the appropriate track.
2. Create or select the event. Check its name, date and track, then add/select the racing classes.
3. Review the competitor list, car numbers, driver details and the rules/settings for that event.
4. In Local Home, select the same track connection and choose Backups & publishing → Publish public snapshots.
5. Confirm that publication succeeded. Open the public and registration links for each class before sharing them.

Publish each event at least once before sharing its website QR codes. A QR code cannot create an event that has never been published.

4. Registration and verified check-in

Before the event

Share the Registration website QR. Drivers can submit while the race laptop is offline. Public competitor lists can show entries marked pending review; those entries still need organizer review.

1. Reconnect the laptop and unlock Local Home.
2. Open Online entries → Download new entries.
3. Review each entry. Add a new competitor or link it to the correct existing local competitor. Linking preserves existing local check-in and points data.
4. If a website acknowledgement failed, use Retry website acknowledgements. Review reported conflicts rather than repeatedly creating duplicate competitors.

At the track

The driver Check-In QR sends an arrival request. Staff must verify the driver and complete official check-in on the race laptop. An online arrival request does not automatically mark someone present or clear their eligibility.

Which QR should I share?

All event QR codes should start with https://sprintcarpro.com/. Replace old printed codes that use 127.0.0.1, localhost or a laptop IP. A phone does not need to share the laptop’s Wi-Fi to open website QR pages.

5. Run the race and publish progress

1. Verify the competitor list and official check-ins before building lineups.
2. Work through the event’s Time-ins → Heats → Mains → Points stages. Check the selected class before entering results or changing lineups.
3. Save results and verify finishing order, status and points against your official records.
4. Publish public snapshots after changes that drivers, fans or announcers need to see.
5. Open a public page on a phone and confirm the latest published stage and results.

Public and announcer views follow Registered → Time-ins → Heats → Mains → Points and refresh about every 30 seconds. Refreshing cannot reveal results that have not been published. A successful website publication needs an internet connection on the laptop.

If internet fails during racing, continue permitted local operations and publish after reconnecting. Clearly tell the announcer and officials that the website may be behind the laptop. This edition’s snapshot publishing is not an automatic live transponder timing feed.

Optional direct Wi-Fi access

For staff who need supported live laptop controls, use Wi-Fi setup in Local Home and approve Windows. The devices must share the laptop’s Wi-Fi and the laptop must remain on. Use the displayed local address; do not share that address as the permanent public event link.

6. Invite other tracks to host a series race

1. On the website, open My Account → Race series and host invitations.
2. Create a named series, choose its season and a class from your published races.
3. Invite a registered host track. Select the proposed race date and name; use Add another race for more dates in the same invitation.
4. Repeat for additional host tracks. The series is not limited to two tracks.
5. Each host signs in with its own assigned website account and accepts or declines. The organizing track can cancel pending invitations.
6. Each accepted host connects its own published event to its scheduled race.
7. On the laptop, choose Series setup → Download accepted series policies, then review eligible completed event results before approval.
8. Publish the approved event information and verify the combined standings on the public series page.

Only accepted, connected events can contribute through the host-invitation workflow. Keep driver identities consistent across tracks and review mappings before approving points. Invitations appear in My Account; automatic invitation email is not enabled, so tell the host to check its account.

7. Back up and update the laptop

1. Open Local Home → Backups & publishing → Download backup.
2. Keep a copy on another drive or storage destination, particularly before upgrades and after an event.
3. Keep the entire RaceControl data folder when upgrading the installed app. Do not replace it with a clean subscriber package’s empty data folder.

Full backups include local tracks, events, series mappings, approvals and their history. Passwords and website credentials are excluded; store those securely and separately. Automatic previous versions inside the laptop’s data/backups folder do not protect against loss of the laptop.

Import existing data accepts a matching v2 track backup without overwriting existing events. A full local backup can be restored only into an empty installation; ask for assistance rather than importing over a working race installation. Verify event counts and recent results after recovery.

Published website snapshots are not a substitute for a full operational backup. Automatic Google Drive backup is not configured.

8. Troubleshooting

Contact cybersofracing@gmail.com with the track/event/class, app page and exact error. Do not email organizer passwords, signed licence files or private publishing tokens.

Updated 11 October 2026. Use your browser’s Print command to save this manual as a PDF.