Read your training log, run better

A training log is most useful when it helps you decide what to do next, not when it merely records kilometres. To use a training log to spot patterns and improve performance, treat every entry as evidence: a small sample that gains meaning when compared with sleep, terrain, effort, recovery and the goal you were chasing.

Start with a simple weekly review and keep the record easy enough that you will continue. Note the date, session type, distance or duration, terrain, perceived effort, heart rate if useful, weather, sleep and anything unusual. A notebook, spreadsheet or dedicated app can all work; consistency matters more than elaborate software.

Over time, those entries reveal more than fitness. They show which sessions produce a good response, which changes precede fatigue, and where pacing or fuelling breaks down. The aim is not to judge every run by one number, but to make better choices from a reliable history.

Record context, not just output

Distance and time tell you what you did, but not why the session felt hard. Add the purpose: easy recovery, steady aerobic work, tempo, hills, a long race simulation or a genuinely unplanned effort. Tags should stay consistent; renaming the same workout each week makes comparisons harder than leaving a field blank.

Context prevents false conclusions. In Melbourne, one run may be cool and still, while the next is humid, windy and affected by rain—locals often joke about four seasons in one day. Recording wind, temperature and surface lets you separate a fitness change from conditions that altered heart rate and pace.

Use both objective and subjective data, but do not let either dominate. A watch might show seven minutes slower while your effort felt normal; your rating might say brutal while the pace suggests an easy day. Look for agreement across several sessions before deciding that something has changed.

Find patterns across comparable sessions

Patterns become visible when comparisons are like for like. Compare this month’s easy runs with last month’s, then examine hill sessions, long efforts and race efforts separately. A rolling average over three to six weeks is usually more informative than reacting to the latest run, because daily readiness moves around for ordinary reasons.

Separate performance from workload. If pace at the same effort drifts upward, that may reflect improving fitness. If resting heart rate rises, sleep worsens or the same easy run feels heavier, the pattern may point to accumulated fatigue. No single marker proves either case, so require several signals to point the same way.

That is why weekly review habits matter: a short review turns records into a decision for the next week, much as sustained project work needs regular review rather than blind repetition.

Read fatigue before it becomes injury

Watch for changes in the relationship between effort and outcome. A familiar flat run may suddenly require more breathing, heart rate may climb at the same pace, or recovery may take longer than usual. Persistent pain deserves professional assessment, while ordinary tiredness should be met with a planned adjustment rather than another hard session.

Climate can hide the signal. Brisbane’s summer humidity and thunderstorms often force early starts, while Adelaide’s dry heat can lift the temperature sharply by the afternoon. On hot runs, note shade, fluid intake and whether effort stayed controlled. Comparing a hot-weather session with a cool-weather session as though conditions were equal creates bad conclusions.

Life outside training belongs in the log too. Work stress, travel, poor sleep, illness and family commitments can change your response to the same session. A simple readiness score from one to five, recorded in the morning, creates a useful bridge between what happened during the day and what you should do that evening.

Change one variable at a time

Once the log suggests a weakness, test one change for two or three weeks. If climbing is limiting, add a specific hill session rather than increasing everything. If fuelling is inconsistent, practise eating during long efforts and record what you tolerate. This keeps cause and effect visible and prevents a busy training diary from becoming random stress.

Build changes around the event and terrain that matter. A Blue Mountains course can punish climbing and technical descents, so flat pace alone may hide a weakness; Perth’s long, exposed routes can make heat and hydration more important than short hills. Record how you handled those features, then rehearse the missing skill in training.

Practise the event’s operating environment as well as its distances. Australian ultras may impose mandatory gear, checkpoint bagging and strict cut-offs, while popular races can close entries well before race day. For a night event, rehearse running by headlamp, managing an aid station and starting when tired, because these demands rarely appear in a flat morning run.

Plan in blocks, then adjust

Review the log at several levels. Use the daily notes to adjust the next session, the weekly review to check workload and recovery, and a four- to twelve-week block to assess direction. Keep planned versus completed sessions visible. The gap often reveals time constraints, unrealistic targets or an overreliance on one kind of workout.

Missing sessions are information, not a verdict. Mark the reason, resume with a smaller load and avoid copying missed volume into the next day. Australian race culture may describe a difficult finish as a blow-up or a DNF, but the useful question is which decision caused it: pacing, preparation, nutrition, heat management or something that had not been trained.

At the end of a block, compare goal attainment with the quality of your training process. Did you hit the intended effort, arrive healthy and execute the plan? Were the strongest sessions spaced with enough recovery between them? A log cannot remove every bad day, but it can show whether your judgement is improving even when the result is not.

Keep the weekly review short enough to sustain. Highlight the strongest pattern, choose one adjustment for the coming week and schedule a date to review it again. That creates a feedback loop without turning your log into a source of pressure or a spreadsheet project that lasts for two weeks.

The useful rule is simple: record enough context to compare like with like, look for several matching signals, and make one measured change at a time. A well-used training log becomes a record of decisions, giving each block of training a clear purpose and each race a stronger basis for execution.