Three wet days and the round comes apart
It rains Monday, Tuesday and half of Wednesday. You get out Wednesday afternoon and do what you can. Now what? Do you push the whole round back a few days, squeeze Monday and Tuesday into Thursday and Friday, or catch them up on Saturday? Each option moves customers who expected you on a certain day, and the eight-weekly customers who were due that week may now slide into next month.
By the following week, you are working from a notebook with crossings out and arrows. A customer texts to ask why you have not been. Another texts to ask why you came so soon after last time. And someone who pays when you knock is not in, because you turned up on the wrong day for them.
Weather decisions are made in the van, and the round has no memory
Rescheduling is a daily judgement call about wind, rain and forecasts, and only you can make it. The problem is what happens next: the round has to be shuffled by hand, and a notebook or simple list does not remember why a customer moved or when they were really due.
- Missed work is moved by crossing out and rewriting.
- Due dates drift, so customers' four-weekly cycles become five or six weeks, or three.
- Customers are told about changes one by one, or not at all.
- The knock-on effect on the following weeks is not visible.
- Payment rounds and collection days fall out of step with cleans.
Confused customers and lost cleans
Customers who do not know when you are coming leave gates locked and cars on drives, or assume you have stopped and find someone else. Cleans that slip off the round are income lost for that cycle. Cleaning a house too early annoys customers who pay per clean. And the evenings spent reworking the notebook are unpaid time.
A round that reschedules itself when you say so
We build a rescheduling feature into your round records, either inside your current round management app where it allows, or in a small web app built around your customer list.
- You mark a day or part of a day as lost to weather with one tap in the van.
- You choose your rule, or set a default: push the round back, spread the missed houses over the next few days, or catch up on a set day.
- The system shows the effect before you commit: which customers move, which days get busier and which cycles stretch.
- Each customer's due date is recalculated from their frequency, so the next clean is set from when they were actually cleaned, not the original plan.
- Only the customers whose day changes get a text, with the new day and any reminder about gates or cars.
- Customers who pay on the day or have access arrangements are flagged, so you know which ones need extra notice.
| Rain day consequence | Notebook | Rescheduling tool |
|---|---|---|
| Where the missed houses go | Decided and rewritten by hand | Chosen rule, applied in one step |
| Customer due dates | Drift over time | Recalculated from the real clean date |
| Customers told | Some, by individual texts | Every affected customer, automatically |
| Next week's workload | Not visible | Shown before you commit |
The decision to work or not stays with you. The tool only takes the admin out of the consequences.
Weather still wins, but the round stays in order
After a wet week, you get back to work with a clear list for each day and customers who already know when you are coming. Cycles stay close to what customers pay for. You stop spending evenings rewriting the round. And when someone asks when you are next due, you can tell them.
In a wet month, the difference is bigger. Instead of the round unravelling a little more each week, it is reset each time you mark a lost day, so it never drifts far from where it should be.
Does bad weather do this to your round?
- After a wet spell you are not sure who is due.
- Customers text asking when you are coming, or why you came early.
- You rewrite the round in a notebook after rain days.
- Some customers go much longer than their frequency between cleans.
- You only tell some customers when their day changes.