Asset confirmation
Scan the expected QR or barcode, with a short manual PIN fallback and an explicit mismatch path.
Driver app
Signal optional.
Proof required.
The driver experience starts with a simple truth: the jobsite and transfer station do not care whether the phone has service.
The current service day and next published service day stay available through an encrypted, durable offline workflow.
9:41
NEXT STOP · SWAP
Riverside Roofing
20 yd · Container C-184
2812 Mason Ave
Gate code and placement notes available
Gate code and placement notes available
Offline readyRoute and evidence requirements saved
A focused stop workflow
The next action stays obvious.
Large targets, clear status, and the minimum job context help a driver move through the stop without navigating office software.
- 1Acknowledge
Review the assignment and confirm the stop is on your route.
- 2En route
Signal that you are moving so dispatch can follow progress.
- 3Arrive
Mark your arrival and bring access and placement notes forward.
- 4Start
Begin the work and follow the proof requirements for this job type.
- 5Complete or explain why not
Capture the required evidence or record the exception before moving on.
Evidence engine
Capture it where it happened.
Requirements can change by job type, so the app asks for the right proof instead of relying on memory at the end of the day.
Job photos
Placement, condition, damage, contamination, and blocked-access evidence remain connected to the job.
Customer signature
Collect a signature when the agreement or job requires it and retain the context around acceptance.
Scale tickets
Capture the original ticket offline. Assisted extraction begins after reconnect and remains subject to human review.
Wait time
A visible timer records start, pause, and stop events through process interruption.
Exceptions
Partial jobs, failed access, damage, rejected loads, and missing evidence take a named recovery path.
Offline by design
No fake “offline mode.”
The daily route, stop details, access notes, and evidence requirements are designed to be downloaded before the driver needs them.
- Encrypted local queuePending events and media stay protected on the device.
- Visible sync stateThe driver can see what is saved, queued, uploading, or needs attention.
- Idempotent replayRetries do not create duplicate accepted events.
- Conflict handlingOffline changes surface for resolution instead of silently winning.
Safe field decisions
The edge cases belong in the workflow.
The app preserves performed work and evidence while keeping commercial, custody, and authorization conflicts visible to the office.
Route revisions
Published changes carry a new revision. The driver acknowledges the current route, while stale or conflicting work returns to dispatch for resolution.
Payment-aware completion
COD stops show paid, unpaid, or stale status. Completion waits for a verified hosted payment or an audited office release; drivers never handle card or bank credentials.
Job-scoped communication
Masked call and text actions keep the customer and driver connected without exposing either party’s personal number.
Incident and recovery
Damage, accidents, blocked access, contamination, facility rejection, and partial or failed work retain evidence and open the appropriate recovery path.
Single-user device security
An enrolled driver session uses encrypted local storage, PIN or biometric unlock, a bounded offline lease, and remote revocation without deleting queued evidence.
Location with boundaries
Foreground job location supports dispatch and evidence. History is access-controlled, and off-shift tracking is not part of the workflow.
See the field workflow
Bring the driver who knows every workaround.
A useful demo includes the person using the route in bright sun, bad weather, dirty gloves, and weak service.
Request pilot access 30-day sandbox · No card required · Guided setup