Delivery Scorecard Review
Review delivery exceptions with route records, jobsite changes, and named owners for the next request.
A delivery scorecard becomes constructive when both sides can trace each exception to the conditions around it. The account manager should avoid treating one percentage of deliveries made on schedule as a verdict. Pull the delivery date, route record, request time, site contact, access notes, and any customer change that occurred after scheduling. Then group the review by branch or project so the people who can improve the work see their part clearly.
Jo, a regional superintendent, said, “We had six late deliveries this month. Are you going to fix this before our next pour?” Malik replied, “I want to review each event with the branch owner and your project contacts. Which delays caused a crew impact, and which deliveries had a change in gate access or timing?” Jo pointed to two loads that arrived after a lane closure began and one that was rescheduled by the customer late in the day.
Malik said, “I will ask dispatch for the route notes and mark the customer schedule changes separately. For deliveries affected by lane closures, can your traffic lead join a review with the branch manager? We can agree on the information dispatch needs before future requests are released.” He did not promise a delivery outcome. He committed to a review with named records and owners.
That approach respects the customer’s frustration while keeping the scorecard accurate. A recovery plan may involve dispatch timing, better access instructions, or a customer contact who confirms a changing site.
Use a past delivery exception in practice. Explain the difference between a route record and a conclusion about fault. Ask the customer for the business impact, then propose one review meeting with people who control the next request. Finish with an action list that includes update dates.
Practice these next
Plan a contractor yard move by separating delivery, return, billing, and account detail decisions.
Turn utilization data into a fair renewal discussion by checking project timing, equipment need, and service history.
Map equipment, site prerequisites, and customer approval owners before coordinating support across locations.
Build a seasonal fleet forecast that separates awarded work from bids and records decision dates.
Create a governed discovery session before combining entities, sites, and equipment needs.
Use forecast confidence and clear owners when a project needs scarce equipment.