Rain Moves One Visit. What Happens to the Next Twelve?
The message is polite, which somehow makes it worse. "Hi, I think you might have missed us. The grass is getting pretty long." You check. Her lawn is every other week, due Tuesday the 2nd. It rained, so the crew moved her to Friday the 5th. The next visit was already on the calendar for Tuesday the 16th, eleven days later instead of fourteen. Then that one slid too. Somewhere in there the rhythm broke, nobody noticed, and she has now gone twenty-four days without a cut.
Weekly accounts forgive this. Every-other-week accounts do not. Break the rhythm once and the lawn is either cut too soon, which costs you money, or cut too late, which costs you the customer.
This guide is about the two questions behind that message: when a moved visit should drag the rest of the series with it, and how to know which properties are due without keeping it all in your head.
Why every-other-week work slips
- The schedule is a fixed calendar. Most software drops future visits onto dates and leaves them there. Move one and the rest do not care, so the gap after the moved visit is short and the gap before the next one is long.
- Every other week only means something relative to a day. Once the anchor slides, the following visits are measured from the wrong day, and the error stays in the schedule until a human spots it.
- Rain hits the same route twice. A wet Tuesday and a wet Friday in one fortnight, and a two-week cadence becomes three.
- Nobody is counting days since. A weekly account announces itself: it is on this week's route. A biweekly account is absent from the route half the time, which looks exactly like a biweekly account that was forgotten.
When should the rest of the series move?
Not every move should ripple. Shifting a whole season because a crew came a day late creates more churn than it prevents. Shifting nothing after a week-long delay means the next cut lands on top of the last one.
The rule that works in practice is a threshold, set by how often the job repeats. Here is the one we settled on in Jeero:
Repeats | Series stays put | Series follows |
|---|---|---|
Weekly | Moves of up to 3 days | 4 days or more, by whole weeks |
Every other week | Moves of up to 3 days | 4 days or more, by whole weeks |
Monthly | Moves of up to 7 days | 8 days or more, by the same number of days |
Daily | Any move | Never, tomorrow already has a visit |
Several weekdays | Any move | Never, the visits are days apart anyway |
Weekly and every-other-week series shift by whole weeks, which means they land back on their usual weekday. That matters more than it sounds: your Tuesday route stays a Tuesday route, so nothing has to be resequenced. Move an every-other-week Tuesday out to Saturday and the rest of the series moves one week, still on Tuesdays.
Only visits after the one you moved are touched, and only ones still scheduled. A finished visit stays in the past and the job a crew is working right now stays on today's route. Each moved visit keeps its notes, line items, crew and client, because the visits are moved rather than deleted and recreated. Future visits the system generates from then on follow the new rhythm too.
See it before you save it
A rule that fires invisibly is worse than no rule. Before you save a new date, Jeero spells out what it is about to do, for example that the next three visits in the series will move one week later. Pick a closer date and the note disappears, because nothing else needs to move.
The same sentence follows the change everywhere afterwards: the confirmation on screen, the toast in the mobile app, the notification an owner gets when a crew lead moved the visit, and each job's own history, which records the old date, the new date and how far the series shifted.
Moving a whole rained-out day works the same way. The Move day preview adds a line for the recurring work on that day, such as three later visits in one recurring series will move too, so you know how far the week is shifting before you commit.
Only the customer whose visit you moved hears about it. Customers whose visits shifted along behind it are not messaged, and still get their usual reminder the day before each visit. The full rules are in the When a Recurring Visit Moves guide.
Knowing which lawns are due, without remembering
Rhythm is half the problem. The other half is knowing where each property stands right now.
Every recurring job shows its last visit, the next one due, and a plain status: on schedule with the days to go, due today, overdue by however many days, or nothing scheduled. It sits on the job itself, on the client's page under Recurring visits, and in the mobile app. An owner with six properties is one page, not six.
The safety net for the one that slips anyway
Some visits slip past every good intention. So a series is flagged once it has gone a full extra cycle beyond its rhythm without a finished visit:
Cadence | Flagged after |
|---|---|
Weekly | More than 2 weeks with no visit |
Every other week | More than 3 weeks with no visit |
Monthly | More than a month and a week with no visit |
Daily | Never |
When a series crosses that line the job page warns with the number of days, the client's list shows a badge, and the jobs list grows a filter button with a count so you can pull up just the slipped ones. Overnight, owners and managers get a single notification naming how many series slipped and which has waited longest, not one message per lawn. Finish a visit and the flag clears on its own. If it slips again later, you hear about it again. You can switch the notification off under company notifications, or per person in notification preferences.
A five-minute weekly routine
Whatever software you use, this keeps every-other-week work honest:
- After any rain day, check that the moved visits and the next scheduled ones are still a full cycle apart.
- Scan for any property past its cadence plus a week, and book those first.
- Keep an eye on the accounts that slip repeatedly. A lawn that keeps going three weeks is usually telling you the cadence, the price, or the route position is wrong.
- Once a season, ask which every-other-week accounts should simply be weekly during peak growth.
Frequently asked questions
If I move one visit of a recurring job, should the rest move?
Only when the move is big enough to matter. A day or two is still the same week, so the cadence should hold. Four days or more on a weekly or every-other-week job means the next visit would land too soon, so the rest of the series should shift by whole weeks and keep its usual weekday.
How many days is too long between biweekly visits?
Fourteen days is the plan, and seventeen or eighteen is usually fine in slower growth. Past twenty-one days the lawn looks neglected and the customer notices before you do, so treat three weeks as the line where the account needs a visit booked immediately.
Does moving a recurring visit mess up my routes?
It should not. If the series shifts by whole weeks, every visit lands on the same weekday it always used, so the route it belongs to is unchanged. Only the dates move, and the visits keep their crew, notes and line items.
Do I have to tell every customer when a series shifts?
No. Tell the customer whose visit actually moved. The later visits are still weeks away, and those customers get their normal reminder before each one. Messaging everyone about a date that changed by a week creates confusion, not confidence.
Keep the rhythm, keep the customer
Biweekly accounts are quiet until they are not. The lawn that goes twenty-four days is the one that cancels, and it is almost never a decision anyone made. It is a rain day, a moved visit and a fortnight nobody was counting.
See it working in the demo, or start a free trial and set up one every-other-week job to watch what a moved visit does to the rest of the series. Compare what each plan includes on the pricing page.