Forms that work in the rain: designing inspection and job forms for field teams

There is a reliable way to find out whether a field form was designed by someone who has stood on a site: look at how many taps it takes to record that everything is fine.

Field work is dominated by the normal case. Most inspections pass. Most jobs complete. Most assets are where the record says they are. A form that treats every visit as an exception — demanding notes, confirmations and free text on items that were fine — trains crews to do the thing every office fears: complete the paperwork in the van, from memory, at the end of the day.

Key takeaways

• The competing tool is a notes app, so the form must be faster than typing. - Design for gloves, glare and one hand: large targets, high contrast, no pinch-zoom. - Default to pass and record exceptions, so a clean site takes seconds. - Treat photographs as evidence: geotag, timestamp and tie them to the failed item. - Assume the signal drops; queue offline and sync without losing a keystroke. ## The real competitor is the notes app

A field form is not competing with a rival product. It is competing with a photograph, a voice note, and a WhatsApp message to the supervisor. Those tools win because they are instant, forgiving and available with one hand.

Anything you build has to be measured against that bar. If recording a completed job takes longer than describing it in a message, the message wins and your system holds partial truth.

Compliance is not achieved by requiring fields. It is achieved by making the honest answer the fastest one to give.

Design for gloves, glare and one hand

The physical context sets most of the design rules, and they are not the same as office software.

Targets need to be large, because fingers are gloved and hands are unsteady on a ladder. Contrast needs to survive direct sunlight, which rules out light grey labels and thin type. Layout should tolerate a device held in one hand, meaning primary controls stay within thumb reach. Text entry should be the last resort: every free-text box on a site form is a box that gets filled in with "n/a".

Voice dictation deserves explicit support rather than tolerance. It is often the only practical way to capture a paragraph of detail while holding something in the other hand.

Pass-by-default, exception-by-exception

The single biggest gain in inspection form design is structural. Present each check as a state that defaults to nothing recorded, make "pass" a one-tap action, and reveal the follow-up questions — severity, photo, note, remedial action — only when a fail or an observation is selected.

A twenty-point inspection where everything passes should take under a minute. The one point that failed should then get a serious, structured record: what, where, how bad, photographed, who needs to know.

That asymmetry is the whole trick. It puts the effort exactly where the value is, and it stops crews learning to rush the parts that matter because the parts that don't were exhausting.

Photographs are the evidence, so treat them properly

In field work, the photograph is frequently the deliverable. Design for it.

Attach photos to the specific check rather than dumping them at the end, so nobody has to reconstruct which image showed which defect. Allow several per item. Let a caption be optional but easy. Compress on the device so a bad signal does not block the submission. And keep the original timestamp, because on a dispute about when a defect appeared, that metadata is the argument.

Annotation matters more than resolution. A circle around the crack communicates more than a sharper picture of the whole wall.

Assume the signal will fail

Basements, plant rooms, roofs, rural sites, tunnels. A field form that requires connectivity at the moment of submission will lose data, and it will lose it in the least convenient way: after the work is done and the crew has driven away.

The behaviour to aim for is unremarkable to the user. Entries persist locally as they are made. The submit action queues rather than fails. The device syncs when it can and says clearly what is still waiting. Nothing is silently dropped, and nothing needs re-typing.

Equally important: the crew should be able to see what they already submitted for the day. Uncertainty about whether a job was sent produces duplicates, and duplicates produce invoicing arguments.

Sign-off, safety and the paper trail

Many field forms exist to prove something happened. That means the record has to carry the proof rather than imply it.

Capture a signature where a client or a responsible person is confirming completion, with their printed name and role alongside it. Record the time and, where appropriate, the location. Where a check is safety-critical — isolation, permit to work, gas or electrical certification — treat the sequence as a sequence: certain steps cannot be skipped, and the form should be honest about which ones those are rather than blocking everything equally.

Then close the loop with the person on site: send them a copy of what they signed, automatically, without anyone in the office having to remember.

The office side is the point

Field forms fail at the handover more often than at the input. Crews complete them properly and the data lands somewhere nobody uses.

Route submissions by job type and severity, not just into one pile. A failed safety check should notify a named person immediately; a routine completion should update the job and stay quiet. Give supervisors a filtered view of outstanding defects rather than a chronological feed. Make export and PDF generation ordinary, because clients, insurers and principal contractors will all ask for the record in their own preferred shape.

And keep the asset history joined up. The value of five years of inspections is in seeing the same unit fail the same check repeatedly — a pattern no individual submission reveals.

What to change first

If you own a field form today, three changes usually pay immediately. Make pass a single tap and hide the follow-ups behind exceptions. Attach photos per check rather than at the end. Make submission queue offline instead of failing.

After that, the useful metric is not completion rate but completion timing: what fraction of forms are submitted on site rather than hours later. Move that number and the data gets more accurate for reasons no amount of policy could achieve.

Frequently asked questions

Should inspection forms work offline?

Yes. Assume no signal in basements, plant rooms and rural sites. Queue submissions locally, sync when connectivity returns, and show the inspector a clear pending state so nothing is submitted twice.

How many photos should an inspection form allow?

Enough for the worst case — typically ten or more per failed item — with compression handled for the inspector. Attach each photo to the specific item it evidences rather than to the inspection as a whole.

Is a signature field legally sufficient for sign-off?

For most operational purposes, a captured signature with a timestamp, the signer's name and a device or location record is adequate. Where a regulator specifies a format, follow the regulator and keep the audit trail immutable.

How do I stop inspectors ticking everything as pass?

Make exceptions cheap and passes automatic, then require a note or photograph on any fail. Rushed clean sheets usually signal that recording a problem is slower than ignoring it.