PoinT GOResearch
research·research·velocity based training

Why a Two-Load LV Profile Gives You the Wrong 1RM

A two-load velocity profile can be off by 10-20% on your 1RM when the loads sit too close together or bunch at one end. Here's why - and the fix.

PoinT GO Research Team··9 min read
Why a Two-Load LV Profile Gives You the Wrong 1RM

A coach messages you before Tuesday's session: the two-point LV test says the squat 1RM jumped from 152 kg to 168 kg in eleven days. Nobody adds 16 kg to a back squat in eleven days without a very good explanation, so before anyone reprograms percentages off that number, something needs checking - and it usually isn't the athlete's strength that changed.

The two-point load-velocity method earned its popularity honestly. Instead of a maximal-effort 1RM test, you take two submaximal sets - often folded straight into the warm-up - fit a line through the velocity readings, and extrapolate to the athlete's known minimum velocity threshold. Done well, it is accurate to within a few kilograms. Done with the wrong pair of loads, it produces a number that looks exactly as confident as the good version, because a straight line drawn through two points never looks messy. The problem isn't visible in the output. It's in which two loads you picked.

The Regression Math Nobody Explains Before You Test

Every load-velocity extrapolation runs on the same equation: estimated 1RM = a − (b × MVT), where the slope b and intercept a come from the two measured points. The slope is nothing more than the change in velocity divided by the change in load between your two data points. Shrink that load gap and the denominator shrinks with it - so any noise in the velocity readings, even the ordinary ±0.02-0.03 m/s variation you get from rep to rep on the same load with a linear position transducer or IMU, gets divided by a smaller number and comes out the other side as a much bigger swing in the slope.

That swing gets multiplied again on the way to the 1RM, because the minimum velocity threshold typically sits well outside the two loads you tested - often 0.15-0.30 m/s below the lighter point. Extrapolation error scales with how far you're reaching past your data, so a slope that's already unstable from narrow spacing gets stretched even further from the truth once you extend it out to MVT.

Here's the detail most two-point protocols never mention: a straight line drawn through exactly two points has an R² of 1.0, always, by definition. There is no possible pair of velocity readings that produces a bad-looking fit on a two-point graph - the mathematics guarantees a perfect line every time, whether the underlying data is trustworthy or garbage. A four- or six-load profile lets you eyeball whether the points actually sit on a line; a two-point profile gives you no such check. The only lever available is choosing the two loads correctly before testing, not evaluating the fit after.

What Happens When the Two Loads Sit Too Close

García-Ramos and colleagues (2018) put this directly to the test in the bench press, working with 30 resistance-trained men and comparing six two-load pairings drawn from 20%, 45%, 60%, 75%, and 90% of 1RM against each subject's directly tested maximum. The pattern was consistent: pairs separated by roughly 30% of 1RM or more (20-60%, 20-75%, 45-75%) produced a standard error of estimate around 2.6-4.2 kg - close to what a full multi-load profile achieves. Pairs separated by less than 15-20% of 1RM (45-60%, 60-75%) pushed the SEE past 8-11 kg, and individual predictions in that narrow-spacing group missed the true 1RM by more than 15 kg in several cases.

Two limitations are worth flagging before generalizing this to your own gym: the study tested a single exercise in one session per condition, saying nothing about between-session reproducibility or about squat and deadlift, where bar-path constraints differ, and it drew on population-level analysis rather than every subject's own previously-established MVT for every pairing - closer to a best-case scenario than how most coaches actually run the two-point method. If anything, that makes the narrow-spacing error rates a floor, not a ceiling.

The Other Failure Mode: Both Loads Bunched at One End

Narrow spacing in the middle of the range - say, 70% and 78% - is one problem. A separate problem shows up when the two loads sit at the same end of the usable range, even when the raw percentage gap looks acceptable on paper.

At the light end, the issue is resolution relative to noise: velocity differences between two light loads are large in absolute terms, but small technique inconsistencies - bar path drift, a rushed setup, a rep taken without full intent - show up as a larger share of that light-load velocity signal than they would at a heavier load. Two loads both under roughly 40% 1RM tend to produce a shallow-looking line that, extended all the way out to MVT, systematically overshoots the true 1RM.

At the heavy end, the mechanism reverses. Testing two loads both above roughly 80% 1RM in the same session means the second set carries real residual fatigue from the first - not enough to feel like a grinder, but enough to shave 0.02-0.04 m/s off a rep that would have moved faster fresh. That shaved velocity steepens the apparent slope and pulls the extrapolated MVT crossing point closer, which underestimates 1RM.

