Changing a recurring series is a negotiation, not a bulk edit — because some of those future visits already belong to someone. Your contractor accepted them; a client contact may have been told the day. This page explains exactly what happens when you change a series' day, week, or cadence, and how to read the calendar while a change is in flight.
What happens the moment I change the series?
Two different things, depending on each future visit's state:
- Unbooked visits (spawned but not yet dispatched to a contractor) are respun onto the new pattern immediately. Nothing was promised to anyone, so nothing needs confirming.
- Booked visits (dispatched — a contractor holds them) are proposed a move, not moved. Each gets a pending amendment proposal targeting its paired new date. The visit stays on its current date, and the calendar badges it: "→ moving to [new date] pending contractor confirmation." The confirmation toast after your edit says it plainly: "Series updated. N booked visits await contractor confirmation — they stay on their current dates until confirmed."
This is deliberate. A committed visit is a promise with a person on the other end; the platform never silently rebooks it.
When do the held visits actually move?
When the contractor accepts. Re-accepting the ongoing series (through their work order) actions every pending date proposal in one step: each committed visit moves onto its paired new date, and if the scheduler had already minted a placeholder on that date, the placeholder is absorbed so the period ends with exactly one live visit. Declining a proposal releases it — the visit keeps its original date and the proposal is closed, not left dangling.
If you change the series again before the contractor responds, stale proposals pointing at dates the new pattern no longer wants are superseded automatically and fresh ones are raised. You never need to clean up old proposals by hand.
What stops a double-booking while all this is pending?
The scheduler's period guard: one live visit per contract line per period. While a committed Wednesday visit occupies October, the nightly scheduler will not also place the new Thursday date into October — it records a loud, queryable skip event instead. The new cadence takes over period-by-period as each committed visit either moves (contractor confirmed) or completes.
Two things worth knowing before a big tidy-up
- Cancellations notify. Cancelling a dispatched visit tells the assigned contractor, in-app and by email (settings-gated). Cancelling eleven strays in one sitting sends eleven notifications — consider a one-line heads-up to the contractor first.
- Two lines on one site is not a conflict. If a site deliberately runs two cadences — an outside line on one weekday and an inside line on another, or two lines placed to marry up with different runs — each line holds its own one-visit-per-period rule independently. Same-day visits from different lines can legitimately coexist.