Pace Notes at Pro Level: Your Own System, Timing and Blind Trust in the Cockpit

How advanced crews compress their pace note system, tie call timing to speed and build trust systematically instead of leaving it to chance.

Sport: Rallye · Level: Pro

Introduction

At pro level the winning crew is not the one with the most detailed notes but the one with the most compressed: maximum information, minimum syllables, always in the same rhythm. The framework stays what it was on day one — corner severity 1 to 6, direction, distance in metres, plus extras such as "square" for roughly 90 degrees, "crest" for a brow and "caution" for genuine danger [1]. What changes is density and discipline.

Straight talk: your system has to satisfy two conditions. First unambiguity — every syllable carries exactly one meaning and the scale always runs the same way. Some crews invert it, which is allowed, but only if you fix it before the recce and never touch it again [1]. Second speakability under load: at a world championship event, peak heart rate in competition was 166 beats per minute and well over 30 degrees Celsius were measured in the cockpit [5]. Whatever you cannot pronounce cleanly at a pulse of 166 does not belong in the notes.

And the real pro topic is not notation but trust: the driver has to act on the call before he verifies it. That trust is not a character trait, it is the product of a thousand calls that were kept.

What You Need

Step by Step

1. Compress your own system

Delete everything that does not trigger an action. Every note must tell the driver what to do, not what is there. Merge standard sequences into a single expression instead of three separate notes, and keep the order severity, direction, distance rigid [1]. A system with two variants on the same day is not a system.

2. Recce with a read-back

First pass: the driver dictates, the co-driver writes [2]. Second pass: the co-driver reads at calling pace and the driver corrects immediately. Anything that hesitates on the second pass is a mistake in competition. Changes get written in the car, never from memory in service.

3. Tie pace to speed

Calling is not reading aloud, it is a control loop: the higher the speed, the further ahead the co-driver reads; in tight, slow sections he moves closer. Advanced crews use fixed lead windows and a stable base rhythm for this. The driver should hear the next corner before he sees it — but only one.

4. Build trust systematically

Trust grows through repetition under controlled conditions: same system, same rhythm, documented errors. Use the shakedown for it — the full-speed test before the rally where several timed passes are possible [3]. There you are not only testing the car but the communication at competition speed.

5. Treat the recce as a physical load

The slow recce is, of all things, the hardest leg for the right-hand seat: among rally co-drivers, nausea occurred in 15.3 percent during reconnaissance but only 2.3 percent on the stage [4]. The reason is gaze work — on the stage your eyes stay locked on the notes and your brain anticipates the accelerations, while on the recce they jump constantly between road and book [4]. Plan the recce as a load, not as a drive.

Common Mistakes

Safety Notes

At this level the notes are a safety document, not a stopwatch tool. "Caution" means caution — use the word loosely and you make it worthless, ignore it and you risk exactly what it warns about [1]. So keep one hard rule: warning terms are never softened, never abbreviated and never overrun.

Second: even professionals cover road sections in normal traffic and drive recces on open roads — normal traffic law applies there without exception, and the recce is not a test session [3]. Third: concentration is a physical quantity. At a pulse of 166 and over 33 degrees Celsius in the cockpit [5], calling becomes high-load work — fluid, cooling and breaks belong in the plan.

And here too: this guide explains and motivates — it never replaces training at a rally school, the licence course or instruction from experienced crews.

Pro Tip

Keep a shared calling logbook: after every stage you note in two columns which call came late and which was missing. After three events you see the pattern — almost always the same two corner types, usually fast sequences before tight corners. Know your error pattern and you fix the system rather than the driving style — and that is exactly where the seconds sit that no setup and no engine will hand you. Welcome to the elite.

FAQ

How do professionals train calling pace and trust?

Through repetition under controlled conditions: a frozen system, two recce passes with a spoken read-back [2], full-speed testing at shakedown [3] and an error log after every stage. Trust is the measurable result of calls that were kept, not a question of courage.

Should you develop your own pace note system?

Yes, but sparingly. The framework stays corner severity 1 to 6, direction and distance with extras like square, crest and caution [1]. Custom shorthand only pays when it saves syllables and stays unambiguous. What matters is that both of you use the same system and do not change it mid-season.

How far ahead should the co-driver call?

Far enough that the driver hears the corner before he sees it — and no further. The lead grows with speed and shrinks in tight sections. A steady rhythm, clear volume and one call at a time matter more than any rule of thumb in metres.

Why do I feel worse on the recce than on the stage?

Because there your gaze jumps constantly between road and notebook, while on the stage it stays locked on the notes and your brain anticipates the accelerations [4]. Measured figures: 15.3 percent nausea on the recce against 2.3 percent on the special stage [4]. Fresh air, breaks and habituation through repetition all help.

Key Takeaways

Next guide

Classes & Progression: From Rally5 and Club Sport Toward Rally2 — The Regulations Strategy

Related guides

← More Rallye guides