A person dies. The fact is clear, final, and—in administrative terms—significant. It terminates contracts, closes accounts, transfers assets, ends subscriptions, requires notification across a range of organisations that had ongoing relationships with the person who no longer exists.
It is also, and this appears to cause the most difficulty, entirely predictable. Not in its timing for any individual, but as a category of event that every organisation with a customer base will encounter, regularly, as a matter of statistical certainty.
Death is not an edge case. It is a known event that happens every day, to people who have bank accounts, utility contracts, insurance policies, subscriptions, memberships, and all the other administrative relationships that constitute a modern life. Every organisation that holds such relationships will, at some point, need to respond to the death of the person on the other side of them.
Many organisations do not know how.
In 2010 my partner died. I notified the relevant organisations. The responses varied, but the pattern was consistent: sympathy was offered, and then a pause, as though the sympathy were the response rather than the beginning of one. What happened next was largely improvised—by me, by the person on the other end of the phone, by both of us together trying to navigate a situation for which neither of us had a map. The organisations were not unkind. They were unprepared.
In 2023 my wife died. I went through the same process with the same expectation, adjusted slightly upward by the intervening years and the various events—including a pandemic that had produced, among other things, a great deal of death and presumably a great deal of administrative experience in handling it—that might reasonably have prompted organisations to develop clearer procedures.
Some had. The banks, in particular, had developed defined bereavement processes—specific teams, clear guidance, a sequence of steps that was communicated at the beginning of the call and followed through to completion. The person on the other end of the phone knew what they were doing. They had been trained for this. The conversation was still difficult, because the subject is difficult, but the difficulty was human rather than procedural. The process itself was functional.
Others had not. In the thirteen years between the two deaths, those organisations had continued to onboard customers, maintain accounts, generate invoices, and process payments with considerable efficiency. They had not, in that time, developed a clear process for what to do when the customer died.
Sorry for your loss. The phrase arrives reliably, delivered with what sounds like genuine feeling, in a tone calibrated to acknowledge the gravity of the situation. It is not insincere. It is also not sufficient, and the moment after it is where the system reveals itself.
In a prepared organisation, the moment after is a procedure. A sequence of steps, communicated clearly, each one assigned to someone responsible for its completion. The bereaved person is told what is required of them and what the organisation will handle. The conversation has a shape. It moves toward resolution.
In an unprepared organisation, the moment after is a pause. The sympathy has been delivered. The person delivering it does not know what comes next, because nothing comes next. There is no next, no defined sequence, no one whose responsibility it is to own the process from this point. What follows is improvisation: the staff member asking questions they are making up as they go, transferring the call to someone else who is also making it up, or defaulting to the normal operational process because the normal operational process is the only one available.
The normal operational process continues the account. It generates the next invoice. It sends the reminder. It processes the standing order. The account remains active. The person does not.
Organisations are, in general, well-designed for acquisition. The onboarding process—the creation of an account, the establishment of a relationship, the capture of information required to begin providing a service—is typically smooth, well-documented, and executable by frontline staff without uncertainty. The system knows how to begin.
It does not know how to end.
This asymmetry is not accidental. The systems are built to retain customers, to maintain accounts, to ensure continuity of relationship. Churn is a problem to be minimised. Account closure is, from the system’s perspective, a failure—something to be prevented, delayed, or at least made sufficiently inconvenient that it doesn’t happen. The training, the incentives, and the procedures all point in the direction of continuation.
Death does not continue. It stops. It requires the system to do something the system is not designed to do—to close, cleanly and completely, a relationship that was intended to be ongoing. The system encounters this requirement and, in many cases, does not have the tools to meet it.
One organisation, notified of my wife’s death, attempted to charge me to keep her account open. The charge was the standard monthly fee. The account was hers. She was dead. The system’s default operation—generate monthly charge, apply to account—had continued past the point at which its continuation made any sense, because no one had intervened to stop it and the system had no mechanism for stopping itself.
The account continued. The person had not.
In the absence of a defined process, the bereaved person becomes the process.
This is the burden that the system’s unpreparedness transfers, invisibly and without acknowledgment, to the person least equipped to carry it. The bereaved person—who is managing grief, legal administration, the practical requirements of settling an estate, and the sustained emotional difficulty of a period that is genuinely one of the hardest in a human life—becomes the navigator of a system that should be navigating itself.
They explain the situation to each organisation. They explain it again when transferred. They correct the staff member who is about to process a charge that should not be processed. They initiate the account closure that the organisation should have initiated. They follow up when the process stalls, which it frequently does, because stalling is what a process does when it has no clear owner and no defined endpoint.
I have, on two occasions separated by thirteen years, done this work. The work is not technically complex. It is administratively detailed, time-consuming, and emotionally exhausting in the specific way that doing practical tasks while grieving is exhausting—because the tasks require a quality of attention that grief makes difficult, and because the tasks are a constant reminder of the administrative trace left by a person who is no longer there.
The trace is extensive. A modern life generates a significant number of accounts, memberships, subscriptions, and contracts. Each one requires a separate notification. Each notification begins a separate process—or, in many cases, does not begin a process at all, but requires the bereaved person to supply the process from their own resources.
The banks, in my experience, are an exception worth examining because they demonstrate that the alternative is possible.
A bank with a defined bereavement process knows, at the moment of notification, what will happen next. There is a bereavement team. There is a sequence of steps. There is someone whose role is to own the process from notification to resolution. The bereaved person is guided through what is required of them—which documents, which timelines, which aspects of the estate will be handled by the bank and which require external action. Some banks extend support beyond the transactional: information about counselling services, acknowledgment that the process may take time, a named contact for further questions.
This is not generosity. It is competence. It is an organisation that has recognised death as a known event requiring a defined response and has built that response into its operations. The result is a process that functions—not without difficulty, because the subject is inherently difficult, but without the additional difficulty of a system that doesn’t know what to do.
The contrast with unprepared organisations is not a contrast in values. It is a contrast in design. The unprepared organisation is not indifferent to the bereaved. It is simply not ready—its systems, its training, its frontline procedures all oriented toward the continuation of relationships rather than their end, in a way that leaves the endpoint unaddressed.
Death is treated as an exception. It is a certainty.
The preparation is not complicated. It requires the recognition that death will occur among the customer base, at a predictable rate, and that each occurrence will require the organisation to do something specific and defined. It requires the translation of that recognition into a procedure—a sequence of steps, assigned to people who know they are responsible for them, executable from the moment of notification to the moment of resolution.
It requires training frontline staff not only in the emotional register of bereavement—the sympathetic tone, the careful language—but in the procedural one. What happens after the sympathy. Who owns the next step. What the bereaved person needs to know and when they need to know it.
It requires the design of systems that can stop, not only continue. Account closure as a defined state, reachable without the bereaved person having to force the system into it.
None of this is beyond the capacity of organisations that can design onboarding processes, billing systems, and customer retention programmes of considerable sophistication. The capability exists. The application of it to the endpoint of the customer relationship has, in many cases, not been made.
Death closes the life. In many organisations it does not close the account, the subscription, the membership, or the relationship—not without sustained effort from the person who has just experienced the loss.
The system responds. It does not resolve.
Sympathy is provided. Procedure is not.
Death is certain. The response is not.
The system knows how to begin a relationship with a customer. It does not, in many cases, know how to end one—and has transferred the responsibility for ending it to the person for whom the ending is most present, most personal, and most difficult to manage alongside everything else the ending requires.
The system continues. The person has stopped.
The account remains open. That is the mismatch.
