Field notes for operations software

Designing for no signal

Field apps fail in basements, lifts and rural roads. Rules we apply:

• Write every action to a local queue first; the network is a delivery mechanism, not the source of truth.
• Show sync status per item (queued, sent, confirmed), not a global spinner.
• Give each action a client-generated ID so retries never duplicate a delivery.
• Decide conflict rules in advance: last-write-wins is acceptable for notes, never for stock counts.
• Test with airplane mode toggled mid-action, not only before.

Exception inventory template

Before estimating, list exceptions per task in a table with five columns: task, what goes wrong, how often (per shift), who resolves it, what proof is needed. Rows with high frequency and a photo or signature as proof are your first screens to design — they decide whether staff trust the tool.

Dispatch tables that work

• Freeze the identifier column; dispatchers scan by order number.
• Use tabular figures for times and quantities so columns align.
• Colour encodes status only, always paired with a text label or icon.
• Bulk actions need a visible count: “Assign 14 orders to route 7”.
• Keyboard: J/K to move, Enter to open, Esc to close — and document it on screen.

Store review checklist

• Organisation developer accounts registered to your legal entity, not an employee.
• Privacy policy URL live and matching what the app collects.
• Location permission: explain purpose in the prompt text; request background location only if essential and justified.
• Demo account for reviewers if the app requires login.
• Screenshots from the current build; no features that are not shipped.
• Google Play: complete Data safety and target the current required API level.

Writing a brief we can estimate

A one-page brief is enough if it answers: who uses it (roles, count, devices); the three most frequent tasks; current tools; systems that must connect; constraints (deadline, budget range, hosting); how you will judge success in numbers. Use the dispatch planner to draft it.

Glossary

POD

Proof of delivery: signature, photo or code captured at handover.

WMS / TMS

Warehouse / transport management system.

Slotting

Assigning storage locations or delivery time windows.

Staged rollout

Releasing an update to a percentage of users first.