How Can I Reduce Key-Person Risk Before Selling My Business?

Start with dependencies, not personnel files

A personnel list tells a buyer who works in the business. It does not show what would stop if a particular person became unavailable. Build a dependency map around work and decisions. For each core process, record the accountable owner, the backup, the systems used, the records consulted, the approvals required, and the consequence of a missed or delayed step.

Include dependencies that are easy to overlook: pricing exceptions, scheduling, vendor ordering, customer renewals, field dispatch, payroll inputs, bank access, license renewals, quoting, collections, and escalation decisions. Then mark where the owner or one employee is the only person who knows the context. This turns a vague concern into a finite remediation list. A useful map distinguishes knowledge concentration from formal authority. Someone may know how to solve a problem without being authorized to approve the solution, while another person may hold approval rights without understanding the operating facts. Both gaps matter.

Rank roles by impact and vacancy risk

Do not try to eliminate every single-person dependency at once. Rank each role or responsibility by two questions: how much operating disruption would an absence cause, and how difficult would it be to replace the capability? The Department of Commerce succession guide uses a similar framework by identifying key positions, assessing position risk, documenting success criteria, and evaluating competency gaps [2]. Its public-sector context is different from a privately held company, so use the method as a planning model rather than as a requirement.

A practical owner review can classify items as critical, important, or routine. Critical items need a named backup and a tested handoff before you market the business. Important items need current documentation and cross-training. Routine items can follow normal operating procedures. Revisit the ranking after a new customer, system, location, service line, or regulatory obligation changes the business. Risk is not static, and a plan that was accurate last year may now omit a new dependency.

Delegate authority with clear boundaries

Cross-training is incomplete if the backup can perform a task but cannot make the decision required to finish it. Write down the authority that moves with each responsibility. Specify what the backup may approve, what requires escalation, which records must be updated, and who can act when the primary owner is unavailable. Use thresholds or decision rules only where they fit the business and have been reviewed by the appropriate owner or adviser.

Ready.gov's business continuity template calls for defined roles and responsibilities, lines of authority, succession of management, and delegation of authority [3]. Apply those concepts to ordinary operations, not just emergencies. For example, a customer-service lead might be authorized to resolve a defined class of service issue, while larger credits or contract changes remain subject to a separate approval. The point is not to publish sensitive credentials or give unlimited access. It is to make the decision path explicit and keep access permissions aligned with actual duties.

Cross-train through observed work

A document cannot transfer judgment by itself. Pair the primary owner with the backup while real work is performed. Have the backup complete the task, explain the decision points, and record questions. Then reverse the roles: the backup performs the work while the primary observes and corrects. This exposes exceptions that a polished procedure may omit.

Use a small pilot for each high-risk responsibility. Choose a normal transaction and a deliberately unusual one, such as a rush order, customer escalation, failed payment, staffing gap, or supplier delay. Define the reviewer before the pilot begins. The reviewer checks the result against the source-of-truth records, confirms that required approvals occurred, and records any correction. If the backup cannot complete the pilot without undocumented intervention, stop treating the role as transferred and update the training plan.

Move relationships beyond one person

A business can have documented processes and still depend on one person because customers, suppliers, referral partners, or employees trust only that person. Identify the relationships that materially affect delivery, retention, purchasing, or reputation. For each, record the business purpose, current status, relevant commitments, next expected interaction, and a second internal contact who understands the history.

Make relationship handoffs gradually and honestly. The owner or key employee can introduce the successor, explain the successor's responsibility, and remain available for a defined transition period. Do not imply that a customer or supplier has agreed to a change unless that agreement actually exists. Keep relationship notes factual and proportionate. Avoid copying unnecessary personal information into a sale file, and follow applicable confidentiality, privacy, employment, and contract requirements before sharing records with anyone outside the business.

Document operating routines that another person can run

A useful operating routine answers five questions: what triggers the work, what steps happen in order, what evidence shows completion, what exceptions require judgment, and who reviews the result. Store the current version where authorized users can find it. Link to the system or record of truth instead of duplicating data that may become stale. Include revision dates and an owner for keeping each procedure current.

Start with routines that connect directly to continuity and diligence: opening and closing procedures, order-to-cash steps, service delivery, purchasing, scheduling, payroll inputs, financial close, customer renewals, safety or quality checks, and critical system administration. Add a short exception log. It is more credible to say that a process has known exceptions with assigned owners than to present a generic manual that no one uses. IBBA guidance likewise emphasizes job descriptions, documented operational processes, strategic plans, and organized business records when preparing for a sale [1].

Test the handoff before a buyer tests it

Schedule a practical continuity test. The primary owner steps out of a defined process while the backup runs it using the documented routine and permitted systems. A human reviewer checks accuracy, approvals, customer impact, and record updates. Record the failure points, fix the procedure or training, and repeat the test after a material change. Ready.gov specifically includes manual workarounds, training, testing, exercising, and periodic plan maintenance in its continuity template [3].

Set stopping conditions in advance. Stop the test if it could create a customer, payroll, safety, legal, privacy, or financial error. Stop if the backup needs access that has not been approved. Stop if the source record is missing or contradictory. Escalate the issue to the responsible owner and, where appropriate, qualified legal, tax, accounting, employment, technology, or security advisers. A test is useful because it finds a gap while the owner can still correct it; it is not a certification or guarantee that disruption cannot occur.

Prepare evidence without oversharing

As you prepare for a possible sale, assemble a controlled evidence set. It can include the dependency map, organization chart, role descriptions, authority matrix, operating procedures, training records, continuity-test results, and a list of open remediation items. Each item should have an accountable owner and a review date. Keep sensitive personal, customer, security, and contractual information restricted until the disclosure is appropriate and authorized.

Diligence is a review of whether the business operates as represented. IBBA's buyer guidance says due diligence can cover organizational structure, personnel policies, operations, contracts, technology, and leadership, culture, strategy, and competencies in addition to financial material [1]. That does not mean every buyer receives every internal record at the first stage. It means you should know what supports your statements, who may approve disclosure, and which items require redaction or professional review.

Make the plan part of sale preparation

Key-person risk reduction is an operating improvement, not a last-minute document exercise. Review the map and procedures on a recurring cadence and whenever ownership, staffing, customers, systems, or vendors change. Ask the backup to identify what is unclear. Ask the owner to identify decisions still made from memory. Ask the reviewer whether the evidence would let an informed outsider understand how the business continues.

Early preparation can preserve options because it gives the owner time to develop staff, document operations, and clarify the transition rather than trying to prove continuity during negotiations. IBBA's seller-preparation guidance emphasizes starting early and organizing information before sale terms are negotiated [4]. Tax, legal, employment, privacy, and transaction questions depend on facts and jurisdiction, so discuss those issues with qualified advisers before making a disclosure or committing to a deal structure.

Acquivo is a software platform that delivers the entire sell-side M&A process, valuation, marketing materials, buyer matching, and deal management, on one platform for business owners, M&A attorneys, and boutique investment banks. Acquivo gives business owners the entire sell-side process an investment bank would run, as software, with no success fee. The software is user-operated: the owner and authorized advisers remain responsible for source checks, permissions, review, and decisions.