Keep the assignment, arrival, field evidence and service confirmation with the work order. Your team can see who has the job and decide whether to accept the work, without piecing it together from messages and invoices.
Follow acceptance, travel, arrival and work completion.
Check required fields and evidence before accepting a confirmation.
Retain the assignment, labour, parts references and external cost.
The repair may be complete. Your record of it is still in someone else’s inbox.
A job goes out by phone and nobody knows whether the crew accepted it.
Choose the provider, technician or crew, schedule and work centre. Check capacity before release.
Updates depend on calling the provider or waiting for a message.
Acceptance, travel, arrival and completion record who changed the status and when.
Photos, job notes and time records turn up in different places.
Capture completion notes, labour, external parts references and the evidence your confirmation requires.
Field completion is treated as approval before your team checks the evidence.
An internal reviewer accepts the confirmation or returns it with a reason. Accepted cost stays on the work order.
See how a contractor assignment comes together in Imara Nexus.
Choose a technician, operating region and work centre. Available capacity stays visible in the field desk, helping you plan the assignment before release.
Explore it in your workspaceCheck the draft’s provider, assignee, region and work centre, with its schedule in the queue and its history alongside it. Releasing it to the provider is a separate step in the manager controls, so it stays deliberate.
Explore it in your workspaceRecorded in Imara Nexus with sample data. Dropdown choices step through their options without opening the list. The final control in each clip is highlighted, not pressed, and no assignment is released.
A provider saying “complete” and your team accepting the work are separate steps.
Select the work order, provider, crew or technician, planned start and work centre.
Release the assignment. The provider accepts or declines, with a recorded reason for a decline.
Record travel, arrival and completion against the same assignment.
The provider completes the configured confirmation fields and supplies the required evidence.
Your team accepts or rejects the confirmation. Work-order completion follows the account’s configured acceptance rules.
Access follows provider membership and assignment. Technicians see their own or their crew’s work; coordinators see their provider’s work.
Purchase orders, invoices and inventory remain in your ERP or catalogue. Parts are recorded as external references and quantities.
Critical alerts require your Meta setup and a verified, opted-in provider number. SMS delivery is not included.
Supported field actions can queue through short connection losses after the screen is opened. This is not a full offline copy of the application.
Tell us how a job reaches your provider and what evidence comes back. Discuss the assignment and acceptance steps your team needs.
Prefer to explore first? Start a core-platform trial. Specialist workflows are enabled and configured separately.