Delivery & courier
Drop sequences, proof of delivery, failed attempts recorded with a reason.
Mobile Workforce Application
The job list, the proof and the paperwork — on the phone your team already carries.
Jobs go out by WhatsApp and come back as photos in someone's camera roll, so the office spends the evening reconstructing the day. A workforce app hands each person their list, captures the evidence on the spot, and closes the job before they drive away.
Job dispatch
and list
and list
Photo and
signature proof
signature proof
Works
offline
offline
Live job
status
status
Job assignedOn the crew's list, not in a chat
Proof capturedPhoto and signature on the job
SyncedUploaded once signal returns
The problem
The work gets done. The record of it does not
Field teams are rarely the problem. The problem is that everything they do has to be re-entered by someone in an office who was not there, from photos, texts and a damp job sheet.
- Jobs are sent by WhatsApp and confirmed by reply, so the day is reassembled afterwards from a chat log.
- Proof of delivery or completion is a photo sitting in a personal camera roll.
- Paper job sheets come back at the end of the week, incomplete and hard to read.
- The office cannot say what is finished and what is outstanding without ringing round the crews.
- Signal is patchy in basements, plantations and industrial sites — exactly where the work happens.
Built for field teams
Teams whose work happens away from a desk
If your people spend the day at addresses rather than in an office, the same three things matter: what is on the list, what proves it was done, and how quickly the office finds out.
Installation & maintenance
Scheduled and reactive jobs, with parts used and before-and-after photos.
Facilities & cleaning
Recurring site visits with checklists that prove the round was completed.
Utilities & telco crews
Work orders against an asset, with readings and compliance forms captured on site.
Merchandising & field sales
Store visits with shelf photos, stock counts and orders taken at the door.
Inspection & audit
Structured forms with pass and fail items, photographs and a signed-off report.
Offline is the decision that shapes everything else. If your teams work where there is no signal, the app has to hold the job, the photos and the form on the device and reconcile them later. That is a different build from one that assumes a connection, and it is not something to add on afterwards.
If your crews are always in coverage and you only need a shared job list, a good task tool with a mobile app may be enough. Custom pays off once there are forms to fill, evidence to capture, and the record has to reach your own back office.
From dispatch to invoice
How a job moves through the system
Six steps. Step five is the one that matters technically — everything captured on site has to survive a dead zone and arrive intact.
Dispatch
The office assigns jobs to a person or crew, by area, skill or route.
Accept
The job appears on the phone and is accepted, so the office knows it has landed.
Travel
Navigation to the address, with arrival time recorded rather than estimated.
Do the job
Checklist completed, parts recorded, photos taken, customer signs on the screen.
Sync
Held on the device if there is no signal, uploaded the moment there is.
Close
Job closed with its evidence attached, and passed to billing or payroll.
Failure has to be a first-class outcome. A job that could not be completed — nobody home, access refused, part unavailable — needs a reason code and a photo just as much as a successful one, otherwise crews leave it blank and the report lies.
Core modules
Main modules and functions
Most operations start with dispatch, the mobile job list and proof capture. Stock, payroll exports and customer notifications come once crews are working in the app daily.
Job dispatch
Assignment by area, skill or route, with reassignment and priority when the day changes.
Mobile job list
Today's work in order, with address, contact, instructions and history of the site.
Forms & checklists
Your own forms per job type, with mandatory fields and pass or fail items.
Photo & signature
Evidence captured against the job, stamped with time and position at the point of capture.
Offline & sync
Full working without a connection, with conflict handling when two updates disagree.
Time & attendance
Start, break and finish recorded on site, feeding overtime and allowance calculations.
Location & route
Where crews are now, distance travelled, and the order stops were actually visited in.
Parts & stock
Van stock drawn down as parts are used, with replenishment requests from the field.
Reports & exports
Jobs completed, first-time fix rate, time on site, and exports to billing and payroll.
From a live build
Screens from a field operations system we built
From the Bolt X Yunda delivery platform. These are the office screens — the job states shown here, including a failed delivery attempt, are what a courier records in the field. Names in these screens are sample data.
Implementation
Typical implementation
Six stages. The crews have to be involved from the first one — an app designed in an office gets left in a pocket.
Scoping workshop
With dispatchers and two people who actually do the work. We map a real day, including what goes wrong and how it is currently handled.
Output: job types, forms and outcome codesField & device audit
What phones the crews carry, what condition they are in, and where coverage actually drops. This decides how much has to work offline.
Output: device baseline and offline requirementDesign & sign-off
Screen-by-screen design of the app and the dispatch board, designed for one thumb, bright sunlight and gloves where relevant.
Output: signed-off screens, build scheduleBuild in stages
Dispatch, job list and proof capture first, so one crew can run live jobs while forms and reporting are still being built.
Output: test build on real handsetsPilot crew & UAT
One crew runs a fortnight of real work on the app, deliberately including a site with no signal, a failed job and a same-day reassignment.
Output: pilot findings, signed UATRollout & handover
Crew by crew rather than all at once, with the pilot team helping train the next group.
Output: live app, SOP, support window
Timeline
About four months for app and back office
For a workforce of twenty to two hundred with offline working and custom forms. A connected-only job list with no forms is closer to eight weeks.
Month 1Month 2Month 3Month 4
Scoping workshop
Field & device audit
Design & sign-off
Core build & offline sync
Forms, stock, reporting
Pilot crew & UAT
Rollout by crew
Offline sync is the part that takes the time. Anyone can build a job list; making it behave sensibly when two people edited the same job in a dead zone is where the engineering goes, and it is worth paying for once rather than patching later.
Client feedback
From a mobility client we've worked with
It has been a pleasant experience so far working with UNO. They are understanding and responsive towards giving solutions that cater for our needs and requests.