Transportation performance does not depend only on the quality of a company’s TMS configuration. It depends just as heavily on the quality of the carrier network operating through that system. Carriers determine whether tenders are accepted, whether pickups occur on time, whether freight arrives intact, whether milestones are updated reliably, and whether disruptions are handled professionally when conditions deteriorate. A TMS gives the company the data and workflow structure to manage those outcomes, but it still needs a deliberate model for measuring carrier performance, governing carrier relationships, protecting the network during disruption, and responding to growing sustainability expectations.
This chapter addresses that operating model. It explains how to design carrier scorecards that drive the right behavior, how to structure relationship governance so carrier conversations are based on facts rather than anecdotes, how to build a disruption and risk mitigation framework that is usable in live operations, and how to enable sustainability and emissions reporting without turning carbon tracking into a disconnected reporting exercise. The broader theme is that carrier management should be treated as an active discipline, not as a contract archive and a quarterly meeting routine.
11.1 Carrier Performance Scorecard Design
Scorecard design: A carrier scorecard is the operational translation of what the company expects from its transportation providers. It should make clear which behaviors matter, how those behaviors are measured, how performance differs by lane or service type, and what consequences follow when results improve or deteriorate. Many companies say they have carrier scorecards when what they really have is a set of monthly metrics produced for procurement, often too late and too aggregated to influence day-to-day behavior. A strong TMS-supported scorecard is different. It is tied to shipment facts, updated on a useful cadence, and designed to support both operational intervention and commercial governance.
The starting point is metric discipline. A good scorecard does not try to measure everything. It focuses on the handful of indicators that reveal whether the carrier is helping the company achieve cost, service, control, and risk objectives. At a minimum, most shippers need to see tender acceptance, on-time pickup, on-time delivery, damage rate, claims ratio, status update compliance, and invoice accuracy. Many also add accessorial behavior, proof-of-delivery timeliness, appointment compliance, and exception responsiveness. The right mix depends on the operating model, but the logic should be consistent: measure the things that influence service and cost in a way the carrier can actually manage.
On-time delivery is the most obvious example of why definitions matter. Some organizations measure against requested delivery date, others against promised arrival window, and others against the booked appointment time. None of those are automatically wrong, but a carrier cannot be governed fairly if the definition changes from one report to the next or differs by business unit without explanation. The same problem appears in tender acceptance. Is acceptance measured against the primary offer only, all offers, or only tenders sent with sufficient lead time? Scorecard design should resolve these questions before performance meetings begin. If the math is not trusted, the governance conversation will collapse into an argument about the metric instead of action on the result.
Segmentation is just as important as definition. Carrier performance should not be reviewed only in aggregate. A carrier may perform very well on regional truckload lanes and poorly on retailer appointment deliveries. A parcel provider may show excellent transit reliability and weak claim resolution. A broker may look strong on acceptance and weak on invoice cleanliness. The scorecard should therefore be segmented by mode, lane family, service level, region, or customer environment wherever those distinctions materially affect performance. Aggregated numbers often flatter average carriers and conceal concentration of risk in the places the business most cares about.
Damage rate and claims ratio deserve more attention than they often receive. Many transportation teams treat them as after-the-fact customer service issues rather than carrier management indicators. That is a mistake. Claims activity reveals whether a carrier is handling freight carefully, whether packaging assumptions are realistic, whether handoffs are controlled, and whether proof standards are strong enough to resolve liability efficiently. A good scorecard should therefore capture not only the number and value of claims, but also the speed of response, the quality of documentation, and whether the pattern is concentrated on specific lanes, locations, or shipment types.
Compliance metrics are increasingly important in TMS-enabled environments. It is no longer enough for a carrier to move the freight physically. The carrier also needs to operate through the company’s control model. That means accepting tenders through the defined channel, providing status updates in the required format and timing, complying with appointment procedures, sending documentation promptly, and billing according to contract structure. In practice, compliance quality often separates carriers that are operationally scalable from carriers that consume disproportionate management time. The scorecard should make that visible rather than rewarding only low rate performance.
Weighting is another important design choice. Not every KPI should count equally. A service-sensitive retailer network may care more about appointment compliance and on-time delivery than about small invoice variances. A manufacturing network exposed to plant stoppages may place heavier weight on pickup reliability and disruption responsiveness. A high-value product network may weight claims and damage behavior more heavily. These weights should reflect transportation strategy, not just historical reporting habits. If leadership says service reliability is critical but the scorecard still rewards cheapest rate and broad acceptance above all else, the scorecard is misaligned with business intent.
The cadence of performance measurement should also match the operational need. Some KPIs, such as same-day tender acceptance or urgent exception response, are useful in daily or weekly operating reviews. Others, such as claims ratio and invoice discrepancy trends, may be better suited to monthly or quarterly analysis because the pattern matters more than the daily reading. The TMS should support both. Operational teams need a near-real-time view of emerging failures, while procurement and leadership need a structured view of sustained carrier behavior over time.
One of the most effective scorecard designs uses a mix of lagging and leading indicators. On-time delivery and claims are lagging because they tell the company what already happened. Acceptance behavior, status compliance, and milestone timeliness can be leading because they signal whether service risk is rising before the final failure occurs. A carrier that accepts fewer primary tenders, sends status updates late, and misses pickup confirmations is often telling the shipper that service quality is about to deteriorate. A scorecard that includes those early signals is much more useful than one that waits for the final miss to show up weeks later.
The scorecard should also distinguish between carrier-controlled and shipper-controlled outcomes. If a shipment is late because the warehouse released it late, a carrier should not be penalized as if it created the problem. If detention is caused by dock congestion at the shipper site, the carrier relationship discussion should reflect that. This is one reason shipment-level facts matter so much. A TMS-supported scorecard can separate true carrier failure from network failure, preserving trust while still exposing the real operational causes. Without that discipline, carriers learn to discount the scorecard and internal teams use it mainly to externalize blame.
A practical carrier scorecard often includes the following measures:
- Service: On-time pickup, on-time delivery, appointment compliance, proof-of-delivery timeliness.
- Commercial: Tender acceptance, routing-guide compliance, invoice accuracy, accessorial pattern.
- Quality: Damage rate, claims ratio, shortage frequency, documentation completeness.
- Control: Status message timeliness, EDI or API compliance, exception responsiveness, dispute closure speed.
The final design principle is usability. A scorecard should not be a dense report that only analysts can interpret. Carrier managers, planners, procurement leaders, and the carriers themselves should be able to see what the result is, why it changed, and what action is required. The strongest scorecards connect each KPI to an action pathway. Falling acceptance may trigger lane review. Rising damage may trigger packaging and handling analysis. Weak status compliance may trigger onboarding remediation. This is where the scorecard stops being a report and becomes a management tool.
The real test is simple: does the scorecard change decisions about carrier allocation, corrective action, network design, or sourcing behavior? If not, the company is measuring performance without really managing it. A TMS makes much better scorecards possible, but they only matter when leadership uses them to govern share, accountability, and improvement.
11.2 Carrier Relationship Governance
Relationship governance: Good carrier relationships are not built on friendliness alone and they are not preserved through quarterly business reviews that focus only on rates and generic service slides. They are built through a steady operating rhythm in which both parties understand expectations, see the same performance facts, discuss root causes honestly, and act on corrective priorities quickly. A TMS helps because it provides shared evidence, but the company still needs a governance structure that makes that evidence useful.
The first step is to recognize that carriers should not all be governed in the same way. Strategic core carriers require a different relationship model than occasional spot providers or highly specialized niche carriers. Strategic carriers usually deserve a formal governance cadence, senior sponsorship, lane-level performance transparency, and joint improvement work. Secondary or tactical carriers may need simpler operational reviews focused on acceptance, service compliance, and dispute resolution. The company should segment the carrier base and apply the right level of relationship attention to each segment rather than forcing one governance template across the entire portfolio.
Quarterly business reviews are still valuable, but only when they are grounded in real transportation data and connected to the daily operating reality. Too many QBRs fail because both parties walk in with different numbers, different definitions, and different stories about what happened. The TMS reduces that problem by anchoring the review in shipment-level facts, scorecard measures, and exception histories. That allows the conversation to move quickly from disagreement about outcomes to discussion of causes, commitments, and needed policy changes.
A strong governance model usually has three layers. The first is daily or weekly operational contact focused on tender issues, service failures, urgent claims, and status or appointment problems. The second is a monthly performance review focused on trend analysis, recurring lane issues, invoice behavior, and open corrective actions. The third is a quarterly or semiannual strategic review focused on share allocation, market outlook, network changes, contract alignment, technology adoption, and continuous improvement priorities. Each layer serves a different purpose. When companies collapse everything into an occasional QBR, operational issues linger too long and strategic topics are crowded out by recent firefighting.
Ownership on the shipper side is critical. Carrier governance often fragments across procurement, transportation operations, regional logistics teams, and finance. That fragmentation leads to mixed messages. Procurement may emphasize rate commitments, operations may emphasize acceptance and service, finance may emphasize invoice disputes, and no one may own the integrated picture. A mature TMS program usually establishes named carrier managers or governance owners who coordinate this conversation and ensure that the same facts drive both operational and commercial decisions.
The content of the governance conversation matters as much as the cadence. Carrier reviews should not be a generic walk-through of service metrics. They should focus on the gaps that most affect the business. Where is acceptance below target and why? Which lanes are generating repeated late deliveries? Which accessorial categories are rising? Are claims concentrated at particular facilities or on certain product families? Is EDI or API compliance improving? Are corrective actions from the last review actually complete? This is where the TMS gives the company leverage. It allows both sides to examine performance patterns at lane and shipment level rather than speaking in broad generalities.
Governance should also include forward-looking discussion. Carriers often know before the shipper does where capacity is tightening, where service networks are changing, where labor or terminal risks are rising, or where seasonal pressure is likely to create volatility. The relationship model should create room for this exchange. Carriers should understand upcoming promotions, new customer launches, network changes, and regional peaks that will affect freight demand. In return, the shipper should expect early warning on capacity constraints, service disruptions, technology changes, or pricing structures that may affect execution. A well-run relationship is not only a review of the past. It is a preparation mechanism for what is coming next.
Corrective action discipline is often the difference between real governance and ceremonial governance. Every significant performance issue should end with a named action, a due date, and a means of validation. If tender acceptance is weak because lead times are too short, either the carrier adjusts staffing or the shipper changes tender timing. If status updates are inconsistent, either the carrier fixes the integration or the shipper changes connectivity expectations. If detention is concentrated at one facility, local operations must be drawn into the remedy. Too many carrier meetings identify the same issues repeatedly without ever translating them into owned action. The TMS can surface the problem, but only governance can force closure.
Relationship governance should also influence sourcing, not sit beside it. Carrier performance data should shape future awards, share allocations, renewals, and backup strategy. Otherwise, procurement may negotiate in one universe while operations live in another. A carrier with slightly higher rates but consistently better acceptance, lower claims, and cleaner invoices may be more valuable than a cheaper carrier that creates operational instability. The TMS provides the evidence required to make that case credibly.
Escalation pathways are also important. Some carrier issues can be resolved through local operations. Others require higher-level discussion because they involve contract interpretation, chronic underperformance, or a growing strategic risk. The governance model should define when a performance issue remains in routine review and when it escalates to senior leadership. This is particularly important in disruptions, where speed matters and neither side benefits from uncertainty about who can actually authorize alternate capacity, service adjustments, or exception funding.
Trust is an outcome of this structure, not a substitute for it. Carriers are usually more willing to invest in integration quality, capacity protection, and joint planning when they believe the shipper governs fairly and consistently. Shippers are more willing to share forecasts and concentrate volume when carriers provide transparency and follow through on commitments. A TMS-supported governance model helps create that trust because both sides can see the same shipment history and performance trajectory. The better the evidence, the less the relationship depends on anecdote, personality, or escalations after damage is already done.
Carrier relationship governance works when operational teams know how issues are surfaced, commercial teams know how performance affects future business, and carriers know the standards against which they will actually be judged. At that point, the TMS is no longer only a transaction platform. It becomes the information foundation for a disciplined carrier ecosystem.
11.3 Disruption and Risk Mitigation Framework
Risk mitigation framework: Transportation networks do not fail only because a carrier misses a pickup. They fail because multiple forms of disruption interact faster than the organization can respond. Weather, port congestion, labor action, equipment shortages, driver capacity, geopolitical events, cyber incidents, warehouse outages, system failures, and sudden demand shifts all put pressure on freight flows. A TMS cannot remove those risks, but it can help the business detect them earlier, respond more systematically, and preserve service where it matters most. That only happens if disruption management is designed as a formal operating capability rather than as an informal expectation that planners will somehow improvise when things go wrong.
The first step is to define the major disruption categories the network actually faces. Some risks are external and visible, such as storms, strikes, cross-border holds, road closures, or market-wide capacity tightening. Others are internal, such as ERP latency, TMS outages, late order releases, warehouse bottlenecks, dock congestion, or poor master data that creates impossible plans. Still others are partner-driven, including carrier insolvency, broker nonperformance, weak milestone updates, or customs broker delay. The framework should cover all three. Many transportation teams focus only on external disruption and underestimate how often service failures actually begin inside their own operating model.
Risk segmentation should follow business impact, not only probability. Some disruptions are likely but manageable. Others are rare but severe enough that the business must prepare explicitly. A missed pickup on a standard replenishment lane is very different from a customs hold on critical inbound material or a regional carrier outage during peak season. The TMS and control tower model should therefore classify disruption according to consequence: customer penalty risk, production interruption, revenue exposure, safety concern, regulatory exposure, or reputational damage. This allows the business to prioritize resources instead of treating every exception as equally urgent.
Contingency routing is the most visible component of the framework. The company should know, before a disruption occurs, which alternate carriers, modes, routes, or nodes are available for critical flows. This is where carrier strategy and network design connect directly to risk management. Backup carriers must be genuinely onboarded, not merely named in a spreadsheet. Alternate modes must have rate logic, service rules, and approval thresholds already defined. Critical lanes should have documented fallback options rather than relying on whoever can be found under pressure. A TMS can then execute those options quickly because the contingency choices already exist inside the planning model.
Backup carrier logic should not be limited to primary tender rejection. The network may need to shift capacity because a carrier is service-degraded, because weather blocks one region, because a port or terminal is congested, or because a carrier’s system connectivity has failed. The TMS should support more than one fallback trigger. It should also distinguish between tactical substitutions and strategic risk actions. Moving one shipment to a backup carrier is not the same as temporarily reallocating a lane family during a severe event. The framework should say who can authorize each level of response and how the decision is recorded.
Mode-shift policy is another critical lever. During disruptions, the business often turns quickly to premium freight without first examining whether lower-cost recovery paths remain available. A mature TMS environment structures those choices. It may allow a shift from truckload to team service, from ocean to air, from intermodal to over-the-road, or from direct delivery to pool distribution, but only under clear risk conditions and approval rules. The purpose is not to prevent emergency action. It is to ensure that emergency action is disciplined, visible, and later reviewable rather than becoming a reflexive cost response.
Control tower processes are essential here. Someone must watch network risk indicators, identify the shipments and lanes most exposed, coordinate interventions, and track whether mitigation actions worked. The TMS provides much of the data needed for this, including tender failures, at-risk ETAs, lane concentration, carrier performance drift, and event status. But the operating cadence matters just as much. During elevated risk periods, organizations often need more frequent reviews, shorter escalation paths, and tighter communication between transportation, warehouse operations, customer service, procurement, and in some sectors manufacturing or sales.
Scenario planning should be part of the framework, not a once-a-year exercise. Transportation teams should periodically test what they would do if a top carrier lost capacity on critical lanes, if a port closure forced rerouting, if a storm disrupted a distribution region for several days, or if the TMS lost carrier connectivity during peak shipping hours. These tests do not need to be theatrical. They need to clarify roles, identify missing fallback rules, and expose dependencies that are invisible in steady-state operations. A company usually discovers during these exercises that backup capacity is thinner than assumed, approval rules are unclear, or manual workarounds are slower than anyone expected.
Cyber and technology risk now deserve explicit inclusion. A transportation network can be materially disrupted not only by physical events but by system outages, ransomware events affecting partners, EDI failures, API instability, or loss of visibility feeds. The TMS program should therefore define degraded-mode operating procedures. Which shipments can still be tendered manually? How will carrier commitments be recorded? How will milestone updates be captured if the primary feed fails? How will duplicate actions be prevented once the system is restored? A resilience model that ignores digital disruption is incomplete.
Risk mitigation should also include supplier and customer behavior where relevant. Some customer requirements increase disruption exposure, such as inflexible appointments or unrealistic lead times. Some suppliers create inbound volatility through inconsistent readiness or weak documentation. The TMS can help expose those patterns, but leadership must decide whether to redesign service commitments, hold more buffer inventory, adjust lane structures, or escalate performance requirements. Transportation cannot own every root cause, even though the failure often shows up in transportation first.
A practical disruption framework usually rests on five elements:
- Risk visibility: Defined signals that show which lanes, carriers, sites, or shipments are under stress.
- Priority logic: Clear rules for which shipments matter most when capacity or time is limited.
- Fallback options: Preconfigured carrier, mode, route, and node alternatives for critical flows.
- Decision rights: Named authority for tactical changes, premium actions, and strategic reallocations.
- Recovery review: Post-event analysis that converts disruption behavior into better policy and configuration.
The last element is often neglected. Every serious disruption should leave behind usable evidence. Which fallback carriers actually responded? Which lanes proved too concentrated? Which sites were least prepared? Which approvals slowed recovery? Which visibility feeds were insufficient? This review is where resilience improves. Otherwise, the company experiences the same disruption pattern repeatedly and calls it bad luck.
The goal of a disruption and risk mitigation framework is not perfect continuity. That is unrealistic. The goal is to reduce uncertainty, compress response time, preserve service where it matters most, and keep emergency behavior inside a governable transportation model. A TMS gives the organization the structure to do that, but only if the business decides in advance how it intends to respond when the original plan fails.
11.4 Sustainability and Emissions Reporting Enablement
Sustainability enablement: Transportation leaders are increasingly expected to answer two questions at the same time. First, how can the company reduce freight-related emissions without damaging service and cost performance unnecessarily? Second, how can it report those emissions with enough consistency and traceability to satisfy internal leadership, customers, and external reporting requirements? A TMS does not solve climate strategy by itself, but it plays a central role because it is often the system that holds the shipment facts required to estimate transport emissions and the operational rules that influence those emissions in the first place.
The first principle is that emissions reporting should be built on operational reality. Carbon outputs are only as reliable as the shipment data beneath them. If the TMS does not hold credible information on mode, distance, equipment, weight, cube, shipment count, carrier, and route or leg structure, then emissions results will be rough at best. That does not mean the TMS must calculate every carbon metric directly. Some organizations use specialized ESG or carbon-accounting platforms. But the TMS should still be designed to provide the clean transportation record those platforms need.
Mode is the most obvious emissions driver, but it is not the only one. Shipment frequency, consolidation quality, empty miles, equipment utilization, route length, dwell, network design, and avoidable premium freight all affect the carbon profile of transportation. This is why sustainability should not be treated only as an external reporting requirement. A TMS-enabled transportation model can reduce emissions operationally through better consolidation, more disciplined parcel thresholds, selective intermodal use, lower expedite frequency, and stronger route governance. In other words, the system helps the business do greener transportation, not just describe it afterward.
Methodology matters. Emissions can be estimated using spend-based methods, distance-and-weight methods, mode averages, carrier-specific factors, or more detailed activity-based calculations where data quality permits. Different reporting requirements may prefer different methods. The TMS team should therefore work with sustainability, finance, and reporting stakeholders to define which method will be used for which purpose and what shipment attributes must be captured to support it. This choice should not be left ambiguous until after go-live. If the enterprise later discovers it needs lane-level distance or leg-level mode separation that the TMS did not capture reliably, retrofit becomes difficult.
Allocation rules are important here too. If one consolidated load serves multiple orders or customers, the company needs a defensible way to allocate emissions across those entities. The same is true for intercompany transfers and multi-leg international movements. The TMS already faces similar questions for freight cost allocation, and the same governance discipline can help with carbon allocation. The exact basis may differ, but the principle is the same: make the rule explicit, repeatable, and consistent with how the business wants to manage performance.
Carrier engagement is increasingly part of the sustainability model. Some carriers can provide more precise emissions factors, equipment data, fuel mix information, or sustainability program details than others. The TMS should make it possible to associate shipment activity with the relevant carrier attributes and, where appropriate, compare carriers not only on cost and service but on sustainability data quality and performance. This does not mean every sourcing decision becomes a carbon decision. It means the company begins to treat emissions as one more dimension of informed carrier management rather than as a disconnected annual disclosure topic.
Reporting enablement should include traceability. Leadership will want to know how emissions were calculated, what data was used, which shipments were included, and how exceptions were handled. Customers may ask for lane-specific or shipment-specific transport emissions in tenders or scorecards. Internal audit or external assurance may ask whether the same methodology is being applied consistently across business units. A TMS-enabled data model helps because the shipment record can be traced back to the operational event chain that generated it. This is much stronger than trying to infer emissions later from invoice spend alone.
Governance is especially important because sustainability metrics can become noisy quickly if no one owns data quality. Distances may be estimated differently across regions. Mode codes may be inconsistent. Shipments may be missing weight or volume. Premium freight may be reported without reason code, masking avoidable emissions. The TMS operating model should therefore extend master-data discipline and exception discipline into emissions reporting. Reliable carbon output depends on the same basic transport-data hygiene that reliable planning and freight audit depend on.
There is also a communication dimension. Sustainability goals are often framed at a strategic level, while transportation teams work shipment by shipment under daily service pressure. The TMS helps bridge that gap by making it possible to show how specific operating behaviors influence emissions. More consolidated truckloads, fewer emergency air shipments, cleaner appointment compliance, and better route adherence all have both cost and carbon implications. When those relationships are visible, sustainability becomes easier to operationalize because teams can see the connection between daily decisions and enterprise goals.
A practical sustainability enablement model usually answers four questions:
- Data: Which shipment attributes must be captured to support the chosen emissions methodology?
- Method: How will emissions be calculated, by whom, and for which reporting uses?
- Allocation: How will emissions be distributed across orders, customers, regions, or business units?
- Action: Which transportation policy changes are expected to improve the emissions profile over time?
The last question is the most important. Reporting by itself rarely changes freight behavior. Operational policy does. A TMS can support lower-emissions transportation by shaping order cadence, consolidation, mode thresholds, routing discipline, carrier mix, and exception approval rules. If those levers remain untouched, sustainability reporting risks becoming a measurement exercise detached from the operating model it is supposed to improve.
When sustainability and emissions reporting are enabled well, the business gains two forms of value. It gains a defensible view of freight-related carbon impact for ESG, customer, and leadership reporting. And it gains a better basis for making transportation decisions that balance cost, service, resilience, and emissions more intelligently. That is the right ambition. The TMS should not merely count transportation after it happens. It should help the company move freight in a way that is both operationally sound and increasingly accountable.
