Notes
Cass Freight Index vs. a port call count: what each one actually measures

If you cover freight or trade flow, you've probably pulled the Cass Freight Index at some point and wondered how it relates to the vessel-level data you're also watching. They're not substitutes for each other. One is a monthly read on US domestic freight spend and shipment volume. The other is a daily physical count of ships showing up at a terminal. Knowing which one answers your actual question saves you from citing the wrong number in a note.
Cass Freight Index: what it's built from
Cass Information Systems processes freight invoices for a book of large shippers, mostly truckload, LTL, rail, intermodal and some parcel. The index aggregates that invoice data into two series: a Shipments Index and an Expenditures Index, both indexed to a base year. It's released around the middle of each month, covering the prior month's activity.
Because it's built from paid invoices, it's inherently a trailing measure. A shipment has to move, get billed, and get processed before it shows up in the number. That lag is fine for the thing Cass is good at: telling you how the broader US domestic freight economy trended last month across modes. It's also a US-weighted, B2B-shipper-weighted sample, not a global trade measure and not an ocean-specific one. Ocean freight shows up in it only indirectly, through the inland moves that follow a container off the dock.
What a port call count measures
A port call count is narrower and more literal. It's the number of vessels arriving at a named port or terminal over a given window, usually built from AIS tracking, satellite imagery, or both. Some providers break it down further, by vessel class, by berth, or by how long ships are sitting in anchorage before they get a slot.
That last piece, the anchorage queue, is often the more useful signal than the raw call count. A port can take the same number of calls in a month and still show a very different throughput story depending on whether ships are turning around in two days or sitting offshore for a week. Call counts and queue length together get you closer to how much cargo is clearing this port than either number alone.
The tradeoff is scope. A port call count tells you about one gateway, or a handful of them if you're tracking several. It says nothing about the Midwest truckload market or rail intermodal volumes the way Cass does. You're trading breadth for immediacy and specificity.
Where the two series disagree
The gap between the two shows up most clearly at inflection points. When ocean import volumes start rolling over at a major West Coast or Gulf gateway, you'll see it in vessel calls and container stack density at the port within days. Cass won't register that shift until the containers have moved inland, cleared customs, gotten trucked or railed to a DC, and the invoices for those moves have cycled through processing. That can be a lag of several weeks between the physical event at the port and its footprint in the Cass print.
So the two series aren't competing for the same job. Cass is a good backward-looking check on how domestic freight performed, useful for validating a trend after the fact or for comparing year-over-year freight recessions. A port call count, especially one paired with stack counts and queue data, is a leading read specifically on what's arriving by sea, available well before that activity shows up anywhere in a monthly freight index or in customs trade statistics.
Using them together
Port-level physical counts give you the early signal; Cass, or the official trade releases, confirm it weeks later. That ordering is the whole reason a series built from daily counts of stacks, calls and queues is worth running next to Cass rather than in place of it. Trade Flow Index builds that series from satellite passes over named ports on a daily cadence, so you're not waiting on an invoice-processing cycle to find out what already happened at the dock.
If you're nowcasting trade flow rather than explaining it after the fact, it's worth putting that kind of daily port-level feed next to whatever monthly index you already track.