Have it on pretty good authority from a colleague whose team develops the reporting that the hours in office data pull calc will be based upon your last timestamp on WF network minus first timestamp for the day because it would be too complex to subtract people swiping out for lunch, to attend company events, take meetings in adjoining buildings etc. so don’t worry too much if you need to step out for lunch or if you want to attend a company event that is outside the building etc.
30 replies (most recent on top)
@d3 my role does not require me to be at my desk all day. I go to meetings on other floors, without my laptop. I attend town hall meetings. I collaborate with coworkers. Isn’t that the kind of stuff we’re coming in to the office to do? We’re better when we’re together, no?
@dx That is what I heard as well (< 6 hrs) -- going after those who are way out of whack on hours.
re: other comments --
yes, they can track what you're doing on office apps -- emails, meetings, teams usage, etc.
comments re: badging out for lunch-- f**k, so actually going to get something to eat is going to count against you? They going to track bathroom usage too?
That makes sense and the only consistent way to track it with out adding other more intrusive methods. .
Hopefully they dont look backwards. Alot of LOB's and managers have been extremely flexible and allowing under 5 hrs, as they were told they were allowed to.
@cg They don’t need you to badge out, they just use the last time your computer connected to the network.
I’ve seen the reporting. It says it’s based on the difference between the first time and last time of either badge or network connection. It does have disclaimers saying BYOD or virtual desktop won’t be picked up on site. It’s a four week average. They are starting the naughty list with anyone under 5 hrs in office on average. Managers are not permitted to quote the exact data/average or share it with the individual when they inquire about their in-office habits. These are “scared straight” kind of conversations - just letting the individuals know it’s being watched, and could eventually lead to performance mgt repercussions.
Eventually they’ll get those other bits ironed out and it will get rolled out.
I don’t think the C-suite really cares about any of that. Do you think such minutiae matters to people who commute to work via private chauffeur? “Figure it out or find another job” will be their response. And that’s what employees will do in the end.
@ca down voted, you should have written more since nobody will bother readin it…just like going into the office and working efficiently.
@bz people who game the system or coffee badge deserve what’s coming to them. It’s the people who have legit unusual schedules that could get shafted. West coast people often have to be working early bc of time zone differences. Some people have to work afternoon shifts for coverage and might have concerns about leaving an office late at night. Some have to work spotty hours on nights and weekends for releases or BCP events.
Our boss told us specifically they are tracking what you doing. It's more than just the difference between the start time and end time they are tracking to see if you are at your desk.
@ca and I wonder how they’ll handle someone working odd hours where they’re tagged as working at 11pm but then log off at 1am (technically the next day)
@cy your Byod usage can be tracked.
@cz vpn and log in to the network.
What about remote days, how is 8 hours of work calculated?
I also either use a BYOD Ipad or HUB, so I’m not consistently on the network. My laptop stays at home. So if I work in uptown CLT and badge in, never hit the network, and never badge out. How are they going to do that? So I gotta make sure, I log onto the HUB computer right before leaving for the day? D-mb.
For the poors who can't do a leisurely fine dining lunch may I recommend going out to McDonald's for lunch and Taco Bell for second lunch.
@ce thank god for OHIO
@cs they can’t use badge on this supposed report because not all building have badge out
Makes sense to swipe when you leave to be safe/ get max time.
They haven’t updated the manager reporting guidance in teamworks. It’s still based on the days in office reporting.
it works because they use a combination of badge swiped and network activity. They know each time you log in and know when you disconnect from the network. not rocket science.
Most of the buildings in uptown CLT don't require badging out, how's that going to work
The local restaurant industry better appreciate that I will be seeking as many slow paced fine dining lunches as possible.
Sounds like true Indian engineering 🤣🤣🤣
just like the rto reporting they will likely do some type of rollong average over time. also, to account for the many false positives and for all various type of work scenarios their will be a wide margin on the 8 hours, with managers getting emails if someone is falling below 6 hours . who knows. I'm sure more info will trickle out as the reporting becomes more readily available. there has been reporting available to senior leadership for most of the year, likely to fine tune
Good intel. Would be good to have clarity if "time stamp" means badge in or network login, or both
This is personally, how I would do it:
You’ve got two data sets, badge swipes and network pings. Take the min and max timestamp of both data sets, grouped by business day and employee ID. Then full join on business day and employee ID. For each business day/employee ID combo, take the max of max_badge_swipe and max_network_ping values, and the min of both the mins as well, a take the difference between the latter from the former.
So time in office is just the earliest of either timestamp to the latest of either. I wouldn’t even distinguish between badge-in vs badge-out, because what if the last thing some one does is badge-in to the office after going to get a snack downstairs, and then they do an in-person meeting without ever opening their work laptop again, and then leave, and their office has no badge out? In this case, at least they had the earliest and latest time the datasets could know for sure they were in the office. This minimizes false positives. The reporting should then allow for a certain number of days under the goal threshold, knowing that there will inevitably be false positive instances saying people stayed less than 8 hours. Maybe make it <7.5 hours, and only flag people who have less than that for 5-10% of their in-office days. They probably don’t want to track down every single false positive, but chances are < 7.5 hours is not going to show up more than 5-10% of the time that the vast majority of employees actually stay a full 8 hours, and if that sort of false positive rate is happening for someone, it probably has an explanation grounded in the particulars of their role/office.
Thanks doggy dog.
@c4 based on the OP is saying, the badge swipe would start it. And last badge swipe or last time on network would end it. If/when they implement it.
So if I come in and go strait to a meeting without connecting to WiFi it doesn’t start the clock?
Yeah I always figured this would be the case. I don’t work on RTO reporting in any way, but as someone who does work on reporting in other areas, this is how I would do it. Sure, there are ways it could be exploited. But for the vast majority of people who work here, it’s not going to make sense to commute twice just to coffee badge twice 8 hours apart. And those doing stuff like that on the regular would eventually get caught through other means.