How Shareide Matches You With a Driver on Your Exact Route

Posting a route only helps if the matching behind it is actually accurate. A driver whose road doesn't really pass near a rider's pickup shouldn't see that request at all - and Shareide's matching is built to check the real road, not just a straight line on a map.

Why a straight line isn't good enough

Two points can look close together on a map while sitting on completely different roads - separated by a river, a highway, or a one-way system that makes them practically unconnected. Matching purely on straight-line distance would put a rider in front of a driver who's never actually going to pass anywhere near them.

How Shareide checks the actual road

When a driver posts a route, the app maps their real road path rather than just their start and end point. A rider's pickup and drop-off are then checked against that actual path - not a straight segment between two pins - so a match means the driver genuinely passes close to both ends of the trip, heading the same direction.

Same-direction matching

Beyond proximity to the road itself, matching also checks that the rider is heading the same way the driver is already travelling - so you're not offered a ride from someone who'd have to double back or drive the corridor backwards to reach your drop-off.

What this means for posting your own route

If you drive or ride the same corridor daily, posting it (covered in the per-seat ride sharing guide) means the app checks your real road against every new request - not just anyone near a straight line between your two endpoints.

Frequently asked questions

Why do I sometimes see rides that don't feel like they're on my road?

Matching is checked against your posted route's real path; if something seems off, re-posting your route ensures the app has your current, accurate road on file.

Does this apply to monthly and scheduled rides too?

Yes, the same road-aware matching applies to monthly commute matching and scheduled ride requests, not just instant rides.

What if I haven't posted a route at all?

Without a posted route, matching falls back to general proximity and demand rather than a specific corridor - you'll still see nearby requests, just not the route-specific matching a posted route enables.