What PoolBoss Says
Triage the route before you rebook anything: service the pools that will turn green first, push the pools that can wait, and record every stop you skipped with a reason the same day. Then plan for the real cost, which arrives about a week later as debris load and algae, not on the storm day itself.
Storm content written for pool owners tells you to cover the pool and shut off the breaker. That is not the problem a service operator has at 2pm on a Wednesday with 19 stops left and a wall of rain crossing the valley. Your problem is a route: which stops still have to happen this week, which can slide, what you bill for a visit you could not make, and what you tell forty customers before they call you. Monsoon season in the desert Southwest and hurricane season on the Gulf each run four to five months, so this is a repeating operating problem, not an emergency.
At a glance
Key takeaways
- Triage skipped stops by how fast each pool degrades, not by their order in the route; a covered pool holds a week and a tree-shaded one does not hold four days.
- Stop the day when the drive stops being safe, not when the route runs out. Standing water, lightning, and downed limbs end the day.
- Record every skipped stop the same afternoon with a specific reason and a photo where the cause is visible; five minutes on the day beats hours of reconstruction in September.
- Slide a whole week forward rather than doubling up a single day, which just moves the failure to Thursday.
- Expect the real cost about nine days out, when debris and phosphate loading turn several pools green at once and each wants a second visit.
- Agree a storm-cleanup rate in writing in spring; introducing it during the week you need it reads as opportunism and rarely sticks.
- Send one proactive message the same day with the new service day and what you'll do about debris; silence after a storm is what triggers cancellations.
How do I run my pool route through storm season?
Run a storm week in four moves, in this order: stop the day, triage what is left, document every skip before you go to bed, and hold back capacity for the second wave that lands a week later. The order matters because the cheapest decision is the first one. A stop you skip on Wednesday and service Thursday morning costs you maybe 20 minutes of extra drive time. The same stop skipped for eight days can cost a full extra visit, a bag of shock, and a phone call you did not want.
The mechanical part of this is simply being able to move stops and rebuild a day's route without re-typing the week. If your schedule lives on paper or in a spreadsheet, a storm week is the week that fact becomes expensive, because every reshuffle is manual and nothing tells you which stops never got serviced.
- Stop the day at the point where the drive stops being safe, not the point where the route runs out. Standing water, active lightning, and downed limbs are where the day ends. Finishing three more stops is never worth a truck in a wash.
- Triage the remaining stops by how fast each pool degrades, not by their position in the route. A screened or covered pool holds for a week. An uncovered pool under two mature trees does not hold four days.
- Document every skipped stop the same afternoon, with a reason attached, while you still remember which pool and why. This is the step operators skip, and it is the one that costs the most later.
- Reserve capacity in the following week before you book anything into it. The storm generates second visits, and a week already packed to the edge has nowhere to put them.
Not every missed stop is equal, so don't rebook them in order
The instinct after a lost afternoon is to push everything forward one day and carry on. That is the wrong move, because the pools on that list degrade at completely different speeds. A covered pool that missed a Wednesday is fine the following Wednesday. An uncovered pool under mesquite and olive that missed a Wednesday in July is green by Saturday and needs a second visit either way. Sort the skipped list by degradation risk and you convert a full lost day into three or four genuinely urgent stops.
The same triage logic applies whenever a day comes apart for any reason. Losing a technician is the other common version of this problem, and the fix there is to spread a lost day's stops across the crew rather than pushing them into tomorrow. A storm is the version where the whole crew loses the same hours at once, so there is nobody to spread to and triage does the work instead.
| Disruption | What to do with the visits | What to bill | What to tell the customer |
|---|---|---|---|
| Half a day lost to rain | Skip the covered and screened pools; service the tree-shaded ones next morning | Full rate on skipped visits if your agreement says so | One message the same day naming the new service day |
| Two or more days out (named storm, flooding) | Slide the whole week forward rather than doubling up any single day | Full rate; a missed week is an interruption, not a cancellation | Proactive notice before the storm lands, not after |
| Route running, heavy debris load | Keep the schedule and add a second visit only where the pool needs one | Storm cleanup at your agreed hourly or flat rate, quoted first | A quote with a photo, sent from the pool before you start |
Record every skipped stop the day it happens
Documentation is the difference between a rough week and a month of invoice arguments. Forty skipped stops recorded at 4pm on the day takes about five minutes. The same forty reconstructed three weeks later from memory takes hours, and you will still lose two of the arguments, because the customer remembers a missed visit far more clearly than you remember which Wednesday it rained.
What has to be captured is small: which pool, which day, and why. "Weather" on its own is weaker than "standing water in the yard, gate impassable" when a customer disputes an invoice in September. Attach a photo where the reason is visible, since a timestamped picture of a flooded pad settles a dispute that your word against theirs will not.
In PoolBoss the skip flow asks for a reason on every skipped visit, and there is no path that records a skip without one. The preset reasons cover locked gate, pet in yard, and customer request, so a weather skip goes in under Other with a typed note, which is required rather than optional. When a storm takes out a whole afternoon, the missed visits can be skipped together from one place with a single shared reason, instead of opened one at a time.
One detail worth knowing before you use it: marking a visit skipped takes it out of billing, and you can reopen it from its own page if you get back to the pool later in the week. So if your agreement lets you bill a storm-missed visit anyway, that is a deliberate line on the invoice, not something that happens by default. Decide which way you are going before the invoices run, not after a customer asks.
The bill for a storm arrives about nine days later
The storm day itself is rarely the expensive part. The cost lands the following week, when debris and phosphate loading turn a handful of pools green at the same time and every one of them wants a second visit. Rain carries organic material, fertilizer, and dust into an open pool, and the chlorine that would normally hold it is diluted right when the demand for it spikes.
Take a three-truck operator running 165 pools across Mesa, Gilbert and Chandler, Arizona. A late-July monsoon cell shuts the Wednesday route down at 2pm with 19 stops left. Nine of those pools sit under mature mesquite and olive and will be unswimmable by Saturday; the other ten are screened or covered and hold to next week. The operator services the nine on Thursday morning, pushes the ten, and records all 19 skips with reasons that same afternoon. The real cost lands the following week: six of the nine need a second visit for debris and a phosphate spike, roughly $540 of labor that is unbilled unless a storm-cleanup rate was already agreed back in May.
That $540 is the whole argument for pricing storm work before the season rather than during it. A written rate for post-storm cleanup, agreed in spring, turns six emergency visits into six billable ones. Trying to introduce the rate in the week you need it reads as opportunism, so set a weather policy in writing while the sky is clear and nobody is annoyed.
Budget the chemistry too. The pools that sat unserviced through a storm week are the ones most likely to need shock, a clarifier, and a return trip, and knowing how to bring a green pool back efficiently is worth more in the ten days after a storm than in the rest of the season combined.
Tell customers what you're doing before they ask
One message sent before customers notice beats forty inbound calls asking where you were. Pool owners are reasonable about weather; they are much less reasonable about silence. A customer who watched a storm roll through and then heard nothing assumes they were forgotten, and that assumption is what turns a skipped visit into a cancellation call.
Keep it to three facts: that the storm cost you the day, when their pool is now being serviced, and what you will do about the debris. Send it the same day, before the complaint arrives. Nothing in this is automatic, and it should not be. A storm message is one of the few times a pool owner genuinely wants to hear from the person who runs the company rather than from a system.
For the pools you had to push a week, one line about what to expect saves a call later: the water will look worse before the next visit, and it will come back. Customers who understand why their pool is cloudy on Saturday do not call you on Sunday. In practice that single message is worth more retention than anything you do at the pool that week.
FAQ
Frequently asked questions
Should I charge for a visit I couldn't do because of a storm?
Yes, if your service agreement says a scheduled visit that could not be completed for reasons outside your control bills at the full rate, and most well-written pool service agreements do. You drove, you staffed the day, and the recurring price covers a year of service rather than a per-visit transaction. Where operators get into trouble is billing it with nothing in writing to point at, which turns every storm week into a negotiation. If you have no such clause today, bill the visits you can defend, add the clause before next season, and tell customers it is coming rather than surprising them with it. One thing to watch mechanically: marking a visit skipped generally removes it from billing, so if you intend to charge for it, that becomes a deliberate line on the invoice rather than something that carries through automatically.
Do I owe customers a make-up visit when I lose a day to rain?
It depends entirely on what your agreement promises, which is why the wording matters more than the weather. An agreement that promises weekly service implies a make-up when a week is missed; one that promises roughly 48-52 visits a year gives you room to absorb one lost day without owing anything. The practical answer for most operators is to make up the visits that matter and skip the ones that do not: a pool that will be green without it gets serviced, a covered pool that missed one week does not need a special trip. What customers actually object to is not the missed visit but the missing explanation. Tell them which it is and almost nobody pushes back.
How much should I charge for storm debris cleanup?
Most operators price post-storm cleanup either hourly, commonly in the $60-95 per hour range depending on the market, or as a flat rate tied to severity, such as $75-150 for a heavy-debris visit and more where the pool needs draining and vacuuming to waste. Quote it before you start, not after, and send the quote from the pool with a photo attached, because a picture of a pool full of palm fronds justifies a number that a text message alone will not. Whichever structure you pick, put the rate in the service agreement in spring so it is a known term rather than a surprise. Charging nothing is the most common mistake here, and it is how a bad storm season quietly erases a quarter's margin.
Should I service pools in the rain or wait it out?
Light rain is workable and often worth pushing through, because the alternative is compressing those stops into an already-full week. Stop for anything involving lightning, standing water in the yard, or visible damage around the equipment pad. The plain safety rule is worth stating once: never work a pool with visible electrical damage or standing storm water near the equipment, and call the utility rather than investigating it yourself. Beyond that, judge it stop by stop, because testing and dosing in light rain still produces a real visit, while brushing and vacuuming in heavy rain mostly does not. The thing that is genuinely wasted in rain is a chemical dose you cannot balance, so if the water is being diluted faster than you can treat it, log the reading, note the conditions, and come back.
How do I catch up a full day of missed stops without wrecking the next week?
Protect the following week rather than absorbing the lost day into it. The instinct is to add the missed stops onto the next day, which makes that day fail too and pushes the problem down the line until the weekend eats it. Two better options: slide the entire week forward by a day so every day carries its normal load, or split the urgent stops across the crew so no single technician takes the whole hit. PoolBoss has a move-a-day action built for exactly the weather case, which shifts a whole day rather than making you re-book stops one at a time, and a cover-a-day action that proposes how to spread one technician's stops across whoever is available and shows you the result before anything is written. Only the genuinely urgent pools need to be caught up at all, which is usually a third of the list rather than all of it.
What should be in my service agreement about weather?
Four lines cover almost every dispute a storm season produces. First, that scheduled visits missed due to weather or other conditions outside your control bill at the full rate. Second, how make-up visits work, including whether they are guaranteed or handled at your discretion based on the pool's condition. Third, a named rate for storm and debris cleanup that falls outside normal service, so the number exists before anybody needs it. Fourth, a simple statement that service may be rescheduled for safety, which is the clause that lets you stop a day without breaching anything. Add all four in spring, before the season, and mention the change to existing customers rather than slipping it into a renewal. An agreement written the week you need it convinces nobody.
How do I keep techs safe around a pool after a storm?
The one rule that is not negotiable: nobody works a pool with visible electrical damage or standing storm water around the equipment pad, and anything involving downed lines is a call to the utility, not a judgment call at the gate. Past that, the common post-storm hazards are ordinary ones made worse by mess, such as broken glass and debris hidden under cloudy water, unstable branches over the deck, and decking that is more slippery than it looks. Make it explicit that a technician can call a stop off and move on without checking with you first, because a tech who feels they need permission will push into something they should have walked away from. Anything beyond that, including structural or electrical damage assessment, belongs to a licensed professional rather than your crew.
