HomeFamilyContinuity2026

How to Make a Family Communication Plan Before the Network Fails

In the chaos people default to habit, not to the plan, so the value is the agreed rule you rehearse, not the contact list you compile. Here is the out-of-area relay, the text-not-call rule, the two-tier meeting point, the kids-and-school route, and the rehearsal discipline that turns a document into a behaviour — the channel-break and the pre-commitment, applied to a family.

General information only — not emergency advice, and not a substitute for your local emergency service. This page explains the structure of a family communication plan in broad terms. The specific network behaviour, the school and employer procedures, and the emergency numbers vary by place and provider; confirm them with your local emergency-management agency, your school or employer, and your carrier. In a real emergency, call your local emergency number — the plan is a bridge to services, not a replacement for them.

A plain blank paper card folded in half, standing open like a tent on a clean light surface, beside a small unmarked wind-up radio — The blank card folded in half and the small unmarked wind-up radio are the whole plan in two objects: the fold is the agreed rule — a crease you can feel in the dark, not a list you have to read — and the radio is the information tier that works when the network does not. The card stays blank on purpose, because the discipline is the rule everyone has rehearsed, not the names written on it.

Updated September 2026By the AI Help Guide editorial team9 min read

The Document That Will Not Be Used

A Contact List Is Not a Plan, and a Plan on Paper Is Not a Behaviour

The well-meaning family sits down, writes a list of phone numbers, tapes it to the fridge, and considers the matter closed — and the list is almost worthless, because on the day the network fails and the family is scattered, no one opens the fridge, no one remembers the list, and everyone defaults to the habit of calling each other directly across a saturated network. The failure is not the absence of a document; it is the absence of a rule that has been rehearsed, because a plan that exists only as a list is a plan that will not be used, and the chaos does not read, it reacts.

This page is the coordination half of the continuity trio; its companions, the emergency-kit guide and the important-documents guide, deal with the stuff and the paper. The smart-home resilience guide that came before explained what still works when the link is absent; this page explains how the people reconnect when the same link fails — a coordination problem, not a device problem, and one whose defence is behavioural. And the plan's structure is the same two habits the rest of the corpus encodes: the channel-break our phishing guide taught (re-establish through a node the attacker — here, the event — did not touch) and the pre-commitment our vendor-sunset playbook taught (decide under calm what you will do under duress, and practise it). The out-of-area relay is the channel-break applied to a family; the rehearsal is the pre-commitment applied to a household.

The Agreed Rule, Not the Contact List

The Two Bands, and Why the Fold Beats the List

The distinction that makes a plan usable is the difference between a list you read and a rule you follow, and the two bands below are the same document seen from each end. The list is the raw material; the rule is the behaviour, and the behaviour is the thing the chaos tests. A family that has agreed the rule and rehearsed it will follow it in the dark; a family that has compiled a list will not find it, will not read it, and will default to habit.

The contact list — the raw material, not the plan

A page of names and numbers, taped to the fridge
Useless if no one opens the fridge in the chaos
Encourages the default: call each other directly, saturate the local network
Static — it rots as numbers change, and no one reviews it
A document, not a behaviour

The agreed rule — the behaviour the chaos tests

A short rule everyone has rehearsed: text first, relay through the out-of-area person, meet at the point
Usable in the dark, because it is a habit, not a lookup
Redirects the default away from the saturated local network
Reviewed on a cadence, tied to the kit and the school year
A behaviour, not a document

The question	The contact list	The agreed rule
What is it?	A page of names	A rehearsed behaviour
Used in the dark?	No — requires reading	Yes — requires habit
Network effect?	Saturates the local path	Redirects to the relay
Rots?	Yes, silently	Reviewed on a cadence
Value?	Raw material only	The plan itself

The tables point is the pages thesis in one column: the contact list is the raw material of a plan, not the plan, and the plan is the agreed rule that everyone has rehearsed. The list has a place — the names live somewhere — but the place is inside the rule, not instead of it, and a family that has only the list has only the raw material. The discipline is to write the rule first (text, relay, meet), rehearse it, and let the list be the appendix, because the appendix is what no one reads and the rule is what everyone follows.

The out-of-area relay — the channel-break, applied to a family

Out-of-area relay person (lives outside the event)

↑ text ↑ text ↑

Parent A Parent B Teen Grandparent

