Emergencies and the protocol

It's Saturday, 4.12pm. Your child fell from a climbing frame at the park. The bone in their forearm doesn't look right. You're putting them in the car. You'll be at A&E in twenty minutes. They've stopped crying but they're pale.

You start to think about calling your Co-Parent. Your mind has gone slow in the way minds go in a crisis. Should I call now? When I get to A&E? After the X-ray? What do I say? Do they need to come? Are they at home?

You can't think clearly because your nervous system is fully occupied with the child in the back seat. The thinking you'd normally do about the call isn't available to you right now.

This article is about the work you do before a moment like this, so that the moment itself has a structure you don't have to invent on the spot.

What this article is about

This article addresses how co-parents handle the real moments where something has gone wrong and quick coordination matters. The fall. The fever that became something. The phone call from the school nurse. The accident on the way to swimming. The moment that requires both parents to know, fast, while one parent is in the middle of handling it.

The principle is this. Emergencies are not when you build communication protocols. Emergencies are when you use them. The work is done in advance, in calm moments, so that when the body and brain are full, the structure is already there.

The article covers four things. What an emergency protocol actually is. How to build one. How to use it in the moment. And the post-emergency debrief.

What an emergency protocol actually is

A short, written agreement between two parents covering five questions.

Who do we call first. When the child is with one parent and something happens, who is the first call? Almost always: your Co-Parent, before anyone else (except 999 / 911 / 112 / 999 / the local emergency number, which obviously precedes everyone). Your Co-Parent gets the first call because they're the only other person with the same primary relationship to the child. Even if they can't do anything immediately, they need to know.

By what method. Phone call, not text. Emergencies move faster than text can. Even if the call goes to voicemail, the missed-call signal is information. Text as backup, not as primary.

With what information. A short, agreed shape for the first call. I'm with [child]. [What happened]. We're [going to / at] [location]. I'll update you when I know more. That's the structure. Not the long version. Just enough that they can orient and start moving if needed.

How often we update. During an unfolding situation, both of you need to know what update cadence is reasonable. Every thirty minutes? When something specific changes? When the situation stabilises? The agreed cadence prevents both the under-updating that produces panic and the over-updating that produces noise.

Who comes if comes is appropriate. If both parents going to A&E is the right move, who comes? The natural answer is usually the one who's currently with the child plus the other, both at A&E. But not always. If both have other children at home, the answer is more complex. If one is travelling, the answer changes. The protocol names the default and the exceptions.

A protocol covering these five questions, agreed in advance, written down, can fit on a single sheet of paper. It doesn't need to be elaborate. It needs to exist.

How to build it

If you don't have a protocol, build one in a single fifteen-minute conversation in a calm moment.

Both parents present. Phone call or in person. Both of you contributing.

Walk through three scenarios. Child gets injured at one parent's house. Child gets sick at school and is sent home. Child has an accident outside school during one parent's hours. For each, walk through who calls whom, in what order, with what information, with what response time.

Identify the assumptions. Most pre-existing assumptions don't hold up under examination. I assumed you'd call me first. I thought you wanted me to wait until you'd seen the doctor. I didn't know you wanted me to come. The conversation surfaces these assumptions, and the protocol replaces them.

Write it down. A shared note. A single document. Both phones. Both parents have access. The document isn't legally binding; it's operationally useful. The act of writing it makes both of you commit to it.

Update it. As the child gets older, the protocol changes. A protocol for a five-year-old isn't right for a fifteen-year-old. Review annually. Update when something significant changes (a move, a new diagnosis, a new partner who might be involved).

The protocol-building conversation feels slightly odd if there's never been an emergency. That's exactly the right time to have it. After an emergency, both of you will be tired and reactive; the protocol gets built poorly. In a calm Tuesday evening, both parents at home, the protocol gets built well.

Using the protocol in the moment

You're at A&E. You've parked. You're carrying the child in. You make the call.

Because the protocol exists, you don't have to think about what to do. You just do it.

Hi. I'm at A&E with [child]. They fell from the climbing frame at Hampstead Park, looks like a possible arm fracture. We're being seen now. I'll call again when we know more.

That's the message. Forty seconds. The protocol's structure has carried you. The recipient knows: where you are, what happened, what's pending. They can now respond.

A few things to know about using the protocol live.