Banyard, Nosaka, Vernon, and Haff (2018) offer useful supporting evidence here, even though their study wasn't designed around two-point spacing directly. Profiling squat and bench press across a full 6-load range, they found the y-intercept parameter - the exact term that anchors where the extrapolated line lands - carried roughly double the between-session variability of the slope parameter, with a coefficient of variation in the 8-9% range against 4-5% for slope. The y-intercept is disproportionately sensitive to exactly the conditions narrow or lopsided load selection creates: a poorly constrained line pivoting on unstable ground.

Which Way the Error Runs: Overestimate or Underestimate

Put together, the two clustering failure modes run in opposite directions, which is exactly what makes a single does-this-look-reasonable gut-check unreliable. Light-end clustering inflates the 1RM estimate. Heavy-end clustering deflates it. Narrow mid-range spacing can go either way depending on which side the day's measurement noise happens to fall on - which is worse in practice, since it means retesting the same athlete with the same narrow pair on different days can produce a rising or falling number that has nothing to do with real strength change.

Load Pair (%1RM)SpacingTypical BiasApprox. Error vs True 1RM
30% / 85%55%Minimal2-5%
45% / 80%35%Minimal3-6%
70% / 80%10%Unstable, either direction8-15%
85% / 92%7%Underestimates6-12%
20% / 30%10%Overestimates15-25%
30% / 40%10%Overestimates10-18%
80% / 92%12%Underestimates10-20%

The ranges above are a synthesis of the spacing effects described in this piece applied across common load-pair choices, not a single study's exact output. The direction of the bias is the reliable part; the exact percentage moves with the individual and the exercise.

A Worked Example: Same Athlete, Three Load Pairs, Three Different Numbers

Here's how that plays out with one athlete's numbers, reconstructed from a training log to keep the arithmetic honest. True back squat 1RM, established two weeks earlier by direct test: 140 kg. Individual MVT from that same session: 0.32 m/s.

Pair A, narrow and mid-range - 105 kg (75%) at 0.52 m/s and 115 kg (82%) at 0.48 m/s. That's a 10 kg spread producing only a 0.04 m/s velocity difference. Add the kind of noise you'd expect from an ordinary session - say the 105 kg rep actually moved at 0.54 m/s rather than 0.52 - and the extrapolated 1RM shifts from roughly 138 kg to 156 kg. A two-value error you'd never notice on the velocity readout becomes an 18 kg swing in load prescription.

Pair B, clustered light - 42 kg (30%) at 1.02 m/s and 56 kg (40%) at 0.89 m/s. Extrapolating that shallower line out to 0.32 m/s lands at roughly 158 kg, 13% above the true 140 kg.

Pair C, wide and properly spaced - 56 kg (40%) at 0.89 m/s and 119 kg (85%) at 0.45 m/s. Same athlete, same MVT, extrapolated 1RM: 143 kg, within 2% of what a maximal test would have given.

Same athlete, same day, three plausible testing choices, three answers ranging from 138-156 kg to 158 kg to 143 kg. Only one of those is close enough to actually program off.

How to Choose Load Pairs That Actually Hold Up

The fixes here are load-selection rules applied before the bar goes on the rack, not corrections applied to the number afterward.

  1. Separate the two loads by at least 30% of 1RM, and treat 35-40% as the safer working target when time allows.
  2. Put one load below roughly 55-60% 1RM and the other above it - straddling the middle of the usable range rather than sitting both loads on the same side.
  3. Use each athlete's own previously-established minimum velocity threshold, taken from a genuine maximal attempt, rather than a population-average MVT value.
  4. Take 3 reps per load with full concentric intent on every rep, discard the first rep as a warm-up artifact, and average the remaining two for the velocity value that feeds the regression.
  5. Leave at least 3-4 minutes of rest between the two loads when the heavier one sits above 80% 1RM, specifically to avoid the fatigue-compression effect that biases heavy-end pairings low.

A pair like 40-45% paired with 80-85% 1RM satisfies all five conditions for most lifters and remains the combination most often recommended in the two-point literature for exactly that reason.

When a Third Point Is Worth the Extra 90 Seconds

The two-point shortcut earns its keep on athletes you already know well: an established MVT, a stable training history, no recent layoff. New athletes, anyone returning from more than a couple of weeks off, and anyone whose 1RM you suspect has moved by more than 5% since the last check don't fit that profile yet - and that's exactly when a two-point line has no built-in way to tell you it's wrong.

