If everyone receives the message, who acts? The problem of unassigned roles

Distribution and responsibility are different

Delivered, read, understood and owned are separate states. A tick or notification does not say who is calling, travelling or checking the second channel.

Agree which signal only requests an update and which opens the protocol. Silence remains ambiguous: network, battery, silent mode and availability can all explain it.

Primary and backup must accept the role

The primary contact verifies first and states the action. The backup has a defined trigger: they take over after the agreed window or when the primary says they cannot act.

Both people accept the hours, task and limits. Membership of a family group does not create on-call duty or professional responsibility.

Ownership needs explicit words

Use an operational sentence: “I own this: I am calling Anna now and will update in ten minutes.” “Seen”, an emoji or “can someone check?” does not assign a person, action and time.

A handover states what was checked, what remains and who receives the task. The backup confirms acceptance; until then, the primary retains follow-up when able.

The family protocol matrix

Ten elements turn a recipient list into a sequence people can verify.

The emergency threshold starts with facts

Do not make no reply the only emergency threshold.

Use concrete triggers: an explicit request for help, observed danger, verifiable information or direction from the relevant services.

For immediate danger, do not wait for a chat turn. Call the appropriate local number; 112 is common and free in the EU. Share known facts and location without inventing a diagnosis.

Rehearse, update and minimise data

Run an announced rehearsal: send a test, have the primary claim it, simulate handover to the backup, then close with a summary. Do not call public emergency services for a test.

Review contacts, hours and numbers after changes. Share only data needed for the task; health details, location and family information should not spread by habit.

• Have primary and backup accepted?
• Are hours and absences stated?
• Is the ownership phrase written?
• Is the handover window realistic?
• Is a second channel available?
• Does the emergency threshold use concrete facts?
• Is shared data necessary?
• Was the announced rehearsal closed and reviewed?

For concrete immediate danger, call the appropriate local emergency service now. No in-app acknowledgement replaces that call.

Practical example: turn the plan into verifiable actions

An SOS reaches four people: the protocol names Anna as primary and Marco as backup for that period. Describe the observable fact without interpreting health or intention.

Anna replies “I’ll call” and updates the group; others avoid duplicate calls while remaining available. Give the next step to one named person and name a backup.

A tick, view or silence assigns no responsibility and does not prove anyone is acting. Write the expected outcome in words everyone understands consistently.

Chat is enough when everyone uses an ownership phrase and follows the agreed roles. If direct conversation solves the task, do not add another app.

When the tool is unnecessary and which backup to use

A routine informational update does not need an emergency response protocol. Prepare calls, SMS, paper and an agreed in-person check where appropriate.

If the primary does not confirm within the agreed margin, the backup takes ownership and states it. Review consent, recipients, numbers and availability after every change.

With concrete danger, the owner calls local responders and shares only necessary information. For immediate danger use the relevant local service without waiting for notifications.

• Example rehearsed?
• Owner named?
• Backup available?
• Data limited?
• Numbers current?
• Fallback agreed?

Frequently asked questions