Field Work Order App for Dispatch, Completion and Sign-Off

A field work order app that dispatches the job, captures parts, labour and photos offline, and closes it with a customer signature and an ERP push.

A technician connecting a service hose to an outdoor air-conditioning unit

What gets in the way, and what fixes it

Getting the job to the right technician without a phone call
Direct, broadcast, pull and scheduled dispatch
Basements, plant rooms and rural sites have no coverage
Offline-first completion on Android and iOS
Parts and labour are written from memory at the end of the day
Repeatable parts and labour lines with inline totals
A signature on a card proves almost nothing
Signature capture plus verified attendance evidence

How it runs

  • Reactive call-out, from raise to invoice-ready record

    Billing starts on the day of the visit, the evidence behind a disputed job is retrievable in seconds, and the parts that were actually fitted are the parts that were recorded.

  • Planned work orders raised automatically from a failed check

    A finding stops being a line in a report and becomes a job with an owner, and the link between the two survives long enough to be measured.

Common questions

What is the difference between a work order and a maintenance log here?

A work order is a single dispatched job with a completion record: it is assigned, executed, accepted and closed, and it ends. A maintenance log is the running record held against an asset over its life, accumulating every intervention, reading and statutory examination. In IndeForms they are different forms serving different questions, "was this job done and can we bill it" versus "what is the history of this asset". Completing a work order can write its outcome into the asset history, and both are queried together through the shared asset identifier.

Can a technician complete a job with no signal and still get a customer signature?

Yes. Everything needed to complete the job is on the device before the visit, including the form, its reference lists and the compiled rules. The signature-pad question, camera captures and audio notes all work offline, and the whole submission uploads when the device next has a connection. Nothing about the on-site experience depends on the network.

Is this a scheduling and routing system?

No, and we would rather be clear about it. IndeForms does not do route optimisation, drag-and-drop scheduling boards or engineer capacity planning. What it does is the work order record itself: assignment through dispatch, offline completion, evidence, approval and the push into your back office. Many customers keep their existing scheduling or ERP system as the source of jobs and use a connector or the API question type to move data between them.

How does a completed job reach our billing or ERP system?

Through a workflow push-destination node that maps individual form fields, including repeatable parts and labour rows, onto target fields in a structured connector such as SAP S/4HANA or Dynamics 365. Alternatively the record can leave as a PDF, as an XLSX or CSV export, as a file over SFTP, or as a JSON payload to a webhook. Connector configuration is encrypted at rest and outbound calls pass a server-side egress allowlist.

How do we handle a job that turns into extra chargeable work on site?

Rules make the variation questions appear the moment the technician records additional work, and require the evidence and the customer acknowledgement that go with it. On submission a workflow branch routes the job to the service manager for approval instead of closing straight through, and the approval decision, approve, reject or send back with comments, branches the run. Send-for-edit can return the job to the technician for one missing detail without discarding the submission.

Can a failed inspection automatically raise a work order?

Yes. A workflow node spawns a new form from an existing submission and resolves its pre-filled values from the parent record through DREL bindings, so the asset, location, observed condition and photograph carry across without retyping. Where the failures sit in a repeatable section, the node can fan out one work order per failed row, and a run-scoped variable keeps the originating reference on every downstream notification and push.

Can we change the job card ourselves as the business changes?

Yes. Supervisors build and edit job cards in the drag-and-drop builder without a developer and without an app-store release. Publishing creates an immutable version, each submission records the version it was captured against, and an earlier version can be restored as a draft. Where several job types share most of their questions, rules and rule groups keep them on one form rather than multiplying near-identical forms.