Saved instantly. Sent once. Live everywhere.
The phone works from its own store, so screens open and saves land instantly with or without signal. Changes wait in the send queue until the phone is back online, then go to the cloud once each. Changes made elsewhere come back within seconds.
Most of the time you'll never notice any of this.
A small status pill appears only when something needs your attention. Tap it for a plain-English list of what's waiting, with Sync now and Retry buttons.
RaceCloud copies your working data onto your phone: baselines, drivers, journal and event entries, this season’s events, championships and calendar, the full track directory and the class list.
So they open instantly, signal or not.
The change is stored on the phone immediately and joins a send queue. The queue survives the app being closed, a crash, or a restart.
It knows when you’re on Wi-Fi with no internet behind it.
With the app open, oldest first. Every change carries its own ID, so nothing is ever sent twice. Failed sends are retried with a slightly longer gap each time.
So syncing is quick even on weak signal. An interrupted download carries on where it stopped.
It compares the phone’s copy with the cloud and quietly repairs any gaps.
What works with no signal.
The most recent edit wins.
Race-day sessions save each part separately: the details, the pacesetter, the conditions, the weather, and each driver's setup and debrief. A mechanic logging pressures and a driver writing their debrief on another phone don't overwrite each other.
Web to phone in seconds.
Changes made on the web reach the phone within seconds while the app is open. The Paddock is live, race-day weather refreshes itself, and permission changes apply without signing out.
Open the app on good signal before you travel.
That's all the preparation it needs. Your baselines, drivers, this season's events and the track directory are already on the phone.