Replacing paper field records with an app

A lot of field work still ends on paper. A crew finishes a job, someone fills out a sheet on a clipboard, and the sheet goes in a binder or a truck door. Weeks later, a customer or an inspector asks for it.

We have built two apps that replace this kind of paper: the Field Crew Portal and Spray Log. One is a private portal for a utility line-clearance company. It handles field safety audits, a crew rewards program, and text reminders. The other is a records app for an agricultural drone-spraying operator. It handles mix and application records, PDF exports, quotes and a map view. Before each app, the same kind of information lived in binders, by hand, and in group texts.

This is what we learned about doing it well. None of it needs a big system. It needs the right record, captured at the right time, on a screen that works in the field.

Start with the record someone already asks for

Do not start with a wish list. Start with the paper you already fill out because someone requires it. That is the record with a real reader: a regulator, a utility, a customer, or your own safety lead.

For the spraying operator, that meant mix records and application records for every job. For the line-clearance company, it meant safety audits built on OSHA and ANSI requirements.

Get the field list from the source, not from memory. If a regulator, your state agency or a customer contract says what a record must hold, use that as your checklist. Rules change, so check the current version with the agency before you design the form, and again before each season.

Then decide when each field gets filled in. The best time is while the work is happening, by the person doing it. A record written that evening from memory is weaker than one tapped in on site. In the spraying app, records are captured once in the field. Nobody copies them over later.

Design for a phone in the field

The line-clearance brief said it plainly: the crews needed one place that worked on a phone in a bucket truck. That sentence should shape every screen.

Some rules that help:

• Pick, don't type. Lists, toggles and checkboxes beat text boxes. Typing on a phone with gloves on is slow.
• Fill in what you already know. Today's date, the crew, the job. Don't make anyone enter it twice.
• Make tap targets big. Small buttons get missed in a moving truck.
• Keep one task per screen. A long form is easier as a few short steps.
• Check contrast in daylight. Pale gray text disappears in the sun.

Then test it where it will be used. Hand a phone to a crew lead and watch. Anything they hesitate on is the next thing to fix.

Exports people will accept

A digital record only helps if the people who ask for it can read it. Many of them want a document, not a login.

The spraying app exports records as clean PDFs. That gives the operator something to email, print or attach without asking anyone to learn new software. Some rules also require you to hand a copy of the record to the customer, so check whether yours do.

When you design an export, lay it out the way the reader expects. Put the fields they look for first. Show who did the work and when. Keep one record per page if you can, so a single job can be handed over on its own.

Every finding needs an owner and a due date

An inspection that finds a problem is only half done. Paper is good at recording a finding and bad at making sure someone fixes it.

The line-clearance portal pairs its audit checklists with a corrective-action workflow. Every finding gets an owner and a due date. That turns an audit from a report into a short to-do list with names on it.

If you build only one feature beyond the basic form, make it this one. Keep it simple: what is wrong, who owns it, when it is due, and whether it is closed. A list of open items past their due date tells a safety lead more than a stack of completed forms.

Let reminders go out on their own

Many field businesses run on reminders. Payroll is due. A certification is about to lapse. Today, someone sends those by hand in a group text, when they remember.

In the line-clearance portal, payroll and certification reminders go out automatically by text from two sending numbers, and every message is logged. The log matters as much as the sending. When someone says they never got the reminder, you can check.

Start with the reminders that already exist. Write down who gets them, when, and what they say. Then automate those exact messages before adding new ones.

Recognition can use the same records

Once crew activity is on record, it can do more than paperwork. The line-clearance portal includes a rewards program with levels, badges, streaks and seasons. A points ledger sits behind every badge and raffle drawing, so every award can be checked. Recognition that can be checked is easier to trust.

Test so a deploy never breaks the season

Field businesses are seasonal. If the app breaks during a busy week, crews are back on paper.

So we test the spraying app two ways. It has 82 unit tests that check small pieces of logic one at a time. It also has end-to-end tests that use Playwright, a browser testing tool. They sign in like a real user and walk through the real flows. That is how a deploy is kept from breaking the season.

You do not need to know how to write tests to ask for them. Ask whoever builds your app two questions. Which flows are tested from sign-in to finish? Do those tests run before every update goes live?

Start small

You do not need to move the whole business at once. A good first step looks like this:

1. Pick the one paper record that matters most, usually the one a regulator or customer asks for.
2. Build that form and its export.
3. Put it in front of one crew and fix what they trip over.
4. Add the next piece: corrective actions, reminders, quotes, a map view.

The spraying app, for example, also keeps quotes and estimates in the same place as the records. You can grow into that once the core records work.

Related work

Related services: Custom software · AI automation