If you live in a gated community, you’ve been there: You request a ride from your apartment complex, expect your driver to come to you as usual, and then — your driver’s car icon just stops right at the front gate. You watch helplessly as the ETA ticks up. A chat message comes in: “Hey, how do I get in?” You scramble to remember the gate code. They try it. It doesn’t work. You end up meeting them awkwardly on the sidewalk outside while your coffee gets cold — a pickup journey frustrating for both you and your driver.
It turns out you’re not alone: Gated community pickups can make up 25–30% of Lyft rides in selected markets. For a long time, our app offered no special guidance in these situations. Riders would drop their pin inside the gates (fair enough — that’s where they are), while drivers would pull up to a locked entrance with no way in, leaving both parties to sort things out over chat. The result was predictable: more cancellations, longer waits, and a lot of unnecessary stress for our customers.
The Lyft Mapping team decided it was time to fix this properly — not with a band-aid, but a new end-to-end experience. Here’s how we did it.
What Was Actually Going Wrong?
We looked through gated ride examples, zoomed into our metrics data, and found two root causes behind most of the friction.
The first was an inflexible selection of pickup spots. Our app would suggest pickup spots near a rider’s location — which, for riders inside a gated community, often means inside the gate. But our data told a different story: many riders actually preferred meeting their driver right outside the gate, knowing their driver couldn’t access the property. The app wasn’t giving them that option clearly.
The second was a communication black hole. Even riders who knew how to get their driver through the gate had no good way to pass along access instructions in advance. Instead, they’d wait until the driver was already idling at the entrance before firing off a text with the gate code, setting off a frantic last-minute back-and-forth.
Two problems, two different moments in the ride flow. This signaled that we needed to fix things both before and after a ride was requested.
Only on Lyft Maps
Lyft’s Mapping team sits in a unique position to solve this problem, with workstreams across map data, pickup spot recommendations, routing, and the rider and driver app experience.
This one needed all of the pieces to complete the map (pun intended).
Piece 1: Drawing Gated Communities on the Map
Before anything else, we needed a map that actually knew about gated communities — where they are, where their entrances are, and how many gates they have.
Our Map Data team built a gate area shape generation algorithm to do exactly this. Gated communities come in all shapes and sizes: some are small apartment complexes with one entrance, and some are large developments with multiple gates and even their own internal road networks. The algorithm had to handle all of it reliably and provided the foundation accurate enough to build our new pickup experience for riders within these gated communities.
How does the app even know I’m inside a gated community? When you open the app, we cross-reference your GPS location against the gate area shapes we generated. If you’re within a known gated community boundary, the app quietly switches into “gates mode” and adjusts what you see as your pickup spot selection process. No extra steps on your end.
Is my community in the system? We’ve built our gate coverage from sources like OpenStreetMap and driver feedback, and we’re continuously monitoring for gaps and adding new communities during every map update — so coverage grows over time without you having to do a thing. That said, no map is perfect, and local knowledge is invaluable. If you don’t see the new experience or encounter issues at your gate, reaching out to Lyft support helps us prioritize the communities that need attention most.
Piece 2: Giving Riders a Smarter Selection of Choices
Now, when you open the Lyft app from inside a gated community, you’ll see pickup spots at your complex entrances (labeled “I’ll walk outside the gate”), right alongside the usual spots near your current location (labeled “Pick me up inside gate”). You can decide freely whether you prefer to wait locally (maybe it’s raining outside) or want to meet your driver outside the gate (get some steps in, right?).
The team looked at historical ride patterns to surface spots that real riders have actually used near gates — so we’re not just pointing you toward the gate in theory, we’re pointing you to where riders in your community actually go.
We also designed the new UI to feel familiar, borrowing patterns from our existing Venues pickup flow so our riders wouldn’t have to learn something from scratch.
Before shipping, we ran a controlled experiment to make sure we weren’t accidentally making things worse — specifically, that the new flow wouldn’t add enough friction to make riders bail on requesting a ride altogether. Good news: no meaningful drop-off. Even better news: we saw actual pickups happening at the spots that riders chose initially, meaning that they no longer have to walk around to find their drivers.
Piece 3: Routing Drivers to the Right Gate
Recommending gate-aware pickup spots to a rider is only half the job. The driver also needs to be routed there correctly.
Normally, a pickup route is simple — get the driver from point A (their location) to point B (the rider’s pickup spot). For gated communities, our Routing team introduced a new “detour”: the gate itself becomes an intermediate stop, an arbitrary, “invisible” stop that the driver passes through on the way to the rider. We use our map data to direct drivers to the right gate, accounting for road direction and the most logical approach path.
Get winnieyan’s stories in your inbox
Join Medium for free to get updates from this writer.
This seemingly small routing tweak creates something valuable: a precise moment in the driver’s journey where we can surface gate instructions at exactly the right time.
Pieces 4: Actually Getting the Driver Through the Gate
Now that we get drivers to the gate, we still need to get them through the gate to meet those who asked to be picked up inside, and we really can’t let our customers resort to back-and-forth communications.
Our Map Experience team brought this to life: After a rider is matched with their driver, they’re prompted to share access information. Rather than presenting a blank text field — which puts all the pressure on the rider to know exactly what to say, right after they’ve just requested a ride — our Design team drew inspiration from the intercom panels riders use every day: a familiar numpad for gate codes, and a short list of plain-language options for everything else. The goal was to make instruction sharing effortless.
We leveraged historical data from gate instructions that riders had previously shared to identify the most common access scenarios. Our Content team worked to make each option feel conversational and specific enough to be useful, without being so wordy that riders would skip past them. The free-text fallback is still there for the edge cases, but in practice, most riders find what they need in the list.
You might be thinking: I usually text my driver the gate code — what’s actually different here? The difference is timing and reliability. When you text, you’re reacting: the driver might be busy driving, or is already at the gate, already stopped, already waiting.
We also paid special attention to how we should show the shared instructions to drivers. They are likely navigating with eyes on the road — so a paragraph of gate instructions on their screen at the wrong moment is unhelpful and more importantly, unsafe. We designed the gate instructions to surface as a small, but obvious banner in the navigation screen at precisely the moment the driver approaches the gates, timed to the routing waypoint we added in Piece 3. The information is brief and scannable — just enough to get through the gate. No extra steps or unnecessary calls or texts.
We also know that sharing a gate code feels more sensitive than sharing a pickup pin — it’s access to where you live, and your privacy is important to us. So we built in privacy controls that let you view or delete your instructions at any time after sharing. Gate codes are never stored between trips, and only your matched driver ever sees them on their navigation screen on their way to pick you up. To further ensure your gate codes stay protected, we implemented safeguards to prevent screenshots.
Does It Actually Work?
We asked riders directly through our optional feedback survey. About 95% responded positively — and their comments said it better than any metric could:
“Driver successfully picked me up OUTSIDE the gate, as requested.”
“Picked me up where I asked.”
We also see data reflecting our goals: riders and drivers are not giving up on a ride just because there’s a gate in the way. Drivers are not looping around a community entrance trying to figure out how to get in. Riders are not wandering the sidewalk looking for a car that’s stuck on the other side of a barrier. Phones are not fired off with chats and calls because our riders and drivers can’t find each other. Those are the moments we were trying to eliminate — and the numbers reflect it.
We observe lower cancellation rates from both riders and drivers, when riders share gate instructions.
In addition, riders are walking less to their final pickup locations from their requested pins, waiting less, and don’t need to reach out to their drivers as much. We also see drivers needing to change course in the final stretch less. Each of these represents a ride that went smoothly instead of sideways.
Now, that same ride from your gated community looks a little different: your driver’s icon moves smoothly past the gate with the instruction you share with a simple tap, and you get into your ride stress-free, with your coffee warm. The results gave us confidence that the approach works — and got us thinking about where else we could take it.
More Gates, and The Bigger Picture: Bringing the Real World to the Map
For gated communities specifically, we’re just getting started. We want to provide riders with the option to save non-sensitive gate instructions for future trips, so riders who regularly get picked up from the same community don’t have to re-enter the same information every time. Your gate intercom instruction isn’t going to change — we shouldn’t make you tell us every time. We will also work on smarter gate selection for communities with multiple entrances, choosing the best gate based on where both you and your driver are at that moment, not just the nearest one on the map.
But the more we worked on this project, the more we realized gates are just one example of a much bigger problem. The real world is full of physical constraints that affect where a driver can go and where a rider can safely and conveniently be picked up — and we see a big opportunity of leveraging our Mapping stack to improve customers’ pickup experiences across many of these situations.
Consider road closures. A street gets blocked for construction, a parade, or a marathon, and suddenly the route our app plotted doesn’t work anymore. The driver gets rerouted at the last second, the pickup pin is now on the wrong side of a barrier, and rider and driver end up circling each other trying to figure out where to actually meet.
Or consider unsafe road segments — a pickup spot that looks perfectly fine on a map but sits on a high-speed tunnel exit way with an accident-prone history. The rider waits on the curb, and the driver pulls over in a spot, attempting to avoid moving traffic. Neither of them had any idea there was a safer option just half a block away.
What the gated community project gave us is a repeatable playbook for all of these situations: encode the real-world constraint into the map, surface that context in pickup spot recommendations, thread it through routing, and deliver the right information at the right moment and place in the app. Whether the obstacle is a gate, a closed road, or an unsafe stretch of curb, the same approach applies.
Gated communities were a specific problem. But the approach behind solving them isn’t specific at all. Every time the real world gets in the way of a safe and convenient pickup, there’s an opportunity to make the map smarter — and the ride a little less stressful for everyone involved.
Lyft is hiring! If you’re passionate about maps, visit Lyft Careers to see our openings.
Source: eng.lyft.com
