If your agency uses recurring transport routes, your admin sets up the route once and Enmantle creates a daily run for each scheduled day. Your job is the easy part: see the runs waiting today, claim the one you're driving, and log the trip when it's done — with most of the details already filled in for you. This guide covers that loop.

A run is one dated trip from a route: today's version of "Tessa B — PM takehome," with the vehicle, riders, pickup, drop-off, and time all set. You claim it so everyone knows it's yours.

See today's runs

Open the Time Clock. Near the top, a Today's runs strip lists the runs available to you.

You'll only see two kinds of run here:

Runs that are unclaimed — the open pool, waiting for a driver.
Runs you've already claimed — yours to log.

Everyone else's claimed runs stay off your list. If there's nothing for you today, the strip simply doesn't appear.

Each run shows the departure time and route name, the pickup → drop-off, and the vehicle and rider count — enough to know at a glance whether it's yours to grab.

You see runs for the homes on your team and the clients you're assigned to. If a run you expected isn't listed, check with your coordinator — it may be scoped to a different location or driver.

Claim the run you're driving

Find your run in the Today's runs strip.
Tap Claim.

That's it — the run is now yours and the button changes to Log trip.

Because the open pool is shared, two drivers occasionally tap Claim on the same run at the same moment. Only one wins. If someone beat you to it, you'll see "Another driver just claimed that run," the strip refreshes, and that run drops off your list. No harm done — pick another.

Log the trip — details prefilled

When the trip is done, tap Log trip on your claimed run. This opens the same Transportation Log you'd use for any trip — but Enmantle prefills it from the route so you're not retyping what it already knows:

Starting Location and Destination — from the route's pickup and drop-off.
Riders — the route's expected riders.
Vehicle name and License Plate — from the route's fleet vehicle.
Start and end times, and the service date.
Trip Purpose — set to the route's billing lane, so the trip bills the way it was set up to.

Every prefilled field is still a normal, editable field. Prefill is a starting point, not a lock — if reality differed (a different rider, a detour), change it. You still enter the odometer readings: fill in Start Miles and End Miles from the vehicle, and Miles computes for you. Then tap Add Trip to save.

Once you save, the run is marked logged and tied to that trip, so it won't show as outstanding and it flows into billing like any other trip. For the fields themselves and how mileage bills, see Logging HPC transportation vs. NMT.

What the run statuses mean

Behind the strip, each run moves through a simple lifecycle:

Unclaimed — in the open pool, waiting for a driver. This is when you see Claim.
Claimed — someone has it. When it's you, you see Log trip.
Logged — the trip has been logged; the run is done.
Missed — the day ended and nobody claimed or logged it. The nightly sweep marks it missed, and it surfaces in your admin's missed-run panel.
Skipped — the run was cancelled for that day (for example a holiday), so it's not counted as missed.

You don't set these by hand — they follow what you do. Claim moves a run to claimed; logging the trip moves it to logged.

If plans change

Claimed a run you can't drive after all? An admin or director can release it back to the open pool for another driver to pick up. Flag it with your coordinator rather than leaving it sitting claimed — an unlogged run at day's end becomes a missed run.

That's the loop

See it, claim it, log it. The route did the setup work; you just drive and document. New to the Time Clock generally? Start with your first shift.