Stick to the structure. The temptation in a crisis is to add detail, to explain how it happened, to manage the recipient's emotional state. None of that is useful in the first call. The structure is location-event-action-update. Stay with it.

Don't apologise. Even if the accident happened during your hours and you feel responsible, the first call isn't the place. I'm so sorry, I should have been watching more carefully, I don't know how this happened. This adds emotional load to a call that doesn't need it. The conversation about responsibility, if it needs to happen, happens later. The first call is operational.

Don't speculate. It might be broken. It might just be a sprain. The doctor said maybe. Speculation isn't information. Wait until you have the actual answer. The phrasing in your first call should be we don't know yet, will update when we do.

Don't escalate the news. Calling and saying something terrible has happened before delivering the actual news is its own small cruelty. The recipient spends the next ninety seconds in maximum fear before learning that the child has a probable arm fracture. The call should land at the right calibration immediately. [Child] is okay. They've had an accident. That sentence does most of the work.

Respect their state too. They're going to be activated by the call. Don't ask them to make complex decisions in the first sixty seconds. I'm going to call you again in thirty minutes. They can absorb. They can decide.

When your Co-Parent is the one calling

Sometimes you're the recipient, not the sender. The protocol works in both directions.

A few specific moves for the recipient.

Receive the information. Let them tell you the protocol-structured first line. Don't interrupt. Don't ask the elaborating questions yet. Let the structure complete.

Acknowledge. Okay. I hear you. Where can I meet you? Or: Okay. Let me know what they say. You're confirming receipt and indicating your availability.

Don't blame. Even if your first instinct is how did this happen on your watch?, don't say it on this call. The Co-Parent is in the middle of handling a situation; they don't need to also defend themselves. The question, if it has a place, has it after the child is okay.

Be available for the next update. Don't go to a movie. Don't put the phone on silent. The agreed cadence means you stay reachable until the situation stabilises.

Move toward A&E if the protocol calls for it. If your default is both parents come, start moving. Don't wait for confirmation. The act of moving is itself part of the response.

After the emergency

The child is okay. The situation has stabilised. You're home. The protocol got used.

A specific thing to do in the next 48 hours: a short debrief.

The debrief is not about blame. It's about whether the protocol worked. What was useful. What was missing. Whether either of you wished something had gone differently. The goal is improving the protocol for next time.

Both of you contribute. What was hard for you. What was hard for them. The recipient often has feedback the sender didn't anticipate. I needed more updates between the first call and when I arrived. Or: The second message was a wall of text, I couldn't read it while driving. The information is useful.

Update the document. If the conversation produces changes, write them in. The next emergency will follow the updated protocol.

Acknowledge the work. Both of you handled something hard. The handling was operational, mostly free of the long-running themes between you. Acknowledge that briefly with each other. We did okay yesterday. Glad you were there. This is not friendship; it's the recognition of competent colleagues having handled a hard thing together. It belongs.

When emergencies become a pattern

Sometimes the emergencies start happening more often. The child is in A&E several times in a year. The school is calling regularly. The pattern is its own information.

If this is happening, it's worth surfacing in a non-emergency conversation. Possible causes range widely: a medical condition becoming clearer, a school environment that's not working, a behavioural pattern that needs attention, something happening with the child that neither parent has fully understood yet. The pattern of emergencies is data; it calls for its own conversation, calmly, between two parents in a quiet room.

The protocol handles the individual events. The pattern needs a different kind of attention.

The closing

You're in A&E. The X-ray confirms a clean fracture. The child will need a cast. They're already eating biscuits.

Your Co-Parent arrives twenty minutes after your call. They walk in. They look at you. They look at the child. They sit down.

You don't have to explain the protocol or what's next. They know. Both of you go through the rest of the afternoon together. The discharge papers. The cast. The trip to the pharmacy. The drive home.

By the time you're at home, evening has fallen. The child is asleep on the sofa. You and your Co-Parent debrief in the kitchen for ten minutes. You both note that the call landed well. They mention they wished they'd known to bring the pyjamas. You note that for next time. Then they leave.

This is what the protocol-in-practice looks like, when it's been built. Not because the day was less hard. Because the structure carried both of you through a hard day without adding a second layer of difficulty to the first.

The child has a cast. The child is going to be fine. The child also, in some way they may not be able to articulate for decades, learned today that when something hard happens, both their parents show up.

Which is, in the end, what they needed to know.

And what you, by building the protocol months before, made sure they could find out.