01 Case study · Crisis and security
panic.app: Turning Crisis Communication into Structured Status Management
icitech has developed panic.app, a platform that allows organisations to collect employee safety status quickly and in a structured way during critical incidents — whether a fire, security threat, or natural disaster. Built across three layers — a mobile app for employees, a web command panel for managers, and an SMS fallback channel for connectivity loss — the platform makes it immediately clear who is safe, who has reported risk, and who has yet to respond, all from a single command view.
01Challenge
The Real Challenge in a Crisis: Building a Reliable Picture, Not Just Sending a Message
During an earthquake, fire, or flood, the core problem for most organisations is not whether they can reach employees — it is whether they can assemble a reliable, up-to-date picture quickly enough to act. When that picture depends on scattered phone calls, chat groups, and spreadsheet lists, prioritisation becomes difficult and response is delayed, which directly increases operational risk. Further, scenarios where internet infrastructure is disrupted expose the fragility of communication models that rely solely on mobile data. panic.app addresses this not as an alternative to everyday messaging, but as a dedicated crisis communication platform designed to collect structured employee safety status rapidly during live incidents and drills alike.
02Approach
Three-Channel Architecture: Channel Resilience as a Design Principle
The defining design decision behind panic.app is treating crisis communication as a channel resilience problem rather than a single-application challenge. The platform is built on three mutually supporting layers: a mobile application on the employee side, a web command panel on the management side, and an SMS fallback channel for scenarios where connectivity is lost. This architecture ensures that the communication chain in a critical moment does not depend on any single channel remaining available.
app is treating crisis communication as a channel resilience problem rather than a single-application challenge.
03Solution
Structured Status Responses and a Single Command View
The platform's second critical design decision is choosing structured status responses over open-ended messaging. An employee responds with a clear status — Safe or At Risk — in a single action. The web command panel aggregates these responses in real time across maps and lists, making it immediately visible who is safe, who has reported risk, and who has not yet responded. When an incident is raised — whether an earthquake, fire, security threat, or planned drill — the system is designed to manage the full flow from notification dispatch to response collection, prioritisation, and assignment within a single screen. Responses received via the SMS fallback channel are consolidated into the same panel, preserving an integrated status picture throughout.
04Result
Post-Incident Audit Trail and Compliance
panic.app retains timestamped records of both live incidents and drills. These records are available for internal post-incident review processes and for meeting compliance requirements — relevant considerations for organisations operating under frameworks such as UK GDPR, ISO 22301, or sector-specific health and safety obligations. Location data is not continuously tracked; it is available only at the moment an employee submits a response during an active incident or drill. Integration with corporate SSO, Active Directory, HRIS, SMS gateways, e-mail systems, and security alarm platforms is within scope; the specific integration footprint is determined per organisation based on its existing estate.
05Result
Outcomes for the Organisation
The practical outcome panic.app delivers is the replacement of fragmented, manual crisis communication with a structured status-collection process and a single command view. HR, health and safety, and operations teams can obtain the situational picture they need to prioritise response during a critical incident — more quickly and more reliably than is possible through ad hoc channels. The SMS fallback channel sustains the response flow even in the most adverse connectivity scenarios, supporting overall system reliability. The platform also allows organisations to test their crisis preparedness periodically through drills and to retain a formal record of those results.
03 FAQ
Frequently Asked Questions
01Is panic.app only suited to large enterprises?
No — the platform is designed to scale across organisations of varying size, from small teams to multi-site group structures. Scope is defined during the discovery phase to match your organisation's footprint.
02Do employees need training before they can use the mobile app?
The mobile interface is intentionally simple, so employees can report their status in a few actions with no prior training. This is particularly important during an active incident where time and cognitive load are constrained.
03When does the SMS fallback channel activate?
The system switches to the SMS channel automatically when internet connectivity is lost, maintaining the response flow without manual intervention. Responses received via SMS are consolidated into the same command panel.
04What information can managers see in real time during an incident?
The web panel gives a live view of safety status across the entire team — safe, at risk, and not yet responded — in a single screen. Map and list views are available simultaneously to support prioritisation.
05How long are incident records retained after an event is closed?
The platform archives incident records to support compliance requirements; retention duration is configurable to reflect your organisation's policies and applicable legal obligations.
06Can multiple incidents be managed concurrently?
Yes — the system is designed to track parallel incidents through independent command views, with each incident managed in its own isolated context.
07Can panic.app integrate with our existing HR or emergency management systems?
Integration with your current estate — including HRIS, Active Directory, SSO, and security alarm systems — is supported via API. The integration scope is agreed per project during the scoping phase.
08Is employee location data collected and shared?
Location sharing is an optional feature and can be enabled or disabled in line with your organisation's policy. It is active only at the point a response is submitted during a live incident or drill, not as continuous background tracking.
09Can the platform handle a large simultaneous load during a major incident?
The infrastructure is designed to scale for the sudden traffic spikes that occur during a crisis, and is capable of processing thousands of concurrent notifications.
10How long does deployment typically take?
Deployment timescale depends on the agreed scope; standard rollouts are completed quickly, and the icitech team provides technical support throughout the onboarding process.