Adding a third load at roughly 55-65% 1RM costs about 90 extra seconds and turns an unverifiable two-point line into a checkable three-point one. If the third point sits close to where the two-point line predicted, that's real confirmation instead of an assumption. If it sits noticeably off the line, a bad extrapolation gets caught before it turns into next week's training percentages - a considerably cheaper mistake to catch in a warm-up set than in a missed heavy single three weeks later.

FAQ

Frequently asked questions

01How far apart should the two loads be in a two-point load-velocity profile?
+
Thirty percent of 1RM is the practical floor - García-Ramos et al. (2018) found pairs spaced 30% or more apart held SEE around 2.6-4.2 kg, while anything under roughly 15-20% pushed error past 8-11 kg in their bench press data. Aim for 35-40% separation when the schedule allows it, and treat anything under 20% as a warm-up set rather than a testing pair.
02Can a two-point profile underestimate 1RM, or does it only ever inflate the number?
+
It can run either direction. Clustering both loads at the light end of the range tends to overestimate, because the shallow line extrapolates too far past where it was actually measured. Clustering both loads near the heavy end tends to underestimate, largely because residual fatigue between two near-maximal sets compresses the second velocity reading and steepens the apparent slope. Narrow spacing in the middle of the range can go either way depending on which side the day's measurement noise falls on.
03If two-point profiling has this many failure modes, is it still worth using?
+
Yes, with the load-pair rules applied deliberately rather than picked out of convenience. The method's whole appeal is replacing a maximal-effort test with two warm-up sets, and when the loads are spaced correctly - roughly 35-40% 1RM apart, straddling the middle of the range, using an individually established MVT - the accuracy holds up close to what a full multi-load profile achieves. The failure modes described here come almost entirely from load-pair shortcuts, not from the two-point concept itself.
04Can I just check the R² value to see if my two-point line is trustworthy?
+
No, and this is the part that catches people out. A straight line drawn through exactly two points has an R² of 1.0 by mathematical definition, regardless of whether the underlying velocity readings are good or noisy. There is no fit-quality signal available from a two-point test after the fact. The only real safeguard is choosing appropriate load spacing before testing, or adding a third load so there's an actual line to evaluate.
05My two-point profile says this week's 1RM dropped 8% from last week - is that the spacing problem or real fatigue?
+
Check the load pair first before assuming a performance change. If the two loads used this week were spaced under 20% apart, or both landed on the same end of the range compared to last week's pair, the spacing itself is the more likely explanation - an 8% swing is well within what narrow or lopsided pairs produce on their own. If the pairs were consistent and well-spaced both weeks, treat the drop as a genuine signal worth investigating, with accumulated fatigue, sleep, or a technique change as the usual next places to look.
Keep reading

Related Articles

research

Load-Velocity Profiling for 1RM Prediction: Accuracy Review

Can load-velocity profiling replace a maximal 1RM test? This review breaks down error rates by method and which protocols hold up in practice.

research

Minimum Velocity Threshold (MVT): Comprehensive Research Review

A fixed MVT can misjudge your squat 1RM by over 15 kg. This review explains why minimum velocity threshold swings 70% between lifters and how to set yours.

research

Load-Velocity Relationship Accuracy Meta-Analysis

A meta-analysis of load-velocity relationship accuracy in VBT: where error creeps in, how exercises compare, and which sensors you can trust in the gym.

research

Force-Velocity Profile: The Complete Guide for Athletes and Coaches

Most athletes are force-dominant or velocity-dominant without knowing it. Here's how to build your F-V profile with Samozino's method and fix the gap.

research

Power Output Decline as a Fatigue Monitoring Tool

What does research say about tracking power output decline to flag fatigue in strength and power athletes? A systematic review of intra-session drop-off.

research

Velocity Loss Thresholds: Hypertrophy vs Power Outcomes

A head-to-head synthesis of 10%, 20%, and 30% velocity loss thresholds — which produces more power, which builds more muscle, and where they overlap.

research

Rising Velocity Mid-Block: Real Gain or Artifact?

Velocity climbing at the same load mid-block? A checklist for telling real strength adaptation apart from technique cleanup and plain measurement noise.

research

When VBT Velocity Jumps After Caffeine: Reading It Right

A caffeine-driven bar speed jump isn't a strength gain. How to separate stimulant-driven VBT velocity spikes from a real 1RM improvement, with numbers.

Measure performance with lab-grade accuracy

Get PoinT GO