Handicap Calculator
The formula
What the handicap tells you
The club-handicap arithmetic: race targets set as a percentage off each swimmer’s own best, so one pool can decide several winners.
Calculation: Target = PB × (1 − handicap%); par-gap fairness check. Enter your inputs and every substitution is shown below the result.
Reading the result
A well-set handicap puts every swimmer within a fingertip of beating their own standard.
Rules of thumb: 5–8% handicaps typical over 50–400 m
Limitations and best practice
PBs that predate a stroke overhaul make the handicap a fiction — refresh the reference, then the percentage.
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
Why not time-on-handicap?
Is handicap used at invitationals?
Source & methodology
Club handicap conventions.
Handicap explained: formula, worked example and honest limits
You are here because you need a specific number, and you want to see how it was produced before you rely on it. There are plenty of pages about Handicap; almost none of them show the working. This one does: the formula, every input, a fully computed example, and a sensitivity analysis calculated live from this engine’s own defaults.
Most confusion about Handicap comes from mixing up the input you control with the input you merely observe. The formula treats them identically, but your decisions should not: one deserves measurement, the other deserves a defensible estimate.
Individual variation is large here: limb proportions, fibre mix and history all shift how a population-average Handicap maps to you. Use it as a starting prescription, then let performance feedback over weeks tune it.
Every figure in the prose is generated by the engine rather than written beside it — the worked example resolves to handicapped target = 67.20 s on the default inputs, and the sensitivity section ranks the inputs that move the result — Personal best first, at ≈10.0 % of the headline for a ten-percent error either way in that input. Work down the page and by the end you could re-derive the result in a spreadsheet from memory.
Every input in Handicap, and what it does to the answer
One formula, published in full: Target = PB × (1 − handicap%); par-gap fairness check. Anything you can read, you can reproduce in a spreadsheet, and that reproducibility is the whole point of printing it rather than hiding it behind a button.
Personal best (s) (example value 70) is a plain measured quantity — the unit shown in the label is the unit the formula expects. Replace the example with the figure from your own records — the tool recomputes instantly and the printed steps follow your numbers.
Standard time (s) (example value 60) is a plain measured quantity — the unit shown in the label is the unit the formula expects. Use the value as of today, not as of the last time you looked — time fields drift silently.
Distance (m) (example value 145) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. 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.
Handicap % (example value 4) is a plain measured quantity — the unit shown in the label is the unit the formula expects. Enter it exactly as your document states it — quoted annual, monthly and effective rates are three different numbers.
The default Handicap calculation, written out in full
Abstract formulas are hard to trust, so here is the complete substitution using the default inputs, written the way an examiner would want it. Starting figures: Personal best (s), Standard time (s), Distance (m), Handicap %. Run to the end, the handicapped target resolves to 67.20 s — A 4% handicap on a 70.0 s PB asks for 67.20 s — still 7.2 s off the 60 s standard: racing the handicap, not the field on the bands this tool uses.
- Target = 70.0 × (1 − 0.040)
- = 67.20 s
- Compare with the 60.0 s standard; the field races the clock
Gap to standard — -10.0 s. Read next to the headline, this is the figure that shows the shape of the trade-off.
% improvement asked — 4.0. If your inputs change, this is usually the first companion figure to move.
Per-100 equivalent — 46.34. Compare it against the main result of 67.20 s before drawing conclusions.
Fairness rule — handicap = % off own PB, never the winner’s. Compare it against the main result of 67.20 s before drawing conclusions.
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 Handicap corridor: your result across a realistic band
The honest version of any estimate is a corridor, and this one is cheap to produce: Handicap was recomputed at 5 points along the dominant input, with every other field left untouched.
| Personal best setting | Handicapped target |
|---|---|
| 80 % of the example value | 53.76 s |
| 90 % of the example value | 60.48 s |
| example inputs | 67.20 s |
| 110 % of the example value | 73.92 s |
| 120 % of the example value | 80.64 s |
The corridor runs from 53.76 s to 80.64 s across that band — which is the range worth planning inside rather than the single 67.20 s point estimate. Reproduce it in the form above by editing Personal best alone; the substitution steps will follow your figures exactly.
What actually moves your Handicap
Nobody should have to guess which input matters. The engine was re-run once per field below — ten percent up, ten percent down, everything else frozen — and the results ranked by how far they moved the handicapped target. Read it as a map of where Handicap is fragile — drawn for the example inputs, which is the map you want when deciding what to measure carefully.
- Personal best +10 % → Handicap = 73.92 s · −10 % → 60.48 s (the handicapped target shifts ≈10.0 %)
- Handicap %: ten percent up gives 66.92 s, ten percent down gives 67.48 s — ≈0.4 % of the handicapped target either way
Personal best is the dominant lever here: ten percent either way moves the result by about 10.0 %, from 60.48 s to 73.92 s. That is where a careless figure does the most damage, so check it against a source, and treat Handicap % as the second priority (≈0.4 % per ten percent). The rest of the inputs earn only a rounding-error of attention, and that asymmetry is the practical payoff of measuring rather than asserting.
Interpreting the Handicap verdict
A number on its own is trivia; a number against a range is intelligence. The default case lands in the “A 4% handicap on a 70.0 s PB asks for 67.20 s — still 7.2 s off the 60 s standard: racing the handicap, not the field” band, and bands are deliberately wide because real situations overlap. The sensitivity list shows how far a modest input error moves you along that ladder: for Personal best, ±10 % covers 60.48 s to 73.92 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.
Related measures answer related questions, and the distinctions matter: Handicap is the quantity, Handicapped target is this tool’s reading of it, and the decision that follows belongs to neither of them separately.
How people get Handicap wrong
PBs that predate a stroke overhaul make the handicap a fiction — refresh the reference, then the percentage. 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.
Reusing a Handicap from last season. In Fitness & Sports the inputs are the thing that drifts; the formula does not.
One mistake is specific to this engine: assuming every input matters equally. The computation above shows Personal best dominating — a careful figure there beats false precision everywhere else.
A final trap is presentation: reporting Handicap to more decimal places than the inputs support. The tool prints what the arithmetic gives; you should quote only what your least precise field justifies.
Before you trust your Handicap: a short checklist
- Recompute once with the dominant input deliberately set low, and see whether the decision changes.
- Compare the output against one published benchmark or a colleague’s independent estimate.
- Re-verify Personal best against a source document — ten percent of error there moves the headline by ≈10.0 %.
- Verify each input against its original source document, not memory.
- Re-run the calculation with a ±10 % stress on the two most sensitive inputs.
- Confirm the answer against one independent method or published benchmark for Handicap.
Step by step: getting a trustworthy Handicap out of this tool
The tool does the arithmetic; the routine below is what makes the arithmetic trustworthy. Five steps, a minute total — and afterwards you will know not just what the number is, but which assumption produced it.
Step 1 — collect, then type. Everything this tool asks for is listed above (personal best (s), standard time (s), distance (m), handicap %). Pull each figure from something you can point at — paperwork, a dashboard, a label — before touching a field. Guesswork at the input stage cannot be repaired at the interpretation stage. Half of a good calculation is knowing which input you would hate to be wrong about.
Step 2 — start from the case you can defend. Enter pessimistic-but-honest figures first; the optimistic run is a ceiling, not a plan. A conclusion that holds on conservative inputs holds everywhere. When in doubt, prefer the boring input: the interesting one is usually the one you misread.
Step 3 — change one input at a time. Nudge a single field by ten percent, watch the headline and its companions move, then undo it. Two or three fields will dominate — the sensitivity table above already ranks them for this engine. The input you reach for first is usually the one you measured longest ago.
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. Comparisons are cheap: run the identical calculation for the alternative and look at the gap.
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. Re-running a number costs seconds; retracting a decision costs considerably more.
Where Handicap matters in practice
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. The input you reach for first is usually the one you measured longest ago.
The companion outputs — Gap to standard and % improvement asked — exist for the second stage of that screen: the headline sizes the prize, while the companions describe the trade-off you are accepting to get it. Precision is a promise you make about your data; make sure your inputs can keep it.
Nothing here is stored or transmitted, so the habit of checking is free: open the page, re-enter current figures, compare with the number you saved last time. The test of a good estimate is not that it feels right but that it changes what you do.
The questions that come up most about Handicap
What affects Handicap the most?
Measured on this engine, Personal best is the dominant lever: moving it ±10 % shifts the handicapped target across 60.48 s to 73.92 s — about 10.0 % of the headline, with Handicap % next at ≈0.4 %. The ranked list in the sensitivity section is computed live, not asserted from a template.
Which matters more: handicap % or personal best?
By the numbers, Personal best: a ten-percent change in it moves the result ≈10.0 %, versus ≈0.4 % for Handicap %. Spend your measuring effort in that order — precision on the weaker lever buys almost nothing.
What is a typical Handicap?
There is no honest universal average for Handicap, but there is a reference point: the defaults on this page produce 67.20 s (A 4% handicap on a 70.0 s PB asks for 67.20 s — still 7.2 s off the 60 s standard: racing the handicap, not the field). Replace the inputs with your own and compare — that comparison is the useful meaning of “typical”.
How do I calculate Handicap by hand?
Three steps: write the formula (Target = PB × (1 − handicap%); par-gap fairness check), insert your values, and simplify. The worked example section shows exactly that chain for the default inputs; replicating it once on paper teaches you more about Handicap than any number of calculator runs.
What happens to Handicap if personal best changes by 10 %?
Try it in the form above and the printed substitution will follow you; the pre-computed answer for the defaults is 60.48 s to 73.92 s across the ten-percent probe, i.e. ≈10.0 % sensitivity on the handicapped target.
Is the Handicap result of 67.20 s good or bad?
Neither, on its own — the label “A 4% handicap on a 70.0 s PB asks for 67.20 s — still 7.2 s off the 60 s standard: racing the handicap, not the field” 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 Personal best alone moves it by ≈10.0 %.
How do I calculate Handicap manually?
Write down the inputs, then follow the printed steps in order — Target = PB × (1 − handicap%); par-gap fairness check. A spreadsheet replicates it with two or three cells. The manual route is worth doing once to build intuition; after that the calculator saves time and eliminates transcription slips.
Is Handicap individualized?
Partly — the tool is mechanical on the inputs you provide (Personal best (s), Standard time (s)); what varies person-to-person is the response. Start at the computed 67.20 s, adjust by results within a few sessions.
Why not time-on-handicap?
Swimming racing is against the clock; water time handicaps keep the meet format intact.
Is handicap used at invitationals?
At club carnivals yes; championship meets swim strict time standards instead.
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.
What the labels on this page mean
- Gap to standard
- -10.0 s in the default Handicap calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- % improvement asked
- 4.0 for the Handicap worked case; it sits next to the main result because it carries context the headline leaves out.
- Per-100 equivalent
- 46.34 on the example inputs — a companion figure printed beside the headline of Handicap so that no result is read in isolation.
- Handicapped target
- The primary output of this tool: 67.20 s for the default inputs, computed exactly from Target = PB × (1 − handicap%); par-gap fairness check.
- Worked example
- The calculation written out in full so that nothing on this page has to be taken on trust.
- Verdict band
- The plain-language label — here “A 4% handicap on a 70.0 s PB asks for 67.20 s — still 7.2 s off the 60 s standard: racing the handicap, not the field” — mapping the computed figure onto experience-based ranges for Fitness & Sports.
- Sensitivity (±10 %)
- How far the Handicap 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 Handicap model comes from
Everything above runs on one stated formula, applied without hidden coefficients: Target = PB × (1 − handicap%); par-gap fairness check. Source of record: Club handicap conventions. 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.
This page is an estimation aid, not professional advice. The design rule is simple: two people entering identical figures must get identical answers. Nothing is smoothed, weighted or adjusted behind the scenes; where judgement enters, this page says so and names the input responsible.
Turning this Handicap into a decision
Re-run the calculation with your own figures, stress the two most sensitive inputs by ±10 %, and only then act on the result.
This page was written for people who need one trustworthy number before their next decision, and the promise is that nothing above required trust. Bookmark the tool, re-run it whenever an input moves by more than a few percent, and keep the date with the number.