Your own response team
Route incidents to an in-house security, operations or clinical response team with group-specific escalation.
For organisations
A safety service configured around your operation.
Deploy on personal or managed smartphones, decide who responds and give teams policies that match their work, without issuing another piece of hardware.
Discuss your deploymentResponse models
Choose who receives the alarm.
Routing is policy, not hardcoded infrastructure. The incident follows the responsible responder organisation.
A monitored response
Address each alarm to the responder organisation responsible for acting, with the same incident and audio workflow.
A hybrid model
Keep the primary response in-house and overflow unanswered incidents through timed escalation without changing the worker app.
Ready for the organisation around the app
From identity to board assurance.
Ordin gives IT, information governance and service leads the controls needed to operate the system without developer access.
- NHS Microsoft sign-in with distinct worker, responder and administrator groups
- CSV provisioning and staff-group policy management
- Configurable check-in, tracking, routing, escalation and retention rules
- VPRS reporting plus versioned privacy and DPIA evidence from live configuration
- Device capability and permission-health evidence across iOS and Android
Replace with a wide product image showing staff groups, an escalation policy and the assurance export controls in one administrator view.
Trust is operational
Privacy and resilience are part of the safety model.
Privacy by state
Location is collected only during active protection or an unresolved alarm. Microphone access belongs to the live alarm state machine.
Resilience by design
Server-held deadlines, durable native state, offline delivery and carrier fallback protect the alarm path from ordinary phone failure.
Evidence by default
Append-only activity, named incident ownership, delivery attempts and policy versions make decisions reviewable.
Accessible safety actions
Plain labels, non-colour status, keyboard access, scalable text and assistive-technology support are treated as release requirements.