Track Days

Track Days is where you plan, log, and review everything that happens at the track. Each track day is a container for one or more sessions, capturing the date, track, weather, schedule, and notes in one place. Navigate to My Track Days in the sidebar to see your upcoming events, with readiness and checklist progress, and every day you've logged.

Page layout

My Track Days opens on what is ahead, then everything you have driven:

1. Header -- Browse events opens the Events catalog, and Add a track day logs one. The ⋯ menu holds Import schedule, Upload telemetry, Connect RaceBox, Telemetry sessions, and Reports.
2. Upcoming -- One card per registered or planned day: the date, the track, and the days, organizer, run group, and car ("Sat–Sun · Chin Track Days · Advanced · Silver"). Below that, Readiness N / 5 (yellow while something is due) and the event's prep checklist progress, with Open checklist taking you to that list on the Checklists page. A weekend stays here until its last day ends. The page shows the next six; Show all N upcoming opens the rest in place.
3. Past -- A table for each year, newest first: date, track, organizer, car, sessions, and best lap. The best lap is teal when that day beat your earlier best at the same track. Analysis opens the day's saved telemetry; days without any say No telemetry. Click a row to open the day.

Delete, re-enroll, and per-day telemetry upload live on each day's own page.

If you don't have any track days yet, the page shows a Ready to hit the track prompt with Import schedule and Add a track day.

You can also drop a telemetry file anywhere on the page to match it to one of your track days.

Track history by venue

When a track day is linked to a saved track, TrackOut can show a Year-at-Track view for that venue. This page shows your session history at the track with filters for year, car, temperature band, and track condition.

Use the sortable table to compare:

• Date and car
• Run group
• Conditions and temperature
• Best lap
• Delta versus your personal best at that track

Filter and sort choices are stored in the URL, so you can bookmark or share a specific view.

If two or more selected sessions have telemetry or video, an Overlay action appears. Full multi-session comparison is coming soon -- for now it opens the first selected session in analysis.

Adding a track day

Click Add a track day in the top-right corner to create a new track day. The dialog highlights the core event details first, then lets you add optional context before saving. If you have logged track days before, a Recent tracks row appears under the track search so you can quickly reuse a track you visit often.

The form asks for:

• Car -- Optional. Select which car you are taking to the track. You can leave this blank and assign a car later from the track day's detail page.
• Date -- The date of the track day.
• Track -- Search for a saved track or pick from recent tracks. If your venue isn't in the track list -- a private club circuit, an autocross lot -- type its name and choose Use “<name>” as a custom venue.
• Configuration -- The track layout you ran, such as "Full Course" or "East Loop." The list shows the track's catalog layouts plus any configuration you have logged there before; choose Other... to type one that isn't listed. For a custom venue, or a track with nothing on file yet, type the configuration in yourself. Editing a track day uses the same list, and changing its track clears the old configuration.
• Run group -- Optional. Record your assigned group, class, or run order for the day.
• Organizer -- Optional. Note who is running the event, such as an HPDE club, school, or racing organization. Pick from the list, or choose Other... and type the name for a club that isn't on it. The organizer you enter shows in the day's header and on the Next Track Day card.
• Description -- Optional event description.
• Notes -- Any pre-event notes or reminders.

Saved venues can be categorized as Motocross, Offroad, or Other, as well as road courses and the other track types. Their category is kept when reference layouts are added; a motocross or offroad venue is not relabeled as a road course. Hidden draft venues and layouts do not appear in the public catalog until they are enabled and published.

Importing a schedule

If your track day organizer provides a PDF or image of the daily schedule, you can import it using the AI-powered schedule importer.

