Getting Started with Work Orders

This guide walks you from a clean install to a working board with at least one assigned task and one rule firing. Plan for about 15 minutes.

Prerequisites

• You are an ops_manager on your subaccount (the role gives you create, assign, and verify permissions)
• At least one teammate is in the system as a tech, lead_tech, or junior_tech
• The teammate has the operator-app installed and is logged in

If any of those are missing, see Settings → Team first.

Step 1 — Open the board

Go to Dashboard → Tasks at /dashboard/tasks. You will see five columns: Created, Assigned, In Progress, Resolved, Verified. The board is empty on day one. The header shows a count per column and quick filters for type, assignee, and vehicle.

Use the tab switcher to flip between Kanban, Table, and Map. The map view places task markers at the vehicle's last known location and is the fastest way to spot a cluster of low-battery work in one zone.

Step 2 — Create your first task manually

Step 3 — Watch the technician app

Have your teammate open the operator-app and tap the Tasks tab. They will see the task under Mine (if you assigned it) or Nearby (if you did not). Tapping the row opens the task detail, where they can:

• Press Navigate to launch Apple Maps or Google Maps with turn-by-turn directions to the vehicle
• Press Start to move the task from assigned to in_progress (a "before" photo is required)
• Capture photos through the in-app camera (EXIF is stripped server-side, geotag preserved separately for audit)
• Press Resolve to move to resolved (an "after" photo is required)

See Technician App Flow for the full walk-through.

Step 4 — Verify and close

Back on the dashboard, the task now sits in the Resolved column with both photos attached. As an ops_manager or lead_tech, open the task and press Verify. The vehicle flips back to available (or offline if telemetry has gone stale). Verification is intentionally a separate step from resolve, so juniors cannot close their own work.

Step 5 — Turn on one rule

The rule engine is what turns Levy Service from a CMMS into a fleet-aware system. Start with one simple rule:

1. Go to Dashboard → Task Rules at /dashboard/task-rules
2. Click New Rule
3. Pick trigger type low_battery
4. In the JSON config, set battery_threshold: 20 and parked_minutes: 360
5. Action: create_task(type=battery_swap, priority=medium, assign_by_proximity=true)
6. Save and toggle Enabled

Within 30 minutes, the /api/cron/task-rule-low-battery cron will sweep your fleet and create one task per parked vehicle below 20% battery. See Rule Engine Setup for the other six trigger types.

What you should have at the end

• One verified task in your history
• One enabled rule (low battery is the easiest first win)
• A technician who has captured photos through the operator-app