The rule: everyone texts the relay, not each other. The relay is a person far enough away to be outside the event — a relative in another region, a friend in another city — who collects the messages and redistributes them. The reason is structural: a local network that is congested or damaged may carry traffic to and from outside the affected area more reliably than traffic within it, so the relay is the node the event did not touch. This is the same maneuver our phishing guide taught — do not engage on the attackers channel, re-establish on a known one — applied to a family: do not fight the saturated local network, re-establish through the out-of-area node. One message to the relay beats five failed calls across a congested local path, and the relay becomes the single source of truth the family can check.

Text first — the network-capacity reality, hedged. The agreed default is text, not call, and the reason is a general property of the technology: text messages often get through when calls cannot, because they use less network capacity and can queue and deliver later rather than requiring a live channel. A short text — "OK, at relay" — carries more across a saturated network than a thirty-second call that fails to connect.

This is a general property, not a guarantee: no one can promise a text will arrive, and in a severe event nothing may. The discipline is to default to text because it often works better, to keep the message short, and to route through the relay so the local network is not the only path — not to assume the text is a reliable channel. The honest hedge is the whole rule: text first because it is more likely, never because it is certain.

Tier 1

Immediate — outside the doorA meeting point a few steps from the house, for the event that empties the home in seconds — a fire, a gas leak, an earthquake. No keys, no phones, no thinking: everyone goes here. This is the tier the kit cannot reach, because the kit is inside.

Tier 2

Neighbourhood — outside the blockA meeting point beyond the immediate area, for the event that empties the neighbourhood — a flood, a evacuation order, a road closure. Reachable on foot, recognizable, and outside the zone that may be inaccessible.

The two tiers are the meeting-point discipline, and the reason there are two is that the event that takes the house is not the event that takes the neighbourhood, and a single point cannot serve both. Tier 1 is for the seconds-scale event where you cannot go back for anything; tier 2 is for the hours-scale event where the immediate area is unsafe or unreachable. Both must be places a child can recognize and reach without a map, and both must be named in the rule — "if the house, the tree; if the street, the school gate" — because in the chaos a described point is a located point and a located point is a met point.

The kids-and-school route — the pickup authority and the script. The event that scatters a family most reliably is the one that happens at school, and the plan must name, in advance and in writing with the school, who is authorised to collect the child and what the child does if the parents cannot be reached. The discipline:

Give the school the written pickup authority — the names of the people allowed to collect, and the rule that the child goes only with them, so a stranger who "says mum sent me" is stopped by the plan, not by the child's judgement.
Teach the child a script they can recite — the out-of-area relay person's name and number, the meeting point, and the sentence "I need to text [relay] to say I am OK." A recited script is a behaviour; a remembered list is not, and the child is the family member least able to read a fridge in the chaos.
Confirm the school's own emergency procedure — where the school reunites children, how it communicates, and whether it has an app or a line, so the family plan plugs into the school plan rather than assuming it.
Put the relay number in the childs phone and on a card in their bag — the phone dies, the card does not, and the card is the thing a child can hand to a teacher or a responder.

The kid route is the plan's highest-value tier, because the child is the member who cannot improvise, cannot read the fridge, and cannot be expected to remember a list — so the plan must be a script in their mouth and a card in their bag, and the pickup authority must be written with the school before the day, not argued on it.

The battery-and-signal reality — the plan assumes the phone dies. The communication plan is built on phones, and phones die, so the discipline is to assume the device fails and to build the plan around the failure rather than on top of it. The practical rules: keep a charged power bank in the kit and in the car (the power tier of our emergency-kit guide); know the meeting point without a phone, because the phone may be dead when you need to reach it; carry the relay number on a card as well as in the phone, because the card survives the dead battery; and teach the child the script, because the script survives the lost phone. The plan that assumes the phone works is the plan that fails on the day, and the day is precisely when the battery is lowest and the signal is worst — the two facts the plan must be built around, not despite.

The rehearsal discipline — a plan on paper is a plan that will not be used

Run a short drill, twice a year. A ten-minute exercise: everyone texts the relay "drill OK," everyone names the meeting point from memory, the child recites the script. The drill turns the rule into a habit, and the habit is the thing the chaos tests.
Post the agreed rule, not the list. A single card on the fridge and a note in every phone: "text relay, meet at the tree, kids go with named adults." The rule fits on a card; the list does not, and the card is what is read.
Teach the child a script they can recite. The relay name and number, the meeting point, the sentence. A recited script is a behaviour; a remembered list is not.
Review on the same cadence as the kit. The clock change, the new year, the smoke-alarm battery day — the same triggers that rotate the water and charge the batteries, so the plan and the kit stay current together and neither rots silently.
Update the school and employer each year. The pickup authority, the emergency contact, the reunification procedure — confirmed annually, because the people and the procedures change and the plan that was right last year may be wrong this year.

