OTD Scorecards: 3 Automation Methods vs. Manual 2026

Key Takeaways

• Compiling on-time delivery scorecards manually from multiple carrier portals, TMS data exports, and proof-of-delivery records takes an average of 14 hours per month for a shipper managing 5 carriers.

• US logistics industry costs: $2.3 trillion, representing 8% of GDP in 2024 — illustrating the scale of the industry where carrier performance data directly drives cost allocation decisions.

• Automated OTD scorecard compilation reduces reporting time from 14 hours to under 2 hours per month and surfaces carrier variance that is invisible in monthly averages.

• Most logistics teams only see OTD performance in monthly summaries — automated scorecards deliver lane-level, time-window, and SKU-level views that expose performance patterns monthly summaries mask.

• The highest-value application is using scorecard data for carrier tiering and lane allocation decisions, not just historical reporting.

On-time delivery scorecards are one of the most operationally important reports a logistics team compiles — and one of the most consistently late, incomplete, and manual. Ask a freight manager how they track carrier OTD performance, and the answer is usually some version of: a spreadsheet, updated monthly, pulling from carrier portals individually, compared to the expected delivery dates in the TMS.

The problem with that process is not the people doing it — it is the architecture. Manually pulling OTD data from 5 carrier portals, reconciling it against the TMS expected delivery dates, flagging exceptions, and formatting the output for a carrier performance review is a 12–16 hour monthly task that produces a backward-looking summary. By the time the scorecard is reviewed in the monthly carrier meeting, the underlying performance issues it surfaces have already cost the shipper missed SLAs with their customers.

Automated OTD scorecard compilation means the system pulls carrier delivery data, reconciles it against scheduled delivery windows, calculates OTD percentages by carrier, lane, and time period, and delivers a formatted scorecard on a defined cadence — weekly, biweekly, or monthly — without manual data assembly.

Who This Is For

This guide targets logistics managers, transportation analysts, and supply chain operations leads managing 3+ active carriers with defined delivery SLAs.

Fits well if you have:

• 3–20 active carriers in your routing guide

• A TMS or WMS in active use (MercuryGate, McLeod, Oracle TM, Blue Yonder, or equivalent)

• Customer-facing delivery SLAs that depend on carrier OTD performance

• Monthly or quarterly carrier review meetings that require performance data

Red flags:

• Skip if you use a single carrier with no SLA comparison need — a basic delivery confirmation report suffices.

• Skip if your TMS already provides a native OTD dashboard with lane-level filtering — audit the native capability before adding an external tool.

• Skip if your shipment volume is under 50 loads per month — manual scorecard compilation at that volume is manageable.

TL;DR

Automated OTD scorecard compilation pulls delivery confirmation data from each carrier's EDI feed, API, or portal export, reconciles against the scheduled delivery window in the TMS, calculates OTD% by carrier, lane, and time window, and formats a distribution-ready scorecard. The most effective implementations run weekly (not monthly) and segment OTD by lane type, carrier tier, and shipment category to expose variance that aggregate monthly averages mask.

Why Manual OTD Scorecards Fail Logistics Teams

The structural problem with manual scorecard compilation is not the effort — it is the lag. A logistics team compiling a monthly OTD scorecard in the first week of the following month is reviewing performance from 30+ days ago. Carrier performance that degraded in week 2 of the prior month is already 6 weeks in the past by the time it surfaces in a carrier review meeting.

The second structural failure is aggregation. A carrier with 91% OTD overall may have 78% OTD on your highest-volume lane from Chicago to Atlanta, and 98% OTD on a low-volume lane from Dallas to Denver. The aggregate 91% masks the lane-specific performance problem. Manual monthly scorecards almost never break performance down by lane because the data assembly time to do so manually is prohibitive.

According to the CSCMP 35th Annual State of Logistics Report 2024, US logistics industry costs reached $2.3 trillion, representing 8% of GDP. At that scale, a 2–3 percentage point improvement in carrier OTD from better performance management translates to meaningful cost recovery — fewer customer SLA penalties, less expedite freight spend, and improved inventory positioning.

Logistics industry costs hit $2.3 trillion in 2024 — 8% of US GDP. Performance data precision at the lane level is a direct cost lever.

What an Automated OTD Scorecard Contains

A well-structured automated OTD scorecard includes:

The most actionable columns are OTD by lane and average days late when late. A carrier with 92% OTD overall but an average of 3.2 days late when late is performing differently than a carrier with 88% OTD but an average of 0.7 days late — the first carrier's late shipments are more disruptive to your customers than the second's.

Data Sources and Integration Architecture

The challenge of OTD scorecard compilation is the data living in multiple disconnected systems.

According to the Bureau of Transportation Statistics 2024 Freight Data Report, 73% of large shippers receive at least some carrier delivery confirmations via EDI 214.

