It's a good thing I actually don't need the hours, or I'd be steamed over this. Still, this strikes me as odd.
Two of my days for this week are marked as "Time Off Approved" on e-Schedule. Thing is, I never put in any such requests. In fact, looking at the "Date Submitted" column of the requests shows that the requests were put in the very SAME DAY the schedule was written. We all know employees can't do that through e-schedule. That means either my schedule writer did it, or someone else who has access to e-Sked did it. The question is... why? If the store is cutting hours (wouldn't surprise me... hooray for even LESS stuff getting done now), why not just not schedule me those two days? I already have two days off because I'm unavailable, but again, I don't need the hours that badly, so I'm actually looking forward to some extra me time this week. It's really a strange way to cut back hours though, to go through the trouble to go in the system, input employee requests, and then approve those requests. That would seem to be a more time consuming process, but maybe it's not.
Ask your schedule writer, he/she may have their weird ways of writing the schedule. They have the power to override one's availability and put in days that said you requested them off when you didn't.
When the schedule writer runs the E-Schedule program. It creates a score. If they make changes to the schedule, the score drops. If it drops below a certain percentage, they get in trouble. The schedule writer can however do things within limits such as put in requests for off days or a certain shift for people in order to get it to generate a better schedule for the department. Maybe by giving you two specific off days the schedule was able to force E-Schedule to generate a schedule that worked better for the department. As long as you get the hours due you based on your seniority then everything is fine.
If they make changes to the schedule, the score drops.
It doesn't actually work that way, but don't feel bad for thinking that; it's a VERY common misconception that gets passed on to new schedule writers who just take it as true because their teacher told them it was.
And GenesisOne, your scheduler probably wanted to specify 2 days off for you and didn't know how to specify that in the schedule screen itself, and only knew how to put in those days off as requests.
It's a good thing I actually don't need the hours, or I'd be steamed over this. Still, this strikes me as odd.
Two of my days for this week are marked as "Time Off Approved" on e-Schedule. Thing is, I never put in any such requests. In fact, looking at the "Date Submitted" column of the requests shows that the requests were put in the very SAME DAY the schedule was written. We all know employees can't do that through e-schedule. That means either my schedule writer did it, or someone else who has access to e-Sked did it. The question is... why? If the store is cutting hours (wouldn't surprise me... hooray for even LESS stuff getting done now), why not just not schedule me those two days? I already have two days off because I'm unavailable, but again, I don't need the hours that badly, so I'm actually looking forward to some extra me time this week. It's really a strange way to cut back hours though, to go through the trouble to go in the system, input employee requests, and then approve those requests. That would seem to be a more time consuming process, but maybe it's not.
Anyone have any insights on this?
Nigga, this is why I be getting 40 every week and they be jacking your shizz all up!
If they make changes to the schedule, the score drops.
It doesn't actually work that way, but don't feel bad for thinking that; it's a VERY common misconception that gets passed on to new schedule writers who just take it as true because their teacher told them it was.
And GenesisOne, your scheduler probably wanted to specify 2 days off for you and didn't know how to specify that in the schedule screen itself, and only knew how to put in those days off as requests.
This is what I was told too, what's the truth then? Without a score/penalty for changing shifts around, how is eSched going to make sure the schedule writer doesn't just make up their own schedule? Or does it not really care?
If they make changes to the schedule, the score drops.
It doesn't actually work that way, but don't feel bad for thinking that; it's a VERY common misconception that gets passed on to new schedule writers who just take it as true because their teacher told them it was.
And GenesisOne, your scheduler probably wanted to specify 2 days off for you and didn't know how to specify that in the schedule screen itself, and only knew how to put in those days off as requests.
This is what I was told too, what's the truth then? Without a score/penalty for changing shifts around, how is eSched going to make sure the schedule writer doesn't just make up their own schedule? Or does it not really care?
eSched is one big mess. Two weeks ago, I went from 12 to ~26 until the schedule was fixed at 20. I had hours where people above me should've had first. This week, it's the same thing essentially; someone above the bottom guy gets 12 hours, but didn't have any requested days off, just unavailable days for school, whereas the bottom guy has 16 (I have 13-ish but that's because I recently changed my availability).
It's crap like that that makes people disgruntled about their forever erratic schedules.
If they make changes to the schedule, the score drops.
It doesn't actually work that way, but don't feel bad for thinking that; it's a VERY common misconception that gets passed on to new schedule writers who just take it as true because their teacher told them it was.
And GenesisOne, your scheduler probably wanted to specify 2 days off for you and didn't know how to specify that in the schedule screen itself, and only knew how to put in those days off as requests.
This is what I was told too, what's the truth then? Without a score/penalty for changing shifts around, how is eSched going to make sure the schedule writer doesn't just make up their own schedule? Or does it not really care?
Esched's goal when it schedules is to approach the predicted headcount from elms as closely as possible. Scheduling exactly to those headcounts would give a 100% schedule rating. But the scheduling algorithm isn't perfect, and it leaves shifts that need tweaking. If those changes deviate shifts from the headcount, you lose schedule rating; over-schedule or under-schedule and lose on your rating. However, make tweaks that bring you closer to your headcount, and your rating rises.
TL;DR: on the 3-job-graph-and-grid screen, make changes that eliminate black (overs) or red (shorts) numbers on the line with the job class, and your rating rises. Otherwise, your rating drops.
If they make changes to the schedule, the score drops.
It doesn't actually work that way, but don't feel bad for thinking that; it's a VERY common misconception that gets passed on to new schedule writers who just take it as true because their teacher told them it was.
And GenesisOne, your scheduler probably wanted to specify 2 days off for you and didn't know how to specify that in the schedule screen itself, and only knew how to put in those days off as requests.
This is what I was told too, what's the truth then? Without a score/penalty for changing shifts around, how is eSched going to make sure the schedule writer doesn't just make up their own schedule? Or does it not really care?
eSched is one big mess. Two weeks ago, I went from 12 to ~26 until the schedule was fixed at 20. I had hours where people above me should've had first. This week, it's the same thing essentially; someone above the bottom guy gets 12 hours, but didn't have any requested days off, just unavailable days for school, whereas the bottom guy has 16 (I have 13-ish but that's because I recently changed my availability).
It's crap like that that makes people disgruntled about their forever erratic schedules.
The bottom guy got more because the other person has restricted days. If you're restricted, you are NOT guaranteed more hours than the people below you.
