TL;DR: To keep rare-lane know-how out of one dispatcher's head, write one short card per unusual lane or customer: equipment, permits and documents, receiver rules, trusted carriers, what went wrong last time. Capture it in five lines after each unusual load, let AI tidy voice memos into the card, and review the cards monthly. Start with the cases nobody else could answer today.
The dispatcher who handles the odd loads is on holiday for two weeks. On Tuesday a regular shipper asks for a flatbed to a construction site that only accepts deliveries before 9:00 and needs the driver to call the site manager from the gate. Nobody else knows the site manager's number, which carrier has the right straps and tarps, or that the last load there was refused because the rate confirmation did not mention the gate call.
Every small brokerage has these cases: special permits, receivers with their own rules, carriers you trust for one awkward lane, customers whose contracts use a particular Incoterms rule. This article shows how to write them down without stopping work. It is part of the wider freight broker marketing guide, because this know-how is a large part of the service shippers come back for.
How this was made: drafted by Miriad with AI assistance; every figure links to its source.
What kind of know-how lives in one dispatcher's head?
The know-how that lives in one head is the exception, not the routine: the receiver who only takes appointments before 9:00, the lane that needs a permit or special document, the carrier who handles oversized flatbed well, the customer who always ships on one delivery term. Routine loads are in the TMS; exceptions are in memory.
A useful way to find it is to ask, for every regular customer and lane: "If you were away tomorrow, what would go wrong first?" The answers tend to fall into five groups:
- Receivers: appointment windows, gate procedures, unloading rules, who to call.
- Permits and documents: oversize permits, cross-border paperwork, declarations for specific goods.
- Carriers: who runs this lane well, who to avoid and why, who to call on a Friday evening.
- Customer habits: delivery terms, invoicing details, who approves rate changes.
- Past failures: what went wrong last time and what fixed it.
Why is it a risk and not just an inconvenience?
It is a risk because the cases that live in one head are the ones that go wrong expensively: refused deliveries, detention, a load given to the wrong carrier. When that person is away or leaves, the brokerage loses the part of its service shippers notice most. The required transaction records do not capture it.
The records a US broker must keep show the gap. For each brokered transaction, a broker must keep the consignor, the carrier name and registration number, the bill of lading number, the compensation received, the freight charges collected and the date paid to the carrier, for three years (49 CFR § 371.3). That record shows what happened on a load. It says nothing about why the receiver refused the first truck or which carrier saved the second.
Carrier knowledge is also a fraud control. TIA describes how criminals impersonate legitimate carriers with stolen USDOT or MC numbers, and recommends disciplined carrier vetting, payment authentication and staff training (TIA, 2026). A dispatcher who "just knows" a carrier is a weak control. A written check that anyone can run is a strong one.
What does a rare-lane card contain?
A rare-lane card fits on one screen and has fixed headings: lane and equipment, documents and permits, receiver rules, trusted carriers, customer habits, last problem and fix, and the date it was last checked. Fixed headings make cards quick to write and easy to scan. The date shows when a card needs checking again.
Lane card: [origin] → [destination], [equipment]
Customer: [shipper], contact [name, phone]
Delivery term: [Incoterms rule and place, if cross-border]
Documents and permits: [list]
Receiver rules: [appointment window, gate procedure, unloading, contact]
Trusted carriers: [name, MC/USDOT or licence, why trusted, last used]
Avoid: [carrier or practice, and why]
Last problem and fix: [date, one line each]
Last checked: [date, by whom]Example (illustrative, not a real case): a card for a monthly flatbed load from a steel stockholder in Birmingham, Alabama to a construction site in Atlanta. Documents: none special, but load must be tarped. Receiver rules: deliveries 06:00–09:00 only; driver calls the site manager from the gate; no unloading after 09:30. Trusted carriers: two named flatbed carriers, one used 9 times this year without a refusal. Avoid: any carrier without tarps listed on the rate confirmation; the March load was refused at 10:15 for arriving late. Last checked: 4 October, by the dispatcher who knows the lane.
How do you capture the know-how without stopping work?
Capture it in small pieces, right after the load that taught it. The person who handled an unusual load writes five lines, or records a short voice memo, the same day. AI turns the memo into the card's headings, and the dispatcher corrects it. Once a month, someone reads the new notes and updates the cards.
The five lines:
- What was unusual about this load?
- What did you do that someone else would not have known to do?
- Who did you call, and what number?
- What went wrong, or nearly went wrong?
- What should the next person do differently?
For cases that already exist only in memory, sit with the dispatcher for half an hour a week and go through past loads: open last quarter's rate confirmations for unusual lanes and ask "what did you know here that is not on this page?" Record the conversation and let AI draft the cards from the transcript.
How do you write down carrier checks so anyone can run them?
Write the carrier check as a short, fixed checklist stored next to the lane cards, with the reason for each step. Anyone booking a new carrier runs the same steps: documents, licence, company verification, call-back on an official number and insurance. The dispatcher's judgement stays, but the steps no longer depend on one person.
Example (illustrative, not a real case): a dispatcher at a Hungarian forwarder finds a cheap truck on a freight exchange for a Budapest to Munich load. Before confirming, she runs the team's one-page checklist: a copy of the carrier's EU community licence; the company verification on the exchange; a phone call-back to the number on the carrier's official records, not the one in the email; and the insurance certificate. The checklist lives in the team's shared knowledge base, so a colleague covering her holiday runs the same steps.
The licence step reflects the rule. International road haulage touching Hungary requires an EU community licence, a CEMT licence or a licence under a bilateral or multilateral agreement (Nemzeti Jogszabálytár, 261/2011 Korm. rendelet). The call-back step reflects the fraud pattern TIA describes: a stolen identity looks right on paper.
Which documents and terms belong in the notes for cross-border lanes?
For cross-border lanes, note the delivery term each customer uses, any declaration their goods need, and the documents carriers must carry. These details change rarely, so they are easy to forget and costly to get wrong. Write them on the lane card with the source and the date checked.
Three examples of what belongs there:
- Delivery terms. Incoterms 2020 contain eleven three-letter rules that set out tasks, costs and risks between seller and buyer (ICC). If a customer always ships on one rule, the card should say so, with the named place.
- Declarations for specific goods. For road transport in Hungary, since 1 January 2021 only goods on the "risky products" lists must be declared in EKÁER, and the EKÁER number is valid for 15 days from issue (NAV, 2021). A card for a lane carrying such goods should say who files the declaration and when.
- Consignment notes. Whether the carrier issues a paper CMR or an e-CMR, and who receives the copy.
Where should the know-how live?
Keep it where the team already works, in one place everyone can search: the notes field of your TMS, a shared document per customer, or a simple knowledge base. The tool matters less than the rule that every unusual lane has one card, and that nobody keeps a private version.
Most brokerages already have the tools. The US occupational profile for cargo and freight agents lists Excel, Outlook, Word, TMS software, web-based dispatch software and brokerage software as typical tools of the job (O*NET OnLine). Pick one of them for the cards. An AI assistant can then read the cards when drafting quotes and status updates, so the know-how shows up in the work, not only in the file.
For how those cards feed quotes, see freight quotes that never book. For which tasks AI can safely take over once the cards exist, see AI for freight brokers. For the full picture, return to the freight broker marketing guide.
If you want the lane cards, carrier checks and customer rules organized once, in a form your team and your AI assistant can both read, the Business Brain Starter Kit is built for that. Get notified when it launches.
FAQ
How do I get a busy dispatcher to write things down?
Make it small and immediate. Five lines or a two-minute voice memo after an unusual load is realistic; a documentation project is not. Let AI turn the memo into the card and let the dispatcher correct it, which is faster than writing from scratch. Review the cards together once a month, so the effort is visible.
Which lanes should we document first?
Start with the cases that would go wrong first if the dispatcher were away tomorrow: lanes with permits or special documents, receivers with strict rules, and customers with unusual terms. Rare but recurring lanes matter more than common ones, because the routine is usually in the TMS already, while the exceptions are not written anywhere.
Is it safe to store carrier and customer details in an AI tool?
Use a tool with business data settings, keep access limited to your team, and store only what the work needs. Never store bank details or carrier payment information in the cards. Keep contact details to work phones and roles. Check the tool's terms and your customer agreements before you upload anything.
How often should lane cards be reviewed?
Review the cards that changed once a month, and every card at least once or twice a year. Each card carries a last-checked date, so stale ones are easy to spot. Update a card immediately when a receiver changes its rules, a carrier is dropped or a document requirement changes.
Sources
- 49 CFR § 371.3 – Records to be kept by brokers — Cornell Legal Information Institute, current text, accessed 2026.
- Carrier Vetting: Part 2 — Transportation Intermediaries Association, J. E. Lee, 2026-03-02.
- 261/2011. (XII. 7.) Korm. rendelet a díj ellenében végzett közúti árutovábbítási tevékenységről — Nemzeti Jogszabálytár, state as of 2026-01-01 (in Hungarian).
- Incoterms® rules — International Chamber of Commerce, Incoterms 2020 in force since 2020, accessed 2026.
- EKÁER – Változások 2021-ben — NAV, Hungarian Tax Authority, 2021-11-11 (in Hungarian).
- Cargo and Freight Agents – 43-5011.00 — O*NET OnLine, U.S. Department of Labor, updated 2026-10-06.