Finding and Completing Service Orders

Overview

Service orders live on the machine's own page in the mobile app, not in a personal to-do list — the organising principle is the machine, because that's where the work is. As a Technician you can see and act on any order for equipment in your licensed groups, not only jobs assigned to you personally.

Finding a machine's orders

Open the machine, then Service orders. An All / Open / Completed switch narrows the list — an upcoming "500-hour predictive service" shows with its badge, priority, and due date. For how orders come to exist (predictive, ad hoc, defect repair) see Services and Maintenance Workflow.

Completing an order

1. 1
   Tap the order — title, priority, service type, and the Assigned to line.
2. 2

   Assigned to someone else? Complete it anyway if you did the work — assignment tracks the plan, not permission. The completion record names who actually performed it.

3. 3

   In Complete service order, enter your notes — "Oil and filters changed, full inspection, no issues" — plus Hours or Kilometres readings where you have them.

4. 4
   Tap Complete. The badge flips to Completed.

If the order was raised from a defect (a defect-repair trigger), completing it auto-resolves the linked defect — one action closes both records — unless a critical checklist item fails (below).

Logging work that was never scheduled

Fixed something on the spot with no order in the system? Log it from the machine's page as a completed service — notes, readings, done. Field-logged services record as completed ad-hoc work; scheduling future work stays a console task, so the plan and the evidence keep their separate owners.

Working against a checklist

Some services carry a service-type checklist. Completing one walks the list item by item — the structured evidence trail for certifications and formal inspections — before the sign-off.

Mark a critical item Fail and the service still completes, but the fault is held like a pre-start's: the item gets a defect (the machine's open one for that item, or a new Critical one), that defect takes the machine out of service until it's closed, and your Administrators and Account Owner are told. On a repair order, the repair's own defect stays open instead of resolving. See Services and Maintenance Workflow.

Edge cases

• Offline — completing and logging services queues like everything else and syncs later. (The exception in the service world is service mode, which is live-only.)
• External workshop work — when the machine comes back from a provider, log the completion on their behalf, recording their company in the notes; the org's console can also record external completions with the provider's name and invoice reference.
• An order you can't see — orders follow the machine, so if the machine isn't in your app, neither are its orders; that's a licence/group question, not a services one.

Troubleshooting