Skip to main content

Moving repeating jobs and understanding end dates

Written by Chris Kiehl
Updated yesterday

When you drag and drop a repeating job to a different day, there are two possible outcomes depending on what you do next. Picking the wrong one can make it look like something went wrong β€” especially when an end date suddenly appears on your job. This article explains what each option does and why.

Quick summary

  • Do nothing β€” a one-off change. Only the visit you dragged moves. Future visits stay exactly where they were.

  • Click "Apply to future visits" β€” changes the repeating pattern from this point onward. The system splits the series in two: the old series ends, and a new series starts from the moved visit.

The end date you see after applying to future visits is expected. It marks where the old series stops and the new one begins.

Option A: Do nothing (default behaviour)

Use this when you need a one-time adjustment -- for example, a public holiday or a scheduling conflict for just one week.

What happens:

  1. Only the visit you dragged moves to the new date.

  2. All future visits keep their existing schedule.

  3. The gap between this visit and the next one may be slightly shorter or longer, but after that the normal interval continues.

Example (14-day pattern):

  • Original schedule: Mar 12 > Mar 26 > Apr 9

  • You move Mar 26 to Mar 27 (one day later)

  • Result: Mar 12 > Mar 27 > Apr 9

  • The gaps become 15 days, then 13 days, then back to 14 days as normal

No new series is created. No end date appears.

Option B: Click "Apply to future visits"

Use this when you want all future visits to follow the new day or date pattern -- for example, permanently moving a fortnightly job from Thursdays to Fridays.

What happens:

  1. The system ends the current series. An end date is added to mark the last visit under the old schedule.

  2. A new series starts at the moved visit date.

  3. Future visits continue from there at the normal interval.

Example (14-day pattern):

  • Original schedule: ... > Mar 12 > Mar 26 > Apr 9 > ...

  • You move the Mar 26 visit to Mar 27 and click Apply to future visits

  • Old series ends at Mar 12 (end date added)

  • New series starts: Mar 27 > Apr 10 > Apr 24 > ... (every 14 days)

Why does an end date appear?

Think of it like version history for your schedule:

  • Series 1 = the original repeating pattern (how the schedule used to run)

  • Series 2 = the new repeating pattern (from the moved visit onward)

The end date is simply the handover point between those two series. It tells SortScape: "stop generating visits for the old pattern here."

This is the same way most calendar applications handle changes to repeating events -- it keeps your scheduling history accurate.

Which option should I use?

  • Do nothing if this is a one-time exception (public holiday, one-off reschedule).

  • Choose Apply to future visits if you want to permanently change the repeating day or pattern from now on.

Tip: If you are doing a lot of one-off schedule shuffling, avoid clicking "Apply to future visits" unless you intentionally want to start a new repeating series. Otherwise you will see end dates appear on jobs that previously had none.

What if I applied to future visits by mistake?

If you accidentally split a series and want to undo it, open the property and check the repeating job settings. You can remove the end date from the old series and delete the new series that was created, then set things back to how they were.

If you need help fixing this, do not hesitate to reach out to our support team.

Did this answer your question?