A technician view that works on the phone they already have.

The technician's view opens on the jobs assigned for today and what each visit actually involves — the property, the units in scope, the devices on the route, and the history that makes this visit different from the last one.

That is deliberately narrow. A technician does not need the operations schedule; they need the next thing, with enough context to do it without calling the office.

• Today's assigned jobs in one list.
• Check-in, check-out and service time recorded as the visit runs.
• Guided job completion, in the browser.

Everything captured after the fact is a reconstruction. Materials get approximated, findings get generalised, and the detail that made a note worth keeping is the first thing to go.

Capturing scans, materials, treatments, notes and photos during the visit is partly about accuracy and partly about the technician's evening. Work recorded on site is work that does not have to be written up later.

Running the field experience in the browser removes a category of problems that has nothing to do with pest control: app store installs on personal phones, version skew between technicians, and a subcontractor who cannot start because provisioning has not happened yet.

A technician opens a link on the device they already carry. New technicians are working the same day rather than the day after IT gets to them.

What the technician records is what the office sees. Completed work, issues raised, materials used and time on site flow into the work order and the account's service history without a re-entry step in between, which is the point at which most field data quietly dies.