Creating Work Orders from Inspection Issues and Fault Codes
What is this?
When an operator reports a defect during an inspection (DVIR), or a fault code fires from Samsara or Tenna, Clue can turn it into a work order automatically. The WO comes pre-filled with the asset, the defect description, photos, and the fault code details. The mechanic gets the job without anyone typing it up.
From inspections (DVIR)
When an operator fails an inspection item and marks a defect:
- The issue appears in Asset Health > Inspection Issues
- Click the issue and select Create Work Order
- The WO auto-fills with the asset ID, defect description, severity, and any photos the operator attached
- Assign a mechanic and set priority. The job is ready.
From fault codes (Samsara, Tenna, OEM)
Fault codes from telematics flow into Clue continuously. For critical codes, the fault code rules engine can create work orders automatically:
- Set a rule in Company Settings > Configuration > Fault Code Rules
- Choose Create Work Order as the action for that fault code
- When the code fires, the WO is created instantly, linked to the asset and the fault code
- The system checks for existing open WOs on the same asset and code to avoid duplicates
Unified triage
Whether the issue came from an operator inspection, a Samsara DTC code, or a Tenna alert, it all ends up in the same place: a work order linked to the asset. One queue for the shop. One history per machine. No switching between telematics apps to figure out what happened.
Tips
- Set auto-create rules for safety-critical fault codes. DEF inducement, engine overtemp, brake system faults. These should generate work orders without waiting for someone to notice.
- Review inspection issues daily. Not every defect needs an immediate WO. Some can be deferred to the next PM. But someone needs to look at them every day.
- Photos from inspections save diagnostic time. The mechanic sees the defect before they even walk to the machine.
