Work Orders Overview
Levy Service is the work order management system built into your Levy Fleets dashboard. It pairs a Kanban board for ops managers with a Tasks tab inside the operator-app for technicians, and ties both surfaces to live vehicle telemetry so most work orders create themselves.
If your fleet has more than 50 vehicles and you currently track maintenance in Slack threads, a shared Google Sheet, or paper, this category is for you.
What a work order is
A work order, called a task throughout the product, is a single unit of field work tied to a vehicle. Every task carries:
- A type (repair, scheduled maintenance, deploy, retrieve, charge swap, battery swap, rebalance, cleaning, inspection, parts replacement, software update, lost and found, vendor dispatch)
- A priority (low, medium, high, critical)
- A status that walks through a fixed lifecycle:
createdthenassignedthenin_progressthenresolvedthenverifiedthenclosed, withblockedandcancelledas off-path states - An assignee (a single team member), a subaccount, and an optional team
- An SLA due time computed from the priority and your fleet's SLA config
- A vehicle UUID linking the task to a specific scooter, bike, or moped
Tasks live in the tasks table. Every status change writes an audit row, and photo evidence is required to move between several states.
The three surfaces
Work orders are managed across three places:
- Dashboard at
/dashboard/tasks— Kanban board, table view, and map view for ops managers. This is where you triage, assign, verify, and pull cost reports. - Operator-app Tasks tab — Field technicians work from a phone. They see "Mine," "Nearby," and "All," capture before/after photos, and resolve tasks one-handed. The tab caches offline and replays when reception returns.
- Vendor magic-link portal — Outsourced repair partners receive an email link, see their queued tasks, upload photos and a Stripe-backed invoice, and never touch a Levy login.
Why the rule engine matters
The biggest difference between Levy Service and a generic CMMS is the rule engine. Tasks can be created automatically when telemetry crosses a threshold you define. Seven trigger types are supported:
- mileage — odometer crosses a service interval
- time — calendar cadence (every 30 days, every 90 days)
- condition_report — a post-ride AI severity rating
- low_battery — battery percentage drops and the vehicle has been parked for a configurable window
- rider_issue — a rider submits an issue through the mobile app
- iot_fault — a Queclink/OKAI fault code lands in
iot_events - geofence — a vehicle leaves your operating zone
A well-configured fleet hits more than 50% auto-created tasks, which is the threshold for getting MTTR below 24 hours on critical work.
Auto-flip to maintenance
When a high or critical task lands on a vehicle, Levy automatically flips the vehicle status to maintenance so it disappears from the rider app. The flip happens at the database level, so it fires regardless of who created the task — manual, rule engine, or vendor. Active rides are never interrupted; the flip waits for the ride to end. On verified, the vehicle returns to available (or offline if telemetry has gone stale).
What to read next
- Getting Started — the 15-minute setup that gets your first task on the board
- Kanban Board — how to drive the daily standup from the dashboard
- Rule Engine Setup — write your first three triggers
- Technician App Flow — what your field team sees on their phones
Where the data lives
Everything described in this category is backed by the tasks, task_assignments, task_photos, task_parts, task_labor, task_rules, task_sla_breaches, vendors, and parts_catalog tables. If you ever need to pull custom reports, your data team can join against tasks.subaccount_id.