How Much Coordination Capacity Does One Load Consume?

Key Takeaways

Coordination capacity is the number of loads a team can carry each month: the coordination hours it actually has, divided by the coordination time one load consumes.
The per-load number is touches per load × minutes per touch, weighted by the mix of clean loads and exception loads, not a borrowed loads-per-coordinator benchmark.
Plan against the peak month, not the average, because exceptions rise when volume rises and they consume capacity fastest.
Wilson, by Cartage, takes on the routine coordination work under company rules, so the minutes left on each load are mostly approvals and escalations.
Recalculate capacity from the shipment history once Wilson runs real lanes, rather than assuming a result in advance.

How many loads can a coordination team actually carry?

A team can carry as many loads as its available coordination hours divided by the coordination time each load consumes, with room left for the peak month. That ratio, not headcount, is the capacity number. Two teams with the same number of people can carry very different volumes because their loads consume very different amounts of time.

Most teams already have a rough sense of how long a load takes. The method for measuring it task by task is laid out in how much time manual freight coordination takes per load. Capacity planning starts where that measurement ends. It answers the next questions: at current volume, how close is the team to its limit? How many more loads can it absorb before something slips? Which part of the per-load time is eating the headroom? And what happens to the limit when routine work moves off the team?

Those questions matter because freight volume rarely grows in a straight line. A new customer with retail delivery appointments, a seasonal peak, or a shift from FTL to LTL can raise the time per load while the load count barely moves. A capacity model makes that visible before the team feels it as missed pickups and unanswered emails.

A four-step capacity model

The model turns a per-load time into a monthly limit. It uses the team's own measurements at every step.

Step 1: Split the per-load time into clean and exception loads

A clean load moves from quote to POD without a change. An exception load has a missed pickup, a cancellation, a rate change, a changed address or a missing POD. Measure both separately, because an exception load often consumes several times the coordination time of a clean one.

Step 2: Weight by the mix

Weighted minutes per load = (share of clean loads × clean-load minutes) + (share of exception loads × exception-load minutes). The exception share is the most important input in the model, and it changes from month to month.

Step 3: Count the hours that are really available

Start from paid hours, then subtract what is not load coordination: meetings, ERP data entry unrelated to freight, internal requests, training and time off. Then set a planning ceiling below the remaining total, so a bad week does not break the plan. The ceiling is a management choice, not an industry figure.

Step 4: Divide and compare

Monthly load capacity = available coordination minutes ÷ weighted minutes per load. Compare it with current volume and with forecast volume. The gap between them is the team's headroom, or its shortfall.

Where the capacity actually goes

The capacity number is an average, and averages hide the pressure points. Four patterns explain why a team can look fine on paper and still fall behind.

Waiting is part of the load. A quote request takes little time to send. The capacity goes into reminders, calls and re-reading threads when a carrier does not answer. Those touches are small, but they repeat on almost every load.

Exceptions cluster. Missed pickups and cancellations tend to arrive together, on the same lanes and in the same weeks, often when volume is highest. A month with a higher exception share can cut capacity sharply even if the load count is flat.

Work arrives at the same hour. Pickup confirmations, ETA checks and customer updates bunch up in the morning and before cutoffs. A team can have spare hours across the week and still be over capacity at nine in the morning.

Interruptions cost more than the touch itself. A coordinator pulled away to chase a POD loses time getting back to the quote they were comparing. Counting only the touch understates the real load.

These patterns are why the capacity plan should be tested against the peak month and the busiest days, not only against the monthly total. They also show which work to move first: the repetitive follow-up and status work that fills the morning, not the decisions.

How to use the number for staffing and growth decisions

Once the model gives a monthly limit, a few rules turn it into decisions:

Volume near the planning ceiling in a normal month: the team has no room for peak. Act before the peak arrives, not during it.
Capacity driven down by the exception share: look at the cause first. Missing order data, unconfirmed pickups and carriers that rarely answer are fixable, and fixing them raises capacity without adding anyone.
Capacity driven down by routine follow-up: the time is going to work that does not need judgment. Moving that work off the team raises the limit more than adding a person, because the extra person would spend the same share of the day chasing replies.
Forecast includes a new customer or mode: recalculate with the expected exception share for that business. Retail appointments, residential deliveries and cross-border loads usually raise it.
Hours freed by automation: decide where they go before they appear. Teams often move them to carrier relationships, customer escalations and planning, so the gain shows up as more loads carried rather than fewer people.

The same logic is behind where logistics capacity actually comes from: headcount follows coordination minutes, so the minutes per load are the lever.

Worked example: one team's capacity today

The numbers below are illustrative, chosen only to show the arithmetic. A team of three coordinators has about 330 hours a month available for load coordination after other duties and a planning ceiling. That is 19,800 coordination minutes. It ships 260 loads in a normal month and expects 320 at peak.

Scenario	Clean-load minutes	Exception-load minutes	Exception share	Weighted minutes per load	Monthly load capacity
Today, normal month	45	150	20%	66	about 300
Today, peak month	45	150	35%	82	about 240

How to read it:

In a normal month, the team runs at about 87% of its capacity (260 of 300). It looks fine.
At peak, capacity falls to about 240 loads while demand rises to 320. The shortfall comes from the exception share, not from the extra loads alone.
To see what changes when routine touches (quote follow-ups, booking within limits, pickup confirmation, status checks, POD requests) leave the team, rerun the same rows with counts from the team's own lanes once the new workflow is running. Don't plug in assumed minutes.

The point is the structure: the exception share and the routine minutes move capacity more than headcount does.

How capacity changes when Wilson, by Cartage takes the routine work

Wilson is an AI logistics agent that executes the coordination work the capacity model counts. It requests quotes from the company's approved carriers, follows up on silence, negotiates against the company's rate targets, books within approval limits, confirms pickups, tracks each load using the best source available, sends updates in Slack, Microsoft Teams, email or SMS, collects PODs, audits and reconciles carrier invoices, and pays carriers from the Wilson Wallet under approval rules.

In capacity terms, that changes what the remaining minutes are made of. The team still spends time on loads, but on decisions: rates above the limit, rebookings that need approval, customer calls on serious delays, and escalations when no approved carrier accepts. Wilson starts with assisted execution, so the first weeks carry more approval minutes. As the company widens the rules step by step, those minutes shrink on the lanes where approvals are routinely granted.

Because messages, confirmations and changes are recorded in each shipment's history, the after-numbers come from the record. The team can rerun the model on the same lanes with real counts and see its new limit. If your team is debating whether next quarter's volume needs another coordinator, bring your monthly load counts and your peak-month plan to Cartage and run the capacity model on your own lanes.