SOP
List

9. Load building, BOL & delivery

Draft
CCR SOP draft v1 · edits are kept for this session only
Purpose
Build loads, ship with a BOL and keep a signed POD per load.
Trigger
Releases ready to ship.
Section
Outbound
Lanes (who typically does it)
Operations; Shop; Customer / GC
Note
-
Last reviewed
-
System of recordPortalaSaQuickBooksSharePointExternalHand-off to another SOPHover a step for detail; click to open its page.
OperationsTrishShopWillieCustomer / GCGeneral contractorsDocumentsSharePointPartialFullReleases ready to ship (Portal)Releases ready toshipBuild the load and add releases by control code. (Portal)Build load; addreleases by control #Is the whole release going on this load, or a partial?Partial orfull?Partials are allowed: the remainder stays open on the release. (Portal)Load partial qty;remainder stays openShip or customer pickup; the BOL prints from the portal. (Portal)Ship or customerpickup; BOL printsReceive delivery; sign the BOL / POD (External)Receive delivery; signthe BOL / PODUpload the signed BOL / POD on the load record (stored in SharePoint). (SharePoint)Upload signed BOL / PODTrack confirmed and upcoming deliveries (Portal)Track confirmed andupcoming deliveriesContinue with SOP 11: Invoicing. (Portal)Invoicing (SOP 11)
  1. 1.Build the load and add releases by control code (partials allowed).Loads / BOLsPortal
  2. 2.Ship or customer pickup; the BOL prints from the portal.Loads / BOLsPortal
  3. 3.Upload the signed BOL / POD (stored in SharePoint).Load recordPortal + SharePoint
  4. 4.Confirmed and upcoming deliveries.DeliveriesPortal
  • Shipped tons and a signed POD per load
Total: 2