I think the reason that they’re cracking down on this is to avoid potential overtime payments
… But what on earth does that have to do with what the person NOT working does with their day? If all they care about is overtime, then the question would be “will either person switching shifts get overtime or violate labor laws like minimum shift separations due to the switch?”
The fact that they explicitly base decisions not on the shift taker - who is more likely to receive overtime pay - but the shift giver and what they are doing OUTSIDE of work says the decision has as little to do with work as whatever you’d miss a shift for.
Literally every shift place I’ve worked has had pretty much the same rules - if you find someone to cover without making it everyone else’s problem and there’s no overtime or labor violations, who gives a f***? Crazy enough, they determined that by 1. Looking at the work schedule and 2. Checking for potential overtime work, and not by asking for a copy of my non-work-related itinerary.
I literally work with ~750,000 line exports on the daily on my little Lenovo workbook. It gets a little cranky, especially if I have a few of those big ones open, but I have yet to witness my hard drive melting down over it. I’m not doing anything special, and I have the exact same business-economy tier setup 95% of our business uses. While I’m doing this, that little champion is also driving 4 large monitors because I’m actual scum like that. Still no hardware meltdowns after 3 years, but I’ll admit the cat likes how warm it gets.
750k lines is just for the branch specific item preferences table for one of our smaller business streams, too - FORGET what our sales record tables would look like, let alone the whole database! And when we’re talking about the entirety of the social security database, which should contain at least one line each in a table somewhere for most of the hundreds of millions of people currently living in the US, PLUS any historical records for dead people??
Your hard drive melting after 60k lines, plus the attitude that 60k lines is a lot for a major database, speaks to GLARING IT incompetence.