When the key person is out

Most small businesses depend on one or two people to keep working: the owner, a senior employee, a long-tenured manager, sometimes a single vendor. When that person is suddenly unavailable, the work either continues or it does not. Cross-training helps. Documented procedures help. Neither closes the gap by itself.

Take the scan The full continuity picture

Quick answer

What happens when a key employee is out?

When a key employee is out, the recurring work they personally carried slips unless that work has been moved into a system with a defined cadence, named backup, and proof at completion. The team continues at a degraded standard, the slips are usually invisible until something compounds, and in a sale the gap shows up as a 10 to 25% key person discount.

Removing the dependency is structural, not just cross-training. See the continuity hub or take the scan to find which task breaks first when they are out.

What “the key person” usually means

In small businesses, the key person is rarely a single named role. It is usually a pattern of one specific human who holds a stack of recurring work the business needs but has not formalized. The morning open. The Friday close. The vendor relationships. The handful of clients who only work with them. The end-of-month numbers.

When that person is out for a week, three or four of those threads slip. The team continues, but at a degraded standard. The slips are usually invisible until something compounds. (This is the same pattern that drives owner dependency when the key person is the owner.)

The financial cost of key-person risk

For a sale specifically, this risk shows up as a key person discount of 10 to 25% in formal valuations. The discount is established business valuation practice and is recognized by the IRS. It is applied because a buyer cannot be sure the business will continue at the same standard once the key person is no longer there.

The discount disappears not when the business has a continuity plan, but when the operational record shows the business actually ran consistently without that person carrying it. (See preparing the business to sell for what that record looks like in diligence.)

What it takes to remove the dependency

01
Identify which recurring tasks the key person actually carries.
Not "their job description." The specific tasks they remember to do, the calls only they answer, the steps only they get right.
02
Define each task as a process: owner, backup, cadence, proof.
Once defined, the task can run the same way whether the key person is there or not.
03
Watch one week of running.
See what holds and what does not. Adjust the proof requirement or the backup until it does hold.
04
Repeat for the next task.
The dependency reduces one task at a time, not all at once.

When the named backup is also out, the chain has to keep moving (see no backup for the backup).

Try one of the key person's tasks as a process

Pick the recurring task that breaks first when they are out. fullyOS turns it into an owner, a backup, a cadence, and what proof of completion looks like.

Take the scan Request an Operating Review

Key-person-out questions answered

What is key-person risk?

Key-person risk is the operational and financial cost of a business depending on one person to keep working. The person could be the owner, a senior employee, or a vendor. The cost shows up when that person is out: missed work, delayed decisions, and in the case of a sale, a key person discount applied to the valuation.

How big is the financial cost?

In formal valuations, a key person discount of 10 to 25% is standard for private companies. The exact percentage depends on the business, but the discount itself is well-established business valuation practice.

What does it take to reduce key-person risk?

The work the key person carries has to live in the system, not just in their head. That means each recurring task they own has a defined cadence, a documented set of steps, a proof requirement at completion, and a named backup. When all four are true, the business does not stop when they do.

Is this just cross-training?

Cross-training is part of it, but cross-training alone teaches the steps. It does not require the steps to be done. The structural fix is moving the work into a system that requires it, not just into a second person who knows how to do it.

How does fullyOS handle this?

Each process has a primary owner and a backup. When the primary is unavailable, the system moves the work to the backup without anyone asking. The proof requirement at completion means even when the backup is doing the work, the standard does not drop.