Home / Case studies
Case studiesTwo case-study shells, marked pending
These are structure, not results. Each page states the lane type, the problem and the approach, and every result field says PENDING until a real completed load and the shipper's approval exist. We would rather publish two honest shells than three invented wins.
No outcomes, savings, volumes, customer names or quotes are published. A case study is filled in only after (1) the load is delivered, (2) the record is complete, and (3) the shipper gives written approval to publish it.
Shell — pending real loads
Liftgate LTL program for a solar distributor
LTL with liftgate and appointment windows · Louisville, KY → Atlanta, GA
Job-site deliveries need a liftgate and a call-ahead appointment, and reclass disputes appear when module density is estimated rather than measured. The shell exists to document how the class check, the appointment handling and the delivery evidence were managed on real loads.
Read the shell →Shell — pending real loads
Import container to a Midwest distribution center
Drayage + FTL, port to DC · Long Beach, CA → Louisville, KY
The container has to clear the terminal, hold its free time, and hit a DC receiving window. The shell exists to document the terminal appointment, the free-time clock and the handoff to the DC.
Read the shell →Why publish an empty case study at all?
Because the alternative is inventing one. The shell shows the standard the finished page has to meet: named lane, named handling, dated evidence, and the shipper's approval. When the first two loads close, these pages are filled from the load records — not from a copywriter's imagination.
Have a lane these shells describe?
Send the lane and handling; the quote shows the planning range and the basis before you commit.