Search the documentation

Find a page by title or section.

Getting started

Your first 15 minutes

The shortest real path from an empty workspace to a trip a driver can run.

Updated

This is the shortest path from an empty workspace to a trip a driver can actually run. It takes about fifteen minutes and leaves you with one vehicle, one driver, two locations and one dispatched trip. Nothing here is throwaway practice — every record you create along the way is a real record you keep.

Who can do this

Role
Administrators
Permission
vehicles:writedrivers:writeorigins:writedestinations:writetrips:write

The admin workspace only admits admin accounts. Drivers sign in to their own portal and never see these screens, so you cannot walk this path from a driver login.

The path

Work through these in order — each step depends on the one before it, and the whole sequence uses nothing but the default sidebar.

  1. 1

    Finish the setup wizard

    Onboarding → Set up your workspace

    A brand-new admin account lands here before the dashboard becomes reachable. The first step asks for a company name and a country, and that pair is the only thing the wizard insists on. The second and third steps — industry, fleet size, address, primary contact — can be skipped and edited later.

  2. 2

    Get your bearings on the dashboard

    Overview → Dashboard

    The header greets you by name, names your workspace and shows a live clock. Everything below it will be empty or zero. That is correct for a workspace with no data in it, and it is the last time it will look like that.

  3. 3

    Add a vehicle

    Operations → Vehicles → Add Vehicle

    One vehicle is enough to start. You can import the rest of the fleet later from the Import button next to Add Vehicle on the same page.

  4. 4

    Add a driver

    Operations → Drivers → Add Driver

    An email address is required, because creating a driver sends them an invitation. The new row appears immediately with a Pending account badge and stays that way until the person opens the invitation and sets a password.

  5. 5

    Add an origin

    Fleet → Origins → Add Origin

    An origin is where goods come from — a warehouse, a hub, a kitchen. A trip starts at one.

  6. 6

    Add a destination

    Fleet → Destinations → Add Destination

    A destination is where goods go. Give it an address and a position on the map: the trip wizard reuses both, and a destination with no coordinates produces a stop the wizard will refuse to schedule.

  7. 7

    Open the trip wizard

    Operations → Trips → Create Trip

    The wizard has four steps, shown down the left as a rail: Trip details, Route, Assign & schedule and Review. The rail summarises each step as you fill it, so you can see the whole trip taking shape without scrolling back.

  8. 8

    Fill the four steps

    On Trip details a type is required. On Route add the destination you just created as a stop — every stop needs a name, a type, an address and a location. On Assign & schedule pick your driver and vehicle and set a scheduled start; the start time is what makes the trip schedulable. Review lists anything still unresolved.

  9. 9

    Schedule it

    Review → Schedule Trip

    One button creates the trip and moves it out of draft in a single action. If you would rather stop and come back, Save draft leaves it in Draft with everything you have entered intact.

  10. 10

    Dispatch it

    Operations → Trips → open the trip → Assign

    A scheduled trip is planned, not dispatched. Assign on the trip’s own page is the moment it becomes that driver’s work.

  11. 11

    Watch it move

    Overview → Live Fleet

    Once the driver starts the trip from their app, they appear here. Until then the map is quiet, which is itself useful information.

What the three statuses mean

The step you are most likely to skip is the last one. Scheduling and dispatching are deliberately separate: a plan you are still editing and a job somebody is expected to drive should not look identical on a board.

DraftScheduledAssigned
How it gets thereSave draft in the wizardSchedule Trip in the wizardAssign on the trip page
Scheduled start requiredNoYesAlready set
Driver requiredNoNoYes
Reaches the driverNoNoYes
Next step availableSchedule, edit or deleteAssign, edit or cancelThe driver starts it
The first three states in a trip’s life, and what each one requires.

If a step will not complete

The four that catch people out

The Schedule Trip button is greyed out on Review
Cause

The wizard found at least one blocking issue somewhere in the four steps.

The footer names the first blocker and the step rail marks which step it belongs to, so you can jump straight there. The usual causes are a missing trip type, a stop with no name, type, address or location, and a missing scheduled start.

Assign is refused and asks for a driver
Cause

Moving a trip from Scheduled to Assigned requires a driver on the trip.

Edit the trip, set a driver on Assign & schedule, save, and try Assign again. Depending on your workspace settings a vehicle may be required as well.

A stop will not save without a location
Cause

Stops carry coordinates, not just an address string.

Pick the point on the map in the stop editor, or set the coordinates on the destination itself so every future stop built from it inherits them.

The route step warns that there are no stops
Cause

An empty route is a warning, not a blocker.

A trip with no stops can be created and scheduled — that is intentional, because some workspaces build the shell first and fill the route later. If you meant to add stops, this is the reminder.

Where to go next

With one trip on the board, the three things most workspaces do next are:

  • bring in the rest of the fleet and the address book through the Import button on the vehicles, drivers and destinations pages;
  • invite the people who will be dispatching alongside you;
  • rename the entities so the product uses your words rather than ours.

Terminology

Your organisation can rename these. If your screens say something else, this is what they mean here.

Trip
One journey with an ordered list of stops. Some workspaces call these routes, runs or jobs.Rename it in Customize → Terminology
Origin
The place a trip collects from. Some workspaces call these depots, hubs or warehouses.Rename it in Customize → Terminology
Destination
The place a trip delivers to. Some workspaces call these sites, customers or drops.Rename it in Customize → Terminology