WikiWorks: Mobile Time & Attendance for UKG Pro WFM
WikiWorks runs its workforce on UKG Pro WFM (labor levels, work assignments, pay codes, the works), but punching in and out, and clearing the exceptions WFM flags along the way, meant sending someone into WFM's own interface for something that should take five seconds at the door.
Punch in by name or by scan
Time entry works two ways: search an employee by name, or scan their badge, whichever's faster at the door.
Exceptions resolve like they do in WFM
A missed punch or late clock-in raises an exception; applying a pay code clears it the same way UKG Pro WFM would, from time entry or from the pay-code screen.
A paired printer, not just a screen
Pair a receipt printer to the device once. Every punch, and every exception resolved by pay code, can print a physical slip as the worker's own proof.
Admin controls that mirror WFM's own model
Default transfer, stand-in, and refreshing employees, labor levels and work assignments straight from the org's UKG Pro WFM setup.
A mobile app that punches by name search or by badge scan, resolves exceptions with the same pay codes UKG Pro WFM would apply, and pairs to a receipt printer so every punch can hand the worker a physical slip on the spot. An admin panel mirrors WFM's own model: default transfer, stand-in, and refreshing employees, labor levels and work assignments straight from the org's WFM setup.
What's in it
Time entry, speed check-in, outpunch, punch-history search by employee name or ID, exception management for both time entry and pay codes, and a pay-code admin screen: the modules shipped so far. An offline mode for time capture is scoped for a later phase.
We don't have a measured outcome yet. No before/after figure like time saved or disputes avoided has been tracked. What we can state exactly, from the project's own task tracker: time entry (by name and by scan), pay-code add, exception management, and the receipt-printer pairing screen were complete as of late December 2025; the admin panel was in progress; an offline mode for time capture was scoped but not yet built. If a real outcome number exists by now, tell us and we'll add it here instead.
Discovery
Understand the problem, the users, and the real constraints before any design work starts.
Design
Architecture and UX decisions made deliberately, before a line of production code is written.
Build
Iterative development with regular check-ins, so direction can be corrected early and cheaply.
Test
QA and hardening against real-world edge cases before anything reaches production.
Ship & Support
Launch, then stay involved: monitoring, fixes, and iteration as the product keeps growing.
