A rally driver approaches a crest at well over a hundred miles an hour, on a road they may have driven only once or twice before, with no idea what lies on the other side. What keeps the car on the road isn't instinct or memory alone — it's a voice in their ear reading a code that was written days earlier, refined into a script precise enough to describe a blind right-hander before the driver can even see it. That system, pace notes, is arguably the single biggest reason rally drivers can go as fast as they do on roads no sane person would otherwise attack blind.
The Core Problem Pace Notes Solve
Circuit racers learn a track by repetition — the same corners, lap after lap, until the car practically drives itself. Rally stages don't offer that luxury. Many are driven once in competition, sometimes never repeated in a driver's career, over public roads temporarily closed for the event. Without some way to know what's coming, drivers would have to drive well below the car's limit just to react safely to the unknown. Pace notes exist to close that gap between what the driver can see and what the car can actually do, turning an unknown road into something closer to a memorized one, purely through description rather than repetition.
The notes are generated during a reconnaissance session before the rally, when the driver and co-driver run the stage roads at reduced speed — well under competition pace, and under rules that cap how many passes they're allowed. During recce, the co-driver calls out every feature of the road as the driver interprets it: the sharpness of a corner, the crest that hides what's beyond it, the camber change, the surface, the distance to the next feature. The driver dictates a description in real time, the co-driver writes it down or types it into a note-taking system, and by the end of recce the entire stage exists as a written script that will later be read back to the driver at full speed.
The Grammar of a Pace Note
The language of pace notes looks cryptic to an outsider but functions like a compact grammar built for speed of speech. Corners are graded by severity, most commonly on a numeric scale where a low number means a tight, slow corner and a high number means a fast, open one — though the exact scale and terminology vary by driver and by the notation system they've adopted. Distances between features are called out, often rounded to convenient increments, so the driver knows how much road they have before the next event. Modifiers stack onto the base call to add nuance: whether a corner tightens partway through, whether it's cut by a ditch or lined by a wall, whether the surface turns to gravel or mud on the exit, whether a jump follows immediately after.
What makes the system work isn't just the vocabulary — it's the rhythm. A co-driver has to deliver calls fast enough to stay ahead of the car, which means compressing information into the shortest phrase that still conveys everything the driver needs. "Long five right, don't cut, into six left, tightens, over crest" might describe two seconds of note-taking but several seconds of driving, delivered in the calm, clipped cadence that lets the driver process it without translating consciously — the words become almost reflexive triggers rather than instructions.
Why the Co-Driver's Timing Matters as Much as the Words
The information in pace notes is only useful if it arrives at the right moment relative to the car's position on the road, and that timing is where a lot of the skill in co-driving actually lives. Call a corner too early and the driver braces for something that hasn't arrived yet, potentially misjudging speed on the corner before it. Call it too late and the whole point of the system collapses — the driver is now reacting to a blind corner just as they would without notes at all. Good co-drivers develop an internal sense of pace that tracks not the clock but the car's real position, adjusting their delivery speed to match how fast the stage is unfolding, speeding up through fast sections and giving extra beats of silence through technical ones where the driver needs a moment to process rather than a wall of calls.
This is also why the driver-co-driver pairing is so personal. The notation system, the pacing, even individual phrasing conventions are typically built collaboratively and refined over seasons, which is part of why successful pairings tend to stay together for years rather than mixing and matching. A co-driver dropped into an unfamiliar car with someone else's notes and someone else's cadence is working with a foreign language, not a universal one.
Recce Rules and Their Effect on Note Quality
Because pace notes are only as good as the reconnaissance that produced them, rally-governing bodies impose limits on recce — typically restricting the number of passes a crew can make over each stage and capping the speed at which they're allowed to drive during that process. These constraints exist partly for safety and partly to prevent wealthier teams from simply out-resourcing everyone else through endless practice. The restriction means a crew has to get the description right in a handful of passes, which puts real pressure on the co-driver's note-taking discipline: vague or rushed notes from recce become dangerous gaps in information during the actual stage, when the car is going two or three times as fast as it was during reconnaissance.
Modern recce is usually done with note-taking software running on a tablet or laptop mounted in the car, which lets the co-driver type shorthand quickly and adjust it on the fly by scrolling back to correct or refine an entry after a second pass. Before this kind of tooling became standard, co-drivers wrote notes by hand in notebooks, which is still how some club-level and historic rally crews operate today — a reminder that the fundamental system hasn't changed even as the tools around it have.
Reading Notes Under Pressure
Reading pace notes at speed is its own discrete skill, separate from writing them. The co-driver has to track the trip meter or distance markers precisely enough to know where on the page they are relative to where the car actually is, all while being thrown around a cabin that's bouncing over rough surfaces and jumps. Losing your place in the notes for even a few seconds on a fast stage can mean calling a slow corner as a fast one, or missing a call altogether — which is why co-drivers train the physical act of reading and tracking almost as hard as drivers train their car control. It's a job that looks passive from outside the car and is anything but from inside it.
Key Takeaways
- Pace notes are a written description of a stage's corners, crests, and hazards, created during a speed-limited recce before the event.
- The notation uses a numeric corner-severity scale plus modifiers for distance, camber, surface, and hazards, all delivered in a rhythm built for speed.
- Timing of the co-driver's call relative to the car's actual position matters as much as the wording itself.
- Driver-co-driver pairings develop their own notation conventions over time, which is part of why long-term partnerships tend to outperform mixed-and-matched ones.
- Recce restrictions on passes and speed put pressure on getting notes right the first time, since stage speeds far exceed recce speeds.
- Bottom line: pace notes are what let rally cars run at the limit on roads drivers have barely seen, and their reliability depends entirely on the discipline behind the recce process, not just the words on the page.
