> ## 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.

# Understand schedule locks and notified orders

> Learn how the before-delivery window and customer notifications protect schedules from automatic movement.

A locked visit keeps a near-term or communicated schedule stable. Automatic planning preserves it, while an authorized operator can still make a deliberate override.

## The before-delivery protection window

The **Days before delivery** setting under **Settings** > **Notifications** controls both reminder timing and calendar protection.

If the value is 2, Planning protects:

* Today
* Tomorrow
* The following day

Past dates are also protected. Automatic planning creates no new route capacity on those dates, so it neither moves existing visits nor inserts unrelated unplanned work there.

## What a notified order means

When a before-delivery notification is created for the current schedule, Sweeply stores the customer promise tied to that schedule.

* For work that does not require presence, the promise normally protects the communicated service date.
* For presence-required work, the promise normally protects the communicated time or arrival window.
* A notified visit is not offered to ordinary automatic reassignment.

The notification delivery result and the schedule promise are separate. A failed email or SMS remains visible for follow-up but does not automatically release the protected schedule.

## What Locked means

Sweeply shows a scheduled, not-started order as **Locked** when either:

* Its service date is inside the before-delivery protection window, or
* A current notification promise matches its scheduled start

The order remains scheduled underneath the display state.

## Override a protected visit

<Steps>
  <Step title="Start the move or route edit">
    Select the protected visit and choose the intended new week, date, member, time, or route position.
  </Step>

  <Step title="Review the customer impact">
    Compare the existing promise with the proposed schedule. A date-only promise may survive a same-date route reorder; a changed presence-required interval normally does not.
  </Step>

  <Step title="Confirm and enter a reason">
    Confirm that you understand the protected schedule is being superseded and record the operational reason.
  </Step>

  <Step title="Apply the change and contact the customer">
    Send an updated notification when offered, or contact the customer deliberately. Review any resulting planning issue.
  </Step>
</Steps>

<Warning>
  Moving a notified visit can make already communicated information wrong. Do not treat the confirmation as a routine click-through.
</Warning>