Originally Posted by
gloopy
Most AUG RR's that I've done/seen have not gone on timecard or even RR on the monthly schedule. Supposedly they're all "hand reviewed" now and the consensus is that takes 2+ weeks. Some rotations actually DROP in credit (if the RR takes a hard fly trip down to an ADG trip) and all there may or may not be is a vague comment burried in the rotation itself.
This will either be a well oiled machine with a company SME on the case in a week or two, or it will be a "deny deny deny" and get paid 6 months later after you can prove it scenario once we break the April ACE backlog.
Good thing we're playing footsie refunding 0.05% dues.
The general problem with reroute and how it interacts with the time card is because of ancient technology and the patchwork of reroute rules over the years. DBMS never really caught up, which is why there isn’t a “unified” or even “coherent” display of reroute pay.
Reroute pay for getting back late (23 L8/9) came first, then that is why it has its own little spot on the time card and little RR notations on the schedule display. It’s been around long enough for DBMS to catch up and is kinda automated.
Mid rotation reroute end state (pre-2019) came much later, with a much more painful history of language and grievance settlements. That’s why there is no automation for it, and they have to figure it manually. When they finally get around to paying it, it’s this obscure status code like 4F1R.
The first mistake people make is that reroute pay is just reroute pay. There are different triggers and different pay treatments depending on the exact nature of the reroute. The second is assuming the person explaining it is correct, which while with good intentions, isn’t always the case. The best thing to do is go to the source.
I agree that reroute pay, all reroute pay, should be clearly itemized on the time card. The new L4 language should also facilitate automation.