More shipments, same logistics team: measure the coordination work first

Key Takeaways

Before deciding how to absorb more shipments, measure the coordination work by workflow from your own records: volume, manual touches, minutes, who does it, and the follow-up, exception and approval counts behind it.
Count each workflow in its own unit (quote rounds, follow-ups, exceptions, approvals, disputed invoices), not in loads, because each one grows with a different driver.
Shipment counts alone cannot tell you how many hours growth will add or how many a new workflow will remove; only a re-measurement of the same sheet can.
Include work done outside the logistics team, such as customer service answering status questions and accounts payable chasing invoice differences.
Wilson, by Cartage, executes much of the routine coordination work and records messages, confirmations and changes in shipment history, so the same sheet can be filled again from the record.

What should you measure before deciding how to absorb more shipments?

Measure the coordination work itself, workflow by workflow, using your own data: how often each workflow happens, how many manual touches it takes, how many minutes those touches cost, and who does them. Then decide whether growth calls for fixing upstream causes, changing approval rules, moving routine work to an AI logistics agent or hiring.

The usual starting point is a ratio: shipments per coordinator today, multiplied by next year's forecast. It feels objective and it is usually wrong, because coordination work does not grow in step with shipments. A new retail customer with appointment-only docks adds status questions and rescheduling without adding many loads. A carrier that stops answering email doubles follow-ups on its lanes with no change in volume. A tighter approval limit adds a queue for one manager.

The case for absorbing growth without hiring is made in more shipments should not require more logistics headcount. This is the step before that argument: building a measurement across every workflow the team touches, so the decision rests on your numbers rather than on someone else's benchmark.

Set up the measurement in five moves

The set-up takes one normal four-week window and produces one sheet that every later decision refers back to.

List the workflows, not the load stages. A typical list: order intake and clarification, quote requests, carrier follow-ups, booking and documents, pickup confirmation, status checks and updates, exceptions and rebooking, approvals, POD collection, invoice questions and payment, and ERP updates.
Give each workflow its own volume unit. Quote requests count in quote rounds, follow-ups in second and later asks, exceptions in incidents, approvals in decisions, invoices in disputed invoices. One load can produce zero or five of any of these.
Pull the counts from records. Sent mail grouped by thread, phone logs, the shared logistics inbox, Slack or Microsoft Teams requests, ERP change logs and the accounts payable queue. Memory understates the small, repeated work.
Time a sample of touches. Have each person time a handful of touches per workflow during normal days and record minutes per touch. Note elapsed waiting separately; waiting is not active work, but it explains why a workflow feels heavy.
Name who does it. Record the role, including roles outside logistics. A status question answered by customer service is still coordination work.

Keep the window clear of peaks and holidays, and record the shipment count for the same window beside the sheet, not inside it.

Follow-ups, exceptions and approvals deserve their own lines

Three kinds of work hide inside other workflows unless they are counted separately: follow-ups, exceptions and approvals.

Follow-up volume is every second or later ask: the reminder to a carrier that hasn't quoted, the call for a missing pickup confirmation, the third email for a POD. Folded into quoting or POD, it disappears into an average. Counted separately, it shows which carriers and lanes generate the chasing.

Exception volume is the count of incidents: missed pickups, cancellations, late loads, changed appointments, reclassifications. Record the cause next to each one. Missing order data, an unconfirmed pickup and a receiver that moves appointments are different problems with different fixes.

Approval volume is the number of decisions a person had to make, such as a rate above the limit, a rebooking, an invoice variance or a payment release, plus how long each waited. A queue in front of one manager can slow the whole team even when the touches are few.

Finally, separate active minutes from elapsed time. A quote round that takes two days end to end may hold only a few minutes of work. Mixing the two makes every workflow look larger than it is and hides where the minutes actually go. For a task-level way of timing a single load, see how much time manual freight coordination takes per load.

How to use the sheet to decide about growth

Read the sheet by asking what each workflow grows with, then match the response to the driver rather than to the shipment forecast.

Rows that grow with shipments (quote rounds, bookings, pickup confirmations): growth will add this work roughly in step. These are candidates for routine execution under rules.
Rows that grow with carrier behavior (follow-ups): look at which carriers drive them before assuming volume is the cause.
Rows that grow with customers and receivers (status questions, appointment changes): a new customer can add more here than its load count suggests.
Rows driven by fixable causes (order clarifications, exceptions from missing data): fix the cause first; the work shrinks without a hire.
Rows that are queues (approvals): revisit the limits before adding people.
Rows outside logistics (customer service, accounts payable): include them, or the decision understates the work.

Two rules keep the decision honest. Do not divide total hours by shipments and project that figure onto next year's forecast; the rows grow at different rates. And do not estimate the hours a new workflow will remove from the shipment count; re-measure the same rows after the change. To turn the sheet into a monthly load limit, use the coordination capacity model per load.

The coordination-work measurement sheet

Fill one row per workflow for the same four-week window. The figures below are illustrative, show only the arithmetic and are not benchmarks.

Workflow	Volume unit	Volume	Touches per unit	Minutes per touch	Hours	Who	Grows with
Order clarification	Orders with gaps	90	2	4	12	Order desk, coordinator	Order data quality
Quote requests	Quote rounds	380	3	3	57	Coordinators	Shipments, lanes
Carrier follow-ups	Second and later asks	520	1	4	35	Coordinators	Carrier responsiveness
Booking and documents	Bookings	340	2	5	57	Coordinators	Shipments
Pickup confirmation	Pickups	340	1	4	23	Coordinators	Shipments
Status checks and updates	Status questions	610	1	3	31	Customer service, coordinators	Customers, receivers
Exceptions and rebooking	Incidents	48	6	8	38	Coordinators, manager	Peaks, new lanes
Approvals	Decisions	75	1	6	8	Logistics manager	Approval limits
POD collection	Missing PODs	110	2	4	15	Billing, coordinators	Carrier mix
Invoice questions	Disputed invoices	64	3	10	32	Accounts payable, coordinators	Accessorials, changes

Hours are volume × touches × minutes ÷ 60, rounded. In this example, follow-ups and status questions together take more hours than booking and documents, and neither grows mainly with shipments. That shape, not the total, is what a growth decision should be built on.

How Wilson, by Cartage fits the measurement

Wilson is an AI logistics agent that executes the routine rows of this sheet, so the team's remaining hours shift toward approvals, escalations and customer decisions.

Wilson replaces the TMS for freight execution and connects to the ERP or the order data flow the company already uses. It requests quotes from approved carriers, follows up on silence, negotiates against rate targets within approval limits, books and produces documents, confirms pickups, tracks each load from the best source available, sends updates in Slack, Microsoft Teams, email or SMS, initiates rebooking from approved carriers within the rules or with approval, collects PODs, audits and reconciles invoices, and pays carriers from the Wilson Wallet under approval rules.

Wilson starts with assisted execution, so the approvals row reflects the approval rules the company sets, and the scope can expand step by step. Because messages, confirmations and changes are recorded in shipment history, the second measurement on the lanes Wilson runs comes from the record rather than an estimate.

Bring four weeks of your workflow counts to a demo with Cartage and see Wilson run the follow-up, status and POD rows on one of your own lanes.