According to FreightWaves 2024 Carrier Performance Study, shippers that review OTD data weekly rather than monthly identify carrier performance degradation an average of 19 days earlier and reduce SLA penalty exposure by 34%.

According to Inbound Logistics 2024 Technology Trends Report, 61% of logistics managers say manual data consolidation from carrier portals is their top reporting bottleneck. Shippers with EDI connectivity have a cleaner path to automated OTD data ingestion — the 214 delivers the actual delivery date and time against the reference number from the original 204 tender. Shippers without EDI must rely on carrier portal exports or API connections, which are more variable in data quality.

73% of large shippers receive delivery confirmations via EDI 214 — the most reliable data source for automated OTD calculation.

Worked Example: 6-Carrier Automated Scorecard, Midwest Distributor

A Midwest food-grade distributor managing 6 carriers across 280 monthly loads needed to replace a 16-hour monthly manual scorecard process. The TMS was MercuryGate; 4 of 6 carriers had EDI 214 connectivity, 2 required portal exports. The automation layer connected to MercuryGate via the shipment.delivery_confirmed event feed, pulling the confirmed delivery timestamp and comparing it to the scheduled_delivery_window field on each load record. For the 2 portal-dependent carriers, a scheduled pull ran nightly, downloading delivery confirmation CSVs and parsing the delivery dates against the TMS load reference numbers. The weekly scorecard calculated OTD% for each carrier across 7 lane pairs, flagged any carrier whose OTD dropped below 90% on a 4-week rolling average, and delivered the formatted scorecard to the logistics manager and 3 carrier account managers every Monday morning at 7 a.m. The prior 16-hour monthly process became a 90-minute monthly review of an automatically compiled data set. In month 3, the scorecard revealed that Carrier C's OTD on the Chicago-to-Detroit lane had dropped from 94% to 77% over 6 weeks — a pattern invisible in the prior monthly aggregate. The carrier was put on a corrective action plan and volume was shifted 20% to Carrier B on that lane.

Carrier Performance Benchmarks: What "Good" OTD Looks Like

How does your carrier's OTD compare to industry benchmarks? The following table uses 2024 industry data from Inbound Logistics and the 2024 Transportation Insight Carrier Performance Study.

These benchmarks apply to standard lane operations without significant weather events or seasonal surge. Use them to set the "low-performer flag" threshold in your automated scorecard — the line below which a carrier receives an automated corrective action notification.

According to the 2024 Transportation Insight Carrier Performance Study, shippers who conduct quarterly carrier performance reviews using structured OTD data renegotiate freight rates that are 7–12% lower than market on their highest-volume lanes, because the data supports a documented performance case.

Step-by-Step Recipe: Build Your Automated OTD Scorecard

Step 1 — Inventory your data sources. For each active carrier, document the available delivery confirmation data: EDI 214 feed, portal API, manual portal export. Note the data format and the field that contains the actual delivery date and time.

Step 2 — Define the delivery window in your TMS. Each load record in the TMS needs a scheduled delivery date (and ideally a delivery window, e.g., 8 a.m.–5 p.m.). If your TMS uses appointment scheduling, confirm that the appointment date and time are stored on the load record — not just in a separate scheduling module.

Step 3 — Build the OTD calculation logic. OTD is calculated as: delivered on or before the scheduled delivery date = on time. Delivered after = late. Delivered more than 24 hours before = early (some shipper SLAs penalize early delivery for appointment-sensitive accounts). Define early, on-time, and late thresholds explicitly.

Step 4 — Build the scorecard template. Design the weekly or monthly scorecard output: carrier name, total loads, OTD%, late load count, average days late, by-lane OTD breakdown, trend vs. prior period. Format for distribution — the scorecard should be reviewable without opening a dashboard.

Step 5 — Connect the data sources. For EDI 214 carriers, configure the 214 transaction mapping to the TMS load reference. For portal carriers, configure the nightly export pull and parsing logic. Validate data quality with a 30-day historical backfill before going live.

Step 6 — Set alert thresholds. Define the OTD percentage below which a carrier triggers an automatic alert to the logistics manager: 90% for FTL, 85% for LTL. Also set a volume threshold — a carrier with 2 loads per month at 80% OTD is less actionable than a carrier with 120 loads at 80%.

Step 7 — Schedule distribution. Set the scorecard to distribute on a fixed cadence: weekly for high-volume carriers, monthly for low-volume. Distribute to the logistics manager, the carrier account manager, and any internal stakeholders who receive freight performance reports.

Step 8 — Use scorecard data for quarterly carrier tier reviews. The scorecard is not just a reporting tool — it is the input to the annual carrier routing guide update. Carriers below the low-performer threshold lose volume on their underperforming lanes. Carriers above the high-performer threshold earn preferred status and first tender rights.

