How shelters plan street outreach routes with the services along the way
Turn a list of regular outreach spots into an ordered route for each team, with the nearest clinic, pharmacy and food point beside every stop and the night's weather.
Part of the guide Workflow automation
A shelter plans a good outreach round by fixing the order of its stops before the team leaves, and by knowing, at each stop, where the nearest help is if someone needs it tonight. Keep your regular outreach spots in a table, let the Route planner block put them in visiting order from the shelter, and let Nearby places add the nearest clinic, pharmacy and food point to every stop. The team gets one sheet with the route, a directions link and the services along the way.
This is for coordinators at shelters, drop-in centres, soup runs and street medicine teams who send volunteers or staff out on foot or by van in the evening. It covers what to put in the stop list (and what never to put in it), how the route and the services are worked out, a made-up evening in Montreal, the mistakes that waste a round, and the AI employee that prepares the plan each afternoon.
What a round needs before it starts
An outreach round is not a delivery round. Nobody is waiting at a fixed address, people move, and the useful part of a visit is often a referral: a bed, a clinic, a hot meal, a pharmacy that is still open. So the plan needs three things the team can read on a phone in the cold:
- The order of the stops, so the van does not cross the city twice and the walking team ends near the shelter.
- The nearest services to each stop, with their distance, so a volunteer can say "the clinic is 400 m that way" instead of "somewhere downtown".
- What could change the night: heavy rain or a hard frost that calls for an extra round, and a road closure on the way out.
Building the stop list
Start with a table in My data: one row per regular spot, with a short name your team recognises, an address or a pin, and a note such as "bring blankets" or "two teams only". A rough list is enough to begin. The table can grow as the team learns the patch, and anyone with access can add a row from a phone.
If you have several teams, add a column that says which team covers the spot. The Route planner can then make one route for each team from that field, instead of sharing the stops out by itself. That keeps a volunteer on the patch where people already know their face, which matters more in outreach than saving a few minutes of walking.
How the route and the services are worked out
- The flow reads the stop list. Each spot becomes an item with its position.
- Nearby places looks around each stop, within a distance you choose (300 m on foot is a sensible start), for the kinds of service you pick: shelters, clinics, pharmacies, food banks and soup kitchens, or whatever types fit your city. Set to pass on each stop with counts, it adds the nearest one and how far it is, without turning each service into a stop.
- A second Nearby places block can do the same for another kind of service, so every stop carries its nearest clinic and its nearest pharmacy side by side.
- Route planner orders the stops from the shelter, on foot or by car, and can bring the route back to where it started. Each stop gets its place in the round, the minutes from the stop before and a directions link.
- Weather forecast adds tonight's rain and lowest temperature for the city, so the plan says when it is a night for an extra round.
- Email or WhatsApp sends the team lead the round, stop by stop.
Two honest limits. The route times are travel times only: the minutes you spend talking at a stop are not added, and on a busy night that is most of the round. And the places database says whether a service was open when it was last checked, not its hours tonight. Phone the night shelter before you promise someone a bed.
A worked example (made up)
Say a drop-in centre in Montreal runs a van round three evenings a week with eleven regular spots around the downtown stations and the old port. The coordinator keeps the spots in a table, each with a note. At 16:00 the flow reads them, finds the nearest pharmacy and the nearest clinic within 500 m of each, and orders the round from the centre and back.
The email that lands is short: "Round for tonight, 11 stops, about 70 minutes of driving. Forecast low of minus 9 and strong wind after 22:00: consider the extra late round." Then each stop, in order, with its directions link, its note and its two nearest services. The van crew reads it on the way out. None of these figures are real; they show the shape of what arrives.
Mistakes that waste a round
- Treating the order as fixed. The planner gives the shortest sensible order. If a spot only matters after the soup kitchen closes, move it by hand or split the night into two rounds.
- Searching too wide. A clinic 3 km away is no help to someone on foot at midnight. Keep the distance short for walking teams.
- Adding people to the data. Even a nickname in a stop note can identify someone. Keep stops about places.
- Forgetting the weather. The nights that need an extra round are the ones nobody planned for. Let the forecast decide when to raise it.
- Never updating the list. Spots go quiet and new ones appear. Review the table every month with the people who walk it.
Doing it with an AI employee
In xMap Flows the whole plan is one AI employee that works each afternoon on outreach days. Its blocks, in order:
- Schedule: Monday, Wednesday and Friday at 16:00, in the city's time zone.
- My data: the table of outreach spots.
- Nearby places: the nearest clinic within 500 m of each spot, passed on as counts.
- Nearby places again: the nearest pharmacy and food point.
- Route planner: from the centre and back, one route per team when the table has a team column.
- Weather forecast: tonight's rain and lowest temperature.
- xMap LLM: one short note for the whole list, written for the team lead, that flags a cold or wet night.
- Email: the round to the coordinator and the team lead, with a map.
What lands in the inbox is the evening's plan: the note at the top, then each stop in order with its directions link and its nearest services. If a road on the way out is closed, add Traffic incidents around the stops and the note will say so. The template Routes for the weekly surplus food pickup is the closest starting point; change its places to your spots in one sentence.
For the conversations after the round, a help finder chat lets a volunteer type "nearest pharmacy to the bus station" and get an answer from the same places database. More on routes in planning a day of visits.
Questions
Can the route planner work for a team on foot?
Yes. Pick walking, and keep the search distance for services short. The minutes it gives are walking minutes between stops; time spent at each stop is not added.
Does it know which shelters have beds tonight?
No. The places database knows where services are and whether they were open when last checked, not their beds or hours tonight. Call before you refer someone.
Can two teams get different routes?
Yes. Give each spot a team column in the table and choose one route for each team, or let the planner share the stops between a number of teams by area.
Should we record the people we meet?
Not in a flow. Keep stops about places and keep case notes in your own case system, under your consent and safeguarding rules.