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

# Time & Attendance

> Electronic Visit Verification, exception maintenance, and aggregator export.

Time & Attendance covers Electronic Visit Verification, exception maintenance, and aggregator export.

This is where a planned visit becomes a verified one. Nothing bills until a visit clears here.

## Who can use it

Organization Admins, Location Admins, Human Resources staff, and EVV Maintenance staff.

## The exception queue

Above the tabs, the EVV maintenance queue lists visits needing correction. Work this queue daily —
every unresolved exception is revenue that cannot be billed and, in Texas, an EVV compliance
data point.

## Tabs

<AccordionGroup>
  <Accordion title="EVV Visits" icon="clock">
    Electronic Visit Verification records with clock-in/out, geofence results, reason codes, and
    aggregator status.

    **Columns:** Member · Attendant · Clock In · Clock Out · Units · Geofence · Status ·
    Reason Code · Aggregator

    | Field                    | What it tells you                                                 |
    | ------------------------ | ----------------------------------------------------------------- |
    | **Clock In / Clock Out** | When the attendant actually started and finished                  |
    | **Units**                | Actual units delivered, derived from the clock times              |
    | **Geofence**             | Whether the clock event happened at the member's location         |
    | **Status**               | `SCHEDULED`, `IN_PROGRESS`, `COMPLETED`, `MISSED`, or `EXCEPTION` |
    | **Reason Code**          | The explanation attached to an exception                          |
    | **Aggregator**           | Whether the visit has been accepted by the state aggregator       |
  </Accordion>

  <Accordion title="Scheduled Visits" icon="calendar-check">
    Planned visit instances materialized from recurring schedules, with unit and conflict tracking.

    **Columns:** Member · Attendant · Date · Start · End · Units · Status · Conflicts

    **Conflicts** flags visits that clash with an authorization limit or another assignment.
  </Accordion>
</AccordionGroup>

## Working exceptions

A visit in `EXCEPTION` status needs a reason code before it can proceed to billing.

<Steps>
  <Step title="Open the exception queue">
    Start with the oldest. Aggregator submission windows are time-bound.
  </Step>

  <Step title="Identify why it failed">
    Common causes are a failed geofence, a missing clock-out, or units that exceed the schedule.
  </Step>

  <Step title="Apply the correct reason code">
    The reason code must reflect what actually happened. It is submitted to the state aggregator.
  </Step>

  <Step title="Confirm the visit reaches COMPLETED">
    Only completed visits without outstanding exceptions can bill.
  </Step>

  <Step title="Check aggregator status">
    A visit accepted locally still has to be accepted by the aggregator.
  </Step>
</Steps>

<Warning>
  Reason codes are a regulatory record, not a way to clear a queue. Applying a code that does not
  match what happened misrepresents visit data to the state. If you cannot determine what happened,
  escalate rather than guess.
</Warning>

## Geofence failures

A failed geofence means the clock event did not register at the member's location. It does not by
itself mean the visit did not happen — a wrong address on the member record produces the same
result.

<Steps>
  <Step title="Check the member's address">
    An incorrect address in [Members](/members) causes systematic geofence failures for that member.
  </Step>

  <Step title="Check whether care was delivered elsewhere legitimately">
    Some services are delivered in the community.
  </Step>

  <Step title="Apply the reason code that matches">
    Then correct the underlying address so the failure does not recur.
  </Step>
</Steps>

## Where visits go next

```mermaid theme={null}
graph LR
    A[Scheduled visit] --> B[Attendant clocks in]
    B --> C{Clean?}
    C -->|Yes| D[COMPLETED]
    C -->|No| E[EXCEPTION]
    E -->|reason code| D
    D --> F[Aggregator]
    D --> G[Billing<br/>claim lines]
```

See [Billing](/billing) and [EVV to paid claim](/guides/evv-to-claim).

## Troubleshooting

| Problem                                  | What to check                                                              |
| ---------------------------------------- | -------------------------------------------------------------------------- |
| A delivered visit is missing             | The attendant may not have clocked in. It will show as `MISSED`.           |
| Units do not match the schedule          | **Units** derive from actual clock times, not planned times.               |
| Geofence fails repeatedly for one member | The member's address is probably wrong. Correct it in [Members](/members). |
| Aggregator status is not advancing       | Check the visit is `COMPLETED` with no outstanding exception.              |
| Verified visits are not reaching Billing | Confirm the member has an active authorization with units remaining.       |

## Related

<CardGroup cols={2}>
  <Card title="Scheduling" icon="calendar-clock" href="/scheduling">
    Where planned visits come from.
  </Card>

  <Card title="EVV matching" icon="link" href="/billing/evv-matching">
    How verified visits become claim lines.
  </Card>
</CardGroup>