The problem
During an emergency, people may not have time to explain their location or reach the right person. Alerts that depend on a single channel can fail silently, leaving contacts and responders without the information they need.
Loading page
Preparing the content for you.
Emergency coordination when every minute matters.
A personal-safety and emergency-response platform designed around SOS alerts, location sharing, trusted contacts, responder escalation, and notification fallbacks to help coordinate assistance during emergencies.
Overview
SafeNaija is built around a simple premise: an emergency alert is only useful if it reaches someone who can act. The system captures an SOS, shares location, notifies trusted contacts, and escalates to responders when needed.
Connectivity is treated as unreliable rather than guaranteed. Notification fallbacks and incident records keep the response coordinated even when one channel fails.
During an emergency, people may not have time to explain their location or reach the right person. Alerts that depend on a single channel can fail silently, leaving contacts and responders without the information they need.
SafeNaija coordinates SOS alerts, location sharing, trusted-contact notification, responder escalation, and fallback delivery into one incident flow with a durable record.
Architecture
A high-level conceptual view of the main stages in this system.
A user raises an alert with minimal interaction.
The current location is recorded and shared with the response circle.
Trusted contacts are alerted through available channels.
Unacknowledged alerts escalate to responders and fallback channels.
Capabilities that are documented as part of the current implementation.
A fast, low-friction way to raise an emergency.
Shares the user's location with trusted contacts.
Defines who should be notified first.
Moves unacknowledged incidents to the next response level.
Uses alternative channels when a primary notification fails.
Keeps a timeline of alerts, acknowledgements, and escalations.
These items are planned and are not available yet. They are listed separately so completed functionality is never confused with future work.
Formal integrations with local emergency-response organizations.
Alert delivery over SMS when data connectivity is unavailable.
A controlled rollout with a community or campus partner.
Technology
The tools and technologies associated with the implementation.
Alert orchestration and service code.
API for alerts, contacts, and escalation.
Incident, contact, and escalation records.
Fast alert state and delivery queues.
Live updates for contacts and responders.
Alert delivery and escalation metrics.
Operational dashboards for response health.
Repeatable deployment of services.
Challenges
The engineering constraints that shaped the design.
The system must make accidental alerts easy to cancel without discouraging real ones.
Alerts need fallback paths when data networks are congested or unavailable.
Location sharing must be limited to the response circle and retained only as long as necessary.
Outcomes
Qualitative outcomes from the design. Measured results are only reported where they have been formally evaluated.
Links
Explore the project through the destinations that exist. Missing destinations are labelled instead of being replaced with a placeholder URL.
No public link has been provided for this project yet.
No public link has been provided for this project yet.
No public link has been provided for this project yet.
No public link has been provided for this project yet.
0 of 4 external links are currently available. Unavailable links are shown deliberately rather than pointing to a placeholder destination.
Keep exploring
Browse the full portfolio or start a conversation about this project.