- Step 1
Confirm the event, session, and run.
Check the team, car, race weekend, and session before entering data. Establish the run being recorded and identify the driver in its notes. Before heading out at a track with driver-specific tire inventories, check fitted tire IDs against that driver’s official eligible list. This matters even when drivers share a car.
Before moving on: Entries will belong to the car and run that actually went on track. - Step 2
Record the conditions.
Capture the track conditions and relevant event notes. Record the observations that will help explain why this session differs from the previous one.
Before moving on: Notes identify the conditions observed for this session rather than a general description of the whole day. - Step 3
Record the change before the next run.
Enter the setup or tire change made between runs, including what changed and any useful reason or observation. Keep the starting setup distinguishable from the session adjustment.
Before moving on: The record describes the change actually made on the car. - Step 4
Capture tire data and driver feedback.
Record available tire temperatures, pressures, condition, and the driver’s feedback for the run. Include when or where the behavior occurred so the note can be interpreted later.
Before moving on: The readings refer to the correct tire IDs, car, and run; the feedback identifies the driver and describes the behavior clearly. Retain notes that will help compare a new division tire across runs and follow long-serving tires across race weekends. - Step 5
Add lap times and review the result.
Record lap times with the correct session. Review them alongside the change, conditions, tire readings, and driver comments before planning the next adjustment.
Before moving on: A faster or slower lap is considered in context; it is not treated as proof that one setup change caused the result. - Step 6
Save and check the shared record.
Save the entries. When another device or crew member needs the information, check connectivity and synchronization before relying on their copy. If data looks missing, preserve the local app data and contact support.
Before moving on: The intended entries are saved and the team is reviewing the correct record.
Tech Center / At Track
At Track: keep each run in context.
Record what happened while it is fresh. The useful race record connects the car, conditions, change, feedback, and result.
Worked workflow
After the first run, record tire readings and the driver’s report of tightness late in the run. Log the adjustment made before run two. Add the next run’s lap times and feedback, then review both runs with their conditions before deciding the next step.
Common mistakes to avoid
- Running a tire outside the driver’s eligible track inventory.
- Putting a second run’s readings into the first run’s record.
- Writing “tight” without saying where in the corner or when in the run it occurred.
- Leaving changes unrecorded until the end of the day.
- Assuming another device has the latest information before checking synchronization.