The first media request arrives while the welfare team is still chasing replies. Your spokesperson wants one casualty number. Your accountability lead has a changing population, contradictory traces and people who have not answered. Both functions need a number, but they are asking it to prove different things.
Pressure for a clean total can end the search early. The Goodyear investigation shows the consequence. Employees were declared accounted for around 8:40 a.m. Contractor accounting ended and the emergency operations centre disbanded around 11:00 a.m. A supervisor found the victim around 1:20 p.m.
A public total therefore needs a controlled relationship with the residual list. You can acknowledge what is known without presenting the unfinished account as final. The control starts before the first denominator leaves the room.
Freeze the population before stating its denominator. A casualty rate or welfare total becomes unstable when people enter and leave the affected population during reconciliation. The visible percentage may improve because a difficult case disappeared rather than because evidence arrived.
Record the inclusion rule, incident boundary, effective time, responsible lead and source versions. Preserve the first population and create a new version for each supported addition or removal. The UK Government Data Quality Framework defines six dimensions and illustrates 98% completeness with 294 of 300 emergency-contact records. Completeness still says nothing about whether the missing records belong to those most exposed.
Source control matters because early lists are operational instruments. For United Kingdom passenger voyages over 20 nautical miles, MSN 1794 requires details before departure and communication within 15 minutes after departure. Those maritime conditions do not set your corporate clock. They demonstrate a bounded population, a timed version and a defined population-changing event.
Keep expected people visible when a source omits them. The Conception manifest contained 32 passenger names and left out one passenger. A neat denominator can therefore carry an error before the first welfare request is sent. Record duplicates, late contractors and disputed inclusions as exceptions rather than silently editing history.
Separate the five operational states. A single dashboard total often mixes transmission, response and welfare. That fails because each event has a different evidential meaning. An alert accepted by a service cannot establish that the intended person received it, understood it or is safe.
Maintain distinct totals for alerts sent, responses received, people confirmed safe, people requiring help and unresolved cases. Add delivery and outside-scope closures where they matter, but do not use them as substitutes. Link every status to a person identifier, source-event time, validation decision and population version.
The FCC’s 2021 Wireless Emergency Alert test found 89.8% receipt among 342 completed eligible survey responses. Among 294 recipients, 32.0% reported a duplicate. Those results show why transmission behaviour and person status belong in separate records. A duplicate does not create another person, and receipt does not create a safe status.
In covered United States workplaces, 29 CFR 1910.38 requires procedures to account for employees after evacuation. OSHA guidance also calls for a headcount and for missing workers’ names and last known locations to reach the official in charge. The procedure follows people through exceptions; it does not stop at a send report.
Turn silence into an owned residual case. Teams misclassify non-response when the unresolved queue has no control fields. Silence can follow failed delivery, incapacity, a dead terminal, a missed message or an ordinary delay. None of those possibilities alone supports a casualty or safe status.
Give every residual person an owner, next authorised action and review time. Record the last reliable observation, current evidence conflict and escalation threshold. The next action may be an alternate contact, a manager, a local accountability lead, an authorised presence source or an emergency contact under the declared purpose.
Prioritise plausible harm and evidence age. Do not sort only by surname or remove the hardest cases. The 2017 US Federal Continuity Directive 1 required daily reporting until 100% accountability for its federal population. That jurisdiction-specific cadence is no corporate deadline, but the repeated ownership of the unresolved denominator transfers cleanly.
Where the welfare threshold is crossed, prepare the residual for transfer. Include identity, incident relevance, last reliable observation, lawful assistance information, checks made and callback details. Record who accepted the case and when. The public figure should then distinguish unresolved cases retained by your team from cases accepted by a competent authority.
Set release latency and update interval on different clocks. Communications pressure often turns “publish quickly” into an arbitrary deadline. A universal deadline ignores the difference between acknowledging an event, confirming observed harm and assigning a final casualty count.
Set the release threshold for each claim. An acknowledgement may need verified occurrence and scope. A provisional casualty number needs a controlled denominator, sufficient evidence for included cases and a declared unresolved count. Set an upper silence bound as well, because an approval queue can otherwise delay even a bounded statement indefinitely.
WHO public-health preparedness guidance uses a 24-hour first-announcement criterion and at least daily media monitoring. Those values belong to that public-health instrument. Your event may require a shorter acknowledgement. The transferable control is an explicit verification threshold, an upper silence bound and a recorded reason when either changes.
Start the next-update clock after release. Set it from the fastest of three clocks: hazard change, arrival of decision-relevant evidence and the time already promised. If nothing material changes, publish a no-change update that preserves the action and resets the review time. Do not inflate the casualty total merely to give the update something new.
Match the speaker to the claim. Seniority can supply organisational authority while leaving the evidence boundary poorly explained. Technical expertise can explain reconciliation while carrying no authority to promise support, remedy or future disclosure. A single speaker may not satisfy both needs.
Test authority, expertise and delivery ability separately. CERC 2018 spokesperson guidance gives two basic selection factors: subject familiarity and clear, confident speech. It also recommends practising key messages in 10–20-second phrases and permits a subject expert to join the primary spokesperson. Agree their division before the briefing.
Give the spokesperson a bounded sentence rather than a naked total. State the status, number, scope and cut-off time, followed by confirmed-safe, requiring-help and unresolved totals where disclosure is lawful. Name the owned source and next update time. CERC 2018 says emergency audiences may remember only three directions, so keep the public action distinct from the reconciliation detail.
Authority must match the verb. The spokesperson may report what the accountability lead has verified. The lead may explain source limits. The incident jurisdiction may confirm deaths. Record which commitments each person can make and which questions transfer to an expert or public authority.
Correct the source before repeating the correction. Reconciliation may add a contractor, remove someone shown outside the boundary or resolve conflicting identity evidence. Quietly replacing the public page leaves screenshots, media copies and internal briefings attached to a total that now has no visible history.
Update the owned source first. Preserve the earlier version, mark it superseded and record the effective time, changed status and evidence basis. Then correct every material distribution: media statement, staff message, family briefing, regulator submission and partner feed. State any changed action as well as the changed number.
US aviation guidance under 49 USC 41113 describes the passenger list as best available at the request time, whether or not names are verified, and requires periodic updates. That jurisdiction-bound model permits urgent use without concealing uncertainty. It also makes correction part of the original transaction.
Close the account only when every included person has supported terminal evidence or a named recipient has accepted the unresolved case. The closing record keeps the original denominator, every version, final status totals, transfers, limitations and corrections. Your spokesperson can publish earlier. The number remains provisional until that record closes.