Carrier files, BOL and POD records, driver SOPs and a dispatch intranet: SharePoint built for logistics companies

Why does a shared drive stop working for a freight operation?

Because nothing in a folder knows which load it belongs to. A folder cannot carry a load number, a carrier, a delivery date or an expiry date, so a POD is found by whoever remembers where it was saved. The drive works while dispatch is small and fails the first time a customer disputes an old invoice.

The setup we are asked to fix usually looks alike. There is a shared drive with a folder per customer or per month, PODs arriving as phone photos in a dispatcher’s inbox, carrier packets saved as one PDF whose insurance certificate expired without anyone noticing, rate confirmations that only exist as email attachments, and procedures printed and pinned in the dispatch office. None of that is a discipline problem. The work is turning the things a freight business already talks about — the load, the carrier, the customer, the claim — into objects the platform understands, so the answer comes from the system rather than from the person who saved the file.

Which logistics documents belong where in SharePoint?

Each document type gets a home matched to how it is looked up and who must see it. BOL and POD files are found by load number, carrier packets by carrier and expiry date, SOPs by role and terminal, claims by status. The table below is the map we scope against, including what we route to a narrower build.

How are BOL and POD records found when a customer disputes an invoice?

By the load or PRO number billing already quotes. Each BOL and POD sits in one library with load number, customer, shipper, consignee, carrier and delivery date as columns, so a dispute is answered with a filter instead of a search through email. The same columns let a customer service rep send the right file the first time.

Getting paperwork into the library is the part that decides whether it gets used. Documents scanned at a terminal, emailed by a carrier or photographed by a driver can be filed by a Power Automate flow that moves the attachment into the library and asks for the load number when it is missing. Where your TMS already stores POD images, it stays the system of record and we do not duplicate it; we decide which system owns which document during scoping. Reading a load number off a scanned image automatically is a separate document-processing question, priced on its own, not something this build assumes.

How does carrier onboarding stay current when insurance certificates expire?

By making the expiry date a column instead of a line in a PDF. Each carrier gets one record holding its agreement, W-9, certificate of insurance and authority details, with expiry dates and an owner. A scheduled flow warns the owner before a certificate lapses, and a view shows every carrier whose paperwork is out of date.

Carriers can upload their own documents through a site that admits named guests and nothing else. Microsoft’s external sharing documentation (opens in new tab) sets out the model: sharing is controlled at the organization level and then per site, and a site can never be more permissive than the tenant. We set link defaults that do not silently create anonymous links, expiry on guest access, and a short list of which sites may share externally at all. To be clear about the boundary: we do not connect to FMCSA data or a carrier-monitoring service, and we do not vet carriers — the build records what your team checked and when. Vendors outside the carrier network follow the same pattern in our vendor management system on SharePoint.

How do rate confirmations, exceptions and claims get approved without email?

Each item becomes one record with the documents attached, and a Power Automate approval routes it to the people you name, in the order you set. A load booked below your margin floor goes to a manager, a claim goes to operations and then finance, and each decision, approver and timestamp is written back to the record.

The mechanism is Microsoft’s standard approval action. Its approval workflow documentation (opens in new tab) covers single approvers, first-to-respond, everyone-must-approve and sequential stages. Two design rules decide whether it survives a busy season and staff turnover: the flow’s connections are owned by a service account rather than a dispatcher who might leave, and every approval step has a named deputy for nights and weekends. Customer contracts and rate agreements are a different object with renewal dates and signatures, which is why they belong in the contract repository build rather than in the load paperwork library.

What goes on a dispatch intranet, and who reads it?

A dispatch intranet is the front door for the whole operation, including people who rarely sit at a desk: drivers, dock leads and the night shift. It carries safety notices and weather or route alerts at the top, links to current SOPs by role and terminal, the forms people actually use, and the after-hours contacts.

The limit is accounts, not pages. Drivers and dock staff who sign in on a phone, tablet or shared screen can read the intranet and the SOP libraries; staff with no Microsoft 365 account cannot. Microsoft’s frontline worker licensing overview (opens in new tab) describes the plans built for people who work away from a desk. We check who holds which license during scoping and tell you plainly what the yard and the cab can reach before anything is built.

How long should BOL, POD and claims records be kept?

As long as your retention schedule says, and that schedule is yours to set with your compliance lead or counsel, not ours. What we build applies it: retention labels on each library or document type, so a POD cannot be deleted before its period ends and old files do not pile up forever after it.

Microsoft’s retention policies and labels documentation (opens in new tab) explains how a label keeps content for a set period, deletes it afterwards, or both. Which retention features your licenses include is part of the scoping check, because labels applied automatically need higher licensing than labels set on a library by default. Claims files usually need a different clock from routine PODs, and the build gives them one.

How is this different from the SharePoint build for manufacturers?

Different buyer, different paperwork. A plant controls released drawings, SOPs and engineering changes; a carrier, 3PL or freight broker controls carrier packets, BOL and POD records, rate confirmations, claims and dispatch procedures. The platform and engineering standards are the same, but the libraries, metadata and approval routes are built around a load rather than a part.

If you run a plant, our SharePoint for manufacturing build is the right starting point; a distributor that also assembles or kits product sometimes needs pieces of both, and we say so in the consultation. Reporting is a separate service line: once loads, carriers and claims carry real metadata, on-time delivery, cost-per-mile and carrier scorecard dashboards are what our Power BI consultant for logistics companies engagement builds.

What does the engagement cover?

Three shapes cover most requests from freight businesses. Every fee is fixed and put in writing after your free consultation — the table shows scope and typical timeline, because an honest number needs to see your document types, your current shared drive and your license position first. Our fixed-fee process explains how the number is set.

Whatever the shape, you own everything: the libraries, the flows, the metadata, the intranet and the documentation stay in your Microsoft tenant from the first day, and nothing we build depends on us to keep running.

Which logistics companies is this a good fit for?

Carriers, 3PLs, freight brokers and distributors of 20 to 500 people, paying for Microsoft 365 and running the back office off shared drives and inbox attachments. The usual trigger is a disputed invoice nobody could prove, a lapsed certificate found too late, a customer audit of carrier files, or a new operations lead.

It fits badly when your TMS or a carrier-compliance platform already holds every document you need and the team actually uses it; adding SharePoint beside it only creates a second place to look. Enterprise operations integrating several TMS and WMS platforms usually need a larger integration partner than a fixed-fee build. We work with freight businesses in all US states remotely from our Orange County, CA base.