Lifecycles

Most objects in Cooriroo hold a status, and that status can only move along a fixed set of paths. Knowing those paths answers the two questions operators ask most: why a button is not there, and what has to be true before it appears. Everything below is the full set — if a transition is not listed, the product refuses it.

Each of those moves has a condition attached. Scheduling needs a scheduled start time. Assigning needs a driver, and needs a vehicle and an origin unless your tenant has made them optional. Starting re-checks the driver and the vehicle, and refuses a vehicle that is not active unless you force it and say why. Pausing, cancelling and failing each need a reason in writing — a pause reason must be one of break, vehicle_issue, weather, dispatch_hold or other.

Departing is the gated one. Before a stop can be departed, any optional tasks still open are skipped for you, and the required ones are checked; an outstanding required task blocks departure and is named in the error. Skipping and failing both need a reason, and a stop marked required can only be skipped by an admin. Departing also advances the next stop and triggers a route recalculation over what is left.

There is no shortcut from pending to completed — a task has to be started before it can be finished, so the timestamps mean something. Completing checks two things: every required checklist item is ticked, and every required proof is captured or waived. Failing needs an outcome written against it. A task marked required cannot be skipped at all, and where a stop enforces task order, a task cannot start while an earlier one is unresolved.

A scheduled shift is the only kind you can edit — once it is active, its times are a record of what happened rather than a plan. An ad-hoc shift skips the scheduled state entirely and starts active. Clocking out totals the shift: elapsed minutes, break minutes deducted, and anything over your overtime threshold flagged as overtime. Breaks are separate rows inside an active shift, and an open break is why a driver reads as on break rather than available. To call off a shift that has not started, delete it — only a scheduled shift can be removed.

A work order moves through open, assigned, in_progress, on_hold, completed and closed. Unlike a trip it is not a strict chain — you can put one on hold and pick it up again — but completed and closed are hard stops: a work order in either state refuses any further edit or status change. Moving to in_progress stamps a start time, and closing stamps a close time. Every status change writes a maintenance log entry, so the history is not something anyone has to maintain by hand.

Inspections sit slightly outside all of this: an inspection is a result rather than a process, recorded as passed, failed or passed_with_defects. What gives it a lifecycle is the work it raises — a defect logged as major or critical opens a work order against the vehicle automatically and links the two, so the finding and its fix stay attached. See Inspections for how that plays out day to day.