Trip tracking and completion

Trip Coordinator uses the ride request to follow pickup progress from Planned through En Route and Arrived. Completing the request records its operating outcome. The trip event history adds the time, location and source of individual observations, including pickup arrival, delay and trip completion. A reported event gives the reviewer something specific to investigate.

Completion evidence connects the booking to the ride request and records when the ride completed. Rider name, signature reference and notes help Operations Reviewer compare the claimed completion with the journey that was assigned. Captured evidence waits for a completeness and consistency check. Verified and Disputed outcomes communicate the result of that examination to colleagues handling follow-up.

• Record actual progress. Trip Coordinator updates the ride request as pickup and travel occur. Keep Missed available for an evidenced no-show so it does not appear as a completed ride.
• Keep event context. Record the event type, observed time and source. A Dispatcher observation and a Driver App observation may need different follow-up when their details disagree.
• Reconcile completion. Operations Reviewer checks that the captured evidence is complete and agrees with the booking and ride request. Keep incomplete evidence Captured; mark contradictions Disputed. Record an escalation and a Failed receipt for either unresolved outcome.

Decide which observations your staff enter directly and which arrive through a connected driver or telematics service. Configure those feeds explicitly, including how they identify the booking and interpret event time. Agree how the team handles delayed messages and corrections before using event order to explain a journey.

Set the evidence needed for completion review. Some operations use a signature reference; others rely on a ride voucher or documented dispatch confirmation. Decide where those documents are retained and who may read rider details. Agree the completion handoff at which Dispatcher marks the performed booking Executed and the resource Completed, then rehearse the separate evidence review.

A rider is dropped off, but a delayed arrival message reaches the desk after completion has been captured. Trip Coordinator checks the observed times and the source of each event before changing the ride request. The completion record should still refer to the actual booking and request, with notes explaining any discrepancy.

Operations Reviewer compares the completion time, rider and supporting evidence. If the completion belongs to another journey, mark the evidence Disputed and investigate the reference. If required evidence is missing, keep it Captured and record the escalation and Failed receipt. Verify only a complete, consistent result and retain the receipt for that action. Finance Operator can then follow the same booking when examining charges, without treating the ride’s completion as payment confirmation.

• Trip completion review — Captured and Disputed evidence requiring examination against the booking and request.
• Ride request board — Pickup progress and outcomes across the requests being coordinated.
• Trip event review — Reported observations with their source, time and location for follow-up.

Use trip to completion for the operating handoff. Follow cancellation and correction when a completed ride needs an authorized correction.