By Vincent Howard, CPA | Managing Partner, Howard, Howard and Hodges | Skillability for Accounting Firms
Last updated: 2026 | 12-minute read
TL;DR — The Short Answer
To retain knowledge when staff leave, you have to accept an uncomfortable truth first: you can’t keep most of it by writing it down. Critical firm knowledge is mostly tacit — the judgment, shortcuts, and client context that live in a person’s hands and can’t be fully captured in a manual. 48% of companies lose institutional knowledge with every departure, and knowledge workers already burn 5.3 hours a week hunting for or recreating information that left with someone else. The only durable defense is to stop concentrating knowledge in individuals and start distributing it across your team through structured development — so that when someone leaves, the firm has already built the same capability into others, before the resignation letter arrives.
Documentation, cross-training, and offboarding interviews all help — but they’re rear-guard actions. The firms that don’t fear departures are the ones where capability was systematically built into the team all along, not trapped in the head of whoever happens to know how to do the thing. This guide covers both: the capture tactics that limit the bleed, and the development system that prevents the wound.
Who I Am and Why You Should Listen
I’ve been in public accounting since 1990. I founded my own firm in 1993, merged it in 2001 to form Howard, Howard and Hodges, and grew it from three people to 50 staff across four locations and multiple states. Our firm was named PASBA Firm of the Year.
I’ve been burned by knowledge walking out the door more times than I’d like to admit. Early on, my firm ran the way most do: the person who set up a client’s books was the only person who truly understood them, the senior who handled a complex return carried the whole logic in their head, and when any of them left, we scrambled. The clients felt it. I felt it. What finally fixed it wasn’t a better wiki — it was rebuilding how we develop people, so capability lived in the firm rather than in individuals. Since 2020 I’ve built a staff-development platform that more than a thousand accounting professionals across dozens of PASBA member firms have moved through, and the data made one thing undeniable: the firms that don’t fear resignations are the ones that distributed knowledge on purpose. This article is what that taught me.
The Real Cost of Knowledge Walking Out the Door
When a staff member leaves, the replacement cost everyone quotes — recruiting, onboarding, ramp-up — is only the visible part. The expensive part is the knowledge that leaves with them.
The data is sobering. 48% of companies lose institutional knowledge with each departure, and 59% report customer impact from key employee exits. Knowledge workers spend an average of 5.3 hours per week waiting for information from colleagues or recreating undocumented knowledge that already existed — a number that spikes when the person who held that knowledge is gone. At the largest scale, Fortune 500 companies lose at least $31.5 billion a year from failure to share knowledge.
For accounting firms, the knowledge loss is acute because so much of the work is judgment-based and client-specific. When a senior leaves, they don’t just take a skill — they take the context of your clients: why this one’s books are structured oddly, which one always needs the extension, the workaround for that one entity’s payroll quirk. As one retention analysis put it, departing veterans take “relationships, context, and tacit knowledge that can never be fully documented or transferred”.
The brutal part: this cost rarely appears on any spreadsheet. The departure shows up as a replacement-cost line item. The knowledge hemorrhage shows up as months of slower work, repeated mistakes, and frustrated clients — and nobody traces it back to the person who left in March.
Why You Can’t Just “Document Everything”
The instinctive fix is documentation: write down the processes, build the wiki, create the SOPs. It’s necessary — but it fails as a complete solution, and understanding why is the key to everything else in this article.
Knowledge comes in two types, and they behave completely differently:
📄 Explicit Knowledge
The documentable stuff: procedures, checklists, the steps to file a return, where files live. This you can write down — and should. Documentation captures it well.
🧠 Tacit Knowledge
The judgment: knowing a number looks wrong before you can say why, how to handle a nervous client, the efficient way to navigate the software. This resists documentation — it lives in the hands, built through practice.
Here’s the problem: in an accounting firm, the tacit knowledge is the valuable knowledge. Anyone can follow a checklist to attempt a bank reconciliation; the value is in the judgment to know when it’s wrong and why. And tacit knowledge is precisely what a departing employee takes that no SOP can hold. You can document the explicit layer perfectly and still lose the part that mattered.
This is why “document everything” feels productive but leaves firms exposed. The wiki captures the 20% that was never the risk and misses the 80% that was. Real knowledge retention requires a different strategy — one aimed at the tacit layer.
The Real Answer: Distribute Knowledge, Don’t Just Store It
If tacit knowledge can’t be fully written down, it can only be retained one way: by living in more than one head. The strategic goal isn’t to capture what your experts know — it’s to make sure they’re not the only ones who know it.
This reframes knowledge retention entirely. The question stops being “how do we record what Sarah knows before she leaves?” and becomes “how do we make sure three other people can do what Sarah does, long before she gives notice?” That’s not a documentation project. It’s a development one.
A firm that systematically develops its people — building the same capabilities into multiple staff through structured, hands-on practice — is a firm where any single departure is survivable, because the tacit knowledge was distributed by design. The departing employee’s judgment isn’t unique; it was built into others through the same structured experience. This is the difference between a firm that fears resignations and one that absorbs them.
You don’t retain knowledge by storing it in a system. You retain it by building it into people — plural — before you need to.
And there’s a compounding benefit: the same structured development that distributes knowledge also reduces departures in the first place. Structured development cuts first-year turnover by 30–40%, because people stay where they’re visibly growing. So the strategy that protects you when staff leave is the same strategy that makes fewer of them leave. (See why turnover is a training problem, not a salary problem.)
A 5-Part Knowledge Retention Strategy for Accounting Firms
Combine the capture tactics (for explicit knowledge) with the distribution strategy (for tacit knowledge):
1. Build capability into multiple people from day one
The foundation. Structured onboarding and development that puts every staff member through the same hands-on training — processing real client scenarios, gated by assessments — means core capability is distributed across the team by default, not concentrated in whoever happened to learn it first. This is tacit-knowledge retention built into how you develop people. (See how to train accounting staff: the complete guide.)
2. Document the explicit layer — and keep it current
Do write down what’s writable: client setup notes, recurring processes, software workflows, login and access maps. The key is keeping it living — stale documentation is worse than none because it teaches the wrong thing confidently. Tie documentation updates to a regular cadence, not a one-time heroic effort that rots within a year.
3. Cross-train so no client is a single point of failure
For every key client and every critical process, make sure at least two people can handle it. The cost of cross-training is a few hours; the cost of a single-point-of-failure client when the only person who understood it resigns is the client itself. Rotate responsibilities deliberately so knowledge spreads through use, not memos.
4. Capture tacit knowledge through practice, not interviews
You can’t extract judgment in an offboarding interview — but you can build it in others through structured practice that mimics the real work. Having staff develop inside realistic simulated client scenarios is how tacit judgment transfers: they build the same instincts the departing expert had, by doing the same work under the same conditions. This is the part documentation can’t reach, addressed the only way it can be.
5. Run a real offboarding process when departures do happen
When someone gives notice, you’re in damage control — but a structured offboarding still recovers a lot: a documented handover of their clients and in-flight work, joint client introductions to whoever’s taking over (so relationships transfer, not just files), and a debrief on anything undocumented. This is the rear-guard action, valuable precisely because the first four steps limited how much is at stake by the time you reach it.
Capture vs. Distribute: Two Approaches to Knowledge Retention
| Capture (document & store) | Distribute (develop people) | |
|---|---|---|
| Works for | Explicit knowledge (processes, steps) | Tacit knowledge (judgment, context) |
| Captures the valuable 80%? | No — misses tacit judgment | Yes — builds judgment in others |
| Survives a sudden exit? | Partially | Yes — capability already distributed |
| Also reduces turnover? | No | Yes — 30–40% lower first-year turnover |
| Best role | Necessary supplement | The core strategy |
The takeaway: capture and distribute aren’t competing strategies — but most firms over-invest in capture (the wiki) and under-invest in distribute (developing people), which is exactly backwards relative to where the valuable knowledge lives.
Frequently Asked Questions
How do you retain knowledge when an employee leaves?
The durable answer is to distribute knowledge across multiple people before anyone leaves, rather than relying on capturing it afterward. Most valuable firm knowledge is tacit — judgment, client context, and instinct that can’t be fully documented — so it can only be retained by living in more than one person’s head. The strategy: build the same capabilities into multiple staff through structured, hands-on development; document the explicit layer (processes, workflows) and keep it current; cross-train so no client or process has a single point of failure; transfer tacit judgment through realistic practice rather than interviews; and run a structured offboarding (handover, joint client introductions, debrief) when a departure does occur. Capture limits the bleed; distribution prevents the wound.
Why isn’t documentation enough to prevent knowledge loss?
Because documentation only captures explicit knowledge — the writable steps and procedures — while the most valuable knowledge in an accounting firm is tacit: the judgment to know a number is wrong, how to handle a difficult client, the efficient way to navigate the software. Tacit knowledge is built through practice and lives in a person’s hands; it resists being written down. A firm can document its processes perfectly and still lose the judgment layer that actually mattered when an experienced person leaves. Documentation is necessary for the explicit 20% but misses the tacit 80%, which is why knowledge retention requires developing capability in multiple people, not just storing procedures.
What is the difference between tacit and explicit knowledge?
Explicit knowledge is documentable and transferable in writing: procedures, checklists, the steps to complete a task, where files are stored. Tacit knowledge is experiential and judgment-based: knowing when something looks wrong before you can articulate why, reading a client’s concerns, the muscle memory of navigating software efficiently. Explicit knowledge can be captured in manuals and wikis; tacit knowledge can only be built through hands-on practice and lives in the individual. In accounting firms, tacit knowledge is usually the more valuable and more vulnerable type, because it’s what departing experts take with them and what no documentation can fully preserve — making structured, practice-based development the only reliable way to retain it.
How much does losing institutional knowledge cost a firm?
More than most firms measure. 48% of companies lose institutional knowledge with each departure, and knowledge workers spend an average of 5.3 hours per week recreating or hunting for undocumented information — time that spikes after a knowledgeable person leaves. Replacement cost alone runs 30% to 400% of the departed employee’s salary, but that figure excludes the harder-to-trace knowledge cost: slower work, repeated mistakes, and disrupted client relationships (59% of companies report customer impact from key departures). The true cost is usually invisible on the spreadsheet because it shows up as months of reduced productivity rather than a single line item, and it’s almost always higher than replacement-cost formulas capture.
How do you transfer knowledge from a departing employee?
Through a structured offboarding process, while recognizing its limits. The recoverable steps: a documented handover of the person’s clients, in-flight work, and undocumented quirks; joint client introductions so relationships transfer to the successor rather than walking out the door; and a debrief capturing anything not already documented. However, an offboarding interview cannot extract years of accumulated judgment in a few weeks — which is why the real protection is built earlier, by developing the same capability in multiple people before the departure. Offboarding is damage control; its effectiveness depends entirely on how much knowledge was already distributed across the team beforehand.
Can you prevent knowledge loss before employees leave?
Yes, and it’s the only fully effective approach. Preventing knowledge loss means ensuring critical capability and judgment exist in more than one person before anyone gives notice. The methods: structured development that builds the same skills into multiple staff through hands-on practice; deliberate cross-training so every key client and process has at least two capable people; living documentation of the explicit layer; and a culture of distributed rather than hoarded expertise. As a bonus, the same structured development reduces departures in the first place — cutting first-year turnover by 30–40%, because people stay where they’re visibly growing. The strategy that protects you from knowledge loss is the same one that reduces how often you face it.
The Bottom Line
Every firm eventually loses people — that’s not the problem you can solve. The problem you can solve is whether their departure takes irreplaceable knowledge with it. And the firms that have solved it didn’t do it with a better wiki. They did it by accepting that the valuable knowledge is tacit, that tacit knowledge can’t be stored, and that the only way to keep it is to build it into more than one person before anyone leaves.
Documentation, cross-training, and offboarding all matter — they limit the bleed. But they’re rear-guard tactics around a problem that’s won or lost much earlier, in how you develop your people. A firm that systematically distributes capability across its team doesn’t lie awake worrying about resignations, because no single person is the only one who knows how to do anything that matters. That’s not luck. It’s design.
You can’t stop people from leaving. You can stop their knowledge from leaving with them — but only if you built it into someone else first. Knowledge retention isn’t a documentation problem. It’s a development one.
Want to make sure no single person is the only one who knows how to do the work?
Book Your Free 10-Minute Structural Alignment Review →
In ten minutes we’ll show you how structured development distributes capability across your team — so the knowledge that usually walks out the door is already built into the people who stay — running inside the software your firm already uses.
Our 45-Day Out-of-Pocket Performance Guarantee: Put your next hires through our system — if it doesn’t improve your onboarding, we’ll refund your investment.
To your firm’s capacity,
Vincent Howard, CPA
Managing Partner, Howard, Howard and Hodges
Skillability for Accounting Firms
About the Author
Vincent Howard, CPA has practiced public accounting since 1990. He holds a Master’s degree in Taxation from the University of Central Florida, leads a 50-person multi-state firm, and built the Skillability staff development platform used by accounting firms nationwide through the PASBA network. Howard, Howard and Hodges was named PASBA Firm of the Year and has offices in Lake Mary, Sarasota, and Winter Springs, Florida.
© 2026 Skillability for Accounting Firms. 45-Day Out-of-Pocket Performance Guarantee applies to qualifying onboarding engagements. Contact us for full terms.