How Cooriroo works

Cooriroo turns a day of delivery work into trips a driver can run and a record you can answer questions from afterwards. Work arrives as places and jobs, someone plans it into trips, a driver executes those trips from a phone, and proof flows back as each stop is served. This page follows that arc once, end to end, and hands off to the page that covers each part properly.

Your organisation is a tenant, and every record you create belongs to it. Isolation between tenants is enforced by the database itself rather than by the application remembering to filter, which is covered in Roles and permissions. A tenant also owns its own vocabulary: if your operation calls a trip a run and a destination a site, you rename them once in Terminology and the whole product follows.

An origin is where goods come from and a destination is where they go. Both are standing records — an address, contacts, an optional geofence — so you set one up once and reuse it on every trip that touches it. A stop does not have to be linked to a saved destination; it can carry its own name and coordinates. Linking is what buys you the contacts, the geofence and the history.

A trip is one journey. It has a trip number, a type — delivery, pickup, transfer, return and others — a priority, and an ordered list of stops. Under it sits a route plan: the distance, the expected duration and the shape of the drive between stops. The route is recalculated when the plan changes underneath it, so the estimates a dispatcher sees track the trip as it is actually going.

Drivers work from the mobile app, or from the driver portal in a browser. A driver clocks on to a shift, which is what makes their hours countable and their availability real. Their status — available, on delivery, on break, offline — is not something anyone sets. It is derived from the shift, the break and the trips actually in progress, so it cannot drift away from what is happening on the road.

Work to be done at a stop is a task: scan this, photograph that, collect a signature, read back a PIN. A task lists the proofs it requires, and it cannot be completed until each one is captured or explicitly waived. A stop cannot be departed while a required task is outstanding, which is why proof of delivery arrives as a by-product of the driver moving on rather than as a report someone chases at the end of the day. Tasks can also stand alone with no trip behind them, assigned straight to a person.

A vehicle carries features and an operational status. Inspections record its condition, and a defect serious enough to matter raises a work order automatically instead of relying on someone to file one. Service schedules bring the vehicle back in on mileage, on time, or on both. Together those feed a health picture per vehicle, so the fleet is something you read rather than survey.