Home/Free Tools/Tribal Knowledge Risk Calculator

Tribal knowledge: who's the only person who knows how to do this?

Tribal knowledge is the operational know-how your team carries in their heads rather than in your documentation. Rate 8 processes most DTC teams run every week and see how many break, or are already broken, the moment one specific person is unavailable. No email, no signup.

AY
Anand Yadav · Founder, ReccordSOP
·Last reviewed July 31, 2026

For each one: if the main person left tomorrow, how many people could actually run it?

Refunds & returns

Fulfillment exceptions (damaged or lost shipments, backup carriers)

Chargeback & dispute handling

Escalating an angry or VIP customer

Discount / comp approvals

Inventory reorder decisions

Vendor or supplier communication

Onboarding a new hire on this team

What is tribal knowledge?

Tribal knowledge is the unwritten operational know-how held by individuals on a team rather than recorded anywhere the business can reach. It is the sequence someone follows without thinking, the exception they always catch, the supplier contact only they have, the reason a step exists that nobody else remembers. It is real expertise. The problem is not its quality, it is its location.

The term comes from manufacturing, where it described the shop-floor judgement that never made it into the work instructions. In a DTC business it accumulates fastest in the roles that handle exceptions: the person who knows which chargebacks are worth fighting, who decides when a fulfilment error justifies a reship, who remembers the one warehouse that needs its POs formatted differently.

Tribal knowledge costs you nothing until it moves. Then it costs you all at once, and usually at the worst time: a resignation, a holiday, a sick week during peak. The practical risk is not that the knowledge is undocumented. It is that nobody knows which parts are undocumented until the person holding them is unreachable. That is what this calculator is for.

What this actually measures

This isn't about whether a process is written down somewhere. It's about whether it would survive the one person who actually runs it being gone tomorrow, no notice. A process with a doc nobody follows scores the same as a process with no doc at all, because the real question isn't documentation, it's redundancy.

FAQ

A support lead who knows, without checking anything, which carriers to stop trusting in December, which customers get a reship instead of a refund, and which supplier needs a phone call rather than an email. None of it is written down. All of it is load-bearing. The day that person is unreachable, the decisions still get made, just worse and slower, by someone guessing.

Start where the risk is concentrated rather than trying to document everything. Find the processes only one person can run, then have that person do the work while someone records it, instead of asking them to write a document from memory. People reliably omit the steps they have automated in their own heads, which are the exact steps a newcomer gets wrong. Recording the real run captures the exceptions and the judgement calls that a written draft leaves out.

For each process, you rate how many people could run it if the main person left tomorrow: nobody, just one person, 2-3 people, or it's documented and anyone could pick it up. "Nobody" and "just one person" both count as at risk, since both mean the process breaks or is already broken the moment that one person is gone. Your score is the share of your processes that fall into those two buckets.

The 8 preset processes cover what actually breaks first at most DTC brands: refunds, fulfillment exceptions, chargebacks, escalations, discounts, inventory, vendors, onboarding. Two extra slots let you add something specific to your business without turning this into an open-ended audit that takes twenty minutes.

No. Everything is calculated in your browser. Nothing is collected, nothing is sent anywhere.

Rate it "documented, anyone could" so it doesn't count against you. The calculator is a checklist of the processes that commonly cause this problem, not a mandatory audit of your entire operation.

Related

All free toolsDo you need SOP software?What is SOP driftSOP drift-risk checkerFull SOP software comparison →