The operations layer for moving people, end to end.
Conitero models the operational reality of people-transport: routes and journeys, the fleet that runs them, the people who staff them, and the customers who pay. Every concept is deliberate. Nothing is decorative.
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. Save reusable master routes and instantiate them on demand.
- ▸Ordered stops with address, scheduled time and optional access notes
- ▸Master-route templates you clone into any day
- ▸Multiple runs per driver per day — morning, afternoon, evening
- ▸Reason-codes captured for incomplete or cancelled runs
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, capturing distance, wait time and travel minutes at close.
- ▸Concurrent journeys per route, per guide
- ▸Six states with explicit transitions (Scheduled → In Progress → Completed)
- ▸Skip with reason · ended-early with reason
- ▸Captures km, wait time and travel minutes for per-km / per-minute billing
Your fleet, managed as real assets.
Vehicles aren't just a name on a route — they're assets. Track ownership, lease and depreciation, compliance dates, maintenance history, and a typed seat capacity so the right vehicle meets every passenger's needs.
- ▸Typed seat capacity — standard, wheelchair, booster, child restraint, stretcher
- ▸Owned, leased or contractor-owned, with depreciation and book value
- ▸Insurance & roadworthy expiry, plus a full maintenance log
- ▸Live vehicle location — guide device today, telematics-ready
Resource the run — in-house or outsourced.
Controllers, schedulers, drivers, guides and driver assistants are all resources — employed, contracted, or supplied by a partner company. Offer a planned route to guides and let the first accept bind, or hand the whole route to an external company through a dispatcher portal.
- ▸Resource roles × employment types (employee / contractor / outsourced)
- ▸Route offers — broadcast to guides, first accept binds, siblings expire
- ▸External companies fulfil outsourced routes via a persistent portal link
- ▸Resources can work without an app login — share-link or manual dispatch
From who pays to invoice paid.
A customer is the account holder — an individual, household, school, business or government body — and passengers link to whoever pays. A shared rate and service catalog feeds customer agreements, and the billing engine turns completed journeys into invoices.
- ▸Rate metrics: per-leg, per-return, per-km, per-minute, per-day, flat, fees
- ▸Service catalog — wheelchair, booster, extra stop, after-hours surcharges
- ▸Agreements with cadence, proration, caps, included units and tax treatment
- ▸Quotes convert to agreements + invoices; credit notes, refunds, statements
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
- ▸Push notifications and offline-capable event capture
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.
- ▸Event types covering route, stop, passenger and notes
- ▸GPS captured when available
- ▸Recorded-by stamp on every event
- ▸Exportable to invoicing or BI
One tenant, many branches — cleanly scoped.
Each organization runs on its own subdomain with isolated data. Inside it, branches scope every list — pick a branch from the switcher and dashboards, customers, vehicles, routes, journeys and invoices all follow. Cross-branch assignment still works at planning time.
- ▸Per-tenant subdomains (company.conitero.com)
- ▸Branch switcher scopes all data; single-branch tenants never see it
- ▸Resources and vehicles have a home branch, usable across branches
- ▸Role-restricted accounts via RBAC; encrypted in transit
Onboarding and help, built into the product.
An in-app Mentor explains each screen and runs interactive walkthroughs with an on-screen spotlight. The Learning Academy turns that into structured curricula with quick checks, points, tiered badges and verifiable certificates.
- ▸Mentor help panel — screen explainers and walkthroughs, in context
- ▸Curricula like Coordinator Onboarding and Billing Basics
- ▸Checks, points and bronze→platinum badges on a personal scorecard
- ▸Completion issues a PDF certificate with a public verification link
See it on your operation.
Join early access and we'll line you up for an onboarding walkthrough.