Setting up transport routes and vehicles

A transport route is a recurring trip you set up once and let Enmantle schedule for you. It carries the riders, the vehicle, the days of the week, the pickup and drop-off, the time, and the billing lane. From that template, Enmantle generates a run for each scheduled day — one dated instance a staff member can claim and drive. This guide is for admins setting up routes and the fleet vehicles they use.

If you only run the occasional one-off trip, you don't need a route — log it on the shift instead. See Logging HPC transportation vs. NMT. Routes are for the trips that repeat.

Turn the feature on first

Transport Routes is an opt-in feature, off until it's switched on for your agency. Open Transport Routes from the dashboard. If you see "Transport Routes isn't turned on yet," ask a platform admin to enable feature.transportRoutes.enabled for your tenant. Once it's on, the page shows your routes and the missed-run panel.

Only Super-Admins and Admins can open the routes page — route cards carry rider names, which are protected health information. Directors and DSPs don't see the setup screen.

Add your fleet vehicles

A route can be tied to an agency-owned fleet vehicle, separate from the personal vehicles staff use for ad-hoc trips. Each fleet vehicle carries a name, license plate, passenger capacity, and compliance dates (insurance, registration, inspection).

When you create a route, the Fleet vehicle picker lists your active vehicles by name and plate — or No vehicle if the driver will use their own.

Create a route

1. On the Transport Routes page, click New route. The New Route dialog opens.
2. Give it a Name * — something a driver will recognize, like "Tessa B — PM takehome."
3. Under Riders, search clients by name and add each expected rider as a chip.
4. Under Runs on, tap the weekday circles (S M T W T F S) for the days this route runs.
5. Set the Time the route departs, and pick a Fleet vehicle (or leave it No vehicle).
6. Fill in From (origin) and To (destination). Both use address autocomplete — pick the real place from the suggestions.
7. Choose the Purpose / lane. This is the billing lane the trip will bill on, so it matters.
8. Click Create route.

Pick the right billing lane

The Purpose / lane dropdown mirrors the trip-log purposes, so a route bills the same way an ad-hoc trip of that type would:

• HPC transportation — transportation provided as part of a Homemaker/Personal Care shift.
• NMT (per trip) — non-medical transportation billed as a flat per-trip amount. Choosing this reveals an NMT mode field: Eligible vehicle or Taxi / livery / bus.
• NMT (per mile) — non-medical transportation billed on odometer mileage.
• Administrative
• Personal / dead-head

If a rider you added isn't authorized for the lane you picked, Enmantle shows an advisory warning in amber after you save. The warning never blocks the save — it's there so you catch a mismatch before it becomes a billing correction. For the difference between HPC and NMT, see Logging HPC transportation vs. NMT.

Vary a single day with "Except on…"

Most routes go to the same place every day. When one weekday is different — Wednesday goes to Dad's instead — you don't need a second route.

1. In the route dialog, expand + Except on….
2. Click Add override and choose the weekday.
3. Set a different To (inherits everything else) destination, and/or a different Start time and End time.

An override only changes the destination and the times for that one weekday; everything else — riders, vehicle, and the origin — inherits from the route. The origin is deliberately not overridable: a standing route departs from the same place every day.

How runs get generated

You never create runs by hand. From each route, Enmantle materializes one run per scheduled day:

• A nightly job pregenerates the next 14 days of runs for every enabled agency.
• Runs are also generated on demand the moment someone loads that day's runs, so a route created today is claimable today.
• Generation never backfills the past, and each run snapshots the resolved origin, destination, and times — so editing a route later never rewrites the history of runs already driven.

Every new run starts as unclaimed, waiting for a driver.

The missed-run panel

Under your routes list is Missed runs — last 7 days. A run that reaches the end of its day still unclaimed (or claimed but never logged) is swept to missed by the nightly job. Each missed run shows here as "{route} · {date} · never claimed."

This is the catch that says "someone was supposed to drive this and nobody did." When a single route piles up 5 or more missed days in a row, Enmantle flags it: "This route has been missed N days running — still active?" with an Archive button right there. If the route is genuinely dead, archive it — archived routes stop generating new runs and drop off both the list and the panel.

A cancelled or skipped day is never counted as a miss — only runs that a driver genuinely should have picked up show up here, so the panel stays worth reading.

Editing and archiving

Each route row has Edit and Archive. Editing reopens the same dialog. Archiving stops future runs from generating; it doesn't touch runs already driven and billed.

Next steps

• Show your drivers how to claim and run today's transport routes.
• For one-off trips outside any route, use the per-shift transportation log.