Perceived Effort vs Pace

Perceived effort, often shortened to RPE (rate of perceived effort), is a simple scale, usually 1 to 10, for how hard a run feels rather than how fast it is. Pace tells you what you did; RPE tells you what it cost to do it, and the two don't always agree.

What RPE actually measures

RPE is a rough, self-reported read on effort based on breathing, muscle fatigue, and how easily you could hold a conversation. It doesn't need a device, just honest attention to how a run feels while you're in it. Coaches have used some version of this scale for decades, precisely because it works across very different runners and very different days without needing calibration to a lab test.

Why effort and pace can disagree

Heat, humidity, hills, poor sleep, or accumulated training fatigue can all make a familiar pace feel noticeably harder on a given day, without your fitness having actually changed. Racing by a fixed pace target on a hot or hilly day can push your effort far past what's sustainable long before the number on your watch looks alarming. This is also part of why some runners lean on a run-walk strategy in tough conditions, since it lets effort, not a fixed pace, set the rhythm.

Common mistakes runners make with RPE

The most common mistake is treating RPE as a vibe rather than checking it against something concrete, like whether you could actually hold a conversation right now. Without that discipline, easy runs quietly creep up in effort over weeks, since 'easy' starts to mean whatever pace felt fine that day rather than a genuinely low, conversational effort. The second common mistake is the opposite: using RPE as an excuse to never push hard, since discomfort always registers as a high number even when it's the intended, useful kind of hard.

Both mistakes come from treating RPE as purely subjective mood rather than a specific, describable scale. Anchoring it to breathing and the talk test, rather than a general sense of how the run is going, keeps it useful instead of vague.

When to lean on each one

For easy training days, RPE is arguably the more useful tool, since it protects against the common mistake of running easy days too hard simply because the pace felt achievable that day. For a well-paced goal race, pace is useful for holding a sensible early rhythm, but shifting toward effort in the closing kilometers, especially in heat or on hills, protects against the kind of late fade a fixed pace target can cause. The final 5K of a race is exactly where this shift tends to matter most.

Learning to read your own effort

Effort takes practice to calibrate accurately. Try running a few sessions by feel alone, checking your pace only afterward rather than mid-run, and compare what you expected against what actually happened. Staying properly fuelled and hydrated matters here too, since effort tends to spike well before pace does when you're under-hydrated. See hydration planning for race day for more on that. Over a few weeks, most runners get noticeably better at reading their own effort without needing a watch to confirm it.

A useful exercise is to guess your effort level out loud, or in your head, before glancing at your watch, rather than looking first and reasoning backward into how it should feel. That small habit forces you to actually notice breathing, leg fatigue and rhythm rather than letting a number on your wrist quietly do the noticing for you.

Using both together, not choosing sides

None of this means abandoning pace altogether. Pace is still useful for planning a race, tracking progress over a training block, and giving you an objective marker when perceived effort alone might be skewed by nerves or adrenaline on race morning. The more useful skill is being able to move between the two: starting a race with a pace-based plan in mind, then trusting effort to guide the adjustments once conditions, fatigue or terrain make the original plan unrealistic to hold exactly.