Product

The operations layer for moving people, described in full.

Conitero models the operational reality of people-transport: routes, journeys, stops, events. Every concept is deliberate. Nothing is decorative.

Routes

Routes you build once, run forever.

A route is a driver's planned trip — a guide pickup, an ordered sequence of passenger stops and a guide drop-off. Stored separately from the schedule, so the same route can run any day.

  • Ordered stops with address, scheduled time and optional access notes
  • Native maps deep-linking for navigation
  • Multiple runs per driver per day — morning, afternoon, evening
  • Reason-codes captured for incomplete or cancelled runs
ROUTE / R-2041 · MON 17 MAY
Morning · School run
Greenwood Primary · Run 1
GUIDE  Sara N.DRIVER  Jon P.VEHICLE  VAN-08PAX  3 / 3
Pickup — Guide
07:42Complete
Aisha M. — pickup
Side gate, 22 Park Rd
07:55Complete
Theo K. — pickup
Buzz flat 3B
08:03In progress
Mira S. — pickup
08:12Scheduled
Greenwood Primary
08:30Scheduled
Dropoff — Guide
08:42Scheduled
Journeys

A journey is one passenger's promise.

Each journey tracks responsibility for a single passenger from pickup to drop-off. Journeys overlap inside a route — three passengers in a van means three concurrent journeys. The journey is also the chargeable unit.

  • Concurrent journeys per route, per guide
  • Five states with explicit transitions (Scheduled → In Progress → Completed)
  • Skip with reason · ended-early with reason
  • Journey = the billing unit, full stop
ROUTE R-2041 · 3 CONCURRENT JOURNEYS
G·1ABCSCHOOLG·1Journey · AishaJourney · TheoJourney · Mira
↑   THREE PASSENGERS IN ONE VAN → THREE JOURNEYS, ONE ROUTE
Guide app

A digital journey log, in the guide's pocket.

Guides see only their assigned routes for the day. Tap a stop on arrival. Tap to pick up. Tap to drop off. Add a note if it matters. The phone becomes the source of truth.

  • PWA today, React Native at GA
  • Long-lived mobile sessions for field work
  • Single active session per guide
  • Offline-capable event capture
08:04●●● ●●●●
Today · R-2041
Greenwood · Run 1
STOP 3 OF 6 · 2 ACTIVE JOURNEYS
Up next08:03
Theo K.
P·T·07 · BUZZ FLAT 3B
41 Linden Ave, N4 2QS
Picked upNo-show
QUEUE
Mira S.08:12
Greenwood Primary08:30
Activity & audit

Append-only events power everything downstream.

Every tap in the guide app emits a timestamped event with optional GPS. Events are never edited or deleted — corrections are new events with notes. This is how billing, reporting and compliance get easier instead of harder.

  • 9 event types covering journey, stop, passenger and notes
  • GPS captured when available
  • Recorded-by stamp on every event
  • Exportable to invoicing or BI
JOURNEY_EVENTS · APPEND_ONLY● LIVE
07:42:08
journey_started
ROUTE
07:55:12
stop_arrived
STOP A
07:55:34
passenger_picked_up
P·A·12
08:03:51
stop_arrived
STOP B
08:04:18
passenger_picked_up
P·T·07
08:12:02
passenger_no_show
P·M·19
08:12:24
note_addedFamily rang — sick day
P·M·19
08:30:09
passenger_dropped_off
P·A·12
08:30:33
passenger_dropped_off
P·T·07
08:42:14
journey_completed
ROUTE
Multi-tenant

Each organization on its own subdomain.

Tenant-isolated data, role-restricted users and a Guide role that can only do guide things. Conitero scales from a single shuttle operator to a network of school trusts without leaking a row of data between them.

  • Per-tenant subdomains (company.conitero.com)
  • Role-restricted Guide accounts (read journey, write events)
  • Encrypted in transit
  • Hundreds of guides, thousands of journeys
TENANT ISOLATION
borough-7
borough-7.conitero.com
12 ops · 38 guides
via-care
via-care.conitero.com
5 ops · 14 guides
northline
northline.conitero.com
8 ops · 22 guides
DATA BOUNDARY● ENFORCED

See it on your routes.

Join early access and we'll line you up for an onboarding walkthrough.