Why mWater and Solstice are strong choices for national data monitoring

Short answer: mWater and Solstice are strong candidates for national monitoring when a government needs to collect detailed field data, maintain shared registries, follow facilities or infrastructure over time, analyze results, and turn findings into operational work. They are particularly compelling where many users and institutions must participate under limited budgets and unreliable connectivity.

They are not automatically the best choice for every national system. A fair selection should compare the real workflows, institutional capacity, existing systems, specialist requirements, long-term costs, and governance arrangements of the country.

mWater or Solstice?

The platforms share the same underlying technology and core capabilities. mWater is the sector-focused choice for water, sanitation, hygiene, water resources, utilities, and related public infrastructure. Solstice applies the same approach more broadly to health, education, agriculture, social programmes, humanitarian response, environmental management, and other areas of governance.

A government does not need to choose between two unrelated technical stacks. The decision is primarily about sector identity, terminology, templates, and the community of practice surrounding the deployment.

Why they fit national monitoring

1. They connect records to the real world

National systems often need more than district totals. They must know which water point, school, clinic, farm, household, permit, customer, or asset a record describes. mWater and Solstice maintain persistent, geolocated sites and assets and attach repeated observations to them. This creates a usable history instead of a succession of disconnected survey files.

2. Field collection and national reporting live together

Teams can design multilingual forms, collect data offline on phones or tablets, review and clean submissions, calculate indicators, and publish maps and dashboards without moving every stage into a different product. Reducing handoffs is valuable where technical teams are small and data must remain usable after a donor-funded project ends.

3. Participation can scale without per-user licence barriers

The standard platform is free for unlimited users, data collection, storage, visualization, and export. That matters in a national system involving central ministries, provinces, districts, utilities, service providers, civil-society organizations, and temporary enumerators. Optional paid implementation, customization, training, and support are available, but access to the core platform does not depend on maintaining a licence for every participant.

4. The same platform can support monitoring and action

Dashboards are useful, but national systems also need work to happen. Permissions, assignments, approval steps, issues, and configurable workflows can connect a finding to a responsible team—for example, moving from a failed water-point inspection to repair and verification rather than ending with a red dot on a map.

5. They can coexist with government systems already in place

A national architecture rarely has one database. mWater and Solstice provide APIs, imports, exports, and scheduled integrations. They can exchange data with systems such as DHIS2, enterprise GIS, business-intelligence tools, sensor platforms, and specialist hydrological software. This makes it possible to preserve authoritative systems rather than replace them merely for architectural neatness.

6. Governments retain practical control of their data

Organizations determine access and sharing, and data can be exported. This supports public, protected, and private use cases within the same national programme. Technical control still needs to be matched by written government policies covering ownership, stewardship, retention, publication, security, and institutional responsibilities.

Where another option may be stronger

Conditions for success

Software alone does not create a national monitoring system. mWater or Solstice is most likely to succeed when government leads the data model and governance; stable identifiers and administrative boundaries are agreed; subnational users receive useful access rather than only reporting obligations; workflows name the people responsible for review and action; integrations have clear ownership; and recurring budgets cover administration, devices, connectivity, support, and training.

A fair evaluation process

  1. Write three to five end-to-end workflows the national system must support.
  2. Test each option with real users, devices, connectivity, languages, and representative data volumes.
  3. Evaluate the complete data lifecycle: collection, validation, correction, analysis, action, publication, exchange, backup, and exit.
  4. Calculate total cost over at least five years, including implementation and internal staff—not only software licences.
  5. Confirm data portability, security responsibilities, service expectations, and the plan if a vendor or project relationship ends.

Conclusion

mWater and Solstice deserve serious consideration because they combine national scale with low barriers to participation, offline fieldwork, longitudinal registries, analysis, and operational follow-through. Their strongest case is not that they replace every specialist system. It is that they can provide the connective monitoring layer through which government and partners maintain shared records, understand change, and coordinate action.

Sources and further reading

Review mWater's national monitoring overview, the Solstice overview, and the independent requirements in How to choose a WASH MIS. Claims should be tested against the country's requirements and verified during procurement.