WorkSuite Field
Field Team Mobile App
WorkSuite Field puts the WorkSuite job record in a technician's pocket — the same checklist, photo proof and signature the office sees, captured where the work happens, with or without signal.
Designed & developed by Entrovix
- Year
- 2025
- Discipline
- Field OperationsMobile ProductEngineering
- Services
- Product StrategyUX/UI DesignOffline ArchitectureMobile Engineering
- Built with
- React NativeWatermelonDBSQLiteGraphQLNode.js
The Challenge
The record ends where the signal does
An operations platform is only as truthful as its last update, and the last update happens in a basement plant room with no bars on the phone. When completion notes are typed up back at the van — or back at home — the record the office trusts is really a memory of it.
WorkSuite already held the job from quote to invoice. What field crews carried was a printout and a promise. The brief was the missing half: the same record, in the pocket of the person doing the work, dependable in exactly the places connectivity is not.
The Approach
How we worked
One record, two places
Field writes to the same WorkSuite job record the office reads. Nothing is retyped, nothing reconciled, and a completed checklist is the same fact everywhere.
Offline is the default
Every action lands in the phone's local store first and syncs when it can. Connectivity improves the experience; it is never a requirement for doing the work.
Proof where the work happens
The checklist is ticked at the machine, the photo taken of the finished work, the signature collected in the doorway — not reconstructed at day's end.
The day, in driving order
Jobs are listed in the order they will be driven, each with its time window and status, so the top of the list is always the next decision.
The Solution
The same record, pocket-sized
The day opens as a list a technician can act on: jobs in driving order under the day's header, each card carrying its time window and a status chip, the route between them drawn as a line rather than left to guesswork. A job expands in place — checklist, photo-proof block, and a “Mark complete” pill that means what it says.
Beneath all of it, every tap writes locally first. Completions, photos and signatures join a queue, a small toast reports what is waiting, and the queue drains in order whenever signal returns. The office sees the truth a few minutes late at worst; the technician never waits on a spinner at all.
Inside the product
What it actually does
Every Screen
One product, whatever it is opened on
The phone layout is not the desktop one squeezed down. Density, hit areas and reading order are decided per screen, and the interface keeps its meaning at both ends.
Capability
What we brought to WorkSuite Field
The same services are available on their own — each one links to what it involves, how it runs and what you get.
Built with
- React Native
- WatermelonDB
- SQLite
- GraphQL
- Node.js
Disciplines
Field Operations · Mobile Product · Engineering
The Outcome
What it settled
- Field crews and the office share one job record
- Every action lands locally first; signal is never a precondition
- Proof of completion is captured at the job, not recalled later
- Sign-off happens on site, on the record it belongs to
That was some of our work
Now let’s talk about yours.
Tell us what you’re building. You’ll get a written plan, a clear proposal, and a team that shows its work every week.