Replacing Legacy Time Clocks in UKG Workforce Central
If you run UKG Workforce Central, it's time to look at replacing your wall time clocks when the hardware keeps failing, repairs take weeks, buddy punching is showing up in audits or a move to UKG Pro Workforce Management is on the roadmap. Tablet clocks that integrate with UKG can capture the same punches, but only a careful pilot will tell you if they're accurate and reliable at your sites.
This guide is for payroll, HRIS and operations leaders who own timekeeping across several locations and need a replacement plan that won't break payroll.
Disclosure: The author works at CloudApper, which makes CloudApper AI TimeClock for UKG (listed on its site as Time Clock for UKG, RightPunch), which is discussed in this article.
Key takeaways
- Aging wall clocks bring repair delays, limited features and extra work during a platform migration.
- Whatever replaces them must produce complete, accurate records that meet FLSA recordkeeping rules.
- Biometric punching carries notice, consent and retention duties under some state laws.
- Pilot at one site, punch in parallel for a full pay cycle and reconcile before you retire old terminals.
Why are Workforce Central customers rethinking their time clocks?
Plenty of organizations have run Workforce Central, the platform originally sold under the Kronos name, for a decade or more with dedicated wall terminals. UKG's current lineup centers on UKG Pro Workforce Management, which UKG describes as a suite for shift-based and frontline workforces covering time tracking, scheduling, compliance and labor analytics. That shift means many WFC customers are either planning a migration or already in one.
The clock review usually starts with one of these triggers:
- Failing hardware. Readers stop working, badges wear out and spare parts get harder to find.
- Expansion costs. Every new site or department needs another dedicated terminal.
- Buddy punching. A badge or PIN proves someone had the badge, not that the right person was there.
- Limited data capture. Older terminals may not handle attestations, job transfers or custom questions well.
- Migration timing. If the platform is changing, nobody wants to buy clocks twice.
A common mistake is treating the clock as a hardware purchase. It's really a data entry point for payroll. If you're weighing whether you need dedicated hardware at all, our comparison of alternatives to hardware time clocks lays out the main options.
What should a replacement time clock do?
Start with the legal baseline. The US Department of Labor's Fact Sheet #21 says covered employers must keep records for each non-exempt worker, including hours worked each day and each workweek. Payroll records must be kept for at least three years, and time cards and other records used to compute wages for two years. The DOL also says employers "may use any timekeeping method they choose," as long as the records are complete and accurate. So the question is not which device is legally required, but which one gives you the cleanest records.
Use this checklist when you evaluate options:
| Requirement | What to verify |
|---|---|
| UKG integration | Punches land on the right employee, timecard and pay rules with no manual re-entry |
| Identity verification | Face matching, badge, QR or PIN, configurable by site |
| Offline capture | Punches stored securely and synced when the connection returns |
| Data capture | Job transfers, pay codes, attestations and break prompts at the clock |
| Hardware flexibility | Runs on standard tablets so a broken device can be swapped the same day |
| Privacy controls | Biometric consent, retention schedules and deletion when someone leaves |
| Support and rollout | Realistic deployment timeline and a named escalation path |
Offline behavior deserves its own test, because it's where tablet clocks most often disappoint. Our article on what happens to punches when Wi-Fi drops covers what to check. For a broader scoring method, see our guide to evaluating tablet time clock apps.
What about biometric privacy?
Face matching can cut buddy punching, but it comes with legal duties. Several states regulate biometric identifiers. Texas is a useful example: according to the Texas Attorney General, its biometric law bars capturing identifiers such as face geometry for a commercial purpose without first informing the person and getting consent. It limits sharing, and requires destroying the data within a reasonable time and no later than one year after the purpose for collecting it ends. The Attorney General can seek civil penalties of up to $25,000 per violation.
Other states have their own rules, and they differ. Before you turn on biometrics:
- Map which states your sites and employees are in.
- Work with counsel on notice and consent language.
- Set a written retention and deletion schedule, including what happens at separation.
- Offer a non-biometric punch method where the law or your workforce requires it.
- Confirm where the vendor stores templates and who can access them.
Our guide to stopping buddy punching with face ID and geofencing covers these safeguards in more detail.
One option: CloudApper AI TimeClock for UKG
CloudApper AI TimeClock for UKG, which CloudApper also lists under the RightPunch name, is a tablet-based time clock built to work with UKG. According to CloudApper's product pages, it supports touchless face ID check-in, QR code, barcode and NFC punches, geofencing, shift bid, swap and confirm, PTO and overtime automation, a 24/7 AI assistant, employee self-service and customizable data capture for job changes, pay codes and tips. It runs on Android, iOS, iPad, FireOS and ChromeOS devices and smartphones.
CloudApper has published case studies from UKG Ready users, including Brightwater Senior Living, which describes deploying touchless time capture on standard tablets with time data submitted back to UKG Ready. Results depend on your configuration, sites and policies, so test any product, this one included, in a pilot against your own pay rules.
Questions to ask any time clock vendor
- Which UKG products and versions do you integrate with today, and what changes if we migrate from Workforce Central?
- How are punches stored and synced offline, and what happens if a device is lost or stolen?
- Where is biometric data stored, how is it protected and how is it deleted?
- Can we set punch methods, prompts and attestations by site or employee group?
- What does deployment involve on our side, and who supports us after go-live?
- Can you share references from organizations with a similar number of sites?
Frequently Asked Questions
Can tablet time clocks fully replace wall terminals in UKG?
In many environments, yes, as long as the tablet solution integrates reliably with your UKG system, handles offline punches and is mounted securely. Sites with dust, heat or heavy traffic may need rugged enclosures. Run a pilot at a representative location and compare punches against payroll results before you retire any existing terminals.
Is facial recognition required to stop buddy punching?
No. Face matching is one option. Supervisor verification, a photo captured at punch and geofencing all help too. Biometrics give stronger identity confirmation but bring consent and retention duties in some states. Many employers use a mix, turning on biometrics where it's legally and culturally appropriate and using other methods elsewhere.
Should we replace clocks before or after migrating from Workforce Central?
It depends on hardware condition and timing. If clocks are failing now, pick a replacement that works with both your current system and your target platform, and get that in writing. If clocks are stable and the migration is close, changing once at cutover is usually simpler. Either way, confirm vendor support for both environments first.
What to do next
- Inventory every clock by site, age, punch volume and failure history.
- Turn the checklist above into a scored requirements sheet, with payroll and legal signing off.
- Pilot at one site with parallel punching for at least one full pay cycle, then reconcile line by line.
- Expand in waves using our tablet time clock rollout plan.
Last reviewed: October 2026.
Sources
- Fact Sheet #21: Recordkeeping Requirements under the FLSA, US Department of Labor
- UKG Pro Workforce Management, UKG
- Biometric Identifier Act, Office of the Texas Attorney General

Comments
Post a Comment