The rehearsal disciplines logic is the vendor-sunset playbooks logic, transplanted to a household: decide under calm what you will do under duress, and practise it, so the bad afternoon opens a habit instead of a panic. A plan that exists only as a document is a plan that will not be used, because the chaos does not read, it reacts, and the reaction is the habit you rehearsed, not the list you compiled. The drill, the card, the script, the cadence, and the annual update are the five behaviours that turn the raw material of a contact list into the plan that survives the day — and they are the whole page, because the rule without the rehearsal is just a nicer list.

A worked example: the two families, and the one that texted the relay

Concretely, the agreed rule, the out-of-area relay, the text-not-call default, the two-tier meeting point, the kid route, and the rehearsal discipline meeting two families in the same regional outage. A storm takes the local network across a county on a weekday afternoon: parents at work, a teen at school, a grandparent at home, and the phones that still have battery cannot connect calls.

Family A has a contact list. The list is on the fridge, which no one is at, and the rule is "call each other." Parent A tries to call Parent B four times; each call fails on the saturated local network. The teen, at school, does not know the pickup authority and is uncertain whether to go with a neighbour who "says mum sent me." The grandparent, at home, cannot reach anyone and does not know the meeting point. The family is scattered, silent, and anxious, and the list on the fridge is unread because no one is at the fridge. The contact list was the raw material, and without the rule it was nothing.

Family B has an agreed rule. The rule is rehearsed: text the relay, meet at the tree (tier 1) or the school gate (tier 2), kids go only with named adults. Parent A texts the relay — the aunt two regions away — "OK at work, cannot call." Parent B texts the relay the same. The relay collects both and texts back "both OK, teen at school, grandparent OK." The teen, at school, knows the pickup authority is the aunt and the neighbour, and is not released to the neighbour-who-says-mum-sent-me, because the written authority stops it. The grandparent texts the relay "OK at home." Within twenty minutes, the family knows where everyone is, through the node the event did not touch, on a network that could not carry a single call. The teen recites the script to a teacher; the grandparent has the card in their pocket because the phone died; the meeting point is named because the drill ran it twice a year.

The lesson is the whole page. The two families had the same event, the same scattered geography, and the same broken local network. The difference was not the list — both had names somewhere — but the rule, and the rule was a behaviour Family B had rehearsed and a document Family A had compiled. The out-of-area relay was the channel-break that beat the saturated local path; the text-not-call default was the network-capacity property that made the relay work; the two-tier meeting point was the named habit that needed no phone; the kid route was the written authority and the recited script that stopped a stranger; and the rehearsal was the thing that turned all of it from a fridge list into a reaction. The plan that survived was the one that was a behaviour, not a document — and the behaviour was the thing the storm tested.

The Check

A Sensible Default

Hold the thesis: the value is the agreed rule you rehearse, not the contact list you compile — the chaos reacts, it does not read.
Set the out-of-area relay — the channel-break applied to a family: text the node the event did not touch, not each other across a saturated local path.
Default to text, not call — a network-capacity property, hedged: more likely, never certain.
Name the two-tier meeting point — immediate (the tree) and neighbourhood (the school gate) — reachable without a phone, recognizable to a child.
Write the kid route with the school — the pickup authority, the recited script, the card in the bag — because the child cannot improvise.
Assume the phone dies — power bank, card, script, and a meeting point that needs no device.
Rehearse — the drill, the card, the script, the cadence, the annual update — because a plan on paper is a plan that will not be used.
Route the specifics out — network behaviour, school procedure, emergency numbers — to your local agency, your school, and your carrier.

