Field Operations

A field-operations platform for teams that work outside the office — service technicians, collection agents, delivery crews, sales reps, survey teams: day plans, offline-first capture, geo-tagged proof, and same-evening visibility for the office. Status: deployed and demonstrable.

Why field truth degrades on its way to the office

Visits claimed but unproven. Collections in pockets until deposit day. Forms filled from memory at dinner. And a manager’s dashboard that is a work of collaborative fiction, assembled from what people remember and what they would prefer to have happened.

None of that is dishonesty. It is what happens when the record is made hours after the work, by a tired person, on paper that then has to be typed by somebody else. Every step between the event and the record is a place where accuracy leaks.

The fix is capturing at the moment, on the device already in their hand — which only works if the software assumes the conditions the field actually has.

The design premise: assume disconnection

Networks in the field are worse than any dashboard admits. The highway stretch, the warehouse basement, the building’s lower floors, the border queue. An application that needs connectivity is a demo rather than a tool.

So every action completes locally first: the tap registers, the record is written to the device, the interface responds immediately. Sync happens invisibly afterwards, with state visible per record rather than as a single global indicator — because the crew member needs to know whether this delivery reached the office. [STORY SLOT: the DR Congo field-operations moment, one or two lines] — the instinct came from running operations where infrastructure genuinely fights back, and Indian highways keep it honest.

What the platform covers

• Day planning. Routes, beats and appointments pushed to the phone each morning, with the sequence the office intended and the flexibility the day requires.
• Offline capture. Forms, photographs, signatures, readings and payments — recorded without network, synced on return, conflicts resolved by rules decided in advance rather than by whoever syncs last.
• Geo-tagged proof. Location at check-in and at completion, which verifies work without tracking people. That boundary is deliberate and it is why teams adopt it.
• Collections mode. Receipts issued instantly, collections logged per agent, deposits reconciled daily against collections with an ageing clock on cash in hand.
• Office console. Live-enough boards, exception queues, and an evening settlement that closes each person’s day: visits, expenses, collections, done.

Why the surveillance boundary matters commercially

Teams sabotage tools they experience as monitoring — phones left in vehicles, check-ins batched at the end of the day, data entered to satisfy the system rather than to describe reality. The result is a dataset that looks complete and means nothing, which is worse than no dataset because decisions get made on it.

Tools that verify work rather than track people get adopted, because they also protect the worker: the photograph that ends a damage dispute, the receipt that proves the collection, the timestamp that shows the delay was at the customer’s gate. Field staff have their own reasons to want evidence, and designing for that is both decent and effective.

What deployment looks like

One route, one crew, two weeks. The route that complains most honestly, ideally — their objections are the specification for everything that needs adjusting.

Then the forms get corrected, the workflow simplified, and the labels translated properly. Then waves. The consistent finding across deployments is that the first version asks for more information than anyone needs, and the second version — shaped by watching real use — is the one that sticks.

The office side

Field capture only pays if the office consumes it well, so the console is deliberately narrow: today’s exceptions, today’s settlements, and anything that needs a decision.

Exception queues rather than dashboards. Visits not started by the expected time, collections not deposited, jobs completed without required evidence, devices that have not synced in a day. Silence means healthy — which is the only reporting design that survives contact with a busy operations desk.

The evening settlement. Each crew member’s day closed: what was completed, what was collected, what was spent, what remains. Ten minutes rather than an hour of reconstruction, and it happens while the day is still remembered.

A weekly pattern view. Which routes run long, which customers consume more time than their contract assumes, which crews need help rather than criticism. The data supports that conversation rather than replacing it.

What it does not do

It does not schedule optimally — route optimisation is a specialist product and for most operations the gains are smaller than the vendors suggest. It does not replace supervision. And it will not fix a route whose economics are wrong, though it will make them undeniable.

Related reading

/industries/logistics — drivers, PODs and COD · /products/services-erp — the contracts layer above it · /industries/lending — collections in the field · /services/mobile-apps — bespoke builds on the same principles

Tonight’s field truth, tonight

Pick one crew and one week. If the office cannot see what happened until the paperwork arrives on Monday, that delay is costing you decisions. /contact — ground pe kaam, screen pe sach.