Field team software: offline-first or don’t bother

Field team software: offline-first or don’t bother is the blunt rule when the van is the office and the job must finish before the engineer drives away. If jobs, photos, forms, and signatures only work on office Wi‑Fi, you bought a demo, not a field tool. UK trades and field-service teams learn that in basements, plant rooms, and rural sites where 4G is a rumour and the customer is waiting for a signature.

Why online-only dies on site

A web app that needs a live connection fails the moment the engineer is underground or behind thick walls. They write on paper, take photos on the camera roll, and type it up later. That is how you get duplicate jobs, missing photos, and status that never matches the van. “Just use 4G” is not a product strategy. I’ve watched crews abandon apps that spun forever on a loading screen and go back to WhatsApp and a paper docket in the glovebox, then blame “the system” when the office never sees the photos.

What offline-first means for a buyer

Offline-first means the engineer can open today’s jobs, capture notes and photos, collect a signature, and mark status without a signal. The device queues the work and syncs when connectivity returns. Conflict rules are written in plain English: who wins if the office changes a job while the van is editing it, and what the engineer sees when a sync fails halfway. You do not need a sync-engine lecture. You need to know capture works offline, queue is visible, and sync does not invent twin jobs.

Eight Mile’s SaaS work treats field apps as a normal product slice: offline first, camera and scanning, background sync, on accounts you own. Soft path when the build sits inside a wider eng effort: software development. For trades ops we already run software in that world; the conversation is still a survey and a fixed-price first release, not a feature catalogue. You own the code and the accounts from day one, which matters when the vans are already live.

Portal vs field app

A customer or office portal on the web is enough when work happens at a desk with reliable network. You need a field app when the person doing the job is away from the office and must finish the record before they leave the site. Many companies need both: office portal for planners and customers, offline-capable app for the van, linked to the same jobs and status. Do not force field staff through a desktop UI on a phone with fat fingers and wet gloves.

Ruthless v1 for the field

First release should be jobs list, job detail, photos, status, and sync you can trust. Signatures if you take payment or sign-off on site. Skip the bloated suite: HR, full CRM, and fifteen report types can wait until the van trusts the app on a bad signal day. If v1 cannot complete a job offline and push it later, it is not field software. Ship the thin loop first and add the suite when crews trust the sync on a wet Tuesday with no bars.

Buy for the basement

If you are weighing field team software: offline-first or don’t bother, buy for the worst signal on your routes, not for the Wi‑Fi in the yard or the 4G bar outside the office door.

Capture offline. Queue clearly. Sync without twins.

If you want a field or portal build on accounts you own, contact Eight Mile and say where signal dies and what the van must finish before they leave.