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

# Scheduling

> Recurring attendant schedules, planned visits, and authorization-aware conflict tracking.

Scheduling holds recurring attendant schedules, planned visits, and authorization-aware conflict
tracking.

It sits between an authorization and a delivered visit: what you plan here becomes what your
attendants verify in [Time & Attendance](/attendance).

## Who can use it

Organization Admins, Location Admins, Clinical Managers, Client Coordinators, and EVV Maintenance
staff.

## The week board

Above the tabs, a week board shows the schedule at a glance. Use it to spot gaps and clashes across
the week rather than record by record.

## Tabs

<AccordionGroup>
  <Accordion title="Recurring Schedules" icon="repeat">
    Recurring weekly visit patterns linking members, attendants, and service authorizations.

    **Columns:** Member · Attendant · Authorization · Dept · Start · End · From · To · Status

    Opening a schedule exposes the full pattern: **Service Code**, **Start Time**, **End Time**, a
    checkbox for each day Monday through Sunday, **Effective From** and **Effective To**, status,
    and notes.

    This is the template. One recurring schedule generates many visits.
  </Accordion>

  <Accordion title="Planned Visits" icon="calendar-check">
    Visit instances generated from recurring schedules, awaiting EVV verification.

    Each planned visit is a specific date and time produced by a recurring schedule. They sit here
    until an attendant clocks in against them.
  </Accordion>
</AccordionGroup>

## Authorization-aware conflict tracking

Scheduling checks each visit against the member's authorization. It flags visits that fall outside
the authorized date range, exceed remaining units, or use a service code the authorization does not
cover.

<Warning>
  Conflicts are warnings about billability, not care. A flagged visit can still be delivered — but
  it will not produce a payable claim. Resolve the authorization before the visit happens, not after.
</Warning>

## Building a recurring schedule

<Steps>
  <Step title="Confirm the authorization first">
    The schedule links to an authorization. Check it is active, in date, and has units remaining.
    See [Authorizations](/members/authorizations).
  </Step>

  <Step title="Select the member and attendant">
    The attendant must have current credentials. See
    [Credentials and checks](/employees/credentials-and-checks).
  </Step>

  <Step title="Set the weekly pattern">
    Choose the days and set **Start Time** and **End Time**.
  </Step>

  <Step title="Set the effective dates">
    **Effective From** and **Effective To** bound the pattern. Keep them inside the authorization's
    date range.
  </Step>

  <Step title="Activate and review generated visits">
    Check the **Planned Visits** tab to confirm the pattern produced the visits you expected.
  </Step>
</Steps>

<Tip>
  Set **Effective To** to match the authorization's end date. The schedule then stops generating
  unbillable visits automatically when the authorization lapses.
</Tip>

## Where visits go next

```mermaid theme={null}
graph LR
    A[Recurring schedule] --> B[Planned visit]
    B --> C[EVV visit<br/>attendant clocks in]
    C --> D[Verified]
    D --> E[Billing]
```

See [Time & Attendance](/attendance) and [EVV to paid claim](/guides/evv-to-claim).

## Troubleshooting

| Problem                                          | What to check                                                                                       |
| ------------------------------------------------ | --------------------------------------------------------------------------------------------------- |
| No planned visits generated                      | Confirm the schedule is active and **Effective From** has been reached.                             |
| Visits flagged as conflicting                    | Check the authorization's dates, remaining units, and service code.                                 |
| An attendant cannot be assigned                  | Their credentials may have lapsed. See [Credentials and checks](/employees/credentials-and-checks). |
| Planned visits continue past the authorization   | **Effective To** is later than the authorization end date. Shorten it.                              |
| A visit happened but is not in Time & Attendance | The attendant may not have clocked in against the planned visit. It will appear as missed.          |

## Related

<CardGroup cols={2}>
  <Card title="Time & Attendance" icon="clock" href="/attendance">
    EVV verification and exception handling.
  </Card>

  <Card title="Authorizations" icon="file-check" href="/members/authorizations">
    Units and date ranges that bound your schedules.
  </Card>
</CardGroup>