CarrierPoint Scorecards: On-going Monitoring of Carrier Performance
Carrier performance should be monitored and carriers should be provided timely feedback as part of our partnership with them. This information ensures that both Nucor and our carriers are afforded the opportunity to improve service immediately when issues are noted.
There are several reports in CarrierPoint which were created for the purpose of assisting Nucor in managing freight and carrier performance tracking.
Although these reports may be run on an ad hoc basis, the best practice is to schedule these for automatic delivery via email to the designated teammate(s) for review and action. Depending on the division volume and needs, this may be a daily or a weekly task. However, the recommendation is that on-going monitoring should be at least weekly. If scheduled and there are no loads returned, no report will be emailed.
- Missed Appointments
- Returns loads where either the driver arrived late or the appointment was rescheduled or cancelled after appointment window had passed.
- Enter the time period your division uses for appointments in the “Late Threshold in Minutes” field prior to generating the report (i.e., 30 if arrival is defined as Within Appointment and appointments are 30-min windows, 0 if the arrival is defined as Before Appointment, etc.)
- If upon review it is determined that a missed appointment should be excused, enter the reason on the load in CarrierPoint using the exception code MA-EX. This prevents it from being counted against the carrier in the scorecard.
- Loads Given Back
- Shows all DSM numbers cancelled after a carrier was assigned
- Only loads coded with LGB in the load log will be counted on the scorecard
- If upon review it is determined that an LGB should have been excused, enter the reason on the load in CarrierPoint using the exception code LGB-EX. This prevents it from being counted against the carrier in the scorecard.
- Retractions
- Shows all loads that were retracted by the TMS Automatic Retractions program.
- If upon review it is determined that a retraction should have been excused, enter the reason on the load in CarrierPoint using the exception code RET-EX. This prevents it from being counted against the carrier in the scorecard.
- Nothing needs to be done/entered if the retraction is not excused.
- Missed Deliveries
- Shows all loads where the carrier did not meet either the Required Delivery Date or the specified Customer/Vendor Appointment (usually entered by the carrier)
- Recommendation is to enter reason codes/notations on all loads where delivery is missed, as this can be used to provide Nucor visibility of root cause analysis of delivery concerns
- If upon review it is determined that a missed delivery should have been excused, enter the reason on the load in CarrierPoint using the exception code MD-EX. This prevents it from being counted against the carrier in the scorecard
- There is no way to remove or reverse an "excused" notation on a load. Because of this, we recommend waiting until the delivery confirmation has been entered before entering an "excused" marker -- even if it is likely it will need to be excused. (For example, perhaps a carrier is assigned a load on 4/15 that has there is a required delivery date of 4/15. Although the red date on the load continues to reflect the original customer requirement, the agreement with the carrier is that delivery should occur on 4/16. If an 'excused' marker is added in anticipation of success, then if carrier doesn't delivery the load until 4/18, the load can't be counted as a missed delivery.)
- . Delivery Report v2
- Divisions which review delivery on all loads should use this report to monitor delivery performance as it has three delivery evaluation columns
- Missed Delivery (EST) – If no required date or delivery appointment exists, use estimated transit time from pickup confirmation or last position update
- Missed Delivery (ERP) – if no required date or delivery appointment exists, use the date range shown on the load as sent by the back-end system
- Missed Delivery (ERP time) – same as Missed Delivery (ERP) but uses time as well as date