Why we’re starting with a district.

Start with journeys, then draw the area.

Imagine a hotel, a restaurant, and a gathering place on the same property. Connecting all three sounds straightforward. But a nearby destination may sit beyond a road the service cannot use, or have an entrance where a pod cannot stop. Distance alone does not tell us whether a journey belongs in the service.

A useful district boundary begins with the trips people want to make and the routes and stops that could support them. For a first Loope pilot, we would work with the property team to identify those journeys before deciding what the service area should include.

A smaller area brings a real tradeoff.

Fewer stops can make pickup guidance easier to explain and daily operations easier to understand. The team has a more limited set of routes to evaluate and places to support. That gives development work a clear focus.

It also means saying no to some useful trips. A popular destination just outside the boundary may remain outside it. Adding that destination could introduce a crossing, a different operating responsibility, or a longer return journey that changes pod availability elsewhere. A larger map is not automatically a more useful service.

The boundary should be understandable to a rider. Someone choosing a destination needs to know whether it is served before making a request. A nearby place that is outside the area should not become a surprise at pickup.

Some properties may need a different beginning.

A property is a weaker first-pilot candidate if its useful journeys depend on routes we cannot support, if suitable pickup locations cannot be agreed, or if daily operating responsibilities are unclear. A district with destinations spread too far apart may also ask more of the first service than it can reasonably demonstrate.

These are discovery questions, not a published eligibility checklist. They need to be examined with the people responsible for the property and against the pods and operating model being developed.

The question is whether a defined set of journeys would be useful enough on its own. If the service only makes sense after adding several uncertain connections, we should reconsider where to begin.