Shipments per operator: the metric forwarders miss

A freight forwarder processing 400 shipments a month can state the total volume with precision. Revenue, gross margin, the split between ocean and air: all known. Ask how many shipments each operator actually runs from start to finish, though, and the answer is usually a rough estimate, if one exists at all. Total volume is what shows up in management reports. How that volume is spread across the operations desk is what explains why some shipments fall behind, why certain clients complain more than others, and why bringing on another operator does not always fix the bottleneck.

Shipments per operator is the most telling indicator of operational health in a mid-size freight forwarder. It shows whether the operation can grow with the team it has or whether every new client demands a new hire. Most forwarder owners do not track it.

The metric most forwarder owners do not track

The math looks simple: divide total monthly shipments by the number of operators. A forwarder with 400 shipments and 10 operators would average 40 per person. That average hides more than it reveals. In nearly every forwarding operation, the distribution is uneven. A senior operator managing two large accounts may handle 60 shipments a month. Another, serving five smaller clients with different documentation requirements, handles 25 and works the same hours.

The average does not show where the operation is overloaded or where capacity sits idle. When the owner decides to hire because “the team cannot keep up,” the hire addresses the symptom without touching the cause: workload is poorly distributed, or the tasks consuming most of each operator’s time are tasks the system should handle.

Forwarders who start measuring shipments per operator tend to find two things: the gap between the busiest and the least busy operator is wider than expected, and much of the workload that looks operational is actually administrative.

Shipments per operator measures absorbed capacity, and cargo type changes the math

An ocean FCL import where the forwarder coordinates the booking, monitors transit, checks the carrier invoice and issues the house bill of lading carries one level of operational load. An LCL shipment with deconsolidation, where the operator must check the manifest, split house bills by consignee and track release of each lot at the bonded terminal, carries another. An air freight shipment with perishable cargo that requires a regulatory clearance from the health or agricultural authority, with a 48-hour deadline from landing, carries a third.

Comparing operators by raw shipment count without considering cargo type is like comparing two branch offices by revenue without looking at margin. The absolute number impresses or alarms, but the decision needs context.

The most useful approach among forwarders who take this metric seriously is weighting by operational complexity. A standard FCL import counts as one. LCL with deconsolidation counts as 1.5 or 2, depending on the number of lots. Air freight with regulatory clearance counts as 1.5. Customs brokerage handled by the same operator who manages the logistics counts as a separate increment. Each forwarder calibrates the weights based on its own operation, because the client and mode mix differs.

With that weighting in place, comparisons between operators start to make sense. And the owner can answer the question that matters: is the bottleneck in headcount, or in the amount of work each shipment demands?

Three activities that fill the operator’s day without moving cargo

When you measure an operator’s time over a typical week, three activities appear repeatedly among those that consume the most hours without corresponding to any operational milestone.

The first is re-keying data. The same data point, a container number, gross weight, sailing date or consignee details, gets typed into the forwarder’s system, the carrier portal, the customs system and, in many cases, a parallel tracking spreadsheet. A forwarder running three or four separate systems multiplies the re-keying across every shipment. If an operator handles 40 shipments a month and each shipment requires the same fields entered in three places, that is 120 data entry cycles with 120 chances for error.

The second is status chasing. The operator fields questions from the importer, the sales team and the customs broker about shipment progress. Each question means opening the system, checking the position and replying by email or messaging app. In a forwarder without a self-service portal for business partners, the operator answers the same questions for the same people several times a week. That time does not appear as “customer service” in any report, but it shows up as hours spent without moving any cargo forward.

The third is manual document checking. Before issuing a house bill of lading, the operator opens the booking confirmation, commercial invoice and packing list, and cross-checks field by field. When the draft comes back with errors, the cycle repeats. The checking is necessary because data enters the system through manual keying, and manual keying introduces mistakes. The check corrects errors that the data entry itself created.

None of these activities appears in a shipments-per-operator report, because none of them corresponds to a process milestone. They consume time between milestones. And those invisible hours are what determine, in practice, how many shipments each operator can handle before quality drops.

How to calculate shipments per operator in your own operation

The calculation starts with a definition: what counts as “one shipment” for this metric. In most forwarders, the natural unit is the freight file, from booking or opening through cargo delivery or financial settlement. Customs brokerage handled by the same operator can be counted as an addition to the freight file, if linked, or as a separate file, if a different operator handles clearance.

The second step is to segment by mode and complexity, using operational weights the forwarder itself defines. A forwarder running mostly FCL imports will have different weights than one mixing FCL, LCL and air.

The third step is to pull the number of shipments each operator handled over the last quarter, month by month. A single month can contain distortions: holidays, an exceptional shipment, a client that concentrated volume. Three months show the pattern.

With those three elements, count how many weighted shipments each operator handled per month and compare. A few questions that number answers:

If the gap between the busiest and the least busy operator exceeds 50%, the problem is likely in account distribution rather than team capacity. Reassigning accounts may relieve the bottleneck without hiring.

If every operator is above a threshold where errors rise and deadlines tighten, the operation needs more people or less manual work per shipment. The follow-up question is: how much of each operator’s time goes to tasks the system should handle?

If one operator handles far fewer shipments than the rest and works the same hours, it is worth investigating whether their shipments are more complex, whether they carry administrative tasks others do not, or whether a key-person dependency concentrates knowledge instead of distributing it.

What happens when operators stop re-keying and chasing status

Re-keying, status chasing and manual document checking share a common cause: information does not flow between systems, between the forwarder and the business partner, or between the document and the system record.

When the forwarder runs operations in an integrated system that centralizes quoting, booking, operations, billing and settlement, the operator enters data once. Container number, party details, dates and amounts live in one place, and each process step pulls from the previous one. Re-keying disappears because there is no second system to feed.

When importers and overseas agents access a business partner portal and check shipment status, free-time countdowns, released documents and invoices on their own, status emails stop reaching the desk entirely.

When incoming documents go through automatic extraction that reads fields, validates against rules (container number, port, currency, air waybill) and delivers a ready record for the operator to review, manual checking changes nature. The operator reviews exceptions rather than reviewing everything.

Every hour no longer spent on re-keying, status messages and field-by-field checking becomes available for handling more shipments, or for handling the same shipments with closer attention to the points that genuinely require human judgment, such as a demurrage negotiation, an invoice discrepancy or a special cargo booking.

In implementations at freight forwarders, the increase in capacity per operator shows up in the first quarter, in the form of shipments the team absorbs without anyone working longer hours.

How Tier2 Cargo tracks shipments per operator at each stage

Tier2 Cargo records each shipment with the assigned operator and the 13 operational milestones the shipment passes through, from pre-alert to settlement. Shipments per operator by period, mode and branch come from the reports the system already generates, with no separate spreadsheet.

Because quoting, operations, billing and accounting run in the same system, data is entered once and travels through the entire process. The operator who previously typed the same fields into three systems now works in one. Tier2 Portal, the business partner portal that reads directly from Tier2 Cargo, removes status questions from the operator’s desk. And Autodocs extracts and validates fields from incoming documents, so the operator reviews what is uncertain rather than reviewing everything.

See how it works or get in touch.

The next step for any forwarder owner who has read this far is to pull, from the data already available, how many shipments each operator handled over the last three months, broken down by mode. That number alone already shows where the operation stalls, where there is slack, and where operator time is being consumed by tasks that technology should absorb.