KoridoThe Handbook

How the platform works — from a truck's first GPS signal to the report a fleet owner reads.

1 · Korido

What the product is, who uses it, the system at a glance, and the vocabulary the rest of the book relies on.

One tracker message from the field to the database — position quality, and the parked · Sans GPS · offline distinction.

How raw positions become an operating diary — vehicle state, trips, stops, signal gaps, and fuel from sensor to alert.

Waypoints and road geometry, corridors configured once and reused, and Route Guard watching every deviation.

The work trucks do — assets and drivers, clients, the mission lifecycle, driving rules, ETA, segments, and documents.

Alerts and how they reach people, per-segment analytics and comparisons, and the spatial intelligence learned across the fleet.

What each audience sees — the fleet app, admin portal, driver and owner apps, the customer tracking portal, and WhatsApp.

The guarantees underneath — tenancy and security, the layered data architecture, and reliability in product terms.

The book reads in order, but every chapter stands on its own. If you have a question rather than a reading plan, start here.

New to Korido? Begin with What is Korido?, then see how the audiences meet the product in The surfaces.
Why does a truck show as parked, Sans GPS, or offline? Read Liveness, then Signal gaps.
How does a position become a trip, a segment, a report? Follow Telemetry → The fleet engine → Missions.
What goes into a mission, and how do you dispatch one? See Creating missions.
How do alerts work, end to end? Read Alerts, with Signal gaps for the detectors behind them.