Knowledge transfer from a retiring owner: how to capture decisions

How do you capture a retiring owner's knowledge before they leave?

Capture it as decisions with context and outcomes, inside the systems the company already uses, starting at least a year before the owner steps back. Interviews and handover binders help, but the lasting value sits in written decision records: what was decided, why, who agreed and what happened next.

This guide is for succession advisors, CFOs and COOs, and owners planning a transition. It treats knowledge transfer as a project with an owner, a schedule and a place to store the output, not a series of coffee chats.

Why is knowledge transfer a succession risk, not a soft task?

McKinsey estimates that by 2035 about six million US small and medium-size businesses will face ownership transitions as baby boomers retire, and that more than half of small-business owners are over 55. Many of those owners hold relationships, pricing instincts and exceptions in their heads. When they leave, buyers, successors and lenders see an untested business.

Whether the route is an internal buyout, an employee ownership plan or a sale, the successor needs the same thing. The comparison of an ESOP and a third-party sale shows how the route changes who needs to know what.

What knowledge actually leaves with an owner?

The decision record format: Context, Options, Choice, Outcome

Use one lightweight format for every important decision. It takes five minutes and is the most reusable output of the whole project.

• Context: what was happening, and what information was available.
• Options: the realistic alternatives, including doing nothing.
• Choice: what the owner decided and the main reason.
• Outcome: what happened, added later, ideally within 90 days.

Outcomes matter most. A decision without a result is a story; with a result it becomes something a successor can learn from.

Step-by-step: a 12-month knowledge transfer plan

1. Name a project owner other than the retiring owner, usually the CFO, COO or the intended successor.
2. List the 20 decisions only the owner makes. Ask department heads, not the owner, to build the list; they know where the bottlenecks are.
3. Schedule weekly 45-minute sessions. The successor asks questions; a scribe records decisions in the template above.
4. Capture in shared systems. Use the CRM, ticketing, project tool or a shared drive. Avoid private notebooks and personal email.
5. Shift approvals gradually. Move one category of decision at a time from the owner to a named successor, with the owner reviewing for three months.
6. Interview customers and vendors with the owner present and note the commitments made.
7. Close with a dry run. The owner takes a two-week absence. What broke becomes the next list.
8. Preserve everything. Keep email, chat, ticket and CRM archives as they are, and do not delete old data to tidy up.

The longer-term goal links to reducing owner dependence before an exit. If wealth planning is part of your role, concentrated wealth in a private business covers the owner's side of the same timeline.

Why would AI developers care about decision records?

AI is moving from systems that answer questions toward agents that carry out multi-step tasks. Training and evaluating those agents needs records of how real work is decided and finished: the approvals, exceptions, reviews and outcomes that exist only inside companies. A documented decision with a recorded outcome is exactly that kind of record.

That does not mean you should write decisions for a license. Write them for the successor. If the company later qualifies, the same records may become part of what it can license, with the company in control of scope, price and terms. Nothing is binding until the company signs, and de-identification and redaction rules are agreed with the company before any work begins.

What should the successor do in the first 90 days?

• Sit in on every decision the owner still makes and write the record yourself.
• Ask customers and vendors what they rely on the owner for, and note it.
• Take over one approval category outright, with the owner reviewing weekly.
• Keep a list of questions the owner could not answer and find the answer elsewhere.
• Confirm where each system's history lives and who can export it.

What are the common mistakes?

How does this relate to a records license?

Companies with 50+ full-time employees at peak (contractors excluded), several years of documented operations and rights to license their records may qualify for a SourceX introduction. See who qualifies. A license is separate from the succession route, and owners should discuss disclosure and timing with their attorney. Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. The reward is paid only after the buyer pays and SourceX receives its fee; no reward is guaranteed. Advisors should check their own professional rules on referral fees. Those exploring a sale route can see when a business sale falls through and referral opportunities for business brokers.

When this approach is not enough

• The owner refuses to delegate any decisions.
• Records are mostly personal email accounts or paper.
• The business has no successor and no timeline.
• The company is under the size baseline, though the knowledge work is still worth doing.

Next step

Ask the project owner to list the 20 owner-only decisions this month and start the Context, Options, Choice, Outcome log. If the company has several years of records across many systems, run the company fit checker and register as a partner if you want to make an introduction. Advisors who want to win these owner relationships can read how financial advisors win business-owner clients.