The Question Most Business Leaders Do Not Ask

Business continuity planning has a well-established home at the leadership level.  Most business owners have thought about what happens if they step back, get sick, or exit.  They have considered the succession question, even if they have not fully answered it.  That thinking is healthy and necessary.

But the same rigour rarely gets applied to the operational layer of the business.  And that is where most of the risk actually sits.

Think about the people in your business who carry critical knowledge or perform critical functions.  The person who manages your key supplier relationships and knows which ones need handling carefully.  The team member who understands your scheduling system well enough to keep production moving when things go wrong.  The account manager whose clients would follow them out the door if they resigned tomorrow.  The technician whose experience and judgement is the reason your quality holds up.

Now ask the question: what happens if any one of those people is unavailable tomorrow?  Not eventually.  Tomorrow.

If the honest answer is that the business would struggle, you have a contingency gap.

Why This Happens in Otherwise Well-Run Businesses

The businesses I visited this week were not poorly managed.  They were the opposite.  Strong leadership, clear values, genuine commitment to their clients.  The contingency gap was not a symptom of dysfunction.  It was a symptom of growth.

When a business grows quickly, it promotes or retains its best people and builds processes around them rather than alongside them.  The scheduler who has been there for eight years does not follow a documented process because they are the process.  The account manager who manages the top three clients does not work from a client brief because the relationship exists in their head.  It works, right up until it does not.

There is a second dynamic that compounds this quietly.  In almost every business we work with, the staff interview process reveals the same pattern: people started in one role and are now performing a substantially different one, but the paperwork has never caught up.  Their employment agreement still describes their original position.  Their documented responsibilities reflect where they sat three years ago.  Their authority level has never been formally updated to match what they actually do every day.  The role has grown organically around the person, and nobody has stopped to record what it has become.  This matters for two reasons.  First, when that person leaves, you recruit for the role as it was written, not the role as it was actually performed, and the new person arrives into a gap much larger than they were prepared for.  Second, the undocumented evolution of that role is itself a form of knowledge concentration, because the only person who fully understands what the job now requires is the person doing it.

There is also a human element.  Documenting what a key person does implies that they could be replaced, and that feels disloyal.  Business owners are reluctant to raise it with the person directly, and the person themselves rarely flags their own replaceability as a risk.  So the gap stays open, invisible and unaddressed, until something forces the conversation.

Usually that something is a resignation, an illness, or a personal crisis.  By then, the cost is already accumulating.

What the Gap Actually Costs

The cost of a contingency gap is not just the disruption caused by one person’s absence.  It is the accumulated cost of operating a business where critical knowledge and critical functions are concentrated in individuals rather than embedded in systems.

Operational Disruption

When a key person leaves or becomes unavailable, the immediate cost is visible.  Production slows, clients experience delays, the team burns time and energy covering a gap they were not prepared for.  In a manufacturing or production environment, a single unplanned absence in a critical role can cost tens of thousands of dollars in lost output within a week.

Client Risk

The less visible cost is client risk.  When the relationship between a client and your business is mediated primarily by one person, the client’s loyalty is to that person, not to your business.  If that person leaves and joins a competitor, or simply leaves, the client decision is not automatic.  You have to re-earn trust that was already established.  In some cases, you do not get the chance.

Recruitment and Knowledge Transfer Cost

Replacing a key person in an SME is expensive.  Recruitment fees, onboarding time, and the productivity gap while a new person finds their feet are all direct costs.  But the hidden cost is the knowledge that walks out the door and cannot be fully recovered.  A new person can learn the role.  They cannot learn the ten years of institutional knowledge that made the departing person so valuable.

Owner Re-Engagement

When a key person leaves a business that has not built systems around that role, the business owner typically steps back in to fill the gap.  The strategic work stops.  The growth initiatives pause.  The owner who was building toward greater independence from the day-to-day finds themselves back in the middle of it.  That regression is one of the most costly and demoralising outcomes of a contingency gap.

It Is Not Just About People

People are the most common and most acute form of contingency risk in an SME, but they are not the only one.  The same gap exists in other parts of the business, and a rigorous operational review surfaces all of them.

Single Supplier Dependency

Many SMEs operate with a single approved supplier for a critical input.  While the relationship is strong and the supply is reliable, this feels like efficiency.  When that supplier has a production issue, a delivery delay, or a business problem of their own, the dependency becomes a crisis.  Building a secondary supplier relationship before you need it is not disloyalty to your primary supplier.  It is basic operational risk management.

System and Process Concentration

If your business relies on a single system for a critical function and that system goes down, what is the manual fallback?  In most SMEs, the answer is either a spreadsheet that one person knows how to use or nothing at all.  Documenting the manual process before it is needed is a simple precaution that most businesses never take until they need it.

Cash Flow Concentration

When a significant proportion of revenue comes from a small number of clients, the business carries concentration risk that most owners underestimate.  Losing one large client is a commercial event.  Losing one large client when you have no documented plan for how to respond is a crisis.  The contingency question applies to revenue as much as it applies to people.

How to Close the Gap: A Practical Framework

