One departure, one task that never got reassigned, six missed filings — and a penalty that turned into a seven-figure valuation hit. A case study in what knowledge loss actually costs, and why it's the most preventable risk on the books.
A mid-market private company owned by a private equity firm went through a stretch of turnover in its accounting and finance department. Nothing dramatic — the kind of churn every growing company absorbs. One of the departing team members owned, among many other things, the monthly sales tax filing for the State of New Mexico.
He left. The filing didn't get reassigned. Not because anyone decided it didn't matter — because nobody knew it existed. It lived in his calendar, his head, and his muscle memory. The incoming team member never had the conversation where it would have come up, and the offboarding checklist — to the extent there was one — didn't reach that level of detail.
Sales tax for New Mexico went unfiled for six consecutive months. No system flagged it, because no system knew about it. The state noticed before the company did.
The penalty came to roughly $80,000 — and it was not refundable. Painful, but for a company that size, survivable. The second-order math is where it turned brutal.
The company was owned by a private equity firm, which means it is valued as a multiple of EBITDA. An $80,000 penalty isn't just cash out the door — it's $80,000 straight off EBITDA for the year. At the multiples the company traded against, that single line item translated to roughly $1,000,000 of valuation impact.
One unreassigned recurring task. Seven figures of enterprise value. And the most uncomfortable part for everyone involved: nothing about the failure was exotic. The filing wasn't hard. The deadline wasn't ambiguous. The person who knew about it wasn't negligent — he just left, the way people do, and everything he carried in his head left with him.
The instinctive response to an incident like this is process theater: longer offboarding checklists, mandatory handoff meetings, a policy memo. All of it depends on the same fragile assumption that failed in the first place — that the departing person will remember to mention everything they know, and that the incoming person will remember everything they're told in a two-hour transition call.
The structural fix is different: obligations have to live in a system, not in people. A recurring filing should exist as a recurring task with a named owner, a due date, and automatic notifications — so that when the owner leaves, the task doesn't vanish. It sits there, visibly owned by someone who's gone, which is exactly the signal that forces reassignment. Key person risk doesn't disappear when work is systematized, but it stops being invisible — and invisible is what makes it expensive.
This is the difference between tools that help you do work and systems that remember it. A shared spreadsheet knew nothing when the filer left. A system of record knows everything he was responsible for, everything he completed, and every document he attached along the way.
After the penalty, the company onboarded with Sintris and rebuilt its recurring obligations as a system:
The knowledge-transfer point is the one worth sitting with: even when the incoming and outgoing team members never speak — which is exactly what happened here — the history of task completion, notes, documents, and deadlines is retained for the new person. The handoff conversation is nice to have. The system makes it optional.
Firms that manage obligations for many clients at once live this problem at higher stakes — it's why outsourced accounting teams run every client's calendar in a system with built-in knowledge transfer rather than in per-client spreadsheets. And it's why institutional knowledge that survives turnover is an asset you build deliberately, not a document you write after the fact.
Run the numbers from the other direction. The failure cost $80,000 in cash and roughly $1,000,000 in valuation. The prevention — putting recurring obligations into a system that tracks owners, chases deadlines, and retains history through turnover — costs a few hundred dollars a month and an afternoon of setup.
Most companies don't make that trade until after their version of the New Mexico filing. The ones that make it before are not more disciplined or better staffed. They've just accepted an unflattering truth early: people leave, memories walk out the door, and the only knowledge a company actually owns is the knowledge in its systems.
If your recurring obligations currently live in spreadsheets and heads, it's worth an hour to fix — ideally before the state notices something you didn't.
More from the Sintris blog.
Every operations team has them: the one person who knows how the invoicing system really works, or who owns the vendor relationship no one else understands. Here's how to find them — and fix them.
When people leave, knowledge shouldn't walk out with them. Here's how to capture day-to-day operational data as a transferable, AI-ready knowledge base.
Tax filings, license renewals, data privacy reviews, vendor certifications — these deadlines don't pause because your company doesn't have a compliance function. Here's how operations teams build a system that catches every recurring obligation before it becomes a crisis.
New on operational intelligence, knowledge, and risk — Monday, Wednesday, and Friday.
