Bill Of Lading Template

What you actually need when you ship freight

A Bill Of Lading Template is just a structured document that captures the essentials of a freight shipment in one place. It serves three simultaneous purposes: it acts as a receipt from the carrier, a contract of carriage between shipper and carrier, and sometimes a document of title depending on how it's issued. That third function is where most people get tripped up, and I'll get to that shortly. The core fields are consistent across virtually every template you'll encounter. Shipper name and address, consignee name and address, notify party, carrier name, vessel or trucking company, origin and destination ports, number of packages, weight, freight class, description of goods, HS code, and special handling instructions. Anything missing from those basics creates ambiguity downstream.

Building Your Own Bill Of Lading Template

You don't need fancy software for this. I've shipped containers through East Coast ports with nothing but a well-structured spreadsheet and a carrier portal that accepted CSV uploads. The trick is making sure every field maps correctly to what the terminal and customs actually require. A generic Word document falls apart the moment you need to process more than three shipments per month because there's no way to batch-update or pull data from your ERP without manual re-entry every time. Start with a spreadsheet. Columns should mirror the standard BOL fields plus a few practical additions like your internal PO number, container number, and seal number. Most carriers will ask for those on their own forms anyway, but having them in your master template means you're not scrambling when the freight forwarder calls at 4 PM on a Friday asking for container details you should have captured weeks ago. For the download itself, you can find free BOL templates on shipping association sites or carrier portals. Maersk, FedEx Freight, and XPO all publish their own versions. The problem with carrier-specific templates is they often include fields that don't transfer cleanly when you switch carriers mid-chain. A container starting on a Maersk vessel and switching to a regional trucker at the port of discharge will force you to reformat everything because the trucking company's BOL doesn't have the same fields. That's why building a universal master template in your own system beats relying on any single carrier's form.

The one thing almost no template covers adequately is the special provisions section. This is where you note things like hazardous materials compliance, temperature control requirements, liftgate delivery, or inside delivery. I learned this the hard way in 2019 when I shipped a load of medical equipment through the Port of Savannah. The BOL template my forwarder provided didn't have a dedicated field for temperature range specifications. I scribbled it in the remarks section in plain text, and the receiving warehouse on the other end couldn't verify the cold chain was maintained because their BOL scan didn't surface that information. The load sat at the dock for six hours while someone manually cross-referenced the email chain. After that, I added a mandatory temperature range field to my template and never had that problem again. Here's something most template guides won't tell you: the description of goods field on a BOL doesn't need to be poetic. "Medical equipment parts, plastic and metal, no hazards" is legally sufficient and often preferable to a detailed narrative. Over-describing can actually create problems. I once had a shipment held for inspection because I described electronics components as "sensitive laboratory instruments" when they were just replacement PCBs for existing equipment. Customs flagged it as potentially higher-value regulated goods based on that description. Less is more in that field, and the freight class you assign matters far more than the prose you write. Another counter-intuitive point: the shipper-certified weight field is now a legal requirement under the Ship Security Certification and Weight Verification rules that took effect internationally. If your template doesn't have a certified gross weight field with a signature line, your carrier can refuse the shipment at the terminal. This isn't optional. Every template you use needs that field, and it needs to match the weight on your actual packing documentation within a reasonable tolerance. When I stopped tracking certified weight on my templates, I lost two containers to demurrage at Long Beach because the terminal rejected the BOL outright. That was roughly $3,200 in demurrage and storage fees across two separate shipments that could have been avoided with a single field in the template.

The downsides of using any static template are real. They don't auto-validate. They don't cross-check HS codes against current tariff schedules. They won't flag if you've listed 47 pallets but only provided tracking numbers for 45. You're the one catching those errors, and by the time you do, the shipment might already be in motion. Dynamic BOL generation tools built into modern TMS platforms handle validation automatically and reduce error rates significantly. If you're doing fewer than fifty shipments per year, a spreadsheet template is fine. Beyond that, the manual checks become a full-time administrative burden. For the people who need a starting point, a basic spreadsheet template with the fields I mentioned above will serve most standard domestic and international shipments. Populate it before the carrier picks up the freight. Confirm the freight class with your forwarder before finalizing. Double-check that the consignee and notify party fields match exactly what's on the commercial invoice. And make sure the special provisions section captures anything non-standard about the shipment. That's really all there is to it.