Building MEAL systems that keep working when access is limited
Some of the greatest needs in Ukraine are in exactly the places that are hardest to reach: communities near the front, areas with restricted access, and recently de-occupied territories. For organisations working there, the hard question is not “who can we send to monitor?” - it is “will our MEAL system still produce credible evidence when access keeps changing?”
The real problem is the system, not the site visit
When access is limited, the temptation is to outsource a one-off site visit to a third-party monitor and move on. But an external check does not fix a MEAL system that was never built for volatility. If indicators cannot be revised, if tools assume in-person access, and if data has nowhere to flow, the evidence gap reopens the moment conditions change.
What an access-ready MEAL system looks like
The durable answer is a system designed for exactly these conditions:
- Adaptive indicators and tools that can be revised without rebuilding the whole framework.
- Data pipelines your own team can run - Kobo or ODK forms, clean databases, and dashboards that do not depend on any one person being on site.
- Remote data collection where in-person contact is not possible - above all, monitoring surveys conducted by phone with trained enumerators.
- Accountability built in, so affected communities can raise concerns through feedback channels, not just appear as data points.
Why we build rather than monitor
Umeal is not a third-party monitoring vendor, and we do not deploy field teams. We build and strengthen the MEAL system inside your organisation, so the evidence holds up - in a donor audit and in the decisions you make - even where you cannot be present yourself. Where remote data is genuinely needed, phone-based monitoring surveys are the one field-style service we run.