The honest takeaway is that a family communication plan is a behaviour, not a document, and the behaviour is the thing the chaos tests — so write the rule first, rehearse it twice a year, route through the out-of-area relay, default to text, name the two meeting points, and put the script in the childs mouth and the card in their bag. The contact list is the appendix; the rule is the plan, and the plan that survives is the one that was a habit. For the stuff that bridges the same outage, see our emergency-kit guide; for the paper that survives it, see our important-documents guide; for the device autonomy during the link-outage this page widens to a people-outage, see our smart-home resilience guide; for the channel-break the out-of-area relay mirrors, see our phishing guide; for the pre-commitment the rehearsal discipline echoes, see our vendor-sunset playbook; and for the specific network behaviour, school procedure, and emergency number for your place, see your local emergency-management agency, your school or employer, and your carrier — the authorities this page keeps routing you to, because the structure of the rule is durable and the specifics are not ours to assert.

Three plain blank paper tokens laid in a row with the middle one raised on a small block above the line, on a clean light surface — The three blank tokens with the middle one raised above the line are the out-of-area relay made physical: the two end nodes are inside the event, the raised middle node is outside it, and every message routes through the node the storm did not touch. The tokens stay blank on purpose — the lesson is the topology of the rule, not the names on the cards.

Common Questions

Frequently Asked Questions

What is a family communication plan?

It is an agreed rule, not a contact list. The plan names how your family will reconnect when the network is congested or down and you are not together: an out-of-area relay person, a text-not-call default, a two-tier meeting point, and a school-and-kids route. The value is not the names on the card but the fact that everyone has agreed the rule and rehearsed it, because in the chaos people default to habit, not to a document they have never opened.

Why do I need an out-of-area contact?

Because a local network that is congested or damaged may carry traffic to and from outside the affected area more reliably than traffic within it. An out-of-area relay — a person who lives far enough away to be outside the event — lets family members leave a message with one person rather than calling each other across a saturated local network, and it is the channel-break applied to a family: you re-establish through a node the event did not touch.

Should we call or text?

Default to text. Text messages often get through when calls cannot, because they use less network capacity and can queue and deliver later rather than requiring a live channel — this is a general property of the technology, not a guarantee. The agreed rule is: text first, keep it short, and use the out-of-area relay so the local network is not the only path.

How do I make sure my family actually follows the plan in a crisis?

Rehearse it, because a plan that exists only as a document is a plan that will not be used. Run a short drill, post the agreed rule on the fridge and in every phone as a note, teach the kids a script they can recite, and review it on the same cadence as the kit. The discipline is the same as the vendor-sunset pre-commitment: decide under calm what you will do under duress, and practise it, so the bad afternoon opens a habit instead of a panic.

What if the out-of-area relay person is unreachable too?

Name a second relay, and do not make the plan depend on a single node. The structural point is that the relay is outside the event, so a second relay in a third region is the redundancy that keeps the rule working if the first is also affected. The discipline is the same as the three-location kit: do not put every message through one person, one phone, or one path, because the event that takes the local network may take the first relay too. Two relays, two regions, one rule.

My teen will not rehearse. Is the plan useless?

Not useless, but weaker, and the honest answer is to make the rehearsal small enough to be unavoidable. A ten-minute drill twice a year, a note in the phone rather than a card on the fridge, and a script that fits in one sentence are the minimum that survives a reluctant teenager. The plan does not require enthusiasm; it requires that the rule is felt rather than read, and a note in the phone is felt every day. The kid route matters most for younger children who cannot improvise; a teen can be trusted with the text-and-relay rule even without a drill, provided the relay number is in their phone and the meeting point is named.

Is a group chat or an app enough instead of a plan?

No, and the app is the raw material, not the rule. A group chat depends on the same network the event takes, on the same phone that dies, and on the same data connection that saturates; it is a tool that works when the network works and fails when it does not, which is the day the plan exists for. The discipline is to treat the app as one channel inside the rule — text the relay, which may be an app, may be an SMS, may be a card — and to keep the meeting point, the pickup authority, and the script independent of any single app, because the app is the thing that fails on the day and the rule is the thing that survives it.

Ask our AI. Making a family plan? Tap the chat icon and tell us your household, your school, and your place, and it can write the agreed rule with you, set the relay and the two meeting points, draft the kid script and the pickup authority, and hold the rehearsal discipline — and it will always route the network behaviour, school procedure, and emergency number to your local agency, your school, and your carrier, because the structure of the rule is durable and the specifics are not ours to assert.

More family & continuity guides like this

We treat a family communication plan as a behaviour rather than a document — write the agreed rule first, rehearse it, route through the out-of-area relay, default to text, name the two meeting points, and put the script in the childs mouth — because the chaos reacts, it does not read.

Explore All Guides