Creating a trip

The fields that matter on a new trip, and which of them scheduling actually reads.

Written for
Dispatchers
Reading time
1 min
Last reviewed
August 5, 2026

A trip is one journey from a pickup to a drop-off for one rider. Round trips are two trips linked to each other, not one record with two legs, because the return leg is frequently scheduled differently — or not at all, if it is a will-call.

Creating one

  1. Open Trips and choose New trip.
  2. Enter the rider, then the pickup and drop-off addresses. Addresses are geocoded as you enter them; confirm the match rather than assuming it.
  3. Set the trip date and the pickup time, or the appointment time if the drop-off is what is fixed.
  4. Choose the service type. This determines which vehicles the trip can be planned onto.
  5. Add the payer and any authorization number, so the trip is billable without a later edit.
  6. Add rider notes for anything the driver needs at the door — gate codes, mobility assistance, a second-floor apartment.
  7. Save. The trip enters the unassigned backlog until it is scheduled or assigned.

Fields scheduling reads

  • Service type — a hard constraint on which vehicles are eligible.
  • Pickup time or appointment time — anchors the trip on the timeline.
  • Pickup window — how much flexibility the optimizer has either side of that anchor.
  • Addresses — the geocoded coordinates drive travel-time estimates between stops.

Related

Still stuck?

Technical documentation

API references, data model, webhook payloads and integration guides — the detail behind the workflows described here. Available to signed-in Naveera customers.

Open documentation

Ask your team

Support requests are raised from inside Naveera Console, where your organization and your role are already known — which means the answer can be about your configuration rather than the general case.

Settings → Support, or ask your organization’s administrator