Every delivery is atracked trip
Loader assigns. Driver scans QR. Unloader completes. Office sees it live — and when something goes wrong, trip issues keep reports fair.
End-to-end
Six steps from office setup to closed trip
Each step has a clear owner. The dashboard always shows where every load stands.
Office sets up the job
Engineers create projects from survey CSV or map points, define products and loading places, open sites with chainage segments, and assign company workers (drivers, loaders, foremen).
Foreman starts the site
On the mobile Work tab, the site foreman assigns loaders to each product place, names a supervisor, and starts the site so field trips can begin.
Loader hands off to driver
The loader assigns a driver, starts loading, and shows a QR code (or printed loader paper QR). The driver scans to accept the trip — status moves from loading to driving.
Driver transports the load
The driver carries material to the unloading site. Verification codes can confirm loader and driver identity at handoff.
Unloader completes the trip
At the site, the unloader verifies codes or scans arrival QR. When unloading finishes, the trip is marked unloaded and counts toward delivery totals.
Office reviews and reports
The dashboard shows live trip status, site statistics, and delivery progress. Generate equipment-per-trip reports per site or approve trip issues to update scores automatically.
Trip statuses — always know the phase
Field actions update status in real time. Office filters trips and KPIs by these values.
loading
At product place — loader active
driving
Driver en route to site
unloading
At destination — unloader active
unloaded
Complete — counts toward delivery
needs checking
GPS verification pending
approved
Verified & closed
Handoff
QR scenarios that matter
Train loaders and drivers on the right flow — wrong scans create support tickets. These are the four patterns Econ is built for.
Loader QR → driver scan
Loader creates trip (loading). Driver scans the same QR → one trip moves to driving. No duplicate.
Paper QR from site page
Printed sheet with r: "paper". Driver scan creates a new trip, then accepts → driving.
Driver without loader
When office enabled the site flag, driver creates trip directly → driving (no loader QR).
Fallback by loader + product
QR without identifier: backend finds LOADING trip for that loader and product on the site.
Mobile playbooks
What each role does on a trip
Foreman
- 1.Work → project → Not Started site
- 2.Assign loaders per place + supervisor
- 3.Start site
Loader
- 1.Loader sites → site detail
- 2.Pick driver → show QR
- 3.Sync if offline after handoff
Driver
- 1.Driver sites → scan QR to accept
- 2.Transport load
- 3.Report trip issue if needed
Unloader
- 1.Unloading sites → incoming trucks
- 2.Scan / verify complete
- 3.Trip → unloaded
Trip issues — when delivery doesn't go to plan
Drivers report. Foremen classify. Backoffice approves with fixed report values — so KPIs stay fair and auditable.
NONE → ISSUE_REPORTED → PENDING_APPROVAL → APPROVED
↘ reject → ISSUE_REPORTED (foreman may re-classify)Driver
Reports a trip issue from the mobile app when something goes wrong on the route or at delivery.
Foreman
Classifies what happened (returned to loading, wasted, reached intended site, or new useful location).
Backoffice
Approves or rejects. On approve, report value is fixed by classification; some outcomes mark the trip unloaded and trigger a per-trip equipment report.
Classification outcomes
Fixed report values — set on backoffice approve only
Before approve: trip excluded from product totals (contribution 0).
On reject: classification cleared; foreman can submit a new resolution.
- Material returned to loading site — no delivery credit (0)
- Material wasted at wrong place — negative impact (−1)
- Material reached intended site — full credit (+1)
- Material unloaded at new useful location — full credit (+1)
See your trips live in the dashboard
Log in to watch loads move from loading to unloaded, approve trip issues, and generate site reports — while field staff use mobile for QR and handoffs.