gotstamps
Well-known member
What you say is true but as I explained to the board member giving our meeting, it should be a matter of flipping a switch once all routes have been mapped. There is not need to delay start up for a year start recording data now! All data that will be required we are dealing with now, with the exception of the mapping. Once those points are identified, it just a matter of plugging them into (box location, stop location for package, delivery location) the past years history of activities. As far as all those other scanning functions that we will have to do, use a two week average for each of them and call it good. It won't be the first time we used two weeks data to determine our pay. After using the two weeks test results to get the system up and running lets say in 6 months use real numbers from then on! Its not rocket science, stop kicking the can down the road!
Sorry, but no thanks to your “2-week evaluation” of the extra scanning that we aren’t doing now. That’s been the problem with the past mail counts... 2 weeks of data making the determination of our annual pay. Those “extra” scans we’ll be doing WILL fluctuate through the year. It’ll take more time to load in the Nov-Dec months & in the winters in the north. We’ll have more packages going to the door without scans in those months, too. Rainy seasons will likely extend some scans for some peeps while it makes others hurry faster. Rain also brings more 3849s for pkg pickups.
These are just off the top of my head but I’m sure there are other things I’m not thinking of.