The MARX8 tracking app

MARX8 Routeboard · Delivery dispatch & driver tracking

Plan routes, dispatch drivers, follow every stop live

MARX8 Routeboard is our ready-made tracking app for local delivery and field teams. A dispatcher plans routes and assigns drivers; a driver completes stops from a phone; the dispatcher follows progress live on a map, with ETAs, exceptions and offline-tolerant updates. A built-in simulated trip runs the whole flow with no GPS hardware.

Dispatch → deliverPlan routes, assign drivers, publish
Live trackingPosition, progress, ETAs & exceptions
Offline-tolerantQueued stop updates, never double-applied
Role-basedOwner, Dispatcher, Driver — server-enforced

What Routeboard does

From the dispatch board to the last drop

One app for both sides of a delivery day — a planning board for the dispatcher and a phone-friendly run sheet for the driver, kept in step in real time.

01

Plan routes & stops

Build a route the way the day runs — the right stops, in the right order, with the windows you've promised.

  • Create routes & add stops
  • Reorder stops
  • Delivery time windows
02

Assign, publish & track lifecycle

Hand a route to a driver and put it live — then let its status carry it from draft to done.

  • Assign a driver & publish
  • Draft → published → active → completed
  • Route history kept for every job
03

Driver app, phone-friendly

Drivers see only their own routes and work the stops from their phone, with a note when it matters.

  • Start & end a trip
  • Mark stops Arrived / Completed / Failed
  • Timestamp & optional delivery note
04

Live tracking & exceptions

Follow the run as it happens — where the driver is, how far along, and anything that's gone wrong.

  • Last known position on a map
  • Progress, completed stops & "updated … ago"
  • Exceptions for failed stops; ETAs labelled as estimates
05

Offline-tolerant updates

Signal drops in the real world — Routeboard keeps the run sheet honest when it does.

  • Stop updates queue when offline
  • Synced safely on reconnect
  • Stable idempotency keys — never applied twice
06

Roles, access & CSV

The right people see the right routes — and you can take a finished job's summary with you.

  • Owner, Dispatcher & Driver
  • Drivers see only their assigned routes
  • Completion summary CSV; location history staff-only

Honest by design

What's real, and what's simulated

Tracking software is easy to over-promise. Routeboard is built to be straight with you — the workflow is real, the demo is clearly labelled, and the updates hold up when the network doesn't.

Clearly labelled simulation

A built-in simulated trip moves the position along the route, so the whole flow demos with no GPS hardware or live drivers. Simulated positions and ETAs are always labelled as such — never passed off as real device data.

Offline-tolerant & idempotent

Each stop update carries a stable idempotency key stored under a unique constraint on the server. Updates queue when the connection drops and flush on reconnect, so a replay — even after a lost response — returns the original result and never applies a change twice.

Server-enforced access

Every action is checked on the server. Cross-organisation access is always denied; drivers can open only their own assigned, published routes; and the full location history and CSV export are staff-only. A trip stops accepting location once it ends.

Plan route Assign driver Publish Driver starts trip Live tracking Completion CSV
Maps and routing are configurable with a no-key demo fallback: OpenStreetMap tiles by default, and demo routing that draws straight-line geometry and estimates ETAs from distance. A real road-routing provider and your own map tiles plug in without changing the rest of the app.

A closer look

Follow the run stop by stop

The dispatcher watches the route unfold in real time — which stops are done, where the driver is, and anything that's gone wrong — while the driver works the same list from a phone.

How it works

A delivery run, dispatch to doorstep

The exact flow Routeboard's end-to-end test drives over HTTP — plan a route, send a driver, follow it live and close it out — with a built-in simulated trip so it all works with no GPS hardware.

1

Plan and publish a route

Dispatcher

Build the route, add stops with delivery windows, assign a driver and publish — a route needs at least one stop and a driver to go live.

2

Driver starts the trip

Driver

The driver opens their assigned route on a phone and taps Start trip. Location defaults to a simulated drive, so the position moves along the route with no GPS.

3

Follow it live

Tracking

