Running by feel sounds simple, but most runners don’t actually trust it yet.
They either ignore their watch completely or stare at it so much they forget what effort feels like.
RPE works best when it’s trained — not guessed.
That means occasionally checking your feel against pace or heart rate, especially when conditions change or fatigue creeps in.
In this article I’m gonna do my best to show you how to use RPE the right way: how to calibrate it, when to trust it over numbers, and how it helps you train smarter in heat, hills, trails, wind, and tired legs — without turning every run into a data obsession.
The Full Story
Running by feel is the ultimate goal—but let’s be real, sometimes your “feel” needs a little gut check.
That’s where comparing RPE (Rate of Perceived Effort) with heart rate and pace once a week can help.
Think of it as tuning your internal GPS.
You don’t need to obsess over numbers every run—but one intentional check-in each week can help make sure you’re reading your effort right.
Here’s how I like to do it: pick a steady run. Every mile, I mentally rate my effort—maybe a 5 out of 10 feels about right.
Then I glance at my pace or heart rate (if I’m wearing a monitor).
Did my “easy” RPE 5 line up with my normal easy pace? Was my heart rate chilling in Zone 2 like it should be?
If not—dig in. Let’s say you felt it was an RPE 4, but your heart rate’s spiking.
That’s a red flag.
Maybe you were dehydrated, stressed, under-recovered—or maybe you just misread your effort.
On the flip side, if you felt like you were dying at RPE 8 but the pace was sluggish, that could mean you’re carrying fatigue.
It felt hard because you are tired—even if the numbers don’t scream it.
This kind of cross-check is like stepping on a scale with a known weight once in a while—just to see if it’s still accurate. You’re training your brain to get better at reading your own signals.
Now, don’t get me wrong—there are runs where you ignore the data and listen to the legs.
That’s not laziness—that’s smart running.
Let’s say you planned an 8:30/mile easy run, but it’s 90 degrees and humid.
If that pace suddenly feels like an RPE 7 (which should feel more like a tempo), you slow down.
Don’t be a slave to the watch. I’ve done plenty of these runs where I back off to 9:30 or even 10:00/mile, and guess what? That keeps the effort where it belongs—easy. Heart rate agrees. Boom—smart adjustment.
Here’s another example: you’re in the middle of a tempo run, targeting a steady heart-rate zone, but you feel your effort climbing faster than your HR shows.
That’s a clue.
Maybe cardiac drift hasn’t caught up yet—but your body’s warning light is already blinking. Time to dial it back or cut the run short. I’ve done this more than once and saved myself from blowing up.
Some GPS watches let you log your RPE after a run. I recommend doing this. You’ll start to see trends like: “When my RPE is higher than expected for pace, I need more recovery.” That kind of info is gold for tweaking your training week to week.
My best advice? Once a week, check your RPE against pace or HR. Use it like a tune-up for your internal gauge. If things feel off, figure out why, adjust, and move on.
Mastering RPE on Tough Terrain and Wild Weather
Want to supercharge your effort-sensing skills? Train where pace becomes useless.
Seriously—trail runs, hills, crazy heat, brutal wind… these conditions force you to run by feel. And that’s where RPE becomes your secret weapon.
Trails: Ditch the Pace, Lock in the Effort
The pros know that to survive a 100K with 10,000 feet of climb, you have to run by feel.
So they hike the steep stuff when RPE climbs too high (like RPE 7+), and then flow on the downhills while keeping the same moderate effort.
Try it yourself: on your next trail run, pick an RPE (say 4–5) and stick with it, no matter how slow you move uphill. Let your body guide the effort. That’s real control.
Hot & Humid Days: RPE Saves Your Butt
In the heat, pace is straight-up misleading.
That 8:45/mile you cruise at in spring? It’ll feel like death in 90-degree heat.
Your heart rate’s already 20 bpm higher.
And before you know it—you’re cooked.
Here’s what I tell my athletes: screw the pace.
Pick an easy RPE (like 3 or 4), and just hold that. Let the heat slow you down. You’ll breathe heavier, sweat buckets, and move slower—but you’ll finish the run without ending up on the sidewalk dry-heaving.
One guy told me, “I used to push through in the heat… until I ended up dizzy and dragging. Now I just go by effort, and it saves me every time.”
Wind: Learn the Art of Not Fighting It
Wind can be a silent killer—especially headwinds. Too many runners burn out fighting it just to “hold pace.” That’s a mistake.
Instead, run by RPE. Into a headwind, a solid RPE 5 might mean a slower pace—and that’s fine. With the wind at your back, same RPE might give you race-pace splits without even trying.
Fun workout: do an out-and-back run on a windy day. Keep RPE 5 both ways. Going out will feel slow. Coming back will feel like flying. Effort stays steady—that’s what matters.
Hills: Control the Urge to Crush
Even if you don’t trail run, find a hilly loop and run it by effort, not pace.
When you charge hills by pace, you blow up early. When you respect effort, you finish strong.
Shorten your stride uphill, keep breathing steady, and hold your RPE to just one point above your flat-ground easy effort. That might mean walking a bit—and that’s okay. Then use gravity to your advantage downhill, without hammering.
The best hill runners know: it’s not about speed—it’s about control.
My best advice? Pick one run a week to be your “RPE focus” workout.
Could be trails, hills, heat, wind—whatever’s gnarly. Tune in to effort. Tune out the numbers.
Run Low, Feel More: Training in the Trenches
You ever go for a run the morning after a brutal workout? Legs feel like bricks, lungs dragging behind? Good. That kind of run teaches you something no pace chart ever could.
I call these “fatigue runs” or “train-low” days — when you purposely run easy on tired legs or low fuel.
I’m not talking about punishment here. I mean using that state to learn. Run by effort, not pace. Tune in. Your body’s giving you signals — RPE (Rate of Perceived Effort) becomes your compass.
Sometimes I’ll tell my runners to finish their long run without checking pace — just hold a steady RPE as the miles wear on. It’s not about speed then. It’s about holding the line when your energy dips. That’s marathon practice right there. When race day comes and you hit mile 20, you’ll know how to manage effort, not panic.
Now, running low on carbs occasionally — yeah, it makes the run tougher. But that’s kind of the point. Just don’t overdo it. Once in a while is enough. Think of it like altitude training for your grit.
Putting RPE Into Your Training Plan
Here’s something I see runners skip way too often: they follow a plan, but never ask, “What should this feel like?”
If you’re running 5 x 1K at 5K pace, write it out: “RPE 8–9.” That anchors you.
Even if your GPS goes haywire or wind slaps you in the face, you’ll still know how the reps should feel.
Long run? “2 hours at RPE 4, finish last 20 mins at RPE 6.” Now we’re training smart.
Some coaches (myself included) build full plans based on effort zones. Not pace. Not heart rate. Just feel. Even if you’re a pace junkie, run both tracks: one foot in data, the other in perception.
Goal Setting with RPE
Don’t just chase finish times — think about how you want to run the race.
Example: “First half at RPE 6. Second half, push to RPE 8.”
Boom. That’s a process goal. You nail the execution, and the time often follows. Most of my PRs happened when I stopped watching the clock and started racing by feel.
Conclusion
Think of RPE like a muscle.
Use it. Rate your runs. Journal it. Compare it to pace and heart rate. Over time, that RPE “muscle” gets strong.
You’ll get so dialed in, you’ll be able to guess your splits within 10 seconds without ever looking at your watch.
Human GPS, baby.
Thank you for stopping by.
Keep training strong.