Look — most peak failures are carrier-handoff failures, not capacity failures, which means the post-mortem template almost everyone uses is broken before the first meeting. Organize the review by carrier and you'll produce a document that blames the last entity to touch the box. The box's problems usually started two handoffs earlier. And you don't have until February to get this right: the January GRI announcement is coming, your negotiation posture depends on what your post-mortem proves, and a review that wraps in March is a history project, not a negotiating asset.
This one's for the VP of Logistics. Here's the method, five steps, run it in December while the bruises are fresh.
Step 1: Sort exceptions by handoff, not by carrier
Take every exception from the wave — late, damaged, re-routed, expedited, refunded — and tag it by the seam where the failure originated, not the carrier whose name was on the label at delivery. The seams: ramp to drayage, drayage to cross-dock, cross-dock to injection, injection to last-mile network, and weather diversions across any of them. This is tedious and it changes everything. A "FedEx late delivery" that started as a three-day dwell at the ramp isn't a FedEx problem and never was. In the region, where six Class I railroads converge and December metering is a fact of life, I've seen networks where a third of the "parcel failures" originated upstream of the parcel network entirely. [S-cite: share of peak parcel exceptions originating in upstream linehaul/rail handoffs]. Until you sort by seam, that's invisible.
Step 2: Price every exception at total landed cost
Not the transport charge — the full bill. The expedite premium, the demand-fee delta on the rebooked service — those layered per-package fees that went live in October are itemized in the carriers' own announcements [S-cite: published demand-fee tables for the current peak] — the refund, the support contact, the dock labor on the re-handle. An exception that "cost" $14 of freight usually cost $60 of business. Your CFO already suspects this. Show the arithmetic.
Step 3: Reconcile announced versus invoiced
Lay the surcharge announcements next to the invoices, line by line. Two findings every year: fees applied outside their announced windows or triggers, which is recovery money — and fees that arrived earlier than your plan assumed, which is calendar drift. The demand fees that used to surface in November have moved to October (S23), and published rate increases have been understating realized increases by 100 to 200 basis points (S2 — the long history of surcharges that never go away). Your post-mortem should produce your own effective-increase number for peak. That number, not the press release, is what January is negotiated against.
Step 4: Find the rail-shaped hole
Now overlay steps 1 and 2: total landed cost of exceptions, by seam, by week. If your network touches Chicagoland to Gary, there will be a shape in that data — a cluster of downstream parcel costs that trace back to gateway dwell events at Elwood or Joliet in specific weeks. That's the rail-shaped hole. It hides because the costs land in parcel budgets while the cause lives in rail operations, and because the people who read parcel invoices and the people who watch ramp dwell have never been in the same meeting. Put them in the same meeting. That alone is worth the post-mortem.
Step 5: Convert findings into January asks
A post-mortem that ends in lessons learned is a diary. Convert every finding into one of three artifacts: a negotiation ask (fee waivers, trigger thresholds, service-level commitments on your worst lanes — backed by your reconciliation file), a network change (an injection point added, a replenishment buffer resized, a weather playbook trigger tightened), or a systems requirement (the surcharge logic, re-promise trigger, or exception costing your stack couldn't do this year). Three lists, owners on each line, dated. That's the whole deliverable.
And then January starts the next cycle, because peak is a project that starts in January, not October — the gateway will spend Q1 telling you exactly how next October goes, in dwell trends and chassis availability, for anyone bothering to read it.
A word on who's in the room, because the roster decides the outcome. The standard post-mortem invites the parcel team and the carrier reps. The useful one adds the people who watch the ramps, the cross-dock supervisors who lived the missed waves, and somebody from finance who can bless the landed-cost math on the spot. The first roster produces a meeting where everyone defends their lane. The second produces the document where the lanes finally connect — which is the entire point of sorting by handoff in the first place.
Tradeoff, stated plainly: this method takes more work in December than the blame-the-carrier version, in the month nobody wants more work. The blame-the-carrier version produces a deck. This one produces leverage.
Concrete ask: we run this five-step analysis with shippers every December and January — your exception file, your invoices, your announcements, reconciled before negotiation season opens. If you want the worksheet to run it yourself, ask and it's yours. If you want it run with you, the December slots go first. Either way: before the GRI drops, not after. After is just reading someone else's terms.