Handling rain days and absences in a service business

Two things reliably knock a service business off course: the weather and an empty seat in the van. Rain washes out a gardening day; a cleaner calls in sick at half past seven. Neither is the real problem. Every service business plans for both. The real problem is the hour of phone calls, the customers who did not get the message, and the week that never quite recovers. The disruption costs you a day; the admin around it costs you three evenings.

Here is a system that makes both kinds of bad morning boring.

Decide early, decide once

The worst disrupted day is the dithered one: half the crew sets off, two jobs get half done, and by ten o'clock everyone is behind and soaked, or covering blind. Set yourself a decision time, the night before or at six in the morning, look at the forecast or the message from your sick team member, and make one call for the day.

For weather, have a written threshold you believe in, even a rough one. Light showers, work on. Persistent rain or waterlogged ground, off. For absence, the same spirit: decide up front which jobs get covered by whoever is in, and which get moved. A pre made rule turns an anxious judgement into a routine.

Tell everyone at once, in one message shape

The moment you decide, two groups need to know: your team and the affected customers. The message to customers should be short, warm and definite:

Morning. We will not be able to visit you today [with today's weather / as one of the team is unwell]. We will fit your visit back in over the next few days and will let you know the new day. Thank you for bearing with us.

Notice what that message does. It cancels, it promises a reschedule, and it removes the need for the customer to reply. The version that causes work is the vague one: "might not make it today, will see how things look." Vague messages generate questions, and questions generate your lost morning.

Keep a list of exactly who was told what. When a wet week and a sick colleague land together, memory alone will drop someone, and the customer nobody told is the one who mentions it in a review.

Cover, move, or skip: the absence triage

An absence differs from rain in one useful way: the rest of the team is still working. So triage the absent person's day in this order. First, the fixed customers, the ones who genuinely need their day or their person: can someone else cover them today? Second, the flexible visits: slide them into the coming days alongside the usual work. Third, anything that cannot move and cannot be covered: tell the customer early and honestly, and put it first on the list for their next visit.

Part days matter here too. Someone at an appointment from nine until twelve has an afternoon you can still use. Knowing your team's real available hours, rather than treating every absence as all or nothing, keeps half days from becoming lost days.

Build the catch up into the round, not onto it

Where does the cancelled work go? If your business runs at one hundred per cent of your hours, the honest answer is nowhere, and every wet day or sick day pushes a bow wave of work in front of you until something gives.

Two habits fix this. First, plan the round to about eighty five per cent of real capacity, so there is standing room for disruption. Second, keep most customers flexible on the exact day. If Mrs Ellis expects a visit roughly every fortnight rather than religiously on Tuesdays, a lost Tuesday barely registers: her visit simply lands on Thursday. The more of your business runs on rhythm rather than fixed days, the more a bad morning becomes a shrug.

For the customers who genuinely need fixed days, agree in advance what happens when their day is lost. Next available day, or skip to the next cycle with a reduced charge if that is your policy. Deciding it once beats renegotiating it every wet Tuesday.

After the disruption

When the weather clears or the team member returns, resist the urge to cram everything into the first good day and blow the schedule for the rest of the week. Spread the catch up over the slack you planned. And watch the pattern: if weather is eating your margins repeatedly, that is pricing information for outdoor work. If absence is, that is a staffing conversation, not a scheduling one.

The short version

Decide early with a pre made rule, for rain and for absence alike. One clear message to team and customers, and a record of who got it. Triage an absent person's day: cover the fixed, slide the flexible, be honest about the rest. Keep slack in the round so cancelled work has somewhere to go. Then the two great disruptors of this trade stop being crises and become Tuesdays.

How RotaRound helps

• Cancel a whole day or one team member's day in one tap, with a reason, and every affected customer is emailed under your name.
• Each cancelled visit waits to be scheduled with a suggested slot; rebook it in one tap or choose another time.
• A team member reports sickness from their page, and the request appears on your dashboard for you to act on.
• The planner knows each team member's hours, absences and part days when it places visits.
• Each customer's usual team member and weekday are kept where they can be, and you can see and change the pattern on their property.