A founder may describe an experienced employee as the person who keeps everything running. A buyer needs to understand exactly what that means.
If the employee is unavailable, can the company still release an order, correct an invoice, restore a critical application, and explain an exception to a customer? Who can make the necessary decisions? What evidence supports the answer?
Critical employee dependency becomes a transaction concern when essential operating capability cannot be reliably transferred or shared. The practical response is to make that capability visible, establish qualified backup coverage, and demonstrate that the business can use it.
Start With The Work That Must Continue
An organization chart will not reveal every dependency. An operations manager may be the only person who understands a billing adjustment. A developer may know why an integration needs a manual restart. A finance employee may maintain a spreadsheet that determines whether revenue is recognized correctly.
Choose a small set of customer and cash-flow commitments. Follow each through the actual work, including exceptions. Ask where the process stops when a particular person cannot participate.
For each dependency, record the task, business consequence, available workaround, and time before the consequence becomes material. Have the business owner validate those assumptions. A system may remain available while an essential decision or manual step prevents the company from completing the work.
This is a focused extension of the five technology questions before selling your business. It turns a general concern about key people into specific operating questions that management can address.
Separate Four Different Gaps
Several conditions can look like the same staffing problem. They require different responses.
Knowledge
Only one person understands the procedure, the exceptions, or the reason for a recurring adjustment. Capture both the normal steps and the judgment needed when something changes. A recording can help, but someone else still needs to find and use the right instruction.
Access
A second person knows what to do but lacks approved access to the application, account, records, or supplier. Establish company-controlled access and an authorized recovery process. Do not solve the problem by sharing personal credentials or giving everyone broad administrative rights.
Authority
Someone can perform the work but cannot approve the decision. Clarify who may authorize a change, accept an exception, escalate a customer issue, or incur a cost when the usual decision-maker is unavailable. Record boundaries and escalation points.
Capacity
A backup is named but cannot take on the work alongside existing responsibilities. Estimate the actual effort and decide what would pause, who would provide temporary help, or which commitments would change. A name in a continuity plan does not establish usable coverage.
Keeping these gaps separate makes the investment decision more useful. Documentation will not fix missing authority. Another hire will not automatically resolve an account that the business does not control.
Test A Handoff Without Putting Customers At Risk
Select one important task and define what successful completion would look like. Use a safe environment, representative test data, or a supervised exercise appropriate to the consequence of an error.
Have a qualified second person attempt the task using the available instructions and approved access. The usual operator should observe rather than silently rescue every step. Record where help was required, why it was required, and whether the outcome met the agreed standard.
The exercise should include a realistic exception. Completing a routine import is useful evidence, but it may not show whether the backup can recognize a rejected record, stop an unsafe retry, or identify the person authorized to decide what happens next.
Do not manufacture a production outage or remove an employee's access to prove a point. Agree on stop conditions and a recovery path before testing. Where a realistic exercise cannot be completed safely, document that limitation and choose another way to assess the remaining uncertainty.
Give Management A Small Evidence Record
A useful dependency register can fit into a working spreadsheet. Keep sensitive operating instructions and access details in controlled systems, with references rather than credentials in the register.
For each critical task, include:
- The customer or operating commitment it supports.
- The primary operator, qualified backup, and accountable executive.
- The knowledge, access, authority, and capacity gaps.
- The most recent handoff exercise, scope, result, and remaining limitation.
- The corrective action, resources required, owner, and target date.
- The decision needed if the gap cannot be closed in time.
Report demonstrated capability separately from planned work. “Backup assigned,” “procedure written,” and “backup completed the task successfully” describe different states. A buyer should be able to understand which state the company has reached without relying on reassuring language.
Use the broader technology debt due diligence readiness framework to connect this record to other transaction dependencies rather than creating a separate list that nobody maintains.
Choose A Proportionate Response
Some dependencies can be reduced through cross-training, clearer instructions, and better access arrangements. Others may require external specialist coverage, a change in responsibilities, or simplification of an unnecessarily fragile process.
Compare the options against the business consequence and the transaction timetable. Include the time of the experienced employee, who may already be supporting daily operations and diligence requests. Training a backup requires protected capacity on both sides.
Retention arrangements may support continuity during a transition, but they should sit alongside an operating plan. They do not demonstrate that another person can run the work. Likewise, replacing a critical application immediately before a sale may introduce more delivery risk than a controlled handoff and a documented improvement plan.
For a founder, the decision may be which gaps to close before approaching buyers. For an investor, it may be which capabilities must remain in place through closing and which can change afterward. For a board, it is whether management's plan addresses the consequence, has adequate resources, and has been tested to a useful standard.
Treat The Employee As A Partner In The Solution
The person holding essential knowledge may have kept the business functioning despite years of limited capacity or unclear ownership. Approach the review as an effort to strengthen the operation and reduce that burden.
Explain the purpose, agree on protected time, and recognize the contribution required to transfer knowledge. Avoid framing the exercise as a test of loyalty or an attempt to make someone expendable. Those messages can undermine the cooperation the business needs.
Give management responsibility for the conditions that created the dependency. If the employee cannot step away because every urgent request comes back to them, leadership needs to change prioritization, staffing, or decision rights rather than asking for another document after hours.
Bring A Defensible Answer To Diligence
Before describing a critical dependency as resolved, ask for the evidence of what someone else can now do, under what conditions, and with which limitations. Have the relevant executive review unresolved gaps with the transaction team and appropriate advisers. Share sensitive personnel and operating information only through the agreed process.
Start with one consequential workflow this week. Identify where knowledge, access, authority, or capacity depends on one person. Assign an owner and arrange a safe handoff exercise. Use the result to decide what needs to change.
Experienced people should remain valuable because of their judgment and contribution. The business becomes easier to evaluate and operate when its essential capabilities can be understood, supported, and carried forward by a qualified team.