Closing the contingency gap does not require a crisis management plan or an expensive consultancy exercise.  It requires a structured, honest assessment of where your dependencies sit and a deliberate effort to distribute knowledge and capability across the business.  Here is where to start.

Step One: Map Your Critical Dependencies

List every function in your business that would create a significant problem if it were unavailable tomorrow.  Be specific.  Not “sales” but “the person who manages our three largest accounts and holds all the relationship history.”  Not “production” but “the person who runs the scheduling system and knows how to reprioritise when a job falls behind.”

For each dependency, ask three questions.  Who else in the business can perform this function right now?  Where is the knowledge required to perform it documented?  How long would it take to recover if this person or system were unavailable for four weeks?

Step Two: Rate the Risk

Not all dependencies carry the same risk.  A critical function performed by a long-tenured, highly engaged team member with no immediate succession risk is different from a critical function performed by someone who has been job-hunting quietly for six months.  Rate each dependency by two dimensions: the consequence of loss and the likelihood of disruption.  The intersections of high consequence and high likelihood are your priority.

Step Three: Document Before You Need To

For every high-priority dependency, the first response is documentation.  Not a formal manual.  A working document that captures what the person does, how they do it, where the important information lives, and what the decision-making process looks like in the most common scenarios.  It does not need to be perfect.  It needs to exist.

The act of creating this documentation is also a valuable conversation.  When you sit with a key person to document their role, you learn things about how the business actually operates that you did not know.  Those insights are valuable regardless of the contingency risk.

Step Four: Build Redundancy Deliberately

Documentation reduces the knowledge concentration risk but does not eliminate the operational dependency.  The next step is to build practical redundancy.  That means cross-training a second person in critical functions, not to replace the primary person but to ensure the function can continue.  It means reviewing supplier arrangements to confirm alternatives exist.  It means ensuring that the systems your business relies on have a manual fallback that more than one person understands.

Step Five: Review Annually

Contingency gaps are not static.  They shift as the business grows, as people change roles, and as new dependencies emerge.  A structured annual review of your critical dependencies, as part of your operational planning cycle, ensures that the gap you closed last year has not quietly reopened.

What Contingency Actually Looks Like in Practice

When business owners hear the word contingency, they sometimes assume it means having a spare John waiting in reserve.  It does not.  Nobody has a backup scheduler sitting in a drawer.

What contingency actually means is being prepared to act quickly and clearly when the gap opens.  For a key person, that preparation looks like this: an up-to-date role description that reflects what the person actually does today, not what they were hired to do three years ago.  A current position advertisement that could go live within 24 hours of a resignation.  A structured set of interview questions designed to identify whether a candidate can genuinely perform the role as it exists now.  And a documented handover framework that gives a new person the best possible start.

When John hands in his notice, or the bus arrives, the shock is unavoidable.  But an hour later, when the shock settles, the business can open that drawer and start solving the problem.  That is what contingency looks like.  Not a spare person.  A prepared response.

The Leadership Conversation You Are Probably Avoiding

There is a version of this conversation that business leaders find uncomfortable, and it is worth naming directly.  Telling a key person that you are documenting their role and building redundancy around it can feel like you are signalling that they are replaceable or that you do not trust them.  Most business owners avoid having it for exactly that reason.

The reframe is simple.  Documenting a key person’s role and building redundancy is not a statement about their value or their security.  It is a statement about how seriously the business takes its obligations to its clients, its team, and its own continuity.  A business that can only deliver its promises when specific individuals are present has not built a business.  It has built a dependency.

The best people in your business understand this.  They do not want to be the single point of failure.  They want to be part of a business that is robust enough to keep delivering even when things go wrong.  That conversation, framed correctly, is one of the most motivating you can have with a high-performing team member.

Where the Fractional COO Engagement Fits

Identifying and addressing contingency gaps is a core part of what an operational review surfaces.  The FBS diagnostic is structured to ask exactly the kind of questions that reveal where a business is carrying hidden risk, including the people, system, and process dependencies that are invisible until they cause a problem.

In a 1-Day Operational Diagnostic, we map your critical dependencies, identify your highest-priority risks, and give you a clear view of where to start.  For most businesses, the findings from a single day of structured review are enough to drive six to twelve months of targeted improvement.

If a longer engagement follows, the contingency framework becomes part of the operational foundation we build.  Documentation standards, cross-training plans, supplier diversification, and process redundancy are not bolt-on activities.  They are the difference between a business that is built to last and one that is built around the people who happen to be there right now.

The Bottom Line

Two well-run businesses.  Two experienced leadership teams.  One question.  A lot of scratching of heads.

The contingency gap is not a sign of poor management.  It is a natural consequence of growth and the human tendency to build around people rather than alongside them.  But it is a risk that compounds quietly over time, and one that most businesses only discover when the cost has already started accumulating.

The bus does not send a warning.  The resignation letter sometimes does, but not always.  The time to close the gap is now, when it is a planning exercise rather than a recovery operation.

If you would like to understand where your business carries this kind of risk, the 1-Day Operational Diagnostic is the right starting point.  Book a discovery call and we can talk through what a structured review would look like for your business.