Follow the next drop-off
Use the next-stop details and the onboard roster. Different passengers can have different destinations. Match the displayed rider to the person leaving the vehicle.
Confirm the passenger’s drop-off
At the correct stopping point, complete the drop-off action and any optional rating. Wait for the server-acknowledged change before assuming that passenger has left the onboard list or the seat has been released.
Continue to the remaining stops
Check the new next stop after each completion. If a rider requests an earlier stop through the app, acknowledge the situation and stop somewhere practical; the original destination may no longer be the active stop.
Read the final summary
At the end of your route, compare Gross rider fares, TagRides service fees, Net earnings and the per-trip lines. Read the settlement note. Settlement pending and mixed cash/wallet records are not proof that every amount has reached a withdrawable wallet.
Reconcile the route’s gross fare, service fee and net earnings.
Web app · sample data · Captured 2026-09-25
- 1Gross, fee and net are different amounts.
- 2Read the settlement note and per-rider line.
- 3Return home after completion.
Return home and keep the records
Use Return to driver home after the route is complete. Consult History for journeys and Wallet for financial entries when reconciling the day.
How you know it worked
Every passenger’s trip is completed and your route summary can be reconciled with the underlying records.
A useful next step
If something goes wrong
The session still shows a passenger after drop-off
Check connectivity and the last confirmation result. Do not start a duplicate journey to clear the screen.
Cash and wallet totals are mixed
Separate cash collected from wallet-settled income. A summary can report the journey economics without proving a bank payout.
The app does not return home
Record the remaining stop/status and contact support. Avoid clearing session data while completion is uncertain.