In a humanitarian emergency, digital transformation is often discussed as if it begins with sophisticated platforms. My experience in Sudan has taught me something more basic: a working phone, a current referral list and a clear rule about who may open a file can determine whether a person reaches support safely. In fragile settings, information systems are not simply administrative tools. They are part of the protection infrastructure.
This became especially clear while supporting mental health, gender-based violence and child-protection services across locations affected by conflict and displacement. Services existed on paper, but the route to them could change overnight. A provider relocated. A phone stopped working. Connectivity disappeared. Staff changed. A referral pathway that looked complete in a document became unreliable in practice. The question was never only whether a tool existed. It was whether a frightened person could use the system at the moment they needed it.
Availability is not the same as access
A hotline can be technically active and still fail the people it is intended to serve. The number may not be known in the community. The phone may be unattended during the hours when risk is greatest. A caller may have limited airtime, fear being overheard or speak a language the responder does not understand. The digital service works, but access does not.
Our practical response was not another platform. It was disciplined follow-up: checking the phones, clarifying shifts, linking callers to trained personnel, updating referral contacts and making the number visible through community networks and safe spaces. We also had to distinguish between general psychosocial information and confidential case support. That distinction protected both the caller and the staff member receiving the call.
The lesson is relevant beyond humanitarian response. Organisations building digital health, social-protection or public-interest services should measure the full journey, not the existence of the interface. A service is available only when people know about it, can reach it, trust it and receive a useful response.
The smallest data decision can carry the greatest risk
Protection work involves information that can expose people to stigma, retaliation or further harm. A badly designed spreadsheet can therefore be as dangerous as a badly designed application. Collecting unnecessary names, circulating a file too widely or leaving access permissions unchanged after a staff transition can turn routine administration into a protection failure.
In practice, safer systems depended on restraint. We used codes where identifying information was unnecessary, separated aggregate reporting from confidential case records and limited access according to role. We asked a simple question before adding any field: do we genuinely need this information to provide the service or account for the work? If the answer was no, the field did not belong there.
This is data governance at its most concrete. It is not a policy document stored somewhere above the programme. It is the everyday decision to collect less, share carefully and make responsibility visible. African organisations working in high-risk environments need privacy-by-design approaches that remain useful when devices are shared, connectivity is weak and staff turnover is high.
Low tech systems can be highly intelligent
During network interruptions, teams could not depend on a single online system. We needed a safe fallback: agreed coding, controlled offline records, scheduled synchronisation and confirmation that referrals had actually been received. Sometimes the most valuable technology was an updated contact sheet held by the right person, supported by a clear escalation process.
Low-tech should not mean informal or insecure. A paper record can be misplaced; a personal messaging account can expose confidential information; an old spreadsheet can produce duplicate or contradictory figures. The strength of a low-tech system comes from the rules around it: version control, minimum-data principles, named responsibility, secure storage and a routine for checking whether the information is still current.
The goal is not to reject advanced technology. It is to choose technology that matches the operating environment. A platform that requires constant bandwidth, specialised support and uninterrupted electricity may become unusable precisely when it is needed most. Resilience must be designed into the service, not added after the system fails.
Technology works through relationships
People do not trust a referral pathway because it has been digitised. They trust it because someone explains what will happen, protects their information and follows through. Community-based networks, women and girls safe spaces, child-friendly spaces and health facilities often become the human layer that makes a digital system usable. They translate a phone number or database entry into a relationship.
That human layer also reveals problems that dashboards miss. Community members can tell us that women cannot call privately, that adolescents do not recognise formal service language, or that a referral point is no longer considered safe. Frontline staff see when a technically correct process asks too much of a person already in distress. Their feedback should shape system design from the beginning.
Building protection into Africa’s digital future
Across Africa, governments, businesses and civil-society organisations are building digital systems for health, cash assistance, education and social protection. The most important question is not whether those systems are modern. It is whether they continue to protect people under pressure.
That requires practical choices: collect only necessary data; design for low connectivity and shared devices; test the entire user journey; create safe offline procedures; assign responsibility for updating information; and involve the communities and frontline workers who understand how the service is actually experienced.
In a crisis, trust is infrastructure. So is a current telephone number. So is a staff member who follows up. Technology becomes protective when it strengthens those relationships instead of pretending to replace them.
