A diaspora map is not there to be looked at, it is there to support decisions. It answers four questions a directory answers badly: where to open a local chapter, where the member base is wrong rather than the diaspora absent, who lives close enough to whom to help out, and which city should host the next event. For all of that, the city is almost always enough: a precise address adds risk without adding a decision. The map does not create engagement by itself, and an empty map discourages more than it motivates. The map module is available from the Pro plan onwards, at 149 € per month; the Starter plan, at 69 €, includes the directory but not the map. If your community fits into two cities, a list filtered by country does the same job.
The map is not an illustration, it is a decision tool
The request almost always comes in the same words: "we would like a map with all our members". The next question, rarely asked, is the one that matters: which decision will that map change? Until it has an answer, the map stays a piece of decoration on a home page, updated for a few months and then abandoned.
The right way to frame the subject is the other way round. A diaspora is a community defined by its dispersal: its members do not run into each other, share neither city nor time zone, and the board reasons about a geography it imagines rather than sees. The map is the tool that makes that geography visible, and therefore debatable. That is not the same thing as a feature that looks good, and there is a simple test for it: if the map disappeared tomorrow, which decision would become impossible to make?
Four decisions pass that test. They make up the rest of this article. Everything else usually credited to a map is a matter of comfort, which is no reason to do without it, but no reason either to make it a platform selection criterion.
Deciding where to open a local chapter
This is the most structuring use. A diaspora association that grows eventually faces the question of territory: do we need a chapter in Montreal, in Brussels, in Abidjan? The answer is usually taken on a hunch, or because one motivated member came forward in a given city. The hunch is a poor guide, because it follows the visibility of members rather than their number: three people who are active in discussions weigh more in the board's perception than forty silent members living somewhere else.
The map puts those two back in the right order. It shows the real concentrations, including the ones nobody had seen, and it also shows their shape: a hundred members spread across a whole region are not run like the same hundred gathered in a single metropolitan area. In the first case, a chapter will struggle to bring anyone together without travel; in the second, the first coffee is enough to launch the relay.
The map obviously does not decide on its own. A local chapter needs someone to run it, a written mandate and a minimum of resources, and no concentration of members replaces those three conditions. But it turns a conversation of opinions into a conversation of facts, which is exactly what is missing when a scattered community organizes itself online and has to arbitrate between several territories without being able to visit them.
Seeing where the base is wrong, not only where members are
The least expected use is also the most profitable. A map displays presence, but what an experienced manager reads in it is absence. A country where the community knows it has dozens of compatriots and which shows up empty on the map says nothing about the diaspora: it says the base is incomplete there.
The distinction is decisive because the two situations call for opposite responses. A genuinely empty area asks for nothing. An area left empty by a failure to register members asks for a targeted campaign, often a local relay, sometimes simply a sign-up form published in the right language. Without a map, those gaps stay invisible, since a directory only ever shows what it already contains.
This is why the map reads as a data quality dashboard, and not only as a view of the members. It provides next quarter's to-do list: the areas to cover, and the profiles with no location. It extends directly the work described in how to map out your diaspora, of which it is the control loop: the census fills the base, the map shows where it failed.
Making nearby mutual help possible
A diaspora constantly produces the same need: someone arrives in a city where they know nobody. A student landing for the start of term, an employee relocated, a family settling in. What that person is looking for is not the complete directory of the community, it is the answer to a narrow question: who is here, now.
The directory answers that question badly. It is organized by name, by profession, sometimes by graduating class, and you already have to know who you are looking for to use it. The map answers exactly the right question, because it is indexed on the only criterion that matters at that precise moment: proximity. That is also what makes it, for a new member, the simplest reason to complete their own profile: they immediately see what the community gives back.
One point of product vocabulary, to avoid a frequent confusion: the map connects people, it does not organize mutual help. Keeping housing listings, availabilities and reviews belongs to a separate module, available on Premium and Business only. The map is there to tell you who to turn to, which remains the first obstacle. Communities that have formalized their mutual help, for instance with a solidarity fund, rely in any case on that same knowledge of the ground to know who can help whom.
Choosing the city, and the hour, of an event
A diaspora event runs into two constraints, and the map sheds light on both. The first is the place: a physical gathering is held where the members are, not where the board lives. Seeing the real distribution before settling on a city avoids the classic mistake of the association that organizes three years in a row in the capital where its president sits, while half of its members live elsewhere.
The second constraint is the hour, and it does not only concern online meetings. The map is the tool that makes time zones concrete: before a slot is even chosen, it shows how many members would be in the middle of the night if the meeting followed the board's own clock. We go through the possible trade-offs in running a diaspora event across several time zones; the map does not settle them, it makes the cost of each option visible.
The events and registrations module, like the map, starts at the Pro plan. The two complement each other in the same movement: the map indicates where to put the effort, the events module turns that indication into a dated event with registered attendees.
How precise should the location be?
This is the technical decision with the heaviest consequences, and it is taken before anything is collected. Three levels are possible: the country, the city, the precise position. The natural temptation is to collect the finest one, just in case. That is almost always a mistake.
Look again at the four uses above: deciding on a chapter, spotting a gap in the base, connecting two members who live close to each other, choosing an event city. None of them needs anything better than the city. A precise position adds no decision and adds three problems: it is harder to obtain, it ages faster, and it exposes the home address of members who have not always measured what they were publishing.
That last point deserves particular care in a diaspora, where some members have good reasons not to display where they live. The prudent rule is simple: the city by default, the member in control of what is displayed and able to leave the map without leaving the association, and visibility restricted to logged-in members rather than open to the public. Where someone lives is personal data, and processing it assumes a stated purpose and clear information: that is the subject of the GDPR guide for a diaspora platform, to be read before opening the map, not after.
A technical point comes on top of it, often discovered too late: city names are written differently depending on the language and the alphabet of the members. A map fed by a free text field ends up with the same city under four spellings, hence four dots. It is a variant of the problem described in the seven traps of a diaspora platform, and it is solved by offering a standardized list of places rather than a free text field.
What the map will not do for you
This has to be said plainly, because the disappointment is common. A map does not create engagement. It makes visible a community that already exists, and it makes just as visible a community that does not exist yet. We put forward no figure here on the effect of geolocation on participation, because we have no verified measurement to publish.
Three failures come back regularly. The first is the map launched too early, almost empty, which gives the member proof that the community is inactive. It is better to seed it quietly and open it once it shows enough people for a member to find someone. The second is the frozen map: a location entered at sign-up and never updated becomes wrong at the first move, and a diaspora moves a great deal. The field must stay editable by the member, and update reminders are part of ordinary community management.
The third is the map with no way out: it shows that twelve members live in the same city, and nothing makes it possible to bring them together. A map is only worth having when it is backed by means to act, a message, a local group, an event. Without them it informs without producing anything, and information alone does not hold a community together, as the comparison between a WhatsApp group and a platform shows.
When a filterable list remains the right choice
There are situations where the map adds nothing, and it is better said before the subscription than after. At least three cases.
- The community fits into one or two cities. A diaspora association concentrated in a single metropolitan area already knows where its members are. The map will show one large dot and confirm what everybody knows. A directory filtered by district would be more useful, and it does not exist.
- The base has no reliable location yet. If half the profiles have no city, the map will not show the community, it will show how far the data entry has got. The correct order is to run the census first and map afterwards.
- The real need is a filter, not a view. Many map requests resolve into a single sentence: "I want the list of our members in Canada". That is a directory search, present in every plan, including Starter at 69 € per month. Subscribing to Pro for a map when a filter was enough is a bad purchase, and we would rather say so.
The map becomes useful the moment the dispersal is real and goes beyond what the board keeps in its head. It is precisely that threshold, and not a number of members, that justifies moving to the Pro plan, at 149 € per month, where the map module is available.
Putting the map into service in six steps
- Choose the level of detail before collecting. Country, city or precise position: decide once, for every member. Going back means revisiting each profile.
- Add the field to the profile, editable by the member. The location belongs to the member, it changes, and nobody else will know that it has changed.
- Write the visibility rule and announce it. Who sees the map, at what level of detail, how you opt out. One line on an information page, not a legal paragraph.
- Seed with what you have, then ask. Import the locations you already know, then run a short campaign to the others, saying what it is for rather than demanding an update.
- Open the map on an action. Publish it with a reason to go there: finding a member nearby, spotting who is attending an event, finding the closest local chapter.
- Review it every quarter. Empty areas, profiles without a location, duplicate cities: those three lists are next quarter's work plan, and that is what separates a living map from an archive.
The map as part of a case file
One last use, rarer but valuable: the map is the document that answers fastest the first question an institutional counterpart asks. A local authority, a consulate or a partner invariably ask how many members the community has and where they are. A screenshot of a map proves nothing by itself, but it makes readable in one screen what a table takes a page to say.
The same caution applies as for any outgoing document: the map shows the state of your base, not the real population of the diaspora, and that has to be written down. It is the rule we set out in producing a credible report for a consulate or a local authority. A map presented for what it is, the picture of an ongoing census, strengthens the credibility of the association; presented as a head count, it damages it durably.
In short
Which plan includes the map?
The map module is available from the Pro plan onwards, at 149 € per month. The Starter plan, at 69 € per month, includes the member directory but not the map.
Do you need members' exact addresses to build a map?
No. The city, and sometimes the country alone, covers almost every diaspora use case: deciding on a chapter, choosing an event city, connecting two members who live close to each other. A precise address adds risk without adding a decision.
What should you do if the map is almost empty at launch?
Do not publish it to everyone yet. Seed it by importing the locations you already know, complete it with a short campaign to members, and open it once it shows enough people for a member to find someone.
Does the map replace the directory?
No, it opens the same data through another door. The directory answers who, the map answers where. A member looking for a profession uses the directory; a member who has just arrived in a city uses the map.
Method and sources. This is a method article: it relies on no external source and puts forward no market figure. What it describes comes from field observation with diaspora associations, not from measurement. We deliberately publish no figure on the effect of geolocation on participation, for lack of a verifiable measurement to quote. The only figures mentioned are Terrilink's public prices, and module availability follows the plan matrix: the map module is included from Pro onwards, the member directory is in every plan, housing and mutual help listings belong to Premium and Business. Handling where a member lives is a personal data question that calls for your own analysis: see the GDPR guide for a diaspora platform.