Open Water vs Pool Calculator
The formula
What the ow conversion tells you
A pace bridge between lane-rope swimming and open water: condition multipliers for chop and current, a drafting discount, and the sighting tax.
Calculation: OW pace = pool pace × condition × draft; sighting +0.5 s/event. Enter your inputs and every substitution is shown below the result.
Reading the result
A 5 km OW race on flat water is usually 4–8% slower than the pool equivalent; a current is a coin flip, not a constant.
Rules of thumb: 800 m pool → OW ≈ +3–6% time; chop adds 5–10%
Limitations and best practice
Drafting cuts the cost but you must bank the skill: swimmers who never practice it pay it back in missed wheels.
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
Do wetsuits offset the penalty?
Does drafting count in the conversion?
Source & methodology
OWS coaching data; triathlon practice.
Open Water vs Pool: the number, the method and the caveats
You cannot reduce what you have not measured, and this page measures it with the factors printed in the open. Open Water vs Pool is the kind of number people argue about from memory. This page ends that argument with arithmetic you can watch happen: enter your figures, get OW pace /100 in real time, and see every substitution printed below.
Most confusion about Open Water vs Pool 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.
Like most useful measures, Open Water vs Pool is a summary, and summaries hide as much as they reveal. The companion outputs and the input table are here to reopen what the headline compressed.
Nothing below is stock text pasted around a number: the worked example computes OW pace /100 = 96.2 s from this tool’s own defaults, and the sensitivity section ranks the inputs that move the result — Pool pace /100 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 Open Water vs Pool, and what it does to the answer
One formula, published in full: OW pace = pool pace × condition × draft; sighting +0.5 s/event. 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.
Pool pace /100 (s) (example value 99) is a plain measured quantity — the unit shown in the label is the unit the formula expects. The example value is there to demonstrate the mechanics, not to describe your situation — overwrite it.
Race distance (km) (example value 10) 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.
Conditions (example value Typical chop) is a categorical input — the option you choose decides which numbers the formula uses. This input feeds the formula directly; a defensible figure here is worth more than false precision anywhere else.
Drafting opportunity (example value Light pack) is a branching choice rather than a figure you measure; the per-option effects are computed below. This input feeds the formula directly; a defensible figure here is worth more than false precision anywhere else.
What each “Conditions” choice actually does: Glass → 89.1 s · Typical chop → 96.2 s · Rough/current → 103.4 s That table is the honest answer to “does this option matter”, re-derived from the formula rather than hard-coded into page copy.
What each “Drafting opportunity” choice actually does: Alone → 101.6 s · Light pack → 96.2 s · Heavy draft → 87.7 s — each value above is the model’s own output for that option, so the choice can be made on evidence rather than on what a category feels like it means.
A fully worked Open Water vs Pool example
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: Pool pace /100 (s), Race distance (km), Conditions, Drafting opportunity. The computed OW pace /100 comes out at 96.2 s, which the interpretation band labels “Pool 99 s → open water 96 s/100 under typical conditions with light drafting — the 10.0 km projects to 160:23 (277 s faster than flat pool pace)”.
- Condition 1.08 × draft 0.90 → ×0.97
- Pace = 99 × 0.97 = 96.2 s/100
- Total = 96.2 × 100 hundreds = 160:23
Condition factor — 1.08. This is the number experienced users quote when the headline alone would mislead.
Draft factor — 0.90. Compare it against the main result of 96.2 s before drawing conclusions.
Projected total — 160:23. If your inputs change, this is usually the first companion figure to move.
Sighting tax — +1–2 s per 400 m at race pace. 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.
Scenario table: Open Water vs Pool at ±10 % and ±20 % of the key input
The honest version of any estimate is a corridor, and this one is cheap to produce: Open Water vs Pool was recomputed at 5 points along the dominant input, with every other field left untouched.
| Pool pace /100 setting | OW pace /100 |
|---|---|
| 80 % of the example value | 77.0 s |
| 90 % of the example value | 86.6 s |
| example inputs | 96.2 s |
| 110 % of the example value | 105.9 s |
| 120 % of the example value | 115.5 s |
Across 5 settings of Pool pace /100, the result spans 77.0 s to 115.5 s. A decision that only works at one row of this table is a decision waiting for an input to move. Reproduce it in the form above by editing Pool pace /100 alone; the substitution steps will follow your figures exactly.
What actually moves your Open Water vs Pool
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 OW pace /100 was recalculated from scratch. It is the fastest honest answer to “what matters most in Open Water vs Pool?” — and it is specific to these defaults, because sensitivity moves with the starting point.
- Pool pace /100 +10 % → Open Water vs Pool = 105.9 s · −10 % → 86.6 s (the OW pace /100 shifts ≈10.0 %)
Pool pace /100 is the dominant lever here: ten percent either way moves the result by about 10.0 %, from 86.6 s to 105.9 s. Measure that input from a document rather than from memory. 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 Open Water vs Pool verdict
The value above only becomes useful the moment you know what it is being measured against. On the example inputs the band reads “Pool 99 s → open water 96 s/100 under typical conditions with light drafting — the 10.0 km projects to 160:23 (277 s faster than flat pool pace)”; your own figures place you on a different rung of the same ladder. The sensitivity list shows how far a modest input error moves you along that ladder: for Pool pace /100, ±10 % covers 86.6 s to 105.9 s. The practical reading rules: ask what would have to change to move you one band. If the answer is “a small, plausible input difference”, the band itself is not the finding — the uncertainty is.
Related measures answer related questions, and the distinctions matter: Open Water vs Pool is the quantity, OW pace /100 is this tool’s reading of it, and the decision that follows belongs to neither of them separately.
How people get Open Water vs Pool wrong
Drafting cuts the cost but you must bank the skill: swimmers who never practice it pay it back in missed wheels. 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.
Chasing precision in Race distance (km) while Pool pace /100 (s) is still a guess. The sensitivity ranking above shows exactly where the accuracy budget should go.
Attention is also misallocated between fields. Having measured this engine, we can say where it belongs: Pool pace /100 first, everything else second.
The subtlest error is answering the wrong question precisely. Confirm that OW pace /100 is actually the quantity your decision needs — the arithmetic is flawless either way, which is what makes the mistake invisible.
Open Water vs Pool verification checklist
- Note the date and the inputs beside the number so the figure can be audited later.
- Re-run the calculation with a ±10 % stress on the two most sensitive inputs.
- Re-verify Pool pace /100 against a source document — ten percent of error there moves the headline by ≈10.0 %.
- Compare the result with one independent method or published benchmark.
- Record the date and the inputs alongside the number so future-you knows what was assumed.
- Repeat the ±10 % test on the inputs that matter and see whether the decision — not just the number — still holds.
How to use the Open Water vs Pool tool properly
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 — one document, one pass. Open the statement, label or record that holds pool pace /100 (s), race distance (km), conditions, drafting opportunity and transcribe straight into the form. Transcription from a single source removes the mismatch errors that appear when figures are assembled from three different places. One decimal place more than your data supports is one decimal place of fiction.
Step 2 — enter the conservative case first. Resist the flattering scenario. Type the inputs you would defend in front of a sceptical reader, read the OW pace /100 (96.2 s for the example values), and note the verdict band. Compare the calculation to the rough guess you arrived with, and ask why they differ.
Step 3 — measure what deserves measuring. The ranked levers above tell you where a careful figure pays off. Everything else can stay approximate, which is a licence to stop hunting for data you do not need. If a result feels obviously right, that is the moment to check the inputs hardest.
Step 4 — compute a corridor, not a point. Three runs — worst, likely, best — turn Open Water vs Pool from a snapshot into a range. Plan against the pessimistic end and treat the optimistic end as the upside story. Write the figure down before moving on; memory flatters whichever number you saw last.
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. Say the answer out loud before you save it; if it sounds wrong, the model did not change, your understanding did.
From calculation to decision: where Open Water vs Pool earns its keep
Numbers earn their keep in conversations, and Open Water vs Pool is no exception. In Fitness & Sports discussions around Swimming, this figure decides whether an option stays on the table: it converts an opinionated debate into an arithmetic one, and arithmetic is the only referee both sides accept. When in doubt, prefer the boring input: the interesting one is usually the one you misread.
Used properly this is a five-minute filter that saves weeks. Compute Open Water vs Pool, reject what fails, and only then bring in the expensive analysis for the survivors. The input you reach for first is usually the one you measured longest ago.
Re-running this page costs nothing and catches the slow drifts that never announce themselves. In Fitness & Sports the expensive mistakes are rarely sudden; they are small changes in Pool pace /100 (s) that nobody recalculated for a year. Suspiciously tidy answers deserve the same scrutiny as untidy ones.
Open Water vs Pool — frequently asked questions
What affects Open Water vs Pool the most?
The short answer: Pool pace /100. The longer answer is the sensitivity table on this page, where every numeric input was probed by ten percent and the OW pace /100 recalculated — Pool pace /100 moved it furthest, by roughly 10.0 % (86.6 s to 105.9 s).
How much does the “Conditions” choice change the answer?
The spread is not cosmetic: this choice alone takes Open Water vs Pool from 89.1 s to 103.4 s with every other input frozen, which is more influence than most of the numeric fields on this page can claim.
What is a typical Open Water vs Pool?
There is no honest universal average for Open Water vs Pool, but there is a reference point: the defaults on this page produce 96.2 s (Pool 99 s → open water 96 s/100 under typical conditions with light drafting — the 10.0 km projects to 160:23 (277 s faster than flat pool pace)). Replace the inputs with your own and compare — that comparison is the useful meaning of “typical”.
How do I calculate Open Water vs Pool by hand?
Three steps: write the formula (OW pace = pool pace × condition × draft; sighting +0.5 s/event), 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 Open Water vs Pool than any number of calculator runs.
What happens to Open Water vs Pool if pool pace /100 changes by 10 %?
On these inputs a ±10 % change in pool pace /100 takes Open Water vs Pool to 105.9 s against the 96.2 s example — around 10.0 % of the headline. The same test on every other field is in the sensitivity section.
Is the Open Water vs Pool result of 96.2 s good or bad?
Good and bad are comparisons, so the honest test is three questions: where does your own Open Water vs Pool sit against the 96.2 s reference above, how far would a plausible input error move it (≈10.0 % per ten percent on Pool pace /100), and what does the alternative option compute to?
Can Open Water vs Pool be negative or empty?
Yes, and that is informative rather than broken: a negative Open Water vs Pool usually means the inputs encode an outflow or a shortfall, and the verdict band above labels exactly that situation instead of hiding it.
Is Open Water vs Pool accurate?
The arithmetic is exact: OW pace = pool pace × condition × draft; sighting +0.5 s/event is evaluated with full floating-point precision and every substitution is printed in the worked example. What limits accuracy is input quality and the model’s assumptions, so treat the 96.2 s result as the correct answer to the question you typed — and check the assumptions section before acting on it.
Do wetsuits offset the penalty?
They claw back 2–5% via buoyancy — see the wetsuit engine.
Does drafting count in the conversion?
The model covers water conditions only — pack swimming can erase the whole gap.
Do I need an account to use this Open Water vs Pool calculator?
No, and no data leaves the tab. The engine runs in the page itself, which is why the worked example, the bands and the sensitivity ranking all respond instantly to your keystrokes.
Key terms on this page
- Condition factor
- 1.08 in the default Open Water vs Pool calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Draft factor
- 0.90 for the Open Water vs Pool worked case; it sits next to the main result because it carries context the headline leaves out.
- Projected total
- 160:23 on the example inputs — a companion figure printed beside the headline of Open Water vs Pool so that no result is read in isolation.
- OW pace /100
- The primary output of this tool: 96.2 s for the default inputs, computed exactly from OW pace = pool pace × condition × draft; sighting +0.5 s/event.
- Worked example
- The calculation written out in full so that nothing on this page has to be taken on trust.
- Verdict band
- The interpretation attached to a result (“Pool 99 s → open water 96 s/100 under typical conditions with light drafting — the 10.0 km projects to 160:23 (277 s faster than flat pool pace)” on these inputs), which turns a bare number into a position on a scale.
- Sensitivity (±10 %)
- How far the Open Water vs Pool moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
Method, sources and what this tool cannot tell you
Everything above runs on one stated formula, applied without hidden coefficients: OW pace = pool pace × condition × draft; sighting +0.5 s/event. Source of record: OWS coaching data; triathlon practice. Any other implementation of this model should return the same figure for the same inputs. If one does not, the difference is in its assumptions — which this page prints and that one probably does not.
Nothing here replaces a qualified professional, and nothing here is approximate either — the arithmetic is exact, and the honesty is in the inputs you supply. The design constraint was set by usefulness rather than by comfort: an estimate you can interrogate beats an answer you have to trust.
Turning this Open Water vs Pool into a decision
Record the figure with today’s date and re-run quarterly; the trend is the actionable number, not the snapshot.
Whoever you are (households and teams measuring consumption or impact), 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.