Last week, I wrote about a study describing how certain timekeeping systems could create wage and hour liability through, among other things, making it easy to "cheat" and providing no transparency when changes are made. (Which makes it impossible to detect and correct errors.) Having addressed the "problem" last week, I wanted to talk this week about solutions.
But before I do that, I want to mention one more "problem" raised by my law partner Zan Blue, head of our Nashville Office. Here's what Zan emailed me last Friday (I've edited very slightly):
My dear Ms. Shea— (Yes, that's the way Zan really talks)Some employers use the auto deduct feature on the timekeeping systems. Seriously.
This feature, much like the “reply all” feature on email, should never have been created, and employers should never let it remain active.
Some employers let time sheets read “8-5” for every day. Some employers don’t even show the actual hours worked, just showing a series of “8” hours. Seriously.
Zan
Well said, Zan. Thank you. I was focused on less-obvious timekeeping issues, but automatic deductions, and use of a "paraphrased" work day instead of an actual work day, are huge problems for any employers who are still doing that.
Here are six timekeeping practices that employers can adopt to keep their risk of wage-hour liability as low as possible (realizing, of course, that there are no guarantees):
SIX TIMEKEEPING PRACTICES THAT REDUCE EMPLOYERS' RISK OF WAGE-HOUR LIABILITY
No. 1: Consider using a timekeeping system that does not allow supervisors to edit time at all. This was the preference of the authors of the study. Instead of editing employees' time, the supervisor can either "accept" or "reject" the time entry (rejections should be made with an explanation), and the rejection is then sent back to the employee. The employee corrects and resubmits the entry himself or herself.
No. 2: Be transparent. Even if supervisors do edit employees' time, that should be fine as long as the original entries and each edit can be seen and tracked. That way, if an employer is involved in wage and hour litigation, the edits and the explanations for the edits will be reviewable. Not to mention correctable, if there is a mistake. (Needless to say, this is also very helpful information to have when the employer is conducting an internal wage and hour audit.)
No. 3: Keep employees informed of all changes to their time entries, and give them an opportunity to dispute the changes. Never leave employees out of the loop. As already noted, most changes are probably legitimate and legal, and the employee will concur. That in itself could be invaluable when you're defending a wage and hour lawsuit. In the rare cases in which the employee disagrees, it's better to air that immediately and come to a prompt resolution rather than to be blindsided by it two to three years later.
No. 4: If you want to "round" time, make sure there is no (or virtually no) net loss to your employees. You may need the help of a consultant and your employment counsel in determining how rounding will affect your employees' pay. Ideally, that analysis will be done before you start rounding. But even if you're already rounding, it won't hurt to make sure you aren't adversely affecting employees and -- if you are -- to adjust your policy and, if necessary, compensate the affected employees before there is a dispute.
No. 5: Train your supervisors (and employees)! Supervisors should be encouraging employees to enter their time completely and accurately. Be sure that your supervisors understand that they are never, ever to adjust an employee's actual time downward. If they believe an employee is working too many hours, they should address that as a disciplinary or performance issue, but they should still pay for the time.
It's also a good idea to make sure that the employees themselves understand that they are expected to post all time worked, with no exceptions. Especially in the salaried non-exempt world, employees often view themselves as "professionals" and may believe it is petty to report every call from the boss while driving in to work, or every work-related email after hours. Training and reinforcement can help eliminate this mind-set.
No. 6: Zan is the man. If you are automatically making deductions for breaks or meal periods, you could have a problem because it's very likely that many of these "breaks" were not actually taken. If not, then you owe the employee for the time. It's also possible that employees will mistakenly or falsely claim they worked during the "break" when they did not. How will you prove them wrong? Do not allow employees to "paraphrase" their time as a standardized "8 to 5" or "9 to 5," but require entry of actual starting and quitting times (and actual break times). Don't ever allow employees to simply post the total number of hours they worked.
Image Credits: From flickr, Creative Commons license. Desk in Saran Wrap by Matt Reinbold; alarm clock by bingham_becky.
- Partner
Robin has more than 30 years' experience counseling employers and representing them before government agencies and in employment litigation involving Title VII and the Age Discrimination in Employment Act, the Americans with ...
Robin Shea has 30 years' experience in employment litigation, including Title VII and the Age Discrimination in Employment Act, the Americans with Disabilities Act (including the Amendments Act).
Continue Reading
Subscribe
Contributors
- William A. "Zan" Blue, Jr.
- Obasi Bryant
- Kenneth P. Carlson, Jr.
- James M. Coleman
- Cara Yates Crotty
- Lara C. de Leon
- Christopher R. Deubert
- Joyce M. Dos Santos
- Colin Finnegan
- Steven B. Katz
- Ellen C. Kearns
- F. Damon Kitchen
- David C. Kurtz
- Angelique Groza Lyons
- John E. MacDonald
- Alyssa K. Peters
- Sarah M. Phaff
- David P. Phippen
- William K. Principe
- Sabrina M. Punia-Ly
- Angela L. Rapko
- Rachael Rustmann
- Paul Ryan
- Piyumi M. Samaratunga
- Robin E. Shea
- Kristine Marie Sims
- David L. Smith
- Jill S. Stricklin
- Jack R. Wallace
Archives
- November 2024
- October 2024
- September 2024
- August 2024
- July 2024
- June 2024
- May 2024
- April 2024
- March 2024
- February 2024
- January 2024
- December 2023
- November 2023
- October 2023
- September 2023
- August 2023
- July 2023
- June 2023
- May 2023
- April 2023
- March 2023
- February 2023
- January 2023
- December 2022
- November 2022
- October 2022
- September 2022
- August 2022
- July 2022
- June 2022
- May 2022
- April 2022
- March 2022
- February 2022
- January 2022
- December 2021
- November 2021
- October 2021
- September 2021
- August 2021
- July 2021
- June 2021
- May 2021
- April 2021
- March 2021
- February 2021
- January 2021
- December 2020
- November 2020
- October 2020
- September 2020
- August 2020
- July 2020
- June 2020
- May 2020
- April 2020
- March 2020
- February 2020
- January 2020
- December 2019
- November 2019
- October 2019
- September 2019
- August 2019
- July 2019
- June 2019
- May 2019
- April 2019
- March 2019
- February 2019
- January 2019
- December 2018
- November 2018
- October 2018
- September 2018
- August 2018
- July 2018
- June 2018
- May 2018
- April 2018
- March 2018
- February 2018
- January 2018
- December 2017
- November 2017
- October 2017
- September 2017
- August 2017
- July 2017
- June 2017
- May 2017
- April 2017
- March 2017
- February 2017
- January 2017
- December 2016
- November 2016
- October 2016
- September 2016
- August 2016
- July 2016
- June 2016
- May 2016
- April 2016
- March 2016
- February 2016
- January 2016
- December 2015
- November 2015
- October 2015
- September 2015
- August 2015
- July 2015
- June 2015
- May 2015
- April 2015
- March 2015
- February 2015
- January 2015
- December 2014
- November 2014
- October 2014
- September 2014
- August 2014
- July 2014
- June 2014
- May 2014
- April 2014
- March 2014
- February 2014
- January 2014
- December 2013
- November 2013
- October 2013
- September 2013
- August 2013
- July 2013
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- January 2013
- December 2012
- November 2012
- October 2012
- September 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- October 2010