Skip to content
HeuriTel
Sign in

Emergency management and public-service operations

Warn the people in an area, without a list of who they are

A river is rising. The agency has to warn the people in its path within the hour, and it has no list of who they are and no right to one.

No demonstration is configured for this journey yet.

Seen by the customer · Cell broadcast, English

From the record, not a run: what would reach them, on Cell broadcast, SMS, in English, Kiswahili.

The case

Annotated from the record

What happened

A river is rising and the agency has to warn the people in its path within the hour, without a list of who they are.

A river is rising. The agency has to warn the people in its path within the hour, and it has no list of who they are and no right to one.

What it reads

  • The approved area and time window
  • Aggregate device counts and the minimum group size
  • The legal basis and the emergency authority
  • Data freshness

Checks before anything is sent

Legal basis, emergency authority, re-identification risk, minimum group size and stale-data checks pass.

Every option considered, including doing nothing

  1. An approved alert to the area, through the operator, on the agency's decisionConsidered
  2. A narrower area or window, where the group size or the basis failsConsidered
  3. Referral to an authorised officerConsidered
  4. No alert, where no emergency authority existsConsidered

No action is a valid outcome, and it is recorded with its reason. Nothing is computed on this page: the options are the record's own, and no run has decided anything.

Evidence record

Preview
Reference
Issued when a run is saved. An evaluation that was never saved has none.
Decision
One of the options, including no action, with the reason.
Checks
Legal basis, emergency authority, re-identification risk, minimum group size and stale-data checks pass.
Evidence kept
  • Purpose approval
  • data agreement
  • aggregation test
  • agency decision
  • alert log
  • impact review
  • public report
The measures
People reached in the area within the window, against alerts sent outside it.
Connection
Stated on every record. In the demonstration no operator system is connected, and each record carries that state.

The shape of the record, with no values. A reference appears only after a run is saved.

The improvement, and how it is measured

Hypothesis

An alert that reaches the people in the path within the hour is the service; one that reaches everyone, or no one, is not.

Desired result: Faster, more accessible and better-targeted public service; improved resilience and resource allocation

Modelled not observed

No figure is modelled for this journey. The mechanism that could produce the result is stated instead.

Authorise purpose → prepare/aggregate → analyse → apply thresholds → agency review → act → log → publish impact and bias checks where appropriate

Observed

Nothing yet. Measurement begins in a pilot’s validate stage, on your systems, against a comparison agreed first.

Geographic/time phased rollout; process baseline; independent privacy and bias review; publish limitations; never infer causal impact without design

Measured on: Response time; queue reduction; service completion; coverage; false alert; excluded population; resource efficiency; public outcome metric

Assumptions, costs and the record’s five answers
  1. 01
    Desired result

    The result wanted.

    Faster, more accessible and better-targeted public service; improved resilience and resource allocation

  2. 02
    Mechanism

    The mechanism that could produce it.

    Authorise purpose → prepare/aggregate → analyse → apply thresholds → agency review → act → log → publish impact and bias checks where appropriate

  3. 03
    Evidence required

    The records kept to show it.

    Purpose approval; data agreement; aggregation test; model/logic version; agency decision; action log; impact/bias review; public reporting

  4. 04
    Costs and risks

    The cost, and the ways it can go wrong.

    Costs: Fixed project + annual managed service; government framework contract; outcome milestone only where measurement and authority are agreed

    If it fails: Withhold unsafe output; escalate to agency privacy/command authority; fall back to official data/process; never expose raw subscriber records

  5. 05
    Measurement approach

    The measure that shows it helped.

    Geographic/time phased rollout; process baseline; independent privacy and bias review; publish limitations; never infer causal impact without design

    Measured on: Response time; queue reduction; service completion; coverage; false alert; excluded population; resource efficiency; public outcome metric

Nothing has been observed for this product. Every line above is the record's own design intent; measurement begins in a pilot's validate stage, on your systems, with the comparison agreed first.

The business side

The change
People reached in the area within the window, against alerts sent outside it.
Running cost
Fixed project + annual managed service; government framework contract; outcome milestone only where measurement and authority are agreed
What evidence supports it
Purpose approval, data agreement, aggregation test, agency decision, alert log, impact review and public report.

The journey in detail

Step by step, from both sides
StepWhat the customer experiencesWhat the operator does
The momentThe moment that started it.A river is rising and the agency has to warn the people in its path within the hour, without a list of who they are.Reads the approved area and time window, aggregate device counts and the minimum group size, the legal basis and the emergency authority, data freshness.
The decisionThe decision to be made.Nothing reaches the customer yet.Prepares an aggregate of devices in the approved area and time window, checks the group size and the legal basis, and recommends the alert's reach.
The safeguardsThe conditions that stop it.Still nothing. No action is sent until every check has passed.Legal basis, emergency authority, re-identification risk, minimum group size and stale-data checks pass.
The actionThe action that reaches the customer.The agency decides; the approved alert goes to the area through the operator, and nobody's identity leaves the network. Reaches them on Cell broadcast, SMS, in English, Kiswahili.Recommends. The system that holds the right confirms, charges or provisions.
When it goes wrongRefusal, failure and recovery.The aggregate is built on counts from the previous evening, and the alert reaches an area the people have already left while missing the one they moved to.The stale-data check refuses the aggregate, a fresh window is drawn, and the impact review records the gap so the freshness rule is tightened for alerts.
The resultThe change it made.What changed for them is what is counted; nothing else is claimed.People reached in the area within the window, against alerts sent outside it.
The proofThe proof anyone can check.Can be answered for, later, from the record.Purpose approval, data agreement, aggregation test, agency decision, alert log, impact review and public report.

Operator systems remain authoritative. HeuriTel reads these to propose an action; it does not decide on their behalf.

Refusal, failure and recovery

What goes wrong

The aggregate is built on counts from the previous evening, and the alert reaches an area the people have already left while missing the one they moved to.

What happens then

The stale-data check refuses the aggregate, a fresh window is drawn, and the impact review records the gap so the freshness rule is tightened for alerts.

The products in this journey

Available to see today

No demonstration is configured for this journey yet.

See HeuriTel configured for your organisation

Verify your work email to open a demonstration configured for your organisation.