3–5 Nov 2026ICT & Logistiek 2026Jaarbeurs, Utrecht · We'll be there!
Learn more
Blog
Back to platform24.aiRequest a pilot
Contemporary office setup with a computer, coffee, and parcels on a wooden desk.Operations
Photo by Tima Miroshnichenko on Pexels

10 min read

Written by

Tribal Knowledge in Logistics: What Your Operation Loses When a Dispatcher Leaves

Tribal knowledge in logistics is the unwritten operating logic that lives in people rather than core systems. It consists of the specific rules dispatchers apply to operational exceptions that transport management systems treat as standard transactions. When an experienced dispatcher leaves, the company retains its transactional order records but loses the operational reasons and custom customer arrangements behind those records.

Key takeaways

What is tribal knowledge in logistics?

Tribal knowledge is the unwritten set of rules experienced people apply without thinking. In logistics, it’s almost entirely about exceptions: the cases the system of record treats as normal, but the operation doesn’t.

A few examples of what it sounds like on a dispatch desk:

None of these sits in a field the TMS checks. All of them change what a dispatcher does next.

Why does logistics run on tribal knowledge?

Logistics runs on tribal knowledge because systems record transactions, and people handle exceptions. A TMS knows an order exists, where it’s going and what status it should have. The arrangements made around that order live in conversations: a call promised to the customer, a tolerance agreed by phone, a workaround for a site under construction.

Those rules pile up faster than anyone documents them. Every new customer, incident and carrier adds a few. Most operations respond to growing volume by hiring people who learn the rules by sitting next to someone who already knows them. That’s why headcount tends to grow in step with volume, a pattern we cover in how to reduce dispatcher workload without hiring in lockstep.

What does an operation lose when a dispatcher leaves?

You lose the reasons, not the records. The orders, statuses and invoices stay. What goes is why things were done the way they were.

That’s becoming urgent in European transport. According to the European Labour Authority’s 2025 analysis of the sector, 38% of people working in EU land transport in 2024 were aged 50 to 64, five points above the economy-wide average, while under-40s made up just 34%. The report describes an ageing workforce that younger workers aren’t replacing fast enough. Every retirement takes a share of the operation’s unwritten rules with it.

The size of that share is harder to measure, but one US study gives a sense of scale. In Panopto’s Workplace Knowledge and Productivity Report, a 2018 survey of 1,001 US employees run with YouGov, 42% of the knowledge people need to do their jobs was unique to them and not shared by any colleague. Our view is that a dispatch desk runs higher than that, because so much of the job is handling exceptions.

Speed on exceptions

The new person handles routine loads fine and stalls on everything else, because each exception means asking a colleague or learning the hard way. Panopto’s respondents also reported losing 5.3 hours a week either waiting for information from colleagues or recreating knowledge that already existed somewhere in the organisation.

Arrangements with customers

Promises made by phone disappear with the person who made them. The customer usually notices before you do, when the call they were promised doesn’t come.

Money

Some tribal knowledge is billing knowledge, such as which waiting time was agreed as chargeable and which customer pays for a redelivery. When that leaves, charges quietly stop being invoiced. We cover where that money goes in revenue leakage in logistics.

Concentration of risk

Each departure leaves the knowledge with fewer people. The remaining senior dispatchers become the escalation point for everything, which makes the next resignation hurt more than the last.

Is your operation running on tribal knowledge?

A few signs that it is:

Why don’t SOPs and handover documents fix it?

Asking experienced people to write down what they know is the least reliable way to capture it. It’s well-intended, but it fails for predictable reasons.

People don’t know what they know. The rules they apply most often are the ones they’ve stopped noticing, so those are the first left off the list. Documents also describe the process as it was designed, not as it runs on a Tuesday when two trucks break down. They go stale the moment a customer changes a requirement. And handovers usually happen in someone’s last two weeks, when they’re busiest and least focused.

Interviews help, but they share the same limit. You only capture what the expert remembers to say.

