Repairs
Repair workflow and statuses
Repairs move through a short fixed status chain, with every major change logged on the repair timeline.
Updated May 29, 2026 5 min read
RepairNode keeps the repair workflow intentionally short so the same status values drive the repair list, dashboard cards, analytics, and customer-facing tracking.
Status chain
- Pending: the device is received but work has not really started yet.
- In Progress: the technician is actively working on it.
- Waiting for Parts: the repair is blocked on stock, supplier delivery, or a parts order.
- Completed: the job is done and ready for pickup.
- Delivered: the device is back with the customer.
- Cancelled: the job was stopped or declined and should leave active workflow counts.
Changing status
- Open any repair detail screen and use the Update Status hero action for the most likely next step.
- Use the full status picker in the action sheet when you need to jump forward, roll back, or cancel directly.
- Status text is localized in the UI, but the stored database values stay in English so exports and analytics remain consistent.
Activity timeline
The repair activity card logs more than status changes. It also records creation, major edits, payment and refund entries, document sharing, and other lifecycle events so the ticket keeps a readable history.
Lists, dashboard, and filters
- The Repairs tab supports status, manufacturer, payment, and date-range filtering.
- Dashboard sections such as urgent repairs, reminders, and awaiting pickup all depend on current repair state and dates.
- Completed and Delivered repairs feed revenue and turnaround metrics; Cancelled repairs drop out of active workflow counts.
Customer tracking
Was this article helpful?