No overtime…

I don’t think so!

And I think you probably feel the same way, right?

Now that we’ve established that fact, let’s hear how this person dealt with some bad management.

Not going to pay overtime? Think again.

“I was discussing this sub with a good friend, and he said, “Boy, have I got a story that’ll fit.” It wasn’t his story, but his brother’s, and I sat with him and got the details. Buckle up, it’s a good one…and a long one.

Let’s call him “Bob”. Bob has been fiddling with computers since he was a kid, and knows them pretty well. As with most IT people, he’s moved from job to job. The employer he worked for was a service/distribution company, and there were two IT employees. The company was located in Ontario, Canada.

Things were changing.

About three years ago, Bob’s employer decided to modernize their software. They had separate programs for Dispatching, for Inventory, for Payroll and Finances, and it was complicated moving information from one program to the other.

They decided to get an ERP (Enterprise Resource Planning) program, and Bob recommended one that he knew inside-out from a previous employer.

For those of you who don’t know, an ERP program handles everything. Purchase orders. Sales. Inventory. Personnel. Vendors. Customers. All of it. You can run a report and find out which customer has bought the most Part ABC in the last year. Which salesman has improved his numbers the most. Which vendor has the fastest delivery time. Which shipper packed the most orders.

This wasn’t easy stuff.

Everyone in the company used the ERP program, but it was very complicated, and they used the aspects of it that related to their position.

For example, the Receiver would accept a shipment, verify the quantity, confirm it was received…and the inventory stats would be available to the Sales people if they wanted to look up how many were on hand. The Receiver didn’t care what the price was, or who the vendor was, he just did his job.

Bob was run ragged during the implementation process, but he managed to train most of the employees on their aspects, and after a few months, everything was running fairly smoothly. Bob still got tickets for tweaks in the operation of the software, and occasional hardware IT issues.

Then the company decided to expand their footprint and was marketing into different time zones.

That messed things up.

Atlantic Canada is 90 minutes early, so if someone sent an email or an order at 8am their time, it would arrive at 6:30am Ontario time.

Pacific Canada is 3 hours late….so an email sent at 3pm Vancouver time would arrive at 6pm. This stretched out the day, so many staff came in early and worked late.

Bob was a busy guy…

Bob would arrive at 8am and there would be people that demanded his immediate assistance, and were annoyed that he didn’t respond instantly, even though their request was submitted before his start time. Same with late in the day…his phone would ring at dinnertime with people that wanted help right now.

They decided to stagger his and his IT colleague’s shift times, Bob would start at 6am and work till 2:30, and his colleague would start at 10:30am and work till 7pm. Bob’s colleague had kids, and refused the shift change. The employer insisted. The colleague quit.

That meant that Bob was the only person in the IT department. The employer said they would look to hire a new IT guy, but they had trouble finding one that knew the ERP system….and they were offering well under a market value salary.

This wasn’t looking good.

Bob asked for a raise and was denied. Then he wanted overtime, and the employer told him that as an IT specialist, he was exempt from overtime laws in Ontario. Bob looked it up, and the employer was correct.

This went on for some time, and he knew lots of IT people socially. They told him what the company was offering, and Bob knew that they wouldn’t find another tech.

Things went downhill from there. Bob would get chewed out if he missed a call or an email, no matter what time it came in. He had to train new hires in the ERP system, as well as take care of the hardware. He asked repeatedly for better compensation, and was denied….so he planned to get a new job.

It was time for Bob to strike back.

Now here’s the revenge.

Bob had access to the entirety of the ERP program. When a user signed in, the time was logged, and even if they didn’t sign out, after 15 minutes it would log them out anyway.

Everyone in the company was on salary, and many of them came in early and stayed late. Ontario labour law states that even salaried workers are entitled to overtime after 44 hours a week, unless they were Managers or Supervisors.

Bob got to work.

So Bob jumped into the program and ran a report for each employee that wasn’t a Manager. All the way back to when the ERP program was started. Then he reached out to an employment lawyer and got the okay to refer employees to him.

Bob lined up another job, and after he left, every employee in the company got an email with an Excel sheet showing the hours they had put in more than 44 hours a week. The subject line said “You’re Legally Entitled to Overtime Pay” In the body of the email was the lawyer’s name.

The **** hit the fan. Almost every employee authorized the lawyer to negotiate with the company on their behalf, and the company had to pay a ton of money.

All the company had to do was pay Bob for the extra work he put in. Instead, they had to pay almost everyone.”

Here’s how folks responded.

This person shared their thoughts.

Another individual said this was a job well done.

One reader doesn’t get this stuff…

Another Reddit user said these folks done messed up!

And this reader had some questions…

Good one!

If you thought that was an interesting story, check this one out about a man who created a points system for his inheritance, and a family friend ends up getting almost all of it.