Job (field app)
What it's for
A job in the field app is one visit from arrival to sign-off. It is where a technician records what they found, what they did, what parts and labour went on, what the customer should know, and gets the paperwork signed — all in the one place, on the phone in their hand.
Reach it by opening any job from the field app home screen. The route is
/tech/<job>.
Tabs
The job is worked in stages rather than tabs, each with its own screen: JHA, Diagnose, Build, Equipment, Inspect, and Wrap.
Panels and controls
Job details
Who the customer is, where the site is, what was asked for, and what the office noted — "e.g. Compressor not starting — hard-locked on start". Equipment linked to the job shows with its service history and readings, so a technician arrives knowing what happened last time rather than asking the customer.
Recording the work
Parts and labour are added as the visit runs. No parts or labor added is the empty state until something goes on. Notes capture "Anything the office should know", and a follow-up records "What's driving the follow-up?" — parts, access, or additional labour.
Findings and recommendations
A finding is written for the customer — "Describe the issue or opportunity for the customer" — with a value against it. That is what becomes a proposal in the office rather than a note nobody reads.
Nameplate capture
A photo of a unit's data plate reads the make, model, and serial off it. It is a shortcut, not a substitute, and it says so when it cannot cope: "Take a photo of the unit's nameplate.", "That image is too large — please use one under 12MB.", and "Couldn't read that nameplate. Try a clearer, well-lit photo — or enter the details by hand."
Service bulletins offline
Use Save offline on an equipment service bulletin before leaving signal. Its validated PDF is stored only in the signed-in technician and organization partition on that device. Open saved copy reads those bytes directly from the device, including after a hard reload while the network is down. The offline shell lists only the current tab's saved bulletin partition; it does not cache the job page or organization data as HTML.
If the bulletin was not saved, the field app says Stored content is temporarily unavailable rather than opening a broken server link. Reconnect, save the bulletin, and retry.
Finishing
Save signature captures the customer's sign-off. Send payment link puts the invoice in their hand before you leave the driveway — which is the single biggest thing a field app can do for cash flow. Create report link shares the inspection result. Complete inspection closes a checklist off.
Moving a visit
Rescheduling from the field asks why — "Why does this visit need to move?" — so the office is not left guessing when a customer calls about it.
What it accepts
| Field | Format | Required | Rule |
|---|---|---|---|
| Notes | Free text | No | "Anything the office should know" |
| Follow-up reason | Free text | Yes, to raise a follow-up | Parts, access, additional labour |
| Finding description | Free text | Yes, per finding | Written for the customer, not the office |
| Finding value | Dollars | No | What it would cost to put right |
| Quantities and readings | Numbers, e.g. 0.00 or 0.0 | Yes, where captured | |
| Nameplate photo | An image under 12 MB | No | Reads make, model, and serial where it can |
| Signature | Drawn on screen | Yes, to sign off | |
| Reschedule reason | Free text | Yes, to move a visit | Sent to the office with the change |
How to configure it
- Inspection templates decide which checklists are offered on this job.
- Compliance settings decide whether a hazard analysis is required before work starts.
- Price book settings supply the parts and labour catalogue.
- Signatures settings decide what the customer is signing and what appears on the document.
- Invoicing and payment settings decide whether a payment link can be sent from the field.
Who can see it
This screen is part of the field app. Technicians see it on their own phone or tablet, scoped to the jobs assigned to them.
Office roles work the same job from the work order record instead.