On-time delivery %
Northgate Fabrication
Scored from your answers. Not a comparison with other companies.
Your answers show several gaps that an AI tool would inherit from this number.
An AI tool reading your on-time delivery number would read the shipping spreadsheet, and a spreadsheet cannot tell it when an input stopped arriving. In the two weeks after the carrier switch, it would have reported on-time delivery from incomplete ship dates with no warning. A model or assistant is only as current as the feed underneath it, and today nothing flags when that feed goes quiet.
Definition and ownership are settled. The blind spot is a feed that goes quiet.
One definition, one owner and one site rule out the usual arguments about what the number means. What is left is the hand-off into the spreadsheet. When ship dates stopped flowing after the carrier switch, the Monday comparison with the ERP report was the only check, and with no change record there was nothing to show when it started. In a spreadsheet, a broken feed and a quiet week look the same.
Count the rows in the shipping spreadsheet for each week of the last two months. A week with far fewer rows than usual points to a feed problem, not a slow week.
Compare last Monday's spreadsheet with the ERP report order by order, not just the totals.
Write down every manual step between the carrier data and the spreadsheet, and who does each one.
If the carrier feed stopped tomorrow, how would we find out, and how long would it take?
Which manual step in getting ship dates into the spreadsheet would we remove first?
Where would we record a change to how on-time delivery is calculated?
This page looks at one number and twelve questions about how it gets made. A Structured Review looks across all five readiness areas (strategy, data, systems, governance and change) with your leadership team in half a day.
Book a time with Jim
Talk this through in 30 minutes
Want to talk through what this means for your team? Book a time below or call me directly.
Book 30 minutes with Jim