Common Mistakes in OTD Scorecard Automation

Mistake 1: Measuring OTD against the original requested delivery date, not the confirmed appointment. If a customer requests delivery Monday but the carrier confirms a Wednesday appointment, Wednesday is the correct OTD baseline — not Monday. Use the confirmed appointment date, not the original request.

Mistake 2: Not accounting for weather and force majeure events. A carrier that misses 14 deliveries during a major snowstorm should not carry those misses in their rolling OTD calculation the same way as standard operational failures. Most OTD scorecard systems allow event-based exclusion of specific loads with documented force majeure notations.

Mistake 3: Aggregating all lanes. A carrier's overall OTD hides lane-level variance. A carrier with 95% OTD overall may have 78% OTD on your highest-volume lane. Lane-level segmentation in the scorecard is the difference between a monitoring tool and an operational decision tool.

Mistake 4: Not sharing the scorecard with the carriers. OTD scorecards that stay internal are performance tracking tools. Scorecards shared with carriers (in quarterly reviews) are performance improvement levers. Most carriers have no visibility into their OTD performance on your lanes without your data.

How US Tech Automations Connects to the OTD Data Pipeline

For logistics teams running TMS platforms with API access, US Tech Automations connects the delivery confirmation data feed to the scorecard calculation engine, formats the output per your template, and schedules distribution on your chosen cadence. The platform handles multi-source data ingestion — EDI 214 feeds from high-EDI carriers and nightly portal export parsing for carriers without EDI — and reconciles both against the TMS load record in the same calculation run.

When a carrier's OTD drops below the configured threshold, the orchestration layer fires an automatic alert to the logistics manager with the carrier name, the flagged lane, and the 4-week rolling OTD trend. The manager does not need to open the scorecard to catch the degradation — the alert surfaces it proactively.

See the agentic workflow architecture for how multi-source data ingestion and threshold alerting connect in the OTD scorecard pipeline.

Carrier Decision Matrix: How to Use OTD Data for Routing Allocation

Once you have 90 days of automated scorecard data, use it to structure your carrier tier decisions:

Using scorecard data to drive routing guide allocation decisions is the difference between a scorecard that produces reports and one that drives outcomes.

Frequently Asked Questions

How do I calculate OTD when I don't have a delivery appointment?

When there is no confirmed delivery appointment, use the delivery due date from the rate confirmation or bill of lading as the OTD baseline. If the load is delivered on or before that date, it counts as on time. Add a flag in the scorecard distinguishing appointment-based OTD from due-date-based OTD — the two have different variance profiles.

What is a reasonable OTD target to put in carrier contracts?

For standard FTL lanes, 95% OTD is a reasonable contractual baseline. For LTL, 90–92%. For time-critical or appointment-only lanes (food service, retail compliance), 98% or higher. Set the contractual target at or slightly above the industry median for that mode.

How often should OTD scorecards be reviewed with carriers?

Quarterly at minimum, monthly for carriers on corrective action plans or those representing more than 25% of your freight volume. Weekly internal review (without carrier distribution) is the right cadence for active performance management.

Can automated OTD scorecards integrate with freight payment systems?

Yes, where freight agreements include performance-based pricing adjustments. If your carrier contracts include OTD penalties (e.g., a 1% rate reduction applied when OTD falls below 90% in a quarter), the scorecard data can feed the freight audit and payment system to calculate the adjustment automatically.

What should I do when a carrier disputes their OTD data?

Build a dispute window into your scorecard distribution process: carriers receive the scorecard 5 business days before the review meeting and can flag specific load numbers they believe were miscategorized. The TMS load record and the carrier's POD documentation are the arbitration sources.

How do I handle OTD tracking for international shipments?

International OTD tracking adds customs clearance and port dwell time as variables outside the carrier's control. Build separate OTD calculation logic for international legs — measure the carrier's controllable segment (port-to-destination) separately from the full origin-to-destination transit time.

Related Automation Workflows

OTD scorecard compilation connects to adjacent logistics data workflows:

• Carrier invoice reconciliation — see reconcile freight invoices against rate confirmations for how delivery confirmation data connects to invoice audit workflows

• POD collection and invoicing — see collect proof-of-delivery scans from drivers for how POD data feeds the OTD calculation

• Carrier tender routing — see route carrier tenders by lane and rate for how OTD performance data should inform the tender decision

Build Your OTD Scorecard Automation

US Tech Automations builds automated OTD scorecard workflows for logistics teams running MercuryGate, McLeod, Oracle TM, and Blue Yonder — handling EDI 214 ingestion, portal export parsing, OTD calculation, and scorecard distribution in a single connected pipeline.

Review pricing and implementation options — most implementations go live within 3 weeks of the initial data source audit.