Patrick Wales-Dinan on How to Read a Training Log Without Overreacting

Every few weeks a runner hands me a training log with a worried look on their face. One workout went badly, or a long run felt heavy, and suddenly the whole season feels like it is slipping away. I have had that conversation more times than I can count, and as Patrick Wales-Dinan, a coach who has spent close to twenty years around distance runners, I can tell you the log is almost never the problem. The problem is how we read it. A training log is a record of what happened, not a verdict on who you are as a runner, and reading it well is a skill anyone can pick up.

Why One Bad Day Means Very Little

A single run tells you about that single day. It might have been a poor night of sleep, a skipped lunch, a stressful exam or a cold that had not shown itself yet. Even the weather can shift how a workout feels by a surprising amount.

I spent time teaching statistics in a classroom, and the lesson that stuck with me is simple. One data point can’t show you a pattern. Two or three might hint at one. It usually takes several weeks of entries before you can say anything useful about how training is going.

So when a runner tells me they had a terrible tempo run on Tuesday, my first question is not about the pace. I ask what the days around it looked like.

What I Look For Instead

When I sit down with a log, these are the things I care about most:

• How easy runs feel at the same effort over several weeks

• Whether hard days are followed by a decent recovery or a long hangover

• Notes on sleep, mood and appetite

• Any ache that shows up twice in the same spot

• The overall direction of the last three or four weeks

Notice that most of those are about direction rather than any single number. A runner whose easy pace is slowly feeling smoother is doing fine, even if one workout fell flat.

Numbers That Get More Attention Than They Deserve

Some numbers are fun to look at but tell you less than people think.

Pace on one run is the obvious one. Weekly mileage is another, especially when it gets compared with a teammate’s total. Your body does not care what the person next to you ran. It only knows what you asked of it.

Watch scores deserve a little caution too. Readiness numbers and recovery ratings can be a helpful extra input, but they are estimates built from limited data. If your watch says you are tired and you feel great, or the other way around, trust the full picture and not the screen alone.

A Simple Weekly Review

You do not need a spreadsheet with ten tabs. Once a week, on a Sunday evening or whenever suits you, I would ask five questions:

1. How did most of my easy runs feel this week?

2. Did I sleep well enough on most nights?

3. Did any ache show up more than once?

4. Did I have energy for the hard sessions?

5. What is one small thing I would change next week?

That is about ten minutes of work. Write the answers in a sentence or two, and over a season you will start to see your own patterns. Maybe you always feel flat in the week after exams. Maybe your legs complain when mileage jumps on a Monday. That kind of knowledge is worth far more than a pretty chart.

When a Bad Week Is Actually a Warning

I do not want to swing too far the other way. Sometimes a rough stretch means something, and ignoring it is its own mistake. These are the signs that make me pay closer attention:

• Easy runs feel hard for more than a week

• Motivation drops and stays down

• A small pain changes its shape or gets worse as you run

• Sleep gets worse even though you are tired

• You start dreading sessions you normally enjoy

One of these on its own might be nothing. Several together, lasting a week or more, is a good reason to talk to your coach and maybe a doctor. And tell someone early. Most of the injuries I have seen get serious started as something the athlete kept quiet about.

What a Coach Adds to the Picture

People often ask what I, Patrick Wales-Dinan, look at first when an athlete hands over a log. Honestly, I read the notes before the numbers. The numbers say what happened. The notes say how it felt, and the gap between those two is where most of the useful information hides.

A good coach can also see context you might miss from the inside. We know what the last block looked like and what races are coming. We remember that a runner always struggles in the middle of a heavy semester and usually rebounds a week later. Having that history makes it easier to stay calm when a bad day shows up.

That calm matters. Athletes pick up on it. If I look worried about one slow workout, the runner will be twice as worried. If I treat it as a normal blip, they usually relax and the next session goes better.

A Quick Word for Parents

If your child runs, you will probably see their log or hear about their results. The most helpful thing you can do is stay curious and keep your reaction small. Ask how they are feeling before you ask about the split. A runner who feels safe talking about a bad day is far more likely to mention a sore shin before it becomes a stress fracture.

Try not to compare their weeks with somebody else’s. Young distance runners develop at different speeds, and a log is only meaningful when you read it against the same person’s earlier entries.

Keep It Simple and Keep It Honest

The best training log is the one you actually fill in. Write down what you ran, how it felt and anything unusual about the day. Be honest on the bad days, because those entries teach you the most. Then step back once a week and look at the bigger picture.

A runner who learns to read their log calmly gets a real advantage. They stop reacting to every dip and start noticing what is genuinely worth changing. Over a few seasons that habit does more for progress than any single hard workout ever will.