1. Choose Import schedule from the ⋯ menu on My Track Days (or Upload schedule on a day's page).
2. Upload a PDF or image of the event schedule.
3. The AI extracts the track name, date, and individual run group sessions.
4. Select which run groups apply to you.
5. Review the extracted schedule and confirm. The review lists the sessions it will create, grouped under each day when the schedule covers a weekend. Gates, the drivers' meeting, and lunch come across as day-log entries, not sessions.

If a row's time or date couldn't be read, it's marked in yellow with a Fix button. Enter the time (and the date, if the whole day was missing one) and it imports with the rest. Rows you don't fix are left out; everything else still imports.

You can import a schedule after you've already logged sessions. TrackOut matches each schedule row to a session already on that day -- one starting within 15 minutes of the printed time, or, for a session with no start time, the one in the same position that day -- and updates its planned times instead of creating a duplicate. Completed sessions keep their times. Rows that don't match become new planned sessions.

The importer creates a new track day pre-filled with the extracted data, including session times and run group information stored as schedule data. When you import from a car's track-days view, TrackOut also creates draft sessions for each planned run so the day plan timeline is ready to complete after you get on track.

Once a schedule is uploaded, it powers the run-time list in the pre-flight quick view and the timeline on the detail page.

When TrackOut can identify the organizer, run groups from the uploaded schedule can be remembered for that organization. The next time you edit your driver profile for the same organizer, those learned run groups appear alongside built-in choices like Instructor and Free Form.

If a track day already exists for the same date, you will be asked whether to update the existing track day with the schedule data or create a new one.

Track day detail page

Click any track day row to open its detail page. The detail page is built around the day itself rather than a flat tab strip -- you'll see a header, an optional day-tabs strip for multi-day events, an at-a-glance stats band, and a two-column main area with your plan on the left and a context rail on the right.

Header

A back arrow at the top-left labeled Track days returns you to the list. To the right are two actions:

• Upload schedule -- Opens the schedule importer for this day.
• More menu -- Re-enroll (only when you withdrew and the event is still on), Edit Track Day, and Delete Track Day.

Ask Crew Chief still lives in the context rail on the right and in the global Crew Chief button -- it is not duplicated in this header.

The headline card below shows:

• Status pill -- Upcoming, Live · Day in progress (with a pulsing dot when today falls inside the event window), or Completed.
• Registration status pill -- Green, amber, or red by registration state, when the day is linked to an MSR registration.
• MotorsportReg badge -- Logo + external-link icon, opens the original event listing.
• Track name and event name, optional event description, full date (or date range for multi-day events), organizer, run-group label, and venue address.
• Layout badge -- The specific configuration (e.g., "Full Course") with direction and length when known.
• Assigned car -- The selected car appears as a badge. Use Assign car when none is set, or Change to reassign or clear it.

Reporting a track data problem

Track names, layouts, lengths, turn counts, and direction come from a shared catalog that every driver sees, so you cannot edit them yourself. When something looks wrong -- a layout listed as clockwise that runs the other way, a length that does not match the timing sheet -- use Suggest a correction.

You will find it on the layout line in the track day header, and on the public track pages in TrackOut -- both for the track itself and for the layout you have selected. The dialog opens pre-filled with the track, the layout, and the value we currently have; pick which field is wrong, enter what it should be, and add a note if there is context worth passing on.

Assigning or changing the car

Use the car picker in the detail header to assign, change, or unassign the car for a track day. For MotorsportReg-linked days, the same choice updates the connected registration, so the track day and its event stay in sync. If you have already confirmed Your days on a multi-day event, changing the car keeps that selection -- the day does not expand back to the organizer's full weekend. Close the day and four-corner readings then file on the new car's own log, not the previous car's.

If a track day has no car assigned, the empty Day plan replaces the disabled session action with Assign car. Once a car is selected, you can start adding sessions and setup notes for that vehicle.

Day tabs (multi-day events only)

Multi-day events get a strip of tabs immediately below the header -- one per day, labeled with day-of-week and date. Today's tab gets a primary dot indicator. Switching tabs scopes the forecast, plan, log, and stats below to that day. Single-day events skip this strip entirely.

Stats band

A row of stat tiles summarizes the focused day:

On a multi-day event the tiles follow the selected day tab: Sunday sessions counts only that day's sessions (numbering restarts each day, as the paddock announces it), with the weekend roll-up beneath it -- for example Weekend 4/8 · 41 laps. The laps tile counts the selected day, and the primary button names the next session to log, such as Log Sunday session 1. The best lap is labeled Event best and covers the whole event -- one record per event, not per day.

Run group picker

When a schedule has been imported, the detail page shows a Run groups · tap yours chip row above the day plan. Tap every group you run in -- instructor rotations, multiple run groups, or a combined weekend assignment all count. Selected groups drive the YOU highlights in the pre-flight quick view and the My day timeline filter.

You can change your selection at any time; updates save immediately to the track day.

Day plan and log

The left column is split into two stacked cards:

• Day plan -- A timeline that interleaves your sessions with gates, drivers' meetings, lunch, tech inspection, and other run groups. A My day view trims it to your runs and key events; All groups shows the full schedule; Sessions shows just your runs.
• Day log -- A feed of everything that's happened today: tread depths logged for the day (in mm), sessions logged, schedule events, and free-form day notes.

Setting up an empty day

When a day has no schedule and no sessions yet, the Day plan shows one Start with the run schedule card instead of an empty timeline:

• Drop the schedule -- Drop the organizer's PDF, a PNG, or a photo of the paddock printout (or click Choose a file). Crew Chief reads it right away and shows you what it found; nothing is saved until you confirm. On a phone the first button is Photograph the schedule, which opens the camera, with Upload a PDF below it.
• Log sessions as you run them -- Skip the schedule and log each session as it happens.
• Use a typical HPDE day -- Adds five planned 25-minute sessions starting at 08:50, with a gap for lunch at 12:15. Every time stays editable, and nothing is logged until you log it. Needs a car assigned to the day.
• Import a timer file -- Pick a lap-timer export; it is read in your browser and offered as a link to this day before it opens in analysis.

When you confirm an imported schedule, gates, the drivers' meeting, and lunch are kept as day-log entries rather than sessions. If the importer can't read a session's start time, that row gets a Fix button so you can type the time in before importing; the rest still import either way. A schedule you drop later, after logging sessions, matches up with the sessions already on the day instead of duplicating them.

Context rail

The right column carries a Pre-flight checklist summary card showing your progress. For an upcoming or active day with an assigned car, the Setup card shows the named sheet with a source line -- Linked to this Track Day, or Currently fitted on the car when no day-specific link exists. Open car setup opens the linked setup and version when available; otherwise it opens the car's Setup tab, where you can choose the setup shown on the card. An empty car reads No setup sheet fitted yet. This is live car context, not a snapshot of what was run at a past session, so the card does not appear on past days. When a car is assigned, a Car readiness card shows its current brake, tire, fluid, oil, and inspection checks for this Track Day, with links to log car checks or ask Crew Chief. The column also has one-tap actions to add a session manually, import laps from a device, upload an event schedule, ask Crew Chief, open Photos, log the service you did after the day, and export the day report. When you have a personal best at this track, a PR at … card shows how far today's best sits from PR.

Photos shows a count of the photos on this day and opens a panel where you can add more without leaving the page. What you see there depends on whether the day is tied to an event:

• Tied to an event -- the event's shared gallery, the same one the event page shows, so your photos sit beside the other drivers'. Uploads land on the event and on the day's car.
• Not tied to an event -- a private gallery that belongs to this track day alone. Only you can see it.

A day with no event and no car assigned has nowhere to file a photo, so the row reads Assign a car first instead of opening.

Logging service after a track day

Service after this day in the context rail opens the usual Add Service Record form, already filled in with the day's date, the car assigned to the day, and the car's current odometer reading, and with a note naming the track and date. You still pick what you did and what it cost -- the point is that a brake bleed or a fluid change done the evening after an event lands in the car's logbook attached to the event that prompted it, rather than as a loose entry you have to date yourself.

The day has to have a car assigned before you can log service against it; until then the action says so instead of opening the form.

Underneath the rail, a Service & wear card lists what is already filed against this day: each service record, with its cost, linking straight into that car's logbook, plus any wear readings you took during the day. On the car's own Maintenance → Service history those records carry an After <track day> link back here, so the two views point at each other.

Exporting a day report

Click Export day report in the context rail to download the whole day as a PDF. The row shows a spinner while the file is being built, and it is unavailable ("Add a session first") until the day has at least one session.

The PDF contains:

• Cover -- track and layout (length, turn count, direction), the date or date range, the event and organizer when the day is paired with a registration, the assigned car, your run group, and the day's weather.
• Summary -- session count, total laps, best lap with its gap to your all-time best at that track, a consistency figure, and total distance driven.
• Sessions -- each session in the order it ran, with its lap table (lap number, time, and gap to that session's best), any laps marked invalid, your session notes, and the Coach debrief when one was generated.
• Day log -- the same chronological timeline the Day log card shows, one block per event day.
• Car state -- mounted tires with size and heat cycles, plus the tread depths and brake pad thicknesses recorded in the day log.
• Notes -- your day notes and day-log notes.

Consistency is reported as the standard deviation of a session's clean laps, alongside the gap between that session's best lap and its median lap. Laps marked invalid -- in and out laps, truncated laps -- are labelled Excluded in the lap table and left out of the best-lap and consistency figures. Distances follow your unit preference; lap times are shown exactly as they appear on the page.

Pre-session brief

For eligible upcoming sessions, a Pre-session brief can appear above the day header. It gives you a short coaching summary and a few supporting stats for the next run, using the event, schedule, weather, car, and recent session context TrackOut already has.

Use Refresh when you have changed the schedule, weather context, or session data and want TrackOut to regenerate the brief.

Session focus and debrief (Focus Flow)

Focus Flow is an opt-in practice loop built on the "one focus per session" coaching method: pick a single skill to work on before a session, then debrief it once you're back in the paddock. Turn it on under Settings -- when it's off, nothing changes anywhere.

With Focus Flow on:

• Pick a focus -- Edit intent on the pre-session brief adds a Session focus picker with curated focus areas (vision, braking reference points, corner entry, throttle application, smoothness, consistency, line accuracy) plus an Other option for your own words. The free-text intent note below it still feeds the brief as before.
• Pick it in the session log too -- The same Session focus picker replaces the quick-pick Session goal pills in the session log's Debrief section, so a session you log directly carries the same focus as one planned from the brief. A session you planned before turning Focus Flow on shows its old goal in the picker, so you can see the focus TrackOut is actually coaching you on -- and change or clear it. While Focus Flow is on the focus is the single field: clearing it clears the old goal behind it, rather than leaving one for the coach to fall back to. With Focus Flow off, the goal pills stay exactly as they were.
• Carry it forward -- When a recent completed session on the same car named "one thing for next session" in its debrief, that suggestion pre-fills the picker. A different car keeps its own history. Choosing a corner to focus on next stint in the analysis cockpit records it the same way, so it pre-fills your next session too.
• See it on the plan -- Planned sessions show their focus as a chip on the day plan timeline.
• Brief it -- The pre-session brief reads the focus you set for today, so its coaching is about the thing you asked to work on rather than only what you wrote on your last visit.
• Debrief it -- A session completed in the last two weeks with no debrief shows a Debrief this session prompt. The debrief asks three things: did you hit your focus, what did you learn, and one thing for next session. Dismissing the prompt keeps it hidden for that session in that browser.

Coach debrief

On paid plans, completed sessions can show a Coach debrief -- a short AI paragraph under the session row that tells you where the time went and what to work on next.

What the coach reads:

• Your stated focus, and your own debrief answers once you have given them.
• Where you drove -- the track, and which layout on a mapped track -- plus the car and how many laps you turned.
• The session's consistency, smoothness, best lap, optimal lap, and biggest sector gaps.
• On a mapped track, the corners with the widest lap-to-lap spread, named by their real turn labels, with the best time, spread, minimum speed, and braking point for each. Those are the corners you are repeating least well, so the coach can name one instead of speaking generally.

It is generated shortly after a session is completed. Answering the debrief regenerates it, however long after the session you get to it, so the paragraph reacts to what you actually said and not only to the numbers. Laps that arrive late -- a device import after the fact -- refresh it too. Refreshes are capped per day; sessions you never come back to keep whatever debrief they already have.

Pit Wall quick capture

On mobile, track day detail can show a Pit Wall entry card for quick capture between sessions. Pit Wall is built for paddock use with large tap targets and four fast actions:

• Driver feedback -- Log push, balance, braking feel, and a quick note after a session.
• Hot pressures -- Capture tire pressures right after the car comes in.
• Fuel & brakes -- Record fuel added and fuel used (gallons), track temperature, and the peak front and rear brake temperatures (°F) for the session just finished. Boxes open with anything already saved; leave one blank to skip it, or empty a saved reading to clear it.
• Next-driver brief -- Review the next upcoming session context, including the last session's fuel used and brake peaks, before sending the car back out.

Paddock view

The Paddock view is a one-column, phone-sized screen for logging a car's track day from the paddock. Open it from the car's Driving tab: Paddock view is in the tab's "..." menu, and on a phone an Open Paddock view card leads the tab.

It opens on today's track day for that car -- or, if there isn't one today, your most recent one, with its date in the header and a button to add today's.

• Track day -- the day's best lap, the heat cycles on the tire set you ran (against its limit, when the set has one), and the air temperature, then every session. A session with no hot pressures yet is highlighted in teal: Log hot pressures while they are hot. A session holding setup changes shows them in yellow, like v7 + 2 changes.
• Log session -- tap a session to enter the four hot pressures. Each corner is checked against its tire's recommended hot pressure, and one that is 2 psi (0.14 bar, 14 kPa) or more off turns yellow (+2 vs target). Below them, queue changes before the next session -- one-tap steps like Front camber −0.2°, or Another change for any setup measurement -- and add a line on how it felt. Save session saves the pressures you typed and the note; Skip readings goes back without saving.
• Leave the track -- if a session holds setup changes, you decide what they are before you go: name the change and Save as setup v8, Discard, stay on v7, or Decide at home to keep them on the session and settle them later from the Driving tab.
• Odometer at the end of the day -- leaving the track also asks, optionally, for the number on the dash. It starts at your last reading, so you only change the last digits; leave it untouched and nothing is logged. It goes into the car's odometer log as a Session reading named for the track, and a number below your last reading is blocked with a yellow warning. Missed it? Log odometer in the day's "..." menu on the Driving tab does the same later (it reads Edit odometer once the day has a reading), and a day with a reading shows Ended at 87,900 mi instead. Logging again replaces the day's reading, and deleting the track day removes it.

Crew Chief suggestions

On paid plans, when a corner's hot pressure runs 2 psi or more off its tire's target, Crew Chief puts one amber suggestion at the top of the Driving tab's track days and on the Paddock view's track day, between the stats and the sessions. It always says what it is based on -- Crew Chief · From S1 hot pressures, or From 2 sessions and hot pressures -- and offers one action:

• Add to changes queues the suggested setup change on your newest session that is pinned to a setup version, just like a change you queue yourself. Nothing is saved as a version until you decide.
• Open Crew Chief appears instead when the suggestion isn't a single setup change (cold-pressure advice, for example).

Not now hides it, with Undo in the confirmation. A hidden suggestion stays hidden until the readings change -- log new hot pressures and Crew Chief looks again. If the readings come back on target, the suggestion goes away on its own.

Setup changes can only be queued on a session that is pinned to a setup version. See changes made at a session for how they become versions.

Sessions

Each session shows up in the Day plan timeline with a colored indicator:

• Green -- Session is marked as completed
• Amber -- Session is still a draft

Each session row shows:

• Session number and status badge (Done or Draft)
• Description -- Optional session label
• Best lap time -- Prominently displayed on the right
• Lap count, weather, temperature, and track condition
• Notes -- Any session-specific notes shown in an indented block

On phones, session rows use a compact layout so the key result fields remain visible without pushing the page sideways. Best lap and lap count appear inline with the session summary, while the wider desktop columns return on larger screens.

Logging a session

Open a session from the Day plan -- or use Start session or Add session -- and the day plan gives way to the session log. The day's schedule stays beside it on tablets and desktops, so you can jump to another session with one tap. On a phone the log fills the screen and its buttons stay pinned to the bottom.

There is no Save button. Everything you enter saves as you go: the log's header says Saves as you type, then Saved. If a save fails, your entries stay on screen and TrackOut tries again as you keep editing. Closing the log, going back to the day, or switching sessions saves first -- if that save can't go through (for example, you're offline), the log stays open with your entries.

The log has four sections:

• Laps -- Your best lap, and every lap as a chip with the fastest highlighted and invalid laps struck through. Import asks where the laps are: A file from your timer (read in your browser; the supported formats are listed), Connect a RaceBox (only in browsers with Bluetooth), Photograph the screen (paid plans), or Type them in. AiM Solo and MyChron units aren't listed because no browser can talk to them -- export their file and import that. A file imported from the log links straight to this session, so you only confirm it. Laps imported from an AiM session are shown but can't be edited.
• Conditions -- Air temperature, sky, and track temperature, each with where it came from: a forecast for the session's start time (not a live reading) or values you entered. Change opens the full conditions editor. Empty a field (air temperature, weather, wind, humidity, or visibility) to clear the stored reading -- emptying wind speed also clears wind direction. Opening Conditions does not overwrite values you already logged; use Log weather when you want a fresh lookup.
• Off the track -- Tap a corner to enter hot and cold pressure on a large keypad, plus tire temp and tread when your car asks for them every session. Below the corners are the other readings your car asks for every session (by default fuel), then a chip for every reading it doesn't -- tap one to record it anyway. New field adds a reading of your own. Fill from S1 copies the previous session's cold pressures and fuel added.
• Debrief -- Your session focus (or goal), How did it go? as Worse / Same / Better, a focus for next session, and notes.

Choosing what each car tracks

Each reading picks its own rhythm, so tire temps can be asked every session while brake pad thickness is asked once a day. Set this per car on the car's Driving tab: choose What the paddock view asks for from the tab's "..." menu to open What gets asked:

• Every session -- asked in the session log's Off the track section. Hot pressures always live here; they mean nothing a day later.
• End of day -- measured when the car is cold, not every session: the session log leaves it out of its prompts and offers it as a chip. By default, brake pad thickness and tread depth. Only readings that can be kept against the day can go here: brake pad thickness, tread depth, and readings you add yourself. Tire temps, fuel, and brake temps are stored with each session, so they're asked every session or only when you add them. Pad thickness is stored against the day, not a session, so clearing it in any session clears the day's value.
• Only when I add it -- never asked; always available as a chip. By default, brake temps.

Track temp isn't in this list: the session log asks for it in its Conditions card. Use the Session / Day switch on a row, or its menu to move a reading to or from Only when I add it -- the menu lists only the options that reading can use. Cadence decides what you're asked for, not what you can record: every reading is a chip in the session log whatever its cadence. If you record the same reading in three recent sessions without being asked, the log offers to ask for it every session -- it never changes on its own.

Add reading adds your own: a number (with a unit), a yes/no, or a note, for the whole car or each corner. A whole-car number can also carry a fresh value and a safety floor -- it then shows up on the car's Driving → Wear ledger and warns near the limit, like brake pads do.

To rename or delete a reading of your own, use its row menu. Deleting removes the values you recorded for it; if it tracked wear, the part and its measurements stay on the Wear ledger. Built-in readings can be moved but not renamed or deleted.

When a telemetry file is linked to a session, its best lap and lap count come from that file. If you type your own, yours is kept, and a Use the parse's numbers link switches back when the file has lap times to use. A session holds one telemetry file at a time -- linking another replaces the first.

In the Lap times list, click a time to edit it, untick Valid to leave a lap out of the best lap, or use the trash icon to delete it. Deleting asks you to confirm first; the laps after it are renumbered.

Nothing past lap times is needed to log a session, and nothing blocks you: the footer names what is still blank. Log session N marks the session complete, which applies its heat cycles and part usage. Log and start session N+1 does the same and opens the next session. Session details -- type, number, date, start time, duration, and lap count -- are behind the settings icon in the log's header; date, start time, and type lock once a session is logged.

Adding a session

Click Add Session to log a new session within the track day. The session log form captures:

Session details:

• Session number, date, and time -- the date defaults to the track day's date so you don't have to change it every time

Weather and conditions:

• Weather condition (Sunny, Cloudy, Rain, etc.)
• Air temperature, track temperature, humidity, wind speed, and visibility
• Track condition (Dry, Damp, Wet, etc.)
• Auto-fetch current weather from the track's GPS location (track temperature isn't part of the weather lookup, so enter it yourself)

Fuel and brakes:

• Fuel added and fuel used, in US gallons
• Peak front and peak rear brake temperature, in °F
• These stay editable when you edit a saved session -- empty a field and save to remove that reading

Session results (shown when completing a session):

• Total laps driven
• Session duration
• Best lap time (accepts formats like 1:32.5, 1:32.45, 92.5, or 1m32.5s -- tenths and hundredths after the decimal are saved as lap-time precision, not milliseconds). Impossible values such as 1:99.5 are rejected instead of being saved.

Scan from device

The Scan from device button in the session form is an AI-assisted screenshot importer for lap-time screens. It does not connect directly to your timing hardware over USB, Bluetooth, or Wi-Fi, and it does not read native telemetry logs from the session form.

Use it when you have a photo or screenshot of the lap summary screen from a timer, phone app, or data logger and want TrackOut to fill in the session results for you.

Currently supported devices and layouts include:

• AIM Solo and AIM Solo 2
• Garmin Catalyst
• RaceChrono
• Harry's LapTimer
• TrackAddict
• Racelogic VBOX
• MoTeC
• Similar timing screens with clearly readable lap data

Accepted file types:

• JPEG / JPG
• PNG
• WebP
• GIF
• HEIC / HEIF

Text documents, PDFs, and other non-image files are rejected with a clear error. Use telemetry upload for raw data files instead.

What TrackOut tries to extract:

• Best lap time
• Lap count
• Session duration
• Individual laps when they are visible on the screen
• Top 3, Top 5, and Best Sequence variance (shown in seconds when present)
• Device/source name
• Weather and condition details if they appear in the screenshot

Example workflow:

1. Finish your session and open the lap summary on your device
2. Take a screenshot or photo that clearly shows the lap times
3. Open the track day in TrackOut and click Add Session
4. Click Scan from device in the Lap Times section
5. Upload the image and review the extracted data
6. Correct anything the AI missed, then save the session

Tire data:

• Cold and hot tire pressures for all four corners (FL, FR, RL, RR)
• Tread depth measurements (inner, middle, outer) for each tire
• Pre-populated with your current mounted tire data

Parts check (shown when the selected car has wear-tracked parts):

• Latest part measurement and unit for each opted-in part
• A new measurement field you can fill after the session
• Saved measurements are linked to the track day and session for later wear analysis

Pre-session checklist (for new sessions):

• Engine oil check
• Tire air pressure check
• Fuel level
• Wheel torque check

Session notes:

• Free-text area for observations, setup changes, and areas for improvement

Novice session logging

If your driver profile is set to HPDE1 or HPDE2, the session form starts with a shorter novice view:

• Best lap
• Conditions
• Focus for this session
• Quick note

Click + More fields when you want the full form with tire, weather, checklist, and parts details. More experienced levels see the full form by default, and legacy accounts without an experience level keep the full form until they choose one.

After you log five sessions in novice mode, TrackOut may show a one-time banner offering Try the full form. Accepting updates your experience level so future sessions open with hot pressures, tread depth, and the pre-session checklist by default. Choose Not yet to keep the shorter form -- the banner stays dismissed for that browser.

Session workflow

Sessions support a draft workflow:

1. Create as draft -- Log session details before you go on track
2. Save as Draft -- Save partial data and come back later
3. Complete session -- After your session, add results (laps, best time) and hot tire data
4. Save Session -- Mark the session as complete

Completing a session is what credits a heat cycle to the tires you ran and adds the session's time to the parts installed on the car. Because those counters are calculated from the session's date, start and end time, and session type, those four fields are locked once a session is complete -- changing them afterwards would leave your tire and part totals out of step with the sessions that produced them. The linked alignment and suspension are locked too, so later setup edits cannot change the setup recorded for the completed run. Notes, laps, pressures, and tread depths stay editable. If a locked field is wrong, delete the session and log it again: deleting hands the heat cycle and part hours back before the row goes away, so the totals stay accurate.

Day notes

Free-form day notes (and the event description) live in the Day log card on the detail page. Anything you type there is preserved alongside session entries in the timeline view, so the day reads like a journal.

Closing the day

When the day is done, click Close the day in the track day header (it also sits beside the session log on tablets and larger screens). One screen covers what belongs to the day:

• Cold readings — tread depth at all four corners, front and rear brake pad thickness, and any reading you set to be asked at the end of the day. If your pads wore, a yellow line says how much and roughly how many more days they have at that rate. Readings the day doesn't ask for are chips you can open.
• Unfinished business — sessions that were never logged. Mark one Didn't run (it stays on the day, labelled) or click Log it to log it now; closing the log brings you back.
• How was the day? — a summary of what your session debriefs said, whether the focus landed (Cracked it, Progress, or Not yet), and what to work on next time. The next-focus pick becomes the suggested focus for your next session.
• Tires and spend — how the tires felt and the event's costs, the same answers the post-event recap collected.

Blank fields are fine: the day closes either way. You can close a day again to correct it.

Weekends

On a multi-day event, pick the day with the day tabs first — each day keeps its own readings and focus, while tire feel and costs cover the whole event. Session numbers restart each day. From day two, a Carried from card shows the previous day's cold pressures, end-of-day tread, the tire set's heat cycles, and fuel burn per lap, and Close the day shows the previous day's tread and pad values greyed out until you click Use to confirm them.

Weather tracking

Track days automatically store weather data when available:

• Temperature -- In °F or °C, following Settings → Units → Temperature
• Weather description -- e.g., "Partly Cloudy", "Clear"
• Humidity -- As a percentage
• Wind speed -- In miles per hour

Weather shows up on each day's detail page, in its stats band and forecast. If your track day is linked to a track with GPS coordinates, you can also auto-fetch current weather conditions from the session log form.

Forecast on the detail page

Multi-day events get a dedicated forecast strip on the detail page that covers the full event window (one tile per day, with the focused day highlighted). Single-day events use a 7-day strip. The strip header shows when the forecast was last updated.

Reminder emails

TrackOut can send a day-before reminder email for upcoming track days. This is controlled by the Track day reminders setting in your account settings and is separate from the 7-day weather forecast email setting.

Multi-day events can send one reminder per event day, so a weekend HPDE can remind you before Saturday and again before Sunday. Each reminder uses the focused day's forecast when weather is available.

Editing, deleting, and re-enrolling

Edit lives under the ⋯ more menu on the detail page. Delete and Re-enroll are available from that same menu.

Editing a track day

Click Edit track day to update the track name, layout, date, description, or notes. On a multi-day event, changing the dates keeps later-day logs, readings, and wear on the same day of the weekend. When a MotorsportReg event is rescheduled and the Track Day moves to the new window, that day's log, readings, and Close the day wear move with it. Changing Your days on Events does not relocate a log you already saved on a calendar day.

Deleting a track day

Click Delete track day to permanently remove a track day. This is a cascade delete -- all sessions, laps, tire data, GPS points, and tire junction records associated with the track day are also deleted.

What you filed against the day rather than in it is the exception, and is kept:

• Photos stay on your Photos page, in their event gallery, and on any car they are attached to.
• Service records logged after the day stay in the car's logbook, with their cost and parts intact.
• Wear readings taken during the day stay on the part they were recorded against.

Deleting the day only detaches these from it.

Re-enrolling after a withdrawal

If you withdrew from a MotorsportReg event, the day shows a Withdrew pill. Open the ⋯ menu in the day's header and choose Re-enroll to restore the registration inside TrackOut (same as Re-register on Events). This does not re-submit enrollment to MotorsportReg. This is not offered when the organizer cancelled the event.

Tire data and wear tracking

Each session can record detailed tire data through the session log form:

• Cold pressures -- Tire pressures before driving (all four corners)
• Hot pressures -- Tire pressures immediately after a session
• Tread depth -- Inner, middle, and outer measurements for each tire

Pressure and temperature units

Pressures and temperatures are shown and entered in the units you choose under Settings → Units: psi, bar or kPa for pressure, and °F or °C for temperature. It is one setting for the whole app -- the session log, Pit Wall, the Paddock view, the car's Overview, Build and Driving tabs, the track day's forecast and printed report, and Reports all follow it. TrackOut keeps storing psi and °F, so switching units never changes a saved reading; a value you type in bar, kPa or °C is converted when you save.

When you complete a session, the form pre-populates tread depth fields with your tires' current measurements, so you only need to update values that changed.

This data is stored per-session, giving you a history of how your tires perform and wear over multiple sessions. See Tire Inventory for managing your tire collection.

If the selected car has parts with wear tracking enabled, the session form also includes a Parts check section. Fill in any new measurements you took during or after the session; TrackOut saves them alongside the session so part wear history can be reviewed in the car's Wear tab.

Alignment and suspension linking

Track days and sessions can be linked to specific alignment and suspension setups from your car's setup records. This lets you track which setup you were running on a given day, making it easy to correlate lap times with setup changes over time.

When you complete a session, TrackOut saves the measurements from its linked setup. Later changes to the setup sheet do not rewrite that run's recorded values. Sessions without a linked setup have no historical setup measurements.