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

# Plan and replan a week

> Run weekly planning, review the result, and understand when a week needs another accepted plan.

Plan a week after its orders, team availability, or scheduling requirements are ready. Replan when Sweeply shows that the current week data has changed or the latest attempt needs attention.

## Automatic planning horizon

Sweeply automatically prepares and processes the current week and the next three weeks. Subscription demand is prepared farther ahead, and you can manually request planning for any non-past week.

## Run planning

<Steps>
  <Step title="Open the target week">
    Select **Planning** and choose the week. Review unplanned orders, member capacity, availability changes, and existing protected work.
  </Step>

  <Step title="Select Plan week">
    Confirm the displayed week. The confirmation reminds you that protected dates, started or completed work, customer promises, and manually locked routes remain unchanged.
  </Step>

  <Step title="Wait for the result">
    Planning runs in the background. The page shows the latest result when it completes.
  </Step>

  <Step title="Review assignments and issues">
    Inspect scheduled and unplanned counts, routes, travel, service time, utilization, overtime risk, and every planning issue.
  </Step>

  <Step title="Correct and replan when needed">
    Use issue actions to fix locations, eligibility, availability, duration, capacity, or hard requirements, then plan the week again.
  </Step>
</Steps>

## Why a week needs planning again

A week may show **Needs planning** after new demand arrives, a scheduling input changes, a planning attempt fails, or a result can no longer be accepted safely.

## Outdated results

If orders, availability, requirements, or other concrete planning inputs change while or after an attempt runs, its result may show **Outdated**. An outdated result is diagnostic history; run planning again to create a current accepted plan.

<Note>
  Planning writes schedules to orders. The temporary run history is not the permanent source of the schedule; order details and order activity remain authoritative.
</Note>