Salt pools recover fastest when you separate “level now” from “rate later”

After a storm, many salt pool owners do the obvious thing: they crank the SWG (salt water generator) from 40% to 90–100% and expect free chlorine (FC) to jump. Then the test still looks low, the water feels “off,” and the cycle of overcorrecting begins. The fix is simple once you see the physics: an SWG changes your production rate, not your FC level today. Storms also create a “double hit” (dilution + contamination) that makes the lag feel worse. This guide explains why the lag happens, what to check first, and how to safely close the FC gap with liquid chlorine while the SWG returns to normal duty.

What storms do to salt pools (the “double hit” that hides in plain sight)

Why your numbers behave strangely for 24–72 hours

A storm is rarely “just rain.” For a salt pool, it usually combines two events that pull FC in opposite directions at the same time: the pool gets diluted, and chlorine demand spikes from new contaminants.

Dilution: overflow, backwash, vacuum-to-waste, or a big top-up can lower FC immediately—and can also lower CYA (stabiliser) and salt.
Demand spike: wind-blown organics, fine silt, pollen, and runoff raise chlorine consumption even if the pool still looks “pretty clear.”
Temperature + equipment effects: cold rain drops water temperature; some SWGs reduce output in cold water, and low flow/dirty filters can reduce cell time-on.
Why this matters

You’re not only “missing chlorine.” You may also have less stabiliser protection (lower CYA), so sunlight can burn off FC faster than normal. That’s why the pool can test low again the next day even after you “raised the %.”

Post-storm priority order: restore FC first (sanitation) → ensure circulation + debris removal (reduce demand) → then re-check CYA and salt once the pool is mixed.

The core misconception: SWG % is not a “dose button”

Rate vs level (the reason “turn it up” feels slow)

Liquid chlorine is a one-time addition: you add a measured amount and FC rises quickly once mixed. An SWG produces chlorine gradually while water flows through the cell. Changing output % changes how much chlorine is produced per hour—not an instant FC increase. That’s why “40% → 100%” can still look like nothing happened, especially if your pump runs only part of the day.

A quick “reality math” check

Think in ppm per day. If your pool consumes 2–4 ppm FC/day after a storm (common with debris), but your SWG setup only produces ~1–2 ppm/day at your current runtime, FC will drift down even if the cell is “working.”

You don’t need perfect numbers—just the habit of asking: “Is my daily production higher than my daily demand?”

Three common reasons SWG recovery is slower than people expect:

  • Runtime limits: 100% output for 6 hours is still only a quarter of a day. If demand is high, the pool never catches up.
  • Real output is lower than rated: scale on the cell, low salinity, cold water, low flow, or an aging cell reduces real production.
  • Storm changed your “lane”: if CYA dropped, you may need a higher FC target for daylight stability until you restore stabiliser.
Useful mental split: Level now is corrected fastest with liquid chlorine. Rate later is tuned with SWG % and pump schedule. Trying to use “rate” to fix “level” is the frustration loop.

Table 1 — Why SWG output lags after storms (symptom → check → fix order)

Use this to diagnose whether you simply need a one-time FC correction, or whether your SWG is underperforming. The “Fix order” column is designed to prevent chasing the wrong variable.

Lag checklist (4 columns)
Symptom Likely cause Quick check Fix order
Rule of safety: If FC is below your normal minimum, treat that as urgent sanitation first. Don’t “wait for the SWG to catch up” while debris is consuming chlorine.

The bridge strategy: close the FC gap with liquid, then hand back to the SWG

A practical, low-drama recovery loop

The goal is not to run the SWG at 100% forever. The goal is to restore a safe FC level quickly, reduce demand by removing contaminants, then tune the SWG so the pool stays in its target band on normal days again.

The “two-step” approach

Step A (today): use liquid chlorine to raise FC to your near-term target (post-storm mode).
Step B (next 2–3 days): adjust SWG % and/or pump runtime so FC stops drifting down between tests.

Here’s a safe operating sequence that works in most post-storm cases:

1) Get circulation going: empty baskets, confirm normal flow, and run the pump so whatever you add mixes evenly.
2) Test FC and pH: if FC is low, fix FC first; if pH is high, plan to correct it soon (SWGs often drift pH upward).
3) Add liquid chlorine to hit target: pour slowly in the deep end or in front of a return with the pump running; brush after.
4) Reduce demand mechanically: skim, brush walls/floor, clean filter if pressure is rising—less debris = less chlorine burned.
5) Re-test after mixing: once the pool has circulated, verify FC is where you expected; then observe the trend the next day.
6) Re-check CYA and salt later: after the pool is mixed and sanitized, confirm whether dilution lowered stabiliser or salinity.
Handling safety: never mix chemicals together; add products separately with circulation; follow your product label for wait times and dosing limits. If you’re unsure, use smaller corrections and re-test rather than dumping a large dose.

Quick dose calculator (liquid chlorine bridge)

Approximate planning tool (verify with your label + test kit)

This calculator estimates how much liquid chlorine (sodium hypochlorite) is needed to raise FC by a chosen amount. It’s designed for post-storm bridging: a measured correction now, then you let the SWG maintain. Use it as a starting point and confirm with testing after circulation.

Enter values to estimate a dose.

Tip: If you don’t know pool volume, use your pool docs or approximate from dimensions; dosing is much safer when volume is correct.

Why “post-storm mode” exists: if debris demand is high, aiming for the low end of your normal range can still allow FC to crash overnight. A slightly higher short-term target can keep the pool protected while you clean and the SWG catches up.

Table 2 — Bridge plan timeline (what to do and when)

The biggest wins come from sequencing: you sanitize first, then you remove what’s consuming chlorine, then you re-tune the SWG. This timeline keeps decisions simple.

Post-storm SWG recovery timeline
Time window Do this What you’re looking for
A common mistake to avoid

Don’t interpret one test taken immediately after swimming, rain, or dosing as “the truth.” Mix first, then compare readings taken at a consistent time (many owners use evening) so you can see the trend.

Re-tuning the SWG: how to stop the “chase” after you bridge

Turn storm recovery into a stable normal routine

Once FC is safely back in range, the job becomes boring again—in a good way. You’re tuning a daily balance: SWG daily production versus pool daily demand. If you only “turn it up” after you see FC low, you’ll keep riding the rollercoaster.

A simple tuning loop (no advanced math required)
  • Pick a consistent test time (often evening) for 3 days after the storm.
  • If FC drops each day, increase daily production slightly (more pump runtime, higher SWG %, or shift runtime into daylight).
  • If FC rises each day, decrease production slightly.
  • Make one change at a time and observe for 48–72 hours before changing again.

If you want a quick “sanity check” on whether your SWG setup could realistically catch up, remember this principle: your cell has a hard maximum output. Even at 100%, a small cell on a large pool can’t produce enough FC per day during heavy demand. That’s not failure—it’s just sizing and conditions. In those cases, the bridge strategy becomes your normal tool: small liquid top-ups during spikes, SWG for baseline.

Also watch pH: running the SWG harder and longer can push pH upward in many pools. Post-storm recovery works best when FC is stable and pH stays in a comfortable range for your surface and equipment.

Concept chart — Why “raise SWG % only” can lag (and how bridging changes the curve)

This chart is conceptual: it shows the shape of recovery many owners experience. When you only increase SWG % (especially with limited pump runtime), FC climbs slowly and can get “eaten” by debris demand. With a liquid bridge, FC gets back into a protective range quickly while the SWG handles maintenance.

FC recovery after a storm (conceptual)
Chart not available on this device.
Concept summary: “SWG % only” tends to raise FC slowly; when demand is high, FC can stall below target. “Liquid bridge + SWG” restores FC quickly, then stabilizes as the SWG maintains.
Note: values are illustrative only, not a promise of results. Your curve depends on debris load, CYA, sun, water temperature, cell health, and pump runtime.

Common post-storm mistakes (and the calm alternatives)

Prevent the “boom-bust” cycle

Most salt-pool headaches after storms come from a few predictable mistakes. Here are the big ones—and the calmer alternatives.

  • Mistake: running the SWG at 100% for days without checking why FC is still low.
    Alternative: bridge FC now, then inspect the “rate” factors (salt level, cell scaling, flow, filter pressure, cold-water limits).
  • Mistake: testing and changing multiple settings daily (percent, runtime, acid, salt) with no baseline.
    Alternative: set FC safe, then change one variable at a time and watch 2–3 day trends.
  • Mistake: chasing salt immediately after heavy dilution without confirming the SWG’s reading vs an independent test.
    Alternative: sanitize first; then verify salinity with a reliable test and adjust gradually if needed.
  • Mistake: ignoring CYA changes after overflow/backwash, then wondering why FC burns off faster in sun.
    Alternative: once FC is stable and mixed, re-test CYA and adjust targets accordingly.
  • Mistake: treating “clear water” as proof sanitation is fine.
    Alternative: treat FC stability as a leading indicator; clarity can lag behind chemistry.
When you should stop and escalate

If the water is turning green, very cloudy, or you cannot hold FC overnight despite cleaning and dosing, you may be dealing with a larger contamination/algae load than a simple bridge is designed for. In that case, the correct process is to follow a structured sanitation protocol rather than “hoping the SWG will win.”

FAQ

Because 100% changes production rate, not an instant dose—and storms usually raise demand at the same time. If your pump runs limited hours, or your cell output is reduced (cold water, low salt, scaling, low flow), the pool can consume chlorine faster than you produce it.

Fast fix: bridge with liquid to restore FC today, then verify the SWG is producing normally and tune runtime/% over the next few days.

Boost modes can help, but they’re still limited by the same physics: they increase production rate for a period of time. If you need FC protection now, liquid is usually the quickest controlled way to close the gap. Boost is most useful when demand is only moderately elevated and you have enough runtime for the extra production to matter.

Practical approach: liquid for the immediate gap, then use boost/percent adjustments to maintain while you clean and re-test.

Re-test after the pool has mixed well (circulation time depends on plumbing and flow). Many owners wait at least 30–60 minutes with good circulation after a carefully poured dose, then confirm FC. If your pool has complex circulation or you dosed in multiple locations, allow more time.

The key is consistency: test at a similar time each day so you can compare trends instead of reacting to noise.

Start with FC (and CC if you track it) and pH. If FC is low, correct that first. Then, after the pool is mixed and sanitized, check CYA (dilution can lower it) and salt if you suspect overflow/top-ups.

This order avoids misreading CYA or salt adjustments when the pool is still actively consuming chlorine from debris.

Takeaway: after storms, don’t fight a “level problem” with a “rate tool.” Bridge FC quickly with liquid, reduce demand with cleaning and flow, then tune SWG runtime/% so the pool stays stable without constant chasing.