> ## Documentation Index
> Fetch the complete documentation index at: https://help.sweeply.dk/llms.txt
> Use this file to discover all available pages before exploring further.

# Move recurring visits to weeks with nearby work

> Analyse subscription visit weeks, review estimated driving and timing consequences, and apply selected changes.

Use **Insights** > **Visit weeks** to find recurring visits that could move to weeks with nearby work. You review and approve each selection. The recurring frequency stays the same, but the transition can create a longer or shorter gap between visits.

## Before you begin

You need read access to subscriptions, orders, and planning. Running an analysis or applying changes also requires permission to update subscriptions and planning.

Suggestions are for active subscriptions with usable map locations. Weekly subscriptions do not receive week-shift suggestions. Check the customer's agreement before changing when visits occur.

## Analyse and review

<Steps>
  <Step title="Run an analysis">
    Open **Insights** > **Visit weeks** and select **Analyse**. You can leave the page while it runs. The analysis creates suggestions without changing subscriptions or visits.
  </Step>

  <Step title="Choose suggestions">
    Review the analysis date, search or filter by area and frequency, and select the suggestions you want. Each row explains the first visit that would move and how nearby work changes. You can select across pages or select all matching suggestions.
  </Step>

  <Step title="Review the selection together">
    Open the review. Check the combined annual driving estimate, the comparison of upcoming service hours, the first affected weeks, the one-time gap, and the visits that need planning. The combined estimate accounts for the selection; do not add the individual row estimates yourself.
  </Step>

  <Step title="Choose customer notifications">
    Set **Notify customers** if you want an email, SMS, or the available combination. It defaults to **Off**. Preview the message before applying. The template is configured under **Settings** > **Notifications** for **Visit week changed**.
  </Step>

  <Step title="Apply and check the result">
    Apply the selected changes and follow the bulk action. Review updated, skipped, and failed subscriptions, plus any notification failures. Open Planning for the visits that now need a new place in the schedule.
  </Step>
</Steps>

<Check>
  Successfully changed subscriptions use the new visit weeks. Applied suggestions leave the list, and the change history records who made each change and the previous and new values.
</Check>

## Understand the estimate

The annual estimate compares how close visits are to other work in the same week, using road distances between addresses. It is not a completed route plan or a measurement of achieved savings.

The analysis does not check working hours, team capacity, qualifications, preferred members, or preferred weekdays. Review the workload comparison and your operational constraints before applying. Actual driving can differ after the visits are assigned to routes.

The estimate compares recurring work over 52 weeks. Immediate consequences are shown separately for the next 12 weeks, so postponing a visit is not counted as a driving saving.

## What changes in the schedule?

A week change moves the recurring pattern by whole weeks. The new pattern starts no earlier than next week and takes protected visits into account.

* Visits protected by customer notices, started or completed work, invoices, or payments are preserved.
* Unprotected generated visits before the new start can be removed, including visits in the current week.
* Later generated visits are replaced by visits in the new weeks that need planning again.
* The normal automatic-planning freeze window is not a subscription-edit lock. Review the stated consequences even for visits within that window.

For example, a subscription normally visited every four weeks in weeks 42, 46, and 50 might move to weeks 43, 47, and 51. If the week-42 visit is already protected, it stays, and the following visit can be in week 47: a five-week gap once, then every four weeks again.

## Follow up on changes and messages

An analysis stays available until you run another one; it does not refresh automatically. Run a new analysis when the surrounding work has changed significantly. A subscription whose recurrence or property changed since the analysis is skipped when applying.

Customer messages are sent after a change is saved. A failed or unavailable delivery does not undo the week change. Check the result and message history, and follow up when a customer still needs to be informed.

## Related guides

* [Understand subscription recurrence](/subscriptions/recurrence-and-cadence)
* [Update future subscription orders](/subscriptions/update-future-orders)
* [Plan and replan weeks](/planning/plan-and-replan-weeks)
* [Choose notification channels](/customer-communication/notification-channels-and-rules)
* [Track bulk actions](/getting-started/track-bulk-actions)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.