How do you keep a shared site registry accurate when many teams add to it?
Control who can create sites, review new ones before they join the master list, and merge the duplicates that appear anyway. Site privacy, site approval and the deduplicator are the three tools that keep one registry usable across many teams.
A site registry degrades in a predictable way: two enumerators visit the same borehole, record it slightly differently, and the district now has two boreholes. Multiplied across a country, the inventory stops being a count of anything. The fix is procedural as much as technical, deciding who may add sites and who checks them, and the platform supports both halves.
How to do it
Set site privacy so it is clear which sites are public and which belong to your organisation.
Use organisations to control who can create and edit sites, rather than leaving it open to everyone.
Add a site question to your surveys so enumerators pick an existing site instead of creating a new one.
Turn on site approval so new sites are reviewed before they enter the master registry.
Run the deduplicator regularly to find and merge sites that are the same place recorded twice.
Import and export sites in bulk when you need to correct a large batch at once.