Applications · Field operations
The visit happened. Prove it, and price it, the same day.
Beat plans, work orders, dispatch and routes for teams that work outside the building, with a native app that captures the visit as evidence: location, photographs, readings, customer signature. The day is re-planned when reality moves, not at the end of the week.
beat plans · work orders · dispatchGeo, photo & e-sign proofNative iOS and AndroidSame-day settlement of claims
One work order · dispatch to verified closureRoute, skill, van stock, SLA and proof meet before a dispatcher changes the day.WO-4812 · En route · stop 2 of 4
Outside arrival fence1.8 km from site
Arrival may be recorded inside 150 m
ArrivalETA 11:18Promise12 min SLA marginProof gateGeo · photo · reading · sign
11:06•••
1.8 km · arrival unlocks inside 150 m
Inlet pressure · 2.4–2.8 bar
Proof remains attached to WO-4812.
Traffic compressed the arrival buffer to 12 minutes.
The field day is one evidence chain, not a mobile form beside a dispatch board.
WO-4812 starts as a service commitment, becomes Ravi’s at-site task, consumes the part already on VAN-27 and closes only when its evidence survives the drive back.
Commit the right engineer.
Skill, parts, SLA window and current location are visible before Priya confirms the route.
Carry the job into the field.
Ravi works the checklist, readings and van-stock consumption on the same order.
Make closure an evidence event.
Geo, time, photographs, readings and signature stay attached to WO-4812.
Let the back office trust the day.
The verified route reaches inventory, claims and service without re-keying.
What changes
Run the route around reality. Keep the authority visible.
Field tools are evaluated on scheduling features and bought on whether the data comes back true. These rows are about both.
Planning & beats
The SaaS playbook
→A monthly beat plan, printed and departed from.
Rebuilt agentic
Plans built from coverage rules, priority and travel time, then re-planned mid-day when a visit is missed: with the trade-off shown to the supervisor.
Dispatch & scheduling
The SaaS playbook
→A dispatcher, a whiteboard, and a phone.
Rebuilt agentic
Jobs matched to skill, parts availability, SLA window and current location; the dispatch agent proposes, the dispatcher confirms in one screen.
Mobile execution
The SaaS playbook
→A form that needs signal and re-typing later.
Rebuilt agentic
The app carries the job, checklist, price list and history; capture continues through weak signal and syncs with the conflict resolved, not overwritten.
Proof of visit
The SaaS playbook
→A check-in button, trusted on faith.
Rebuilt agentic
Location, timestamp, photographs, meter readings and customer signature attach to the job: a visit without evidence does not close.
Parts & inventory
The SaaS playbook
→Van stock in a separate spreadsheet.
Rebuilt agentic
Van and technician stock is a live location in the inventory model, consumed on the job card, so the part leaves the van and the ledger together.
Expenses & payout
The SaaS playbook
→Claims submitted weekly, argued monthly.
Rebuilt agentic
Travel computed from the verified route, allowances applied from policy, and the claim is ready for approval the same evening.
One dispatch surface from today’s route to closure proof.
Priya can see why Ravi should retain the work order, which evidence supports that path and what remains due in the field. Nothing moves until the route decision is recorded.
Work-order 360
En route · stop 2 of 4Preventive maintenance · Pump P-14
Arrival window closes 11:30 · ETA 11:18 · 12 min remaining
08:30–09:15 · Closed 09:08
10:45–11:30 · ETA 11:18
13:00–14:00 · ETA 13:26
15:15–16:00 · ETA 15:31
Waiting for site entry
Required for closure
Range check on capture
Customer sign-off due
Safety step · mandatory
Reading range 2.4–2.8 bar
Consume from VAN-27
Photo + reading required
The proof task is large enough to do, not merely to recognise.
Record, exception, evidence, consequence, prepared path and named action remain together at the technician’s working scale.
Preventive maintenance · Pump P-14
Dispatcher review before any route change
No route or job state has changed.
Dispatcher confirms. Engineer accepts.
11:185G
Inside 150 m · arrival evidence unlocked
Closure stays blocked until all four sources attach.
Priya Shah remains dispatch authority.
The field day, end to end.
One app for field sales, service engineers, collections officers and auditors: the job type differs, the discipline does not. The product boundary is the same job and evidence trail, not a list of disconnected modules.
Beat & territory plan
Coverage rules by frequency, class and territory, with plan-versus-actual visibility per rep and per outlet.
frequency · coverage · pvaWork orders & job cards
Job types with checklists, required readings, parts lists and time standards: configurable per service line.
checklist · parts · standardDispatch board
Live board by technician, skill and SLA window with drag-to-reassign, travel-time estimates and emergency insertion.
skill · sla · reassignRoute optimisation
Ordered routes with travel and service-time estimates, re-sequenced when a job over-runs or a customer cancels.
sequence · re-planMobile capture
Native iOS and Android with resilient capture through weak signal, camera and document attachment, and on-device drafts.
ios · android · resilientProof & compliance
Geo-fence validation, timestamped photographs, e-signature capture and mandatory-field enforcement before closure.
geo-fence · photo · e-signVan stock & returns
Technician stock as a real inventory location, with issue, consumption, return and reconciliation against the job card.
issue · consume · returnAttendance & payout
Field attendance from the first verified visit, distance from the actual route, and allowance computed on policy.
verified km · allowanceGoverned lane
A missed visit that re-plans the day before lunch.
The route agent may prepare a recovery, but Priya confirms the move and Ravi accepts it in the field app. Proof still decides whether the job closes.
“which visits closed yesterday without a geo-verified check-in, and whose”
Three agents on the day. The engineer owns the job.
Agents prepare and verify the day. Dispatch, field acceptance, stock and exception authority remain named.
Matches each job to skill, parts and SLA window, and proposes the reassignment when one over-runs.
dispatcher confirms every moveSequences the day around travel time and priority, and re-plans when reality diverges from the plan.
trade-offs shown, not hiddenChecks proof completeness before closure and flags the patterns that look like desk-filled visits.
supervisor decides on exceptionsReconciles van stock against consumption and returns, and raises the shortfall while the engineer is still on shift.
write-offs need an approver
Bring one beat plan. Walk it in the app.
A 90-minute working session: your job types, proof rules and beat coverage drafted as an FRS, approved, and generated to a staging tenant with the mobile app on your phone.
For your technical team
Field operations is meta on the platform: van stock is a location in the same inventory model, jobs reference the same customer record, and every proof artefact is retained under your own residency policy.