The field app

For the person standing in the crawlspace.

Not the office screens with things hidden. A different shell, with different assumptions about the hand holding the phone and the light falling on it.

Fourteen days, not today

A tech who cannot see tomorrow cannot plan tomorrow. The schedule runs a fortnight ahead, grouped by day, with yesterday’s unfinished work pinned at the top and a separate list of jobs still waiting on a date.

What the job actually is

The scope of work off the quote, the state of the paperwork, and whether anybody has been to this property before — with the two kinds of note kept apart: what to do on this visit, and what is true about the place, like the gate code and the dog.

Photos in both directions

Take them, and see the ones already there. An app that can add a photo but never show one is backwards for the person standing where they were taken.

Built for a thumb, in the sun

Navigation at the bottom, because the top of a phone is the part you cannot reach one-handed. Large primary actions. High contrast, pinned light and not switchable — no contrast ratio rescues a dark screen at midday.

It tells you when it is offline

A persistent strip, never a toast. A notification that has already faded cannot answer the question a tech has thirty seconds later, which is whether that saved.

The decision behind it

Prices are not on the crew’s screen

The scope of work renders without the money attached. A tech holding a phone up in somebody’s driveway should not have a dollar figure on it, and the state of the contract is shown as a chip — signed, deposit cleared — rather than as an amount.

Be clear about what that is and is not. It keeps a number off a screen in front of a customer; it is not a confidentiality boundary, because a staff member with a login can read what their role permits anywhere else in the product. Real confidentiality would mean taking payment records away from the office staff who need them.

What this does not do

  • No GPS breadcrumbs and no location tracking. It is a privacy surface and a support burden for a signal nobody here acts on.
  • Photos will not upload with no signal, and you are told so at the time rather than next week.
  • It is not the whole product on a phone. Anything that reshapes the business happens in the office app.

Questions

What happens in a basement with no bars?

Notes, status changes and time entries are queued and go up when signal comes back. Photographs are the exception and are refused at the time — a tech who believes photos are safe and learns next week that they never uploaded is worse off than one told immediately to try again with signal.

Do I have to give my crew the full system?

No. Which shell somebody sees is a setting, and what they are allowed to do is their role — two separate things. A field tech typing an office URL still gets the same refusal their role would give them anywhere.

Is there an app to install?

No. It runs in the phone’s browser and can be pinned to the home screen, so there is no store, no install and nothing for a new hire to set up on their first morning.

The rest of it

Or start from your trade

See it against one real job

Fourteen days, no card. Put a job you already know through it and judge it on that.

What it costs · How your data is handled