How to use age grading without kidding yourself

Age grading is a brilliant running tool, as long as you do not ask it to become a tiny courtroom that rules in your favour every time.

It adds age and gender context to a race result. That can make comparisons fairer, especially for masters runners, clubmates and anyone trying to understand current form against old personal bests. But it is still context. It is not a get-out-of-jail-free card for every disappointing split.

Age grading is context, not a get-out-of-jail-free card

The raw finish time still matters. If you ran 10K in 55:00, that is the result. Age grading does not rewrite the race clock, move you up the official results, or quietly remove the kilometre where you went out too fast like an idiot.

What it does is ask a more useful second question: how strong was that performance for your age and gender?

That second question can be genuinely helpful. It can also become self-flattery if you ignore everything else. The trick is to use age grading as a fairer lens, not as a replacement for judgement.

Start with the raw time, then add age context

A good way to use age grading is to read the result in layers.

• First, note the raw finish time and pace.
• Then look at the age-graded percentage.
• Then look at the age-adjusted equivalent time.
• Finally, add the human context: course, weather, training, effort and how the race actually unfolded.

That order matters. If you start with the age-adjusted result and forget the race itself, you can make almost anything sound better than it was. If you start only with the raw time, older runners can undersell strong performances. Both mistakes are easy.

Use it to compare current form with old PBs

Age grading is especially useful when old personal bests are still lurking in your memory with suspiciously fresh confidence. A raw PB from your 30s may not be a fair comparison with a race result from your 50s or 60s.

Run the old result through the calculator using your age at the time. Then run the current result using your current age. Compare the age-graded percentage and age-adjusted equivalent time.

You may find the old PB was still stronger. That is allowed. You may also find the current result is closer than the raw clock suggests. That is the useful bit.

Use it carefully when comparing different runners

Age grading can make comparisons between runners of different ages more sensible. A 42-year-old and a 67-year-old running the same time have not usually produced the same age-group performance.

Still, age grading should not be framed as who really won. Official race results belong to the race organiser and timing provider. Age grading gives you another way to understand the performance, not a secret alternative podium.

Do not ignore the messy stuff

The calculator does not know whether the course was hilly, windy, muddy, crowded or measured with heroic optimism. It does not know about heat, humidity, sleep, illness, injury, shoes, training block, taper, pacing or whether you spent half the race negotiating a narrow path behind someone wearing headphones.

That is why the number should sit beside your judgement, not replace it. A lower age grade on a brutal course might still be a very strong run. A high age grade on a perfect day is still good, but it should not make you allergic to nuance.

Let a good percentage motivate you, not flatter you

A good age-graded percentage should be encouraging. It can show that your running is holding up well, that a slower raw time is still strong, or that a current performance deserves more credit than you gave it.

The healthiest use is motivation. Use it to set fairer goals, compare seasons, understand progress and keep racing meaningful as you get older. Do not use it to win every post-run conversation by spreadsheet.

Try the calculator

TruePace Run uses sourced road-running age standards for supported distances and shows the source near the result. Results are informational estimates, not official rankings.

Enter one result, look at the raw time, the age-graded percentage and the age-adjusted equivalent, then add the race-day context yourself. That is the honest version.