It's easy to forget the useful details by the time you're loading the trailer. Not the big moments — the small, useful ones: the exact tire pressures you started on, how the kart felt through the fast left, the change you made after the third run and whether it actually helped. A week later none of it is reliable, and the next session starts from guesswork instead of evidence.
A short, consistent record fixes that. It turns each session into something the next one can build on: you can tell whether a change seemed to help, separate a driving problem from a kart problem, and stop repeating the same experiments. None of this needs special software — a notebook or a spreadsheet is enough. What matters is writing down the same things, every time, while you still remember them.
Record the same things every time
The value of a log comes from comparison, and you can only compare sessions that were recorded the same way. A run you noted in detail and a run you half-remember can't be weighed against each other. So aim for consistency over completeness: a small set of fields you fill in every time is worth far more than an exhaustive form you abandon after two events.
Keep the core short enough that you actually fill it in — the conditions, the tires, the times, how it felt, and what you're trying next. Add the fuller setup and maintenance detail when the session calls for it: a test day earns the setup fields, and the maintenance fields earn their place whenever you're tracking service life or something needs attention. The template at the end is split that way, so the everyday record stays quick.
The context: where, when, and in what conditions
Start with the facts that let you find and group the session later, then the conditions that shape much of what happens.
The fixed details are quick: the date, the track and layout, the session type (practice, testing, qualifying, heat, or final), and who drove. It also helps to note what you wanted from the session — learn a corner, try a change, get race practice — because it frames what the rest of the record means. If you keep notes on the circuit, point to them here rather than rewriting them.
Conditions matter more than beginners expect, because grip changes with them, and so does much of what you'll conclude afterward:
- Air and track temperature, roughly, in °C (°F) — and whether they were rising or falling.
- Weather and wind: sun, cloud, rain, a drying line, a strong headwind onto the main straight.
- Track state: green with little rubber, rubbered-in, dusty, damp, or fully wet — and whether grip was climbing or fading across the day.
A fast lap on a cold, green track and a fast lap on a hot, rubbered-in one aren't the same achievement, and a setup that suited one may not suit the other. Recording the conditions is what stops you drawing the wrong lesson from the times.
The kart: the setup and tires you ran
Write down the configuration the session actually ran on, not the one you meant to run. If you don't, a good result is unrepeatable and a bad one is unexplainable.
For most sessions you only need to note what differed from your usual setup baseline — a pressure, a gear, a seat stay. Save the full description — chassis and engine, axle, seat position and ballast, ride height, front and rear track width, gearing — for the days you're actually testing setup, where the detail earns its place.
Tire identity, condition, and pressure all affect how a kart behaves, so record them consistently. For each set you used, note:
- Which set it was — label your sets so you can tell them apart later.
- Cold pressures set, and hot pressures measured coming in — and when you measured them, since a reading taken straight off the track and one taken ten minutes later aren't the same number.
- Compound or type, and whether it was a control tire.
The cold-to-hot pressure change is useful context, but treat it carefully: measurement timing, track and air conditions, and even which gauge you used all affect the reading, so it isn't a clean measure of anything on its own — a different gauge changes the number you wrote down, not the tire. If you're chasing that level of detail, note the tire's accumulated running and the gauge you used so your comparisons stay honest.
The result: the times and how it actually felt
Two things capture the outcome — what the clock said, and what the driver felt. You want both, because the times tell you what you achieved, and the feel points you toward why.
From timing, record your best lap, a representative lap you could repeat, and, if you have them, sector or split times that show where the lap was won or lost. Consistency is as telling as outright pace: five laps within a tenth is a different session from one hot lap and four scrappy ones. Note anything that made the laps unrepresentative, too — heavy traffic, a spin, a red flag — because a time set in traffic isn't comparable to a clear one, and the log shouldn't pretend it is. If you run a logger, add the sector times; even a basic one puts objective numbers alongside the feel.
For feel, describe the handling where it actually happened, by corner and by phase, not as a single verdict. "No grip" is too vague to act on next week; "pushes wide on entry to the two slow rights, rear steps out on power at the chicane" is something you can test against. Note where the kart understeered, oversteered, hopped, or bound, whether it happened on the brakes, off-throttle, or on power, and how confident you felt pushing it. It's worth adding how sure you are of what you concluded, as well: "fairly certain the rear was loose" and "might have been me" lead to different next steps, and a log that admits the difference is more useful than one that pretends to certainty.
One change at a time — and when you can't
When you're testing, change one thing at a time and record the change, why you made it, and what happened. If you alter pressures, gearing, and seat stays in the same run, the log can't tell you which one moved the lap time, and neither can you — so a controlled test is worth the patience.
Most sessions aren't controlled tests, though. In qualifying or a race you'll do whatever the session needs, and several things change at once. That's fine — still record them all, and just treat the conclusion as weaker. Written down honestly, the sequence becomes evidence you can reason from — "dropped rear pressure 0.2 bar (3 psi) for the hot session, rear felt calmer on power, best lap two tenths quicker" — not proof that the pressure alone did it. Grip may have been changing, the tires were a session older, and you might simply have driven better. Over a season those entries are still more useful to you than a generic setup chart, because they're about your kart, your tracks, and your driving. Keep the changes that seemed to make things worse, too — but note the conditions they failed in, because something that doesn't help on a cold, green track can still be worth trying when it's hot and rubbered-in.
Close the loop: wear and abnormal observations
Two different things go here, and it's worth keeping them apart.
The first is ordinary wear and running data — fuel used, engine running time, and the condition of the parts you expect to consume, like the chain, sprockets, tires, and brake pads. Recording it consistently gives the maintenance history useful context.
The second is anything abnormal — play, a vibration, an unfamiliar noise, a leak, or visible damage. Record those observations separately from ordinary wear so they are easy to find in the maintenance history. This logging guide does not assess what an observation means or whether a kart is fit to run.
Then finish with the most valuable line in the whole record: what to try or check next. A session that ends with a clear next step — a pressure to test, a gear to try, a part to replace, a corner to work on — is a session that improves the one after it.
Copy this session-log template
Keep one sheet per session. The core is short on purpose — fill it in every time, before you pack up. Add the setup block on test days, and use the maintenance block whenever you're tracking service life, not only after a problem appears. Adapt the rows to your class — a two-stroke gearbox kart and a rental-based club runner won't need identical lines — but keep the structure stable so your sessions stay comparable. For rental or arrive-and-drive sessions, record the kart number and skip the setup and pressure fields you can't reach; the conditions, times, feel, and next-step lines still apply.
Core record — every session
| Field | What to record | Your entry |
|---|---|---|
| Session | Date, track, layout, session type, driver, kart or kart number, and run or session number | |
| Objective | What you wanted from the session | |
| Conditions | Air and track temperature and trend, weather and wind, track state and grip trend | |
| Tires | Set label, cold pressures, hot pressures and when you measured them | |
| Times | Best lap, representative lap, consistency, and anything that made laps unrepresentative (traffic, spins, flags) | |
| Feel | Handling by corner and phase — push, rotation, hop, bind — driver confidence, and how sure you are of the conclusion | |
| Next | What to try, check, or replace next session |
Add when you're testing setup
| Field | What to record | Your entry |
|---|---|---|
| Full setup | Axle, seat and ballast, ride height, front and rear track widths, gearing — or only what differed from your baseline | |
| Change and effect | What you changed (ideally one thing), why, and the effect on feel and time | |
| Tire detail | Model and compound, accumulated running, control tire, and the gauge you used |
Add for maintenance
| Field | What to record | Your entry |
|---|---|---|
| Wear and running | Fuel used, engine hours, and the condition of the chain, sprockets, tires, and pads | |
| Abnormal observations | Play, vibration, noise, leak, or visible damage, recorded without diagnosing it here |
Keep it usable
A log only helps if you actually keep it, so make it low-effort:
- Fill in the core immediately, before you pack up — memory fades fast, and the details go first.
- Use one format every time, and keep the sheets together so a whole season sits in one place.
- Read the last session's notes before the next one, so that "next" line actually gets used.
You can run all of this on paper or in a spreadsheet, and for a single kart that's often enough. The friction shows up later: re-entering the same fields every event, and trying to compare ten sessions across a season by flipping between sheets. A tool built for it removes that friction — Kartnote stores your sessions, setups, and results so you can compare runs over time and carry your history between events without rebuilding the sheet. The method above is what matters; an app just saves you the retyping.
Improvement rarely comes from a better memory — it comes from notes that make each session start where the last one finished. Record the same core every time, isolate a change when you can, and always leave yourself a next step. Do that, and the log quietly turns a year of track days into a year of progress.