Supposedly,
There is some new report that shows any P1 pkg. that was del'd more than an hr. later than commit time.
An ops manager said that she had to trace a pkg. the other day and follow up with a CRR in a situation like this.
That's all well and fine for finding out AFTER the fact, but how is this supposed to PREVENT P1 from being delivered more than an hour past committment time?
Are managers going to run this report right after 10:30 for all Couriers they manage - then proactively notify them that they have P1 with van scans and no POD?
It simply won't work. Run the reports for the routes, then get on the computer and send a message to each route that supposedly has a P1 with no POD....
In some cases, it takes up to 15 minutes between the time a scan is done in field and the time that scan shows up in the database. So Couriers would have to make sure all their scans transmitted after they delivered their last P1, then the managers would have to wait 15 minutes for all those scans to be logged in the system, then run the report, then notify the Courier that they have a P1 on board, then have the Courier pull to the side and search their P2.
In tight areas (routes), they might be able to pull off P1 delivery no later than 1 hour post committment time, but else where - Couriers would be making a straight run to the location to get it off, then needing to head back to the point they were when they were initially notified that they had missorted P1 (since most routes have P2 placed in stop order that is the inverse of P1 stop order). Looking at 30 to possibly 45 minutes taken to get off one piece and back on track with P2 stops. That's a hell of a hit to productivity, at least a 8, probably 10% drop in SPH for a route that has 6 hours of actual on road time.
Is Express willing to eat that hit? Is Express willing to eat that loss in productivity WITHOUT pulling out OLCC and Warning letters for the Courier which happens to have a P1 piece missorted in their truck?