Keeping a race logbook: setup sheets, lap times and notes that actually help
Ask a race team how a particular set-up was found and you will often hear a story that starts with a feeling and ends with a change to the suspension. The feeling is useful, but without a record it is hard to repeat. A race logbook turns those stories into knowledge that the team can reuse, compare and build on.
A logbook for every bike and every rider is not glamorous work, but it is one of the habits that makes race weekends more productive. This article explains how to set one up in a way that small teams can actually maintain.
What the logbook is for
The logbook has three jobs. It records what was done to the machine, so that a fault can be traced back to a change. It records what happened on track, so that a set-up can be compared with the results. And it records what the team learned, so that the next person to work on the bike does not have to rediscover the same lesson.
Keep it simple enough that people will use it. A notebook on the pit wall, or a shared spreadsheet on a tablet, is better than an elaborate system that nobody updates.
Set-up sheets
A set-up sheet records the baseline and every change. For suspension, note the preload, compression and rebound settings at the front and rear, and the ride height if it is adjustable. For the engine, record the mapping or any changes to the air or fuel system. For the chassis, note the wheelbase, the swingarm pivot position, the steering geometry and any adjustment to the sprocket or chain.
Always write the date, the track, the weather and the rider's name at the top. Then record each session on its own line, with the changes made and the reason for them. A change without a reason is hard to learn from later.
Lap times and session data
Lap times are the easiest data to collect and the easiest to misread. A fast lap in cool conditions is not directly comparable with a slower lap in heat, and a lap that was ruined by traffic says little about the set-up. Note the lap number, the time, the conditions and any incident. Mark laps that were compromised so that the team does not draw conclusions from them.
If the bike has a data logger, store the files with the session notes and name them clearly. A folder full of files called "test 3 final v2" is useless six months later.
Rider comments
The rider's feedback should be recorded in their own words wherever possible. Write down where the front felt light, where the rear stepped out, which corner caused a problem and whether the feeling came on entry, mid-corner or exit. Ask the rider to rate the feeling if that helps, but do not replace their description with a number.
Rider comments are most useful when they are specific. "The bike feels odd" gives little to work with. "The front goes light on the brake into the second-last corner when the bike is hot" gives the team a clear question.
Maintenance records
Maintenance is part of the logbook, not a separate file. Record every service, every replaced part and every inspection. Include the mileage or engine hours, the date and the name of the person who did the work. Note any torque figure checked, any part that was measured and the result.
When a problem occurs, the maintenance record is often the first place to look. A bearing that was replaced three events ago may be the cause of the vibration that appeared this weekend, and only the record will show it.
Consistency beats detail
There is a temptation to record everything, and it usually ends with nothing being recorded. Decide which information matters for your team and write that down every time. A short, consistent entry after each session is worth more than a long entry written once a month.
Agree on a format and stick to it. Use the same abbreviations, the same units and the same order of information. A consistent format makes it easy for a new team member to read the book and understand what has happened.
Review the book regularly
A logbook is only useful if someone reads it. Set aside time after each event, and again at the end of the season, to review the entries. Look for patterns: does one track always need a softer rear, does a particular change always improve the front feel, does a recurring fault appear after a certain mileage?
These reviews are where the logbook becomes a tool for decisions rather than a record of the past. They also help the team agree on what it believes, which reduces arguments in the garage.
Keep it safe
Store the logbook where it will not be damaged by oil, rain or dust. If you keep it electronically, make a backup. A team that loses its data loses a season of learning, and that is an avoidable mistake.
The habit that pays off
A race logbook takes a few minutes each session and a little more time at the end of each event. In return it gives the team a memory it can trust, a clearer view of each machine and a faster route to the right set-up next time. For a small team, that kind of discipline is one of the few advantages that does not depend on budget.