Where does tribal knowledge actually live?

Tribal knowledge lives in people’s heads, but it also leaves a trail. Every time a dispatcher applies an unwritten rule, it shows up somewhere: a message to a driver, a call to a receiver, an email to a customer, a status changed at an unusual hour. Over months, that trail records the decisions and often the reasons behind them.

This is the part most discussions of tribal knowledge miss. The trail is readable at scale. In one live deployment for a leading US last-mile delivery operator, around 9 in 10 incoming messages are classified automatically, across roughly 2,000 messages a day. Classification isn’t the same as resolving a request, but it shows that the conversation layer can be read as data rather than left as noise.

Reading that history can also surface what nobody on the team had put into words. Across about 1.3 million orders we analysed for the same operator, we found a roughly 50% spike in cancellations and traced it to its root cause, a driver shortage, which their standard reports never showed. The team had been working around the problem for some time. Nobody had written it down.

How do you capture tribal knowledge before it walks out?

Start from the trail, not from a blank document. This method works whether or not you use any software:

  1. Pick one desk or one customer. Trying to capture the whole operation at once produces a long document nobody reads.
  2. Collect the trail for that scope. Gather a few weeks of chats, emails and call notes alongside the TMS export.
  3. Look for repeated decisions. The same kind of message followed by the same kind of response is a candidate rule.
  4. Write each rule in plain language. State the trigger, the action and the exception: “if this, do that, unless…”.
  5. Have your experienced dispatchers review the rules rather than write them. Correcting a draft is much easier than writing from memory, and it’s where the missing exceptions come out.
  6. Decide what each rule becomes. It might be a line in a checklist, a prompt to a dispatcher at the right moment, or an automated step with a person approving anything unusual.

How does Platform24 approach tribal knowledge?

We build on the operation’s own logic, extracted from its data, chats and calls rather than taught to a generic model from the outside. We don’t watch one person at a desk. The extracted rules are written down, readable and editable by the operation. They don’t stay locked inside a tool that only works while it’s switched on.

AI agents then act within those rules. A person signs off on anything unusual, and every action is logged. That’s what lets the knowledge outlast the person who held it. It also means a new hire can read why the desk works the way it does, instead of absorbing it over months.

If tribal knowledge is a risk you’re watching in your own operation, learn more about how Platform24 works. For the wider picture, see our guide to AI in logistics. On how to test any of this safely, see why AI pilots fail in logistics and are AI agents reliable?.

FAQ

What is tribal knowledge in logistics?

Tribal knowledge in logistics is the unwritten operating logic experienced staff apply without thinking: which customer needs a call before delivery, which carrier only answers on WhatsApp, which receiver closes early on Fridays. It sits outside the TMS, mostly concerns exceptions, and leaves the business when the people who hold it do.

Why is tribal knowledge a growing risk in European transport?

The people who hold it are retiring faster than they’re being replaced. The European Labour Authority’s 2025 sector analysis found that 38% of EU land transport workers were aged 50 to 64 in 2024, five points above the economy-wide average, while under-40s made up only 34%.

What does a logistics operation lose when a dispatcher leaves?

It loses the reasons behind decisions, not the records. New staff stall on exceptions, customer arrangements agreed by phone disappear, and charges such as agreed waiting time or redelivery fees can stop being invoiced. Each departure also leaves the remaining knowledge with fewer people.

Why don’t SOPs capture dispatch knowledge?

SOPs describe the process as designed, not how it runs when exceptions pile up. Experienced dispatchers apply their most common rules automatically, so those are the first left out when they write documentation. Handovers also tend to happen in someone’s final weeks, when they’re busiest.

How can you capture tribal knowledge before a dispatcher leaves?

Start from the trail the work leaves rather than a blank document. Collect a few weeks of chats, emails and call notes for one desk, look for repeated decisions, and write each as a plain rule with its exception. Then have experienced dispatchers review the rules instead of writing them.

Sources

Tags

  • operations
  • dispatching
  • logistics management