A pickup flow that survives the real world

Find entrances, match riders and drivers, route continuously, and resolve pickup ambiguity.

Business outcomeShorter pickup times with fewer calls, cancellations, and unsafe rendezvous points.

The operating situation

At a busy railway station, a rider searches for the station name but the legal vehicle pickup point is 420 metres away. The marketplace must suggest a safe entrance, match a driver by road ETA rather than straight-line distance, guide both parties, and preserve a reviewable record if either disputes arrival.

RiderDriverMarketplace dispatcherSafety operatorCustomer support

Keep authority explicit across the stack

01Trip marketplaceOwns request, fare, rider/driver identities, eligibility, assignment, cancellation, safety state, and settlement.
02Pickup intentAutosuggest and map confirmation resolve human text and viewport context to a precise Mappls Pin with entrance/landmark explanation.
03ETA matchingA bounded matrix ranks eligible fresh driver positions; marketplace policy adds workload, vehicle, safety, and deterministic tie-breaks.
04Approach journeyRoute revisions and event-time vehicle observations derive progress, rerouting, pickup-zone entry, and freshness.
05Shared rendezvous experienceRider and driver receive the same stable pickup identity with role-appropriate directions and a support-visible discrepancy trail.

From intent to reconciled outcome

1
Stage 1

Bias search to the rider viewport

Capture intent and source evidence without inventing a more precise state than the inputs support.

2
Stage 2

Confirm a precise pickup pin and landmark

Advance through an idempotent boundary, preserve stable Mappls identity, and expose freshness and ownership.

3
Stage 3

Match with network-aware ETA

Advance through an idempotent boundary, preserve stable Mappls identity, and expose freshness and ownership.

4
Stage 4

Track approach and reroute

Advance through an idempotent boundary, preserve stable Mappls identity, and expose freshness and ownership.

5
Stage 5

Detect arrival and close the trip

Reconcile the terminal result to every authoritative system and retain attributable evidence.

Records that must survive restarts and retries

Ride request ↔ accepted pickup/drop Mappls Pins and selection revisions

Version, authorize, retain, observe, and reconcile this relationship explicitly; do not recover it later from display text or logs.

Driver candidate ↔ capability, availability, position freshness, matrix ETA

Version, authorize, retain, observe, and reconcile this relationship explicitly; do not recover it later from display text or logs.

Assignment ↔ aggregate version, chosen explanation, provider route revision

Version, authorize, retain, observe, and reconcile this relationship explicitly; do not recover it later from display text or logs.

Arrival evidence ↔ event/receipt time, accuracy, zone policy, rider/driver acknowledgement

Version, authorize, retain, observe, and reconcile this relationship explicitly; do not recover it later from display text or logs.

Design recovery before rollout

Search resolves the building centre

Present signed pickup zones/entrances as candidates and require explicit rider confirmation before matching.

Driver location is stale

Exclude it from ETA ranking, show marketplace capacity honestly, and request fresh evidence rather than extrapolating indefinitely.

Rider and driver disagree on arrival

Retain both event streams, accuracy, call/support actions, and apply a versioned human-review policy.

Products and evidence

Earn the right to automate

1
Rollout gate

Instrument current pickup corrections without changing dispatch

2
Rollout gate

Introduce confirmed Mappls Pin pickup at a small set of complex venues

3
Rollout gate

Shadow network-ETA ranking and measure pickup/cancellation outcomes

4
Rollout gate

Enable approach progress and safety operations for one city

5
Rollout gate

Expand only after bias, privacy, driver-experience, and incident reviews

Measure the outcome

Pickup ETACancellation rateDriver idle distancePickup support contacts

Tutorials and downloadable applications

Starter · verified app

Store Locator

Discover eligible branches, compare distance and ETA, preserve Mappls Pin identity, and hand off safely to navigation.

Advanced · verified app

Care Transfer Desk

Confirm the correct receiving entrance, assign eligible transport, preserve courier custody, review condition exceptions, and reconcile receiver acceptance without retaining patient or clinical data.