LogisticsLT Core — Standalone

## The scenario You have joined the Network Performance team at a UK national parcel carrier. The Operations Director needs a weekly Shipment Volume Snapshot — status mix, weight-band distribution, service-type breakdown, SLA breach counts, heaviest active shipments, daily creation trend, in-transit vs delivered, and an unassigned-shipment audit. ## Dataset LogisticsLT is a synthetic UK parcel-carrier dataset hosted on the CareerSwerve Azure SQL training database. For SQL Core you work exclusively with the `LogisticsLT.Shipment` table — the hub entity for the rest of the schema, opened up in SQL Applied. ## Deliverables Eight outputs (A–H) submitted as a single annotated `.sql` file: **A.** Shipment volume by status · **B.** Weight band classification · **C.** Volume by service type and status (two-column GROUP BY) · **D.** SLA breach summary (DATEDIFF + CASE) · **E.** Top 10 heaviest active shipments · **F.** Daily creation trend for the last 30 days · **G.** In-transit vs delivered UNION comparison · **H.** Single-row unassigned-shipment audit. ## Acceptance criteria (summary) Same rigour as the other Core capstones — clean execution, deliberate NULL handling, sargable date filters, logical CASE ordering, business-friendly column headers. Defence focuses on the operational meaning of "SLA breach" and why two-column GROUP BY matters when service-type performance varies by status. Full brief and connection details appear inside the lesson once enrolled.