Answers - sm Posted: Mar 18th, 2018 - 1:16 pm In Reply to: New Schedule Compliance - DJS
If you are getting the no jobs message but there is anywhere between 1-5 minutes between reports, you are supposed to stay in Fluency and wait but log out of Workforce.
Once you get a full 6 minutes of NJA, you can log out of both and that's when you file a Remedy ticket. Then you decide whether you want to make up the time or take time off. If you decide to do time off, you use your own EANP or PTO to put in a leave request for the remainder of that shift. You only put in the NJA Remedy ticket once per shift, though.
All this punching in and out of Workforce will make you short on hours at the end of the day, and you will need to make up the time or use your PTO or EANP for that too.
It is totally unfair because you should not have to use your own PTO/EANP for time off due to NJA, which is not even remotely your fault. But if you ask me, none of this is being handled in a way that is fair to the MTs.
So up until this new Schedule Compliance thing, it has been fine to stay at your computer all day and punch in and out of Workforce and even if you have to sit there 12 hours to get in a full 8-hour shift, it's OK as long as it's the same day your shift is scheduled.
That's what they are now taking away from us. I am assuming they think they've come up with a brilliant plan to make it harder for people to make up time on different days without looking for approved hours on Workforce.
Maybe it works for that. But even if certain people are doing that, it unfairly creates a huge nightmare for everyone else not doing that who have been willing to work crazy long (unfair and unpaid!!) hours to get in their time on the same day because we all know that is way preferable to trying to find a shift on Workforce. That is such a big problem this idea never should have made it off the ground.
You are right, it's ridiculous. That's actually putting it very nicely.
Post A Reply Reply By Email Options
Complete Discussion Below: (  marks the location of current message within thread)
|
