Monday, September 25, 2006

Rejected Timesheet

Last week, The Corporation announced some changes to the website that we use to fill out our time cards. "All changes are very MINOR and should not cause any difficulties when creating and submitting timesheets." I was not overwhelmed with confidence, having had paychecks screwed up before when there were so-called minor changes. The Operations Manager also included this little gem in her e-mail about the change:

"Over the past two weeks, you may have received a Recruitmax Timesheet Training Session Invite. If you did not receive this or you received this invite but was unable to attend, PLEASE DO NOT WORRY. I have attended the Training Session for you and have summarized some of the changes below."

Let's hear that again: "I have attended the Training Session for you." So, is that how training at the Help Desk is being handled now? Management takes the training and the rest of us are to learn by osmosis?

It was, therefore, no surprise, when Friday came along and noone was able to fill out their timesheets properly. My Thursday and Friday slots were blocked out so that I could not enter any times, as if these days were holidays that the offices were closed. The returned message was "Placement ended due to inactivity."

The Operations Manager had coincidentally called off so there was a scramble with HR to figure out what was going on. Team Lead D**** sent out the message:

"Please do not be alarmed by this.... it will be corrected and paychecks will not be affected."

First off, I have no reason not to be alarmed when every time there is a change, things get screwed up. It's not being paranoid if it's true. Secondly, as a Team Lead he had absolutely no authority to make the statement that paychecks would not be affected. He doesn't know shit about what's going on and it's inappropriate for him to make it out like he does.

Well, Monday rolled around and I was able to get back into the system an correct my time card so it looks like they fixed this foul-up. Even so, I have no reason to be confident in that their minor changes failed yet again.

No comments: