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

# Create a patrol route in Rekkeh for guard schedules

> Configure a patrol route with a schedule, ordered checkpoints, and assigned guards so Gate Ops users can run the patrol on their shift.

Patrol routes define the recurring schedule, checkpoint order, and guard assignments for a guard patrol. Once you create a route, assigned guards see scheduled instances in the Gate Ops mobile app and scan each checkpoint in order.

<Note>
  Your facility must have the **Guard Patrol** module enabled, and your account needs the `patrol:create` permission. The **Security Admin** system role has full patrol permissions; **Estate Manager** has full administrative access.
</Note>

## Create a patrol route

<Steps>
  <Step title="Open Patrol Routes">
    Go to **Security > Patrol Routes** and click **New route**.
  </Step>

  <Step title="Enter basic details">
    Enter a **Route name** (1 to 255 characters). Then set the schedule and timing fields (see table below for defaults and ranges).
  </Step>

  <Step title="Add checkpoints">
    Add checkpoints in the order guards must scan them. Click **Add checkpoint** to add more; you cannot delete the last remaining checkpoint. Each checkpoint has a **Name** (1 to 255 characters), an optional **Link to gate**, and optional location fields (**Latitude**, **Longitude**, **Geofence (m)**). A geofence is applied only when both latitude and longitude are set; the default radius is 75 meters (range 10 to 2,000). Blank checkpoints are dropped when you save.
  </Step>

  <Step title="Assign guards">
    Use the **Assigned guards** picker to choose who runs this route. Only active guards are searchable. Remove a guard by clicking the pill next to their name.
  </Step>

  <Step title="Save">
    Click **Create route**. On success you see **Patrol route created**. On failure you see **Failed to save patrol route**.
  </Step>
</Steps>

## Schedule and timing fields

| Field                   | Default | Range          |
| ----------------------- | ------- | -------------- |
| Interval (minutes)      | 120     | 15 to 1,440    |
| Expected duration (min) | 45      | 5 to 480       |
| Active from             | 06:00   | 00:00 to 23:59 |
| Active until            | 22:00   | 00:00 to 23:59 |
| Start window (± min)    | 15      | 1 to 120       |
| Checkpoint grace (min)  | 10      | 1 to 120       |

The route list shows each route's schedule as `Every {interval}m · {active from}–{active until}` and its status as **Active** or **Inactive**.

## Print checkpoint QR codes

Each route row has a QR action showing the checkpoint's QR code. Click **Copy payload** to copy the QR string. Print and mount the code at the physical checkpoint so guards can scan it during a patrol.

<Note>
  QR payloads use the `rekkeh-patrol:` prefix. Editing a route keeps existing checkpoint QR tokens, so printed codes stay valid. New checkpoints get new tokens.
</Note>

## Edit or delete a route

Use **Edit** on a route row to change its fields, checkpoints, or guards, then click **Save changes**. To remove a route, use the delete action and confirm **Delete patrol route?** — the route and its checkpoint schedule are permanently removed.

<Warning>
  Deleting a patrol route permanently removes the route and all its scheduled checkpoint data.
</Warning>

## What's next

* [Run a patrol in GateOps](/security/run-patrol) — how guards use the patrol on their shift.
* [Review patrol logs](/security/review-patrol-logs) — how admins review scan evidence and compliance results.