The Residence Risk Register

In most professionally governed organisations, keeping track of what could go wrong is a matter of routine. Businesses, hospitals, investment funds and other regulated operations maintain a risk register: a record of foreseeable problems that is reviewed on a schedule rather than rediscovered in a crisis. Its presence quietly shapes behaviour, because a risk that has been written down and assigned is treated differently from one that is only sensed. In private residences the same discipline is applied far less consistently, even though a household at this level carries much of the operational complexity of a small organisation.

A residence employs people, relies on suppliers, runs technical systems, holds irreplaceable assets and carries obligations that have consequences if they are missed. Risk within it is usually addressed through insurance and through the judgement of whoever is in charge. Both matter, and neither amounts to a risk register.

Risk by Incident

The usual approach might be called risk by incident. Rather than being anticipated, risk is handled as it appears. Insurance answers the insurable and security answers intrusion, while much of everything else is absorbed by capable people dealing well with whatever a given week brings. A household run this way can appear to be entirely in control, and often is, until the moment it is not.

The limitation is that responding well is not the same as knowing in advance which problems are most likely and what they would cost. A residence managed by incident is not necessarily exposed to more risk; it is simply less aware of the risk it already holds. A risk that has not been named cannot be weighed, reduced or assigned, and so it waits. Each such unattended exposure is a form of continuity debt, accumulating quietly at no apparent cost until the point at which it has to be met.

What a Maintained Register Considers

The risks that most reward this attention tend to be operational or continuity-related, and they often sit outside the usual focus of insurance and security: knowledge that depends on one person, systems that are undocumented, suppliers relied upon without an alternative, and obligations quietly approaching their expiry. The purpose of a register is not to list these anxieties but to make them specific enough to manage.

For each entry, that means understanding the risk itself and how likely it is, the consequence if it occurred, what already reduces it, who is the accountable person for it, what action is required, and when it should next be reviewed. The discipline comes from established risk-management and business-continuity practice, though it needs none of that vocabulary to be useful. Its value lies less in sophistication than in being written down, kept current and genuinely owned.

A single illustration makes the point. Suppose a residence depends on a specialist system, such as its water treatment or standby power, installed some years ago and maintained by one contractor of long standing, a dependency mistaken for a relationship. The chance of failure in any given month is low, but the consequence is high, and the only real safeguard is that contractor’s continued availability. Recorded properly, this becomes a specific entry: a named responsibility, a note that no serviceable alternative has been identified, an action to qualify a second provider, and a date to review it. Left unrecorded, it remains a quiet assumption that all will hold, until the day it does not.

Responsibility, and Where It Sits

The accountable person is not always a member of household staff, and should not be assumed to be. Some risks can properly be held within the household; others require escalation, budget authority or an outside specialist, and assigning those by default to whoever is nearest simply sets them up to fail. Naming responsibility honestly, including where it lies beyond the household, is part of what makes a register real rather than decorative. It also keeps a clear line between the person accountable for managing a risk and the principal who owns the residence.

Keeping the Register Current

A register written once and filed is not a register; it is the memory of a good intention. The value is in keeping it current. Circumstances move: a renovation introduces new exposures and removes others, an additional residence multiplies them, and a key departure can turn a manageable dependency into an urgent one. A register earns its place only if it changes as the residence changes, which is why the review date matters as much as the original entry.

This is continuity work rather than paperwork, and it belongs with the broader account of how a residence operates. The record of how a house runs and the record of what could disrupt it are two halves of the same understanding. Kept together and kept current, they allow capable people to act with shared knowledge rather than isolated fragments of it.

From Visibility to Protection

Understood this way, the register is not an end in itself. It is how a residence turns a general unease about what might happen into something specific enough to act on. As a matter of operational principle, PRC’s continuity work moves in this order: a residence is first made visible, so that its real state is known, and then made more resilient, by identifying and assigning the things that could disrupt it. The register is where visibility becomes protection. It is a discipline, owned and reviewed as part of running the house, rather than a product or a piece of software.

It is worth the effort for a reason that usually becomes clear only in hindsight. Many of the incidents that seriously disrupt a residence were foreseeable in principle. What was missing was not foresight but a place to bring the warning signs together, to assign them, and to review them before they arrived.