@ec+1jhnvs22z
"They never stipulated how many hours you need to be at the office to constitute a "day." "
PRECISELY! It could be argued that the policy of 4 hours PTO counting as a day in office should imply that at least 4 hours are required, it isn't that simple, especially legally.
First-- The expectation of a number of hours would need to be officially communicated (for this example let's say 4 hours in office at least).
Second-- It has to be taken into consideration that people take lunches at different points in their shift and lunch break timing can be controlled by managers. This means if you take your lunch before you hit 4 hours into your shift--and then commute home on your lunch--you wouldn't meet the requirement, and managers could use scheduling to play favorites or use it as a tool to get rid of team members.
Third-- It will be a big effort to monitor this across the company. Even with badge taps, many people at my site badge in and out several times a day. If you lose your badge you have to trust the security folks to link it to your profile properly (I had an issue where I had to prove I was at the office on certain days after I lost my badge and the 3rd party security company messed up linking my profile).
Fourth-- Even if they use network connections to prove time in office it's not a concrete way of proving hours in office. Sometimes I use my phone's hotspot wifi to work. I've gotten to the office before and worked for hours before realizing I was still connected to my hotspot and not through my site's wifi.
There are many legal issues WF could face if they enforce hours in office without making it an official policy communicated to team members ahead of time.
I'm not saying HY won't try it at some point, but if they do expect it to be officially communicated and at least 2-6 weeks for it to be fully implemented, perhaps longer. If HY tries to retroactively apply these expectations, I expect they will face several lawsuits.