What is a shipping SOP?

A shipping SOP is the written standard operating procedure for getting freight out of your building and into the receiver's. It names each step in order, from the driver checking in through proof of delivery, and it names who owns each one. The value is not the list of actions: it is the handoffs, the points where freight stops being one party's problem and becomes another's, because that is where freight actually gets dropped.

How do I write a shipping SOP?

Start from a real lane rather than a blank page. Enter the origin and destination ZIPs and the builder draws the steps a shipment on that lane actually goes through, including the cross docks it passes and the transit it takes. Then edit any step in your own words, name an owner for each one, and download the sheet or send the link to your dock team.

What is a handoff in a shipping SOP, and why does it matter?

A handoff is a step where the freight changes hands from the step before it: your shipping team to the dock lead, the dock lead to the driver, the carrier to the receiver. These are the joints of the process and they are where paperwork goes missing, damage goes unrecorded, and appointments get missed. The builder marks every handoff on the sheet and counts them, so a lane that changes hands five times says so out loud.

Who should own each step of a shipping SOP?

Exactly one party per step. A step with two owners has none in practice, and a step with no owner is the thing that quietly fails an audit. The builder enforces one owner per step by construction and flags any step left unowned, so the sheet you hand over is enforceable rather than descriptive.

Does the SOP include the freight rate?

Yes. The sheet prints the live Warp rate and transit for the lane it describes, with the date it was quoted. A shared sheet re-quotes when the recipient opens it, so a link forwarded next month shows next month's price rather than an old number wearing a fresh date.

Can I share the SOP with my team or my carrier?

Yes, two ways. Copy share link produces a URL that reopens the sheet live and editable for whoever receives it, and Download PNG produces an image for printing or pinning at the dock. Nothing is stored on a server: the whole sheet travels inside the link.

Do I need an account to build a shipping SOP?

No. The builder is free and needs no account, no login and no email. Enter two ZIPs and the sheet draws itself.

Can software or an AI agent generate one of these SOPs?

Yes. POST a plan, or just two ZIPs, to /api/sop and it returns a shareable link to the drawn sheet. GET /api/sop with that link returns the structured plan back, including the owner of each step and which steps are handoffs, so a program can both write a procedure for a person to read and read one a person edited.

Shipping SOP builder

Two ZIPs, and we draw what actually happens to your freight on that lane.

What a shipping SOP is for

A shipping SOP is the written procedure for getting freight out of your building and into the receiver's. Most of them are a list of actions, and a list of actions is a description. What makes one enforceable is an owner on every step, and what makes it useful is marking the handoffs: the points where the freight stops being one party's problem and becomes another's. Those joints are where paperwork goes missing, damage goes unrecorded and appointments get missed.

This builder starts from a lane instead of a blank page. Enter two ZIPs and it draws the steps a shipment actually goes through between them, names the cross docks Warp operates on that route, and prints the live rate and transit on the sheet with the date it was quoted. Every step carries the failure mode that step is known for and what to do about it. Edit anything, then download it or send the link.

For software and agents

The builder has an API. POST a plan, or just two ZIPs, to /api/sop and it returns a shareable link to the drawn sheet. GET /api/sop?url= with that link returns the structured plan back, with the owner of each step and which steps are handoffs. It is symmetric on purpose: a program can write a procedure for a person to read, and read back one a person edited.