Paperwork
Reports typed up at night
From memory, with photos scattered across a personal phone, long after the visit ended.
PILLAR II
The whole job on the technician's phone, signal or not
The field app holds the day's work, each site's history, checklists and guides. Photos and signatures are captured during the job, and everything syncs when the phone finds signal again.
- Critical work available offline
- 100%
- Delta sync on 4G
- < 3s
- Battery used per shift
- < 15%
The problem
Field work happens where the signal drops
Basements, plant rooms, rural sites and highways are exactly where the work happens.
Signal
Dead zones stop the work
An app that needs a connection to open a ticket forces a choice: walk outside or write on paper.
Preparation
Arriving without the part
Without the last visit's notes or the right checklist, the first visit turns into a second one.
How it works
One visit, from the morning sync to the closed job
Each step is recorded on the phone first, with its real time and place, and sent when there is signal.
The day lands on the phone
Tickets, sites, task lists, safety checklists, the van's inventory and published guides sync before the technician leaves. Only what they are entitled to see ever reaches the device.
first sync: snapshot · then: changes only
Navigate and arrive
Turn-by-turn directions to the site. When the phone is within 50 m of the site and moving slower than walking-in speed, the arrival is logged on its own.
arrival: ≤ 50 m and < 15 km/h
Safety before the work starts
Start work stays locked until every mandatory safety checklist is answered and signed. An unsafe answer stops the job. The SOS button is always one long press away.
arrived → in progress only when compliant
Guided through the job
The task list walks the job step by step. The field assistant suggests fixes from similar resolved tickets and the knowledge base, reads a photo of the fault, and drafts the report.
knowledge scoped to the ticket's client
Proof captured as it happens
Photos and video are taken with the camera against each evidence requirement, stamped with GPS and time, encrypted on the phone and uploaded in the background, resuming on poor connections.
time of capture, never time of upload
Closed and synced
The job can't close with required evidence missing. Everything done offline is sent in order and applied exactly once; if the office changed something meanwhile, the server decides, nothing is blindly overwritten.
ordered outbox · applied exactly once
Tickets, sites, task lists, safety checklists, the van's inventory and published guides sync before the technician leaves. Only what they are entitled to see ever reaches the device.
first sync: snapshot · then: changes only
In numbers
Paperwork happens during the visit
Reports, photos, signatures and hours are captured on the phone while the job is under way, so nothing is left for the evening.
Minutes of paperwork per visit
The report and the timesheet account for most of the time saved.
Show the numbers
| Paper and chat | Field app | |
|---|---|---|
| Service report | 9 min | 1.5 min |
| Photos | 4 min | 0.5 min |
| Signature | 2 min | 0.5 min |
| Timesheet | 3 min | 0 min |
Rules that always hold
Made for how technicians actually work
Offline
Work done offline is kept
Every action is written to the phone first and queued in an outbox that survives restarts and dead batteries.
Time
The time it happened
A visit closed at 11:40 in a basement says 11:40, even if it reached the server at 12:30.
Privacy
Tracked only on shift
Location is recorded between clock-in and clock-out, with a visible notification. Off shift, nothing.
Hardware
Built for a mid-range Android
One hand free, a cheap phone and a battery that has to last the day. No special devices.
Scope
Only what they should see
One client's guides never appear at another client's site, and revoked access purges the device.
Evidence
From the camera, at the time
Each photo carries its position and accuracy. Pictures picked from the gallery aren't accepted as evidence.
Configuration
Defaults tuned for the field
- Arrival radius
- 50 m
- Distance from the site that counts as arrived
- Arrival speed
- < 15 km/h
- Separates an arrival from driving past
- Low-confidence fix
- > 50 m
- Readings this imprecise are kept, never acted on
- Tracking interval
- ≈ 50 m
- Distance between readings on shift; 10 m while navigating
- Retry after reconnect
- < 5 s
- When queued work starts sending again
- Evidence media
- Photo · video
- Minimum count per requirement, set by quality rules
Who uses it
Who works with it every day
Field technician
Faisal
Finishes the shift with no paperwork left and trusts that hours, mileage and evidence are right.
Contractor technician
Vendors
Uses the same app with a restricted view: their tickets, what each requires, and evidence that triggers payment.
Operations manager
Sarah
Sees arrivals, progress and evidence live instead of calling for updates.
See it on your own operation
A 30-minute briefing with your dispatch, payroll and asset flows on screen.
Keep exploring
Intelligence
Every AI and ML capability
What each model answers, where it appears, and what it will never do on its own.
The visibility gap
What the office can't see
What running on WhatsApp and spreadsheets really costs, and what changes with one record.
Security
What your IT team will ask
Access by role and territory, sign-in, encryption, the audit log and devices in the field.
Changelog
What shipped, release by release
New capabilities and improvements across the console, field app and platform.