Skip to content
Do the work once. Get the SOP forever.
For carriers, freight brokerages, and 3PLs. The office side of the operation.

How do trucking and freight offices document dispatch and billing work?

Quick answer

The person who already knows the task does it once in the browser with the SopWow recorder running. SopWow writes the procedure, asks about the calls a recording cannot explain (when a carrier packet is complete, when detention gets billed, which loads go to factoring), and flags anything it added until a person approves it. It covers back-office work in a web-based TMS, load boards, and carrier, shipper, and factoring portals.

Most freight offices run on a few people who know how a load gets from tender to paid invoice. They know which shipper wants its own reference number on the rate con, which customer only accepts invoices through a portal, and which carriers always send a certificate that is one detail short. None of that is written down, because the people who know it are busy moving freight.

SopWow is built for that gap. It records the office work, not the trucks.

What back-office work do trucking and freight teams document first?

Start with the tasks that repeat every day and go wrong when someone new does them. Each of these has decision points that a list of clicks would miss.

  • Load entry in the TMS. Stops, appointment windows, equipment type, commodity, and the customer's reference numbers. Decision points: which reference goes in which field for this customer, when a load becomes a multi-stop, and when it needs a special handling flag.
  • Carrier onboarding and packet verification. Checking authority, the certificate of insurance, the W-9, the signed carrier agreement, and payment or factoring details. Decision points: what makes a packet complete, what puts a carrier on hold, and who can approve an exception.
  • Rate confirmations. Building and sending the rate con from the load record. Decision points: which accessorials are agreed up front, which terms apply to this customer, and what to do when the carrier asks for a change before signing.
  • Posting to load boards. Decision points: which loads get posted and which go to known carriers first, whether to show a rate, and when to pull a posting once the load is covered.
  • Invoicing and factoring submissions. Matching the invoice to the rate con and the signed proof of delivery, then uploading the package to a customer portal or a factoring portal. Decision points: what to do when the POD is missing or unreadable, and which customers refuse emailed invoices.
  • Detention and accessorial billing. Decision points: whether the check-in and check-out times support the charge, whether the customer's terms allow it, and whether it needs approval before it lands on the invoice.
  • Filings and renewals in government and insurance portals. Updating registrations, submitting forms, and keeping insurance filings current. Decision points: which filing applies, what date drives it, and who signs off. SopWow writes down the steps; your compliance lead decides what is required.

Carrier insurance certificates and filings are shared work with the insurance agency on the other side of the phone. That is where SopWow started, so the agency version of this work is covered in depth on how insurance agencies document COIs and renewals.

Why do trucking and freight procedures break down?

Freight procedures break down because the rules live with customers, not with the office. Every shipper has its own portal, its own reference format, its own POD requirements, and its own idea of what counts as detention. A new billing clerk can learn the TMS quickly and still get a customer's invoice rejected for a reason nobody told them.

Coverage makes it worse. Dispatch and billing do not stop for vacations, sick days, or the one person who handles a big account leaving for another brokerage. Whoever covers is working from memory, a sticky note, or a checklist that says "verify carrier" without saying what verified means.

And the portals change. A customer moves to a new invoicing portal, a factoring company adds a required document, and the one person who noticed updates their own habits but not the binder.

Writing things down is the fix everyone agrees on. The problem is finding the afternoon to do it. If you are building a plan for new dispatchers and billers, the guide on how to onboard a new back-office hire faster walks through what to document first.

What does a freight SOP step look like when SopWow writes it?

Illustrative example. This is not from a customer recording.

Task: approving a new carrier in a brokerage TMS after the onboarding packet comes in.

A click log says:

Click "Documents." Click "Insurance." Click "Mark verified." Click "Approve carrier."

SopWow says:

Verify the carrier's certificate of insurance before approving. Confirm the named insured matches the legal name on the carrier agreement and W-9, the policy dates cover the first scheduled pickup, and the auto liability and cargo limits meet this customer's requirements. If anything falls short, do not approve. Set the carrier to Pending, note what is missing, and ask the carrier to have their insurance agent send an updated certificate. (In this recording: all checks passed, carrier approved.)

The click log is accurate and does not help a new hire. The recording only saw the happy path. The Pending branch came from the recorder's answer when SopWow asked what happens if the limits come up short. Anything the AI inferred on its own stays flagged until a person keeps or removes it.

That is the difference between a record of what someone did and a procedure that tells the next person what to do. More tasks written this way are collected on the page of SopWow use cases with worked SOP examples.

How does SopWow handle carrier, shipper, and driver data?

Freight records are full of names, phone numbers, addresses, and payment details. Here is what the recorder does with them.

  • Field values are not captured. The recorder stores which field was used on which page, not what was typed into it.
  • Recognizable data is redacted first. Data with a recognizable shape, such as Social Security numbers, card numbers, policy numbers, emails, phone numbers, and street addresses, is stripped in the browser before any text is sent to an AI model, export, or sync.
  • Screenshots never go to an AI model. They build the visual guide and stay in your workspace.
  • A person checks before anything is final. Redaction is pattern based and can miss things: a driver's name in a free-text note, an ID number in an unusual format, or anything visible in a screenshot. Every SOP gets a human review, including a redaction check, before approval.

What won't SopWow do for a freight office?

  • It only sees the browser. A desktop TMS, anything run through remote desktop or Citrix, phone calls with drivers, and paper BOLs are not captured. You can add those steps by hand during review.
  • It is not a compliance tool. SopWow does not decide whether a carrier is qualified, whether a filing is correct, or whether a procedure meets any regulation or customer requirement. It writes down how your team does the work, and your team stays responsible for the rules.
  • It does not integrate with your systems. SopWow does not connect to your TMS, post loads, send invoices, or pull data from a portal. It records a person doing those things in the browser and turns that into a procedure.
  • It does not track trucks or dispatch drivers. It documents the office work around dispatch, not the dispatch itself.

Frequently asked questions

Does SopWow work with our TMS?

If your TMS runs in Chrome or Edge, the recorder can capture work done in it. SopWow does not integrate with any TMS; it records the steps a person takes. If your TMS is a desktop program or runs through a remote session, those steps are not captured, and you would add them by hand in review.

Can a dispatcher record while working live loads?

Yes. The recorder captures only the tab showing the REC indicator, so other tabs stay out of the recording. The dispatcher does the task normally and answers SopWow's questions afterward, when the load is handled.

How do we document billing rules that differ by customer?

Record the task once for the customer with the most typical rules, then answer SopWow's questions about the other branches. For customers whose process is truly different, such as a separate invoicing portal, record that version as its own SOP.

How is pricing set for a small brokerage or carrier office?

You pay per finished SOP, not per seat. A finished SOP is one you approve; drafts, re-recordings, and edits do not count. Your first 3 SOPs are free with no card, and Starter is $39 a month for 15 SOPs.

Ready to write down how a load gets billed?

Pick one task that only one person in the office knows, record it once, and review the SOP SopWow writes. Your first 3 SOPs are free, with no card required.

view as markdown · /industries/trucking-freight.md