Personal Record Gap Calculator
The formula
What the pb project tells you
A feasibility read on a goal time: the gap in seconds, as a percent, spread across the weeks left in the block.
Calculation: Gap % ÷ weeks = required weekly pace drift; per-100 terms. Enter your inputs and every substitution is shown below the result.
Reading the result
Under 0.5 % per week is coachable with two hard sets; above 1 % per week is usually meet-day magic on the calendar already.
Rules of thumb: 1–3 % drops per 8–12 week block are the standard PB project sizes
Limitations and best practice
Counting weeks from today over-counts: subtract a taper — the last 10 days build speed, they do not build it from scratch.
This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Frequently asked questions
Does the same math work for records?
What if the gap is over 8 %?
Source & methodology
Goal-setting practice; linear pace-drift heuristic.
Personal Record Gap: the number, the method and the caveats
This page was written for one job: turning your own inputs into a defensible figure, with the working shown. Searchers land on a Personal Record Gap page for three reasons — to plan, to compare options, and to check that somebody else’s arithmetic is honest. This tool serves all three, and everything after the calculator explains the model instead of hiding it.
A calculation like this one is worth roughly as much as a careful sentence: it forces several vague considerations into one comparable quantity. Once Personal Record Gap is on the table, the argument can stop being about impressions.
Individual variation is large here: limb proportions, fibre mix and history all shift how a population-average Personal Record Gap maps to you. Use it as a starting prescription, then let performance feedback over weeks tune it.
Nothing below is stock text pasted around a number: the worked example computes required drop = -1.0 s from this tool’s own defaults, and the sensitivity section ranks the inputs that move the result — Target PB first, at ≈570.0 % of the headline for a ten-percent error either way in that input. Read the sections in order and you will be able to reproduce every figure by hand.
Inside the Personal Record Gap calculation: formula and every input
The engine implements a single stated model: Gap % ÷ weeks = required weekly pace drift; per-100 terms. There is no hidden coefficient and no login-gated precision — the formula printed is the formula executed, which is also what makes the result citable.
Current best (s) (example value 56) is a plain measured quantity — the unit shown in the label is the unit the formula expects. If you are unsure what belongs in this field, look at the printed steps: the substitution shows exactly how the engine uses it.
Target PB (s) (example value 57) is a measured number in the unit named by the label; the formula does not convert for you. Replace the example with the figure from your own records — the tool recomputes instantly and the printed steps follow your numbers.
Weeks to goal (example value 12) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. Be precise about the boundary (exact date, start of month); time inputs decide the exponent in most formulas.
Event distance (m) (example value 93) is a quantity rather than a category — precision here is cheap and worth having. Small measurement errors grow here: a length that is squared or cubed in the model magnifies a one-percent slip into a three-percent answer.
The default Personal Record Gap calculation, written out in full
The tool prints its own working; this is the same arithmetic on the example values, reproduced so you can follow it by hand. Starting figures: Current best (s), Target PB (s), Weeks to goal, Event distance (m). Run to the end, the required drop resolves to -1.0 s — Dropping -1.0 s (-1.8 %) in 12 weeks means -1.08 s per 100 m — about -0.15 % of pace per week, which is a form-tune-up, not a project on the bands this tool uses.
- Gap = 56.0 − 57.0 = -1.0 s = -1.8 %
- Per 100 m of the event: -1.08 s
- ÷ 12 wk = -0.15 %/wk
As % of current — -1.8%. Read next to the headline, this is the figure that shows the shape of the trade-off.
Per 100 m — -1.08 s. If your inputs change, this is usually the first companion figure to move.
Weekly pace drift — -0.15 %/wk. This is the number experienced users quote when the headline alone would mislead.
New CSS hint — 55.0 s/100. If your inputs change, this is usually the first companion figure to move.
Keep this worked example open while you enter your own figures: matching the shape of the substitution is the fastest way to spot a unit or convention mistake.
The Personal Record Gap corridor: your result across a realistic band
Read this table as the practical error bar on the headline figure. It answers the question people actually have after seeing a single number: how wrong could this be if the main input is off by ten or twenty percent?
| Target PB setting | Required drop |
|---|---|
| 80 % of the example value | 10.4 s |
| 90 % of the example value | 4.7 s |
| example inputs | -1.0 s |
| 110 % of the example value | -6.7 s |
| 120 % of the example value | -12.4 s |
The corridor runs from -12.4 s to 10.4 s across that band — which is the range worth planning inside rather than the single -1.0 s point estimate. Reproduce it in the form above by editing Target PB alone; the substitution steps will follow your figures exactly.
Where Personal Record Gap is fragile — and where it is not
This list was computed for this specific engine just now: each numeric input was nudged ±10 % while every other field held its example value, and the required drop was recalculated from scratch. For Personal Record Gap the ranking is measured rather than guessed, and it belongs to these defaults: shift the starting point and the order can shift with it.
- Target PB +10 % → Personal Record Gap = -6.7 s · −10 % → 4.7 s (the required drop shifts ≈570.0 %)
- Nudge Current best by ±10 % and Personal Record Gap lands between -6.6 s and 4.6 s (sensitivity ≈560.0 %)
Target PB is the dominant lever here: ten percent either way moves the result by about 570.0 %, from -6.7 s to 4.7 s. Spend your verification effort there first, and Current best is effectively tied with it (≈560.0 % for the same nudge), so verify the pair together. The rest of the inputs earn only a rounding-error of attention, and that asymmetry is the practical payoff of measuring rather than asserting.
Is your Personal Record Gap good — reading the result bands
Nobody acts on a bare figure — they act on a figure with a comparison attached. The default case lands in the “Dropping -1.0 s (-1.8 %) in 12 weeks means -1.08 s per 100 m — about -0.15 % of pace per week, which is a form-tune-up, not a project” band, and bands are deliberately wide because real situations overlap. How much of that band is luck? On Target PB alone ten percent either way covers -6.7 s to 4.7 s. The practical reading rules: read the band as a starting hypothesis, then test it: change the two dominant inputs by ten percent and see whether the verdict survives. Verdicts that survive stress are the ones worth acting on.
Set Personal Record Gap beside its neighbours and it usually plays a specific role: this figure establishes the size of something, and the neighbouring tools establish whether that size is acceptable. Skipping the first step makes the second one arbitrary.
How people get Personal Record Gap wrong
Counting weeks from today over-counts: subtract a taper — the last 10 days build speed, they do not build it from scratch. This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Confusing a large number with an important one. Personal Record Gap can be dominated by one input whose absolute value looks unimpressive, which is why this page ranks influence separately from magnitude.
One mistake is specific to this engine: assuming every input matters equally. The computation above shows Target PB dominating — a careful figure there beats false precision everywhere else.
Another is comparing across contexts: a Personal Record Gap computed with one set of conventions should never be lined up against a figure computed with another. Check the inputs behind both before ranking them.
Six things to confirm before acting on Personal Record Gap
- Record the date and the inputs alongside the number so future-you knows what was assumed.
- State, in one sentence, which convention each rate, unit or period in the form is using.
- Check Target PB before anything else: it is the measured dominant input, ≈570.0 % of Personal Record Gap per ten percent.
- Verify each input against its original source document, not memory.
- Confirm the example values are plausible for your own situation before replacing them.
- Confirm the answer against one independent method or published benchmark for Personal Record Gap.
Step by step: getting a trustworthy Personal Record Gap out of this tool
Using a calculator well sounds trivial, but the difference between a decision-grade figure and a throwaway one lives entirely in the routine. The routine for Personal Record Gap takes a minute to learn and applies to every input above.
Step 1 — gather before you type. Personal Record Gap depends on current best (s), target pb (s), weeks to goal, event distance (m). Collect them from a source document — a statement, a report, an invoice, a log — rather than from memory, because recalled inputs are the single largest cause of wrong results. Numbers are cheap to produce and expensive to retract; the extra minute is the cheapest insurance available.
Step 2 — baseline before exploration. Get one defensible Required drop on screen before you start nudging numbers. Without a baseline, every variation looks interesting and none of them means anything. Note the assumption you are least sure about; that is where the real risk lives.
Step 3 — play with the inputs on purpose. Ten percent up, ten percent down, one field at a time. Within a few minutes you will know this calculation better than most people who quote its results. When two sources disagree, it is almost never the arithmetic that differs.
Step 4 — stress before you commit. A decision that survives a ten-percent squeeze on its two biggest inputs needs no luck to be sound. One that does not survive is a decision about hope, not about arithmetic. Suspiciously tidy answers deserve the same scrutiny as untidy ones.
Step 5 — schedule the next run. In Fitness & Sports the inputs drift quietly. Put a reminder a quarter out, re-enter the same fields, and read the change rather than the level. A figure nobody can reproduce is a figure nobody will act on twice.
The real-world conversations Personal Record Gap settles
In Swimming the figure computed here is usually the first one somebody asks to see. Having it — with the formula behind it — changes your position in the conversation from participant to reference. Comparisons are cheap: run the identical calculation for the alternative and look at the gap.
Used properly this is a five-minute filter that saves weeks. Compute Personal Record Gap, reject what fails, and only then bring in the expensive analysis for the survivors. If the verdict changes with a ten-percent nudge, report the nudge alongside the number.
Treat Personal Record Gap like a smoke alarm rather than a painting — its value is in being tested periodically, not in being admired once. Compare the calculation to the rough guess you arrived with, and ask why they differ.
People also ask about Personal Record Gap
What affects Personal Record Gap the most?
Personal Record Gap is driven above all by Target PB. Perturbing only that field by ten percent either way produced -6.7 s against the -1.0 s baseline — a ≈570.0 % response, while Current best manages ≈560.0 %.
Do current best and target pb matter equally?
Effectively. Measured on this engine they land at ≈570.0 % and ≈560.0 % for the same ten-percent nudge, so the honest advice is to get both right; chasing precision in only one of them buys almost nothing.
What is a typical Personal Record Gap?
On the worked example above Personal Record Gap comes out at -1.0 s. Treat that as one point on a distribution rather than a norm: the bands, the companion outputs and the sensitivity ranking tell you how wide the plausible range really is.
How do I calculate Personal Record Gap by hand?
Gap % ÷ weeks = required weekly pace drift; per-100 terms is the entire method. Work the inputs in that order — Gap = 56.0 − 57.0 = -1.0 s = -1.8 % — and you will reach -1.0 s on the default figures, the same number this tool prints.
What happens to Personal Record Gap if target pb changes by 10 %?
The engine was re-run with that field moved by ten percent while everything else stayed fixed: the required drop goes across -6.7 s to 4.7 s, a swing of roughly 570.0 % around the -1.0 s baseline. That ratio is the practical definition of how much this input matters.
Is the Personal Record Gap result of -1.0 s good or bad?
Neither, on its own — the label “Dropping -1.0 s (-1.8 %) in 12 weeks means -1.08 s per 100 m — about -0.15 % of pace per week, which is a form-tune-up, not a project” is the band this figure falls in for the example inputs, and your own inputs will place you elsewhere on the same ladder. Judge the number against your history and your alternatives, and remember that a ten-percent error in Target PB alone moves it by ≈570.0 %.
Can Personal Record Gap be negative or empty?
Yes, and that is informative rather than broken: a negative Personal Record Gap usually means the inputs encode an outflow or a shortfall, and the verdict band above labels exactly that situation instead of hiding it.
What affects Personal Record Gap the most?
Sensitivity depends on where you start, but the inputs Current best (s) and Target PB (s) typically move Personal Record Gap further than the rest because they enter the formula multiplicatively. If you can only measure two things well, measure those and hold the others at conservative defaults.
Does the same math work for records?
Against the WR the % gap is the same ruler — use it with the %WR engine.
What if the gap is over 8 %?
Split it into two PBs: chase the midpoint, re-time the project, then go again.
Is my data private on this page?
Yes — computation happens locally in your browser, with no account, no tracking of your inputs and nothing sent to a server. The printed formula is the whole story of what happens to your figures.
The vocabulary of Personal Record Gap
- As % of current
- -1.8% in the default Personal Record Gap calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Per 100 m
- -1.08 s for the Personal Record Gap worked case; it sits next to the main result because it carries context the headline leaves out.
- Weekly pace drift
- -0.15 %/wk for the Personal Record Gap worked case; it sits next to the main result because it carries context the headline leaves out.
- Required drop
- The primary output of this tool: -1.0 s for the default inputs, computed exactly from Gap % ÷ weeks = required weekly pace drift; per-100 terms.
- Worked example
- The step-by-step substitution printed above, so the arithmetic can be re-derived by hand or in a spreadsheet.
- Verdict band
- The plain-language label — here “Dropping -1.0 s (-1.8 %) in 12 weeks means -1.08 s per 100 m — about -0.15 % of pace per week, which is a form-tune-up, not a project” — mapping the computed figure onto experience-based ranges for Fitness & Sports.
- Sensitivity (±10 %)
- How far the Personal Record Gap moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
Where the Personal Record Gap model comes from
The model is published arithmetic implemented exactly as written: Gap % ÷ weeks = required weekly pace drift; per-100 terms. Source of record: Goal-setting practice; linear pace-drift heuristic. Specialist software layers extra coefficients on top of the same algebra; none are hidden here, and that transparency is what makes a disagreement traceable to a specific input instead of a black box.
Treat the output as a precise answer to the question you typed: exact arithmetic, transparent formula, published source, no hidden rounding. Nothing is smoothed, weighted or adjusted behind the scenes; where judgement enters, this page says so and names the input responsible.
What to do with your Personal Record Gap next
Save the number together with its inputs and today’s date; a Personal Record Gap figure without context is unusable the moment an input changes.
Whoever you are (people who need one trustworthy number before their next decision), the next step is the same: replace the example inputs with your own, note the date, and re-run whenever a figure moves. In Fitness & Sports, a dated figure is a trend, and an undated one is a rumour.