The dispatcher opens Live tracking — the map, last position, "updated … ago", progress and ETA refresh every few seconds.

4

Work the stops

Delivery

The driver marks each stop Arrived or Completed, and a problem stop Failed with a note. The dispatcher's progress and exceptions update as they go.

5

Survive a signal drop

Offline

If the connection drops, a stop update waits to sync and flushes on reconnect. A stable idempotency key means the same action never applies twice.

6

End and share

Done

The driver ends the trip — the route is Completed and location stops — and the dispatcher downloads the completion CSV. Only the assigned driver, in the right organisation, could touch the route at all.

Who can do what

Three roles, enforced on the server

Access isn't just hidden in the interface — every action is checked server-side against the user's role, organisation and route assignment, so people see and touch only what's theirs.

Owner

Organization Owner

Full access across the organisation — everything a dispatcher can do, plus managing the team and settings.

Dispatcher

Dispatcher

Plans and publishes routes, assigns drivers, follows trips live, handles exceptions and downloads completion CSVs and location history.

Driver

Driver

Sees only assigned, published routes; starts and ends trips and marks stops from a phone, with opt-in location sharing during an active trip.

Ready-made, or made yours

Start with delivery — track anything

Routeboard is ready for local delivery and field dispatch today. The broader "Tracking" category — other tracking types, real road routing, dependable background location — is built around it as custom work.

Available now

Ready-made Routeboard

Vehicle & delivery dispatch with live driver tracking — plan routes, assign and publish, follow trips on a map, and export completion summaries, running quickly.

More tracking

Other tracking types

Asset & inventory movement, or field & job tracking for a mobile workforce — your own stop types, fields and workflows, built on the same foundation.

Integrations

Routing, native app & hosting

A real road-routing provider and your own map tiles, a native app for dependable background location, plus hosting on our cloud or yours — ownership agreed in your proposal.

Not sure which way to go? There's an honest custom vs ready-made comparison on the Business Applications page, and we'll recommend the right approach for your situation.

FAQ

Routeboard questions, answered

Straight answers on what's ready today, what's simulated, and how tracking holds up in the real world.

Is MARX8 Routeboard available now?

Yes. The ready-made app runs the whole plan-dispatch-track workflow — dispatchers build routes and assign drivers, drivers complete stops from a phone, and the dispatcher follows progress live. It works out of the box with OpenStreetMap maps (no API key) and a built-in simulated trip, so you can run the full flow with no GPS hardware.

Do I need GPS hardware or paid map keys?

No. Maps use OpenStreetMap tiles with no API key, and a built-in simulated trip demonstrates live tracking with no GPS hardware or live drivers. Real location is opt-in browser geolocation, which updates only while the driver's page is open and in the foreground; dependable background tracking uses a native app, which we build as an extension.

How accurate is the live tracking and the ETAs?

The dispatcher sees the last known position on a map, time since the last update, completed stops and exceptions. ETAs are shown and clearly labelled as estimates. The built-in demo routing draws straight-line geometry and estimates arrival from distance; wiring a real road-routing provider is a small, documented extension that leaves the rest of the app unchanged.

What happens if a driver loses signal mid-route?

Stop updates are queued when the connection drops and synced when it returns. Each update carries a stable idempotency key stored under a unique constraint on the server, so replaying the same action — even if an earlier attempt reached the server but its response was lost — returns the original result and never applies the change twice.

How is access controlled?

Every action is enforced on the server. Cross-organisation access is always denied; drivers can list and open only routes assigned to them, and only once published; starting or ending a trip and marking stops require the assigned driver. The full location history and CSV export are staff-only (owners and dispatchers).

Ready-made or custom — which should I pick?

Ready-made Routeboard suits local delivery and field dispatch you want running quickly. Custom suits other tracking types — asset and inventory, or field and job — plus a real road-routing provider, your own tiles, and a native app for dependable background location. See the honest custom vs ready-made comparison.

See Routeboard on your routes

Tell us what you deliver and where. We'll show you Routeboard with sample routes and map the fastest path from a whiteboard and phone calls to a live dispatch board.