Writing Down How Your Business Runs

Understanding Brain-Dumping and SOPs

In trucking and freight, your business runs on repeatable decisions: routing, dispatch priorities, detention handling, lumper receipts, proof-of-delivery, accessorial billing, and what to do when something breaks. Standard Operating Procedures (SOPs) are how you make those decisions consistent—every day, with every dispatcher, broker rep, or back-office teammate.

Think of SOPs like the “load flow” for your company. If you run a dedicated fleet, a brokerage, or a 3PL, you want the same outcome whether it’s you on shift or a newer team member covering. The goal is to create a system where a new hire can be about 80% effective on day one just by following your SOPs—especially for the high-volume, high-stakes tasks (the stuff you repeat every week).

The Importance of Brain-Dumping

Brain-dumping is transferring all the “tribal knowledge” in your head into a format your team can use. If you don’t write it down, your company’s performance is tied to your attention and your memory. That’s a trap for trucking/freight businesses because things change fast—new accessorial rules, carrier requirements, customer portals, rate confirmations, and daily exceptions.

Real-world example: You know exactly how you handle a detention request when the carrier calls late and the paperwork is messy. You might remember the exact wording to use, how long to wait before escalating, and what proof you need (BOL timestamps, check-in time, live unload windows). If that knowledge lives only in your head, your billing and cash collection slow down the moment you’re not available.

Brain-dumping captures that. Then SOPs turn it into something your team can follow without you.

Creating Effective SOPs

Use this simple structure for each SOP:

1. Why: Start with why this task matters.
- In trucking/freight, “why” usually connects to money or service: fewer missed detention charges, faster POD retrieval, fewer claim disputes, or fewer late updates.

2. What: Detail the exact steps.
- List the steps in the real order your workflow happens. Include what fields to check in your TMS/WMS, what documents to request from the carrier, and what you update in each system.

3. Outcome: Define what success looks like.
- Don’t leave it vague. Success should be measurable: “detention request submitted with complete proof,” “accessorial billed within X hours of POD,” or “exception documented and customer notified within the required window.”

Real-world example: If you’re writing an SOP for “late pickup with carrier no-show,” your “why” is protecting your OTIF performance and preventing rate disputes. Your “what” includes the exact calls/messages, escalation steps, and how to document times. Your “outcome” describes what “resolved” means: update sent to customer, new pickup/ETA confirmed, and the case notes ready for billing or claims.

Organizing Your SOPs

SOPs must live in one place, searchable by the whole team. In trucking/freight, people don’t have time to hunt.

Set up a “single source of truth” like:
- A Notion wiki
- Google Drive folder structure with permissions
- Your internal knowledge base

Real-world example: Make it easy to find the SOP for “lumper receipt reimbursement” when a carrier sends a blurry photo and the driver is already on the next run. If someone can’t locate the right process in under 60 seconds, the SOP isn’t finished—it’s too hard to use.

The Loom-First Approach

Writing SOPs takes time. In trucking/freight, speed matters because you need to document what you do before the process changes.

Use Loom (screen recording) to capture the steps while you do them on your system. A video SOP is ideal for:
- Entering shipment milestones
- Submitting detention claims
- Downloading POD and matching it to the correct stop
- Processing an accessorial invoice

Real-world example: Record yourself handling “POD missing” in your tracking tool—show where the missing doc is flagged, what you check first, the message you send to the carrier, and how you document the follow-up in your load record.

Then someone can follow the video and avoid guessing.

Building a Culture of Self-Reliance

You can’t coach every exception on the fly. The culture you want is simple: the first stop is the SOP vault.

Train your team to check the SOP vault before asking you. When they hit a question, they should be able to say:
- which load
- which step they’re stuck on
- what SOP they already reviewed

Real-world example: A dispatcher asks, “How do we handle a detention dispute when the carrier claims the clock started late?” The right response isn’t “Ask me.” It’s “Check the Detention Dispute SOP—are you missing any of the required proof? If yes, then follow the escalation steps there.”

When this works, your business becomes less dependent on your availability, and your service quality becomes more consistent—across every dispatch shift, billing cycle, and customer update.