Quick Answer: RPE tracking transforms your training log from a simple weight record into a genuine performance dataset. The best apps for this are built around set-level RPE entry with trend analytics โ and Gladiator Lift is the strongest option available for strength athletes who want to autoregulate intelligently.
RPE โ Rate of Perceived Exertion โ is the most powerful tool modern strength athletes have for managing training intensity. And it's wildly underused, mostly because most tracking apps treat it as an optional text field rather than a first-class data point. This guide changes that.
We'll cover the science of RPE, how to use it correctly, which apps support it properly, and why Gladiator Lift has built its entire training framework around RPE as a primary input rather than an afterthought.
The Science of RPE in Strength Training
RPE in strength training uses a modified version of Borg's original scale, adapted for resistance training by Dr. Mike Tuchscherer and popularized through Reactive Training Systems. The relevant scale runs from 1 to 10:
| RPE | Description | Practical Meaning |
|---|---|---|
| 6 | Moderate effort | Could do 4+ more reps |
| 7 | Somewhat hard | Could do 3 more reps |
| 8 | Hard | Could do 2 more reps |
| 9 | Very hard | Could do 1 more rep |
| 9.5 | Near maximal | Might have 1 more rep |
| 10 | Maximal | Could not do another rep |
For strength training purposes, most working sets fall in the RPE 7โ9 range. Hypertrophy work sits around RPE 7โ8. Strength work targets RPE 8โ9. Peaking work approaches RPE 9โ10.
The critical insight: the same weight produces different RPEs on different days. If 315 lbs for 3 reps feels like RPE 8 one session and RPE 9.5 the next, that's not inconsistency โ it's real physiological information. You're more fatigued, less recovered, or under more systemic stress in the second session. A good training app captures this signal and acts on it.
Why Most Apps Get RPE Wrong
The common implementation of RPE in general fitness apps looks like this: a text field at the session level where you can optionally type a number. This is nearly useless for serious training because:
Session-level RPE is too coarse. Your squat might be RPE 9 while your accessory bench work is RPE 7 in the same session. A single session-level RPE number loses all that nuance. Optional entry means inconsistent data. If RPE is optional and you skip it when training feels fine (i.e., when the data would show low RPE), you end up with a dataset biased toward high-RPE sessions only. The average looks terrible. No trend analysis means no actionable insight. Logging RPE without analyzing trends is like taking a patient's temperature without recording the results. The number is meaningful only in context.Gladiator Lift solves all three problems by treating RPE as a required set-level field with automatic trend surfacing.
How Gladiator Lift Implements RPE Tracking
Gladiator Lift integrates RPE at three levels of granularity, each serving a different analytical purpose: Set-level RPE is the foundational input. After completing each working set, the app prompts you to log the RPE. This takes about two seconds and creates the richest possible dataset. Over time, you can see how your RPE at a given percentage changes across a training block โ the hallmark of a fatigue accumulation and recovery cycle working correctly. Lift-level RPE trends aggregate your set-level data per movement. Gladiator Lift shows you rolling 4-week averages of your squat RPE at given load zones, so you can see whether 80% of your max is getting easier (RPE dropping) or harder (RPE rising) over time. Session-level RPE summary is auto-calculated from your set data โ no manual entry needed. This lets you see your overall training stress across a week or month without any additional logging.Setting Up RPE-Based Autoregulation
Autoregulation means adjusting your training load in response to real-time performance feedback rather than adhering rigidly to a pre-written prescription. Here's how to implement it step by step in Gladiator Lift:
- Establish your RPE calibration baseline. In your first 2โ4 weeks of logging RPE, your numbers will be approximate. Most lifters underestimate RPE initially. Log anyway โ calibration happens through repetition.
- Program to RPE targets, not just percentages. Instead of "5ร3 at 82%," program "5ร3 at RPE 8." Gladiator Lift supports both inputs. RPE-based loading is more flexible and adapts to your daily readiness.
- Use the RPE-to-percentage table. At a given rep count, specific RPEs correspond to specific percentages. For example, a 3-rep set at RPE 8 is approximately 86% of your 1RM. The app maintains this table for you.
- Identify your RPE tolerance window. Most programs are designed with a ยฑ0.5 RPE tolerance. If a set is supposed to be RPE 8 but lands at RPE 7, you can add weight. If it lands at RPE 9, you should drop weight on the next set.
- Review your RPE trends weekly. Gladiator Lift's weekly summary shows whether your RPE has been trending up (fatigue accumulating) or down (fitness improving). Use this to confirm or modify next week's load plan.
RPE Reference Charts for the Big Three
For practical application, here are approximate load-RPE relationships for the three primary barbell lifts. These assume solid technical execution โ RPE is not a substitute for good form.
Squat RPE/% Table (5-rep sets):| % of 1RM | Approximate RPE |
|---|---|
| 70% | RPE 6โ6.5 |
| 75% | RPE 7 |
| 80% | RPE 7.5โ8 |
| 85% | RPE 8.5โ9 |
| 90% | RPE 9.5โ10 |
Similar tables exist for bench press and deadlift (with slight differences based on individual mechanics). Gladiator Lift stores these tables and uses them when you switch between percentage-based and RPE-based programming.
RPE Tracking for Intermediate vs. Advanced Lifters
RPE tracking becomes more valuable as you advance, but the way you use it changes.
Intermediate lifters (1โ3 years of consistent training) primarily use RPE to avoid going too heavy. The biggest mistake intermediates make is grinding at RPE 10 every session. Staying at RPE 8โ8.5 for volume work allows more consistent training and better recovery. The app enforces this discipline by flagging sessions where your RPE is consistently above target. Advanced lifters (3+ years) use RPE for more nuanced management: detecting early fatigue signals before they become injuries, identifying peaking readiness (RPE dropping at a given load is a classic sign that you're ready to peak), and managing the trade-off between training density and intensity. Gladiator Lift surfaces different RPE analytics depending on your training profile, so the insights you see are relevant to where you are in your development.Apps Compared: Depth of RPE Implementation
| App | RPE Entry Level | RPE Trend Analysis | Auto-Load Adjustment | RPE-to-% Table |
|---|---|---|---|---|
| Gladiator Lift | Set-level | โ Full | โ | โ Built-in |
| Basic gym log | Session-level | โ | โ | โ |
| Advanced tracker | Session-level | Limited | โ | Manual |
| Powerlifting-specific app | Set-level | Partial | โ | External |
The difference between set-level and session-level RPE is not subtle โ it's the difference between a dataset that can drive training decisions and one that can't.
Building Long-Term RPE Intelligence
The most elite powerlifters and their coaches develop what might be called RPE intelligence โ the ability to accurately predict performance from feel, and to adjust programming preemptively based on subtle signals before performance drops.
Gladiator Lift accelerates this development by surfacing patterns in your RPE data that would take years to notice intuitively. When the app shows you that your RPE reliably spikes in Week 3 of any training block, or that your bench press RPE is disproportionately high relative to your squat RPE, you have actionable information.
The lifters who progress fastest aren't always the ones who train hardest. They're the ones who train most intelligently โ and in the modern era, that means using RPE data the way a serious athlete should. Gladiator Lift makes that level of intelligence accessible to any lifter willing to take two seconds after each set to log a number.