Melbourne pools don’t drift because owners “forgot a number.” They drift because the schedule doesn’t match real demand: UV intensity, swimmer load, wind-blown debris, and storms that dilute water and spike contamination. This playbook shows how to set pump timers and chlorination so water stays consistently clear — by changing slowly, logging trends, and using seasonal “modes” rather than overreacting to one test.
The core rule: stability beats the “perfect number”
The biggest scheduling mistake is treating your pool like a spreadsheet: “summer = X hours, winter = Y hours.” In reality, you’re controlling a moving target. A stable schedule isn’t one that hits a universal turnover idea — it’s one that keeps three things reliably true:
A stable schedule keeps sanitizer present, keeps water mixed (no dead zones), and keeps filtration coping (pressure and flow don’t quietly collapse). When these three are stable, chemistry adjustments become smaller and less frequent — because you’re not fighting the schedule.
A simple operator habit that works year-round: set a baseline schedule, then use short-term overrides for events that add load (heatwaves, storm fronts, parties, leaf-drop weeks). When conditions normalize, return to baseline instead of permanently “ratcheting up.”
Summer schedule (Melbourne UV + bather load)
In Melbourne summer, the stress is rarely “heat alone.” It’s the combo: strong UV around midday, more swimming, and windy days that add dust and organics. The schedule that wins in summer is the one that gives you coverage windows when demand happens — not a single overnight run that looks neat on paper.
If your pump (and SWG, if you have one) runs mostly at night, you can spend the highest-demand hours under-mixed and under-produced. A safer summer pattern is split runtime: one window that overlaps daylight, plus a second window after swimming to help filtration polish the water.
Here’s a practical summer tuning method that avoids guessing:
- Start with a baseline week: pick “normal summer” conditions (not a heatwave, not a storm) and run a consistent split schedule for 3–5 days.
- Watch two signals: (1) sanitizer stability (no repeated “near-zero mornings”), and (2) filtration coping (pressure rise pattern, skimming effectiveness).
- Adjust in small steps: add time to the daylight window first if you’re drifting in peak UV, then add a short post-use window if water goes dull after busy days.
Two common summer mistakes to avoid:
- All runtime in one block: the pool gets a long mix once, then coasts through high demand with poor distribution and weaker skimming.
- Reacting with “big jumps”: doubling runtime overnight because one test looked low usually creates new problems (higher pH drift, filter load, noise, unnecessary energy) without solving the real gap.
The practical summer mindset: aim for steady sanitation and steady removal. Summer algae problems often start quietly with short daily “low chlorine windows” plus a filter that can’t keep up after windy or high-use days. A split schedule closes those windows and gives the filter more consistent opportunity to work.
Winter schedule (lower demand, but not zero)
Mild-climate winter is where many pools “quietly” go backwards. Demand drops — fewer swimmers, weaker UV, cooler water — so owners cut runtime hard and turn chlorination down aggressively. The problem is that winter doesn’t remove the need for mixing and baseline sanitation. It removes the need for summer intensity.
Your winter schedule should still do three jobs: (1) keep sanitizer present, (2) mix the pool so you don’t build dead zones, and (3) keep skimming and filtration functioning so debris doesn’t become “food” for problems later.
The safest way to reduce in winter is gradual:
Another winter lever that often gets overlooked is cover use. A cover can reduce debris entry and smooth temperature swings, which can support shorter, calmer schedules — but only if you handle it correctly (keep it clean, don’t trap strong treatments under it for long, and secure/remove it before severe wind).
The winter “don’t do this” list is short but important:
- Don’t go to zero: “off for winter” often becomes algae pressure + staining + spring recovery.
- Don’t cut everything at once: if you reduce pump time and sanitizer together, you can’t see which change created the drift.
- Don’t ignore storm events: winter storms can still add debris and dilution — treat them as short override modes.
Shoulder seasons (spring/autumn): change slowly
Shoulder seasons are where automation earns its keep: Melbourne can swing from warm UV-heavy days to cool, windy spells quickly. If you “chase today’s weather,” you end up in a yo-yo loop (turn down → water dull → turn up → overshoot → turn down again). The fix is not more math — it’s a disciplined change process.
In shoulder seasons change one parameter at a time: either pump runtime OR SWG output (or dosing frequency). Hold that change for a consistent observation interval, then decide the next step.
A clean shoulder-season loop looks like this:
Spring has an extra risk: warming water plus more sunlight increases algae pressure fast. If your schedule is still “winter small,” you can get the classic pattern: clear one day, dull the next, then slippery walls — even though the pool “looked fine” at the start of the week. Autumn has its own trap: leaf drop weeks can overload baskets and filtration, reducing flow and skimming when you need them most.
Variable-speed pumps: RPM planning without guessing
Variable-speed pumps tempt owners into one of two extremes: “run very low all day” or “blast high for a short time.” The right approach is neither universal — it depends on what job you’re trying to do at that moment: basic mixing, skimming, vacuuming, heater/solar flow, or polishing fine debris through the filter.
Low RPM for longer can be excellent for gentle mixing and steady filtration. High RPM for shorter windows can be useful for skimming, manual vacuuming, priming after maintenance, or when you need to push through a specific flow-dependent loop. The goal is not a magic RPM number — it’s using RPM as a tool for different tasks.
Instead of chasing universal pressure or flow targets, use your own system baselines:
- Log “clean filter” behavior: note how returns feel and what your pressure gauge reads right after a proper clean/backwash.
- Watch the trend: if pressure creeps up and returns weaken sooner than normal, filtration is getting load — you may need maintenance or a temporary schedule boost.
- Use a two-window pattern: low RPM for the long mixing/polish window, and a short higher RPM window for skimming or post-use cleanup.
Variable-speed also interacts with salt systems: SWG cells usually require adequate flow to operate reliably. If you run ultra-low RPM, make sure the chlorinator is actually producing (flow switch satisfied, no intermittent “no flow” stops). If production is inconsistent, you can end up with a schedule that looks long but produces less sanitizer than you think.
SWG / chlorination: how to adjust output with runtime
The simplest way to adjust a salt-water generator (SWG) or timed chlorination is to treat it like a controlled model: Output % × hours is your daily chlorine production effort. It’s not a promise of exact ppm — it’s a practical way to keep changes measured. When you shorten runtime (winter, shoulder seasons, noise constraints), you decide whether to compensate with output %, or accept a lower effort because demand also dropped.
- Change one lever at a time: either change hours or output %, then observe 3–5 days.
- Prefer daylight production in summer: SWG produces only with flow, so aligning production with the hours demand happens reduces daily lows.
A clean tuning loop that avoids guessing:
Remember: SWG changes are rate changes, not instant corrections. If you had a storm or a heavy weekend, a targeted one-time correction plus extra filtration can be cleaner than cranking output to extremes and hoping it catches up.
Quick troubleshooting: when the schedule is wrong
Scheduling problems show up as repeating patterns — not one dramatic reading. Use symptoms to identify which “job” your schedule is failing: mixing, sanitation stability, or filtration coping.
- Cloudiness after wind: not enough post-event filtration, or baskets clogging reduces flow right when debris spikes.
- Slippery walls / dull feel: repeated low-sanitizer windows + dead zones (insufficient mixing, especially steps/corners).
- Pressure rises faster than usual: filter is catching load (good), but if you don’t respond, flow drops and everything gets weaker.
- “Zero in the morning” pattern: daily production is losing vs demand; often worse with night-only summer schedules.
Most fixes are small and targeted:
- Debris-driven dullness: add a short extra window after windy days + clear baskets more often during leaf weeks.
- Sanitizer drift: increase daily production (hours or output) modestly — not both at once — and confirm by trend.
- Filter overload: improve mechanical removal (skim/brush/filter maintenance) and make sure you have enough polish time.
FAQ
| Season | Goal of the schedule | Common mistake |
|---|
Use a method, not a magic number. Build a baseline schedule for the season, then confirm stability by trend: sanitizer doesn’t repeatedly crash, water stays mixed (no dead zones), and filtration keeps up (pressure/flow trend stays normal). In summer you usually need a daylight coverage window; in winter you usually reduce but keep a minimum daily mixing window.
Best practice: change one lever at a time (hours OR output), observe 3–5 days, then adjust again if trend still drifts.
In peak UV weeks, a daylight window is usually safer than night-only. The goal is coverage when demand happens: sanitation distribution, skimming action, and (for salt pools) SWG production during the hours the pool is being stressed. Split schedules (daylight + post-use) often outperform one long overnight run for real-world stability.
Split windows usually win when conditions change through the day (UV peaks, swimmers, wind). A long single run can be fine in calm, low-demand weeks, but it often fails in summer because the pool “coasts” through high demand without mixing and skimming. Split windows also help after swimming by giving the filter time to capture fine debris before it settles.
Change in small steps. Cloudiness often appears when you cut too much at once and create longer “low-mixing” windows. Keep one stable test time, make one change (hours OR output), then observe multiple days. If a storm or party hits during the observation window, treat it as a temporary mode rather than rewriting your baseline.
Use output % × hours as your daily production effort. If runtime drops and demand hasn’t dropped as much, you may need a modest output increase. If demand drops too (common in winter), you may not need to compensate fully. Make one change at a time and confirm by trend over several days.
Heating loops can impose flow and timing constraints. Separate “heat window” from “filtration/mixing window” where possible, and ensure pump speed (on variable-speed systems) satisfies the loop while it’s active. When heating is running, steadier windows often work better than short bursts.
Rain can be dilution plus contamination. “Enough hours” in a normal week may not be enough in a storm week. Treat storms as a temporary mode: extra skimming, baskets cleared, and a short extra filtration window after the event can prevent the dull-water spiral.
It’s worth it when your biggest issue is consistency: you travel often, your pool drifts after weather events, or you keep “catching up” after busy weekends. Automation makes seasonal modes easy: stable baseline schedules plus quick, temporary overrides.
If you want a clean seasonal setup (baseline + heatwave mode + storm mode) tuned to your equipment and your site conditions, book automation services.
A proper setup focuses on stability: predictable circulation windows, sensible SWG output planning, and maintenance signals you can actually trust.