Begin with the devices already available
List the phones and computers your employees can appropriately use. Check the browsers, connectivity and any workplace rules about personal devices. An inexpensive software plan is not a reason to ignore device access or shift costs onto employees without review.
Separate a browser clock from a shared kiosk
An employee browser account identifies one person. A shared PIN kiosk has different security and supervision requirements. Gates supports the authenticated browser workflow; its legacy public PIN kiosk is disabled pending secure company-specific pairing.
Test at the actual place of work
Try the clock where people will use it, including a weak-signal jobsite or a back room. A browser app needs a connection. Do not assume a native beta safely preserves offline timestamps merely because it displays a queued action.
Show what a saved punch looks like
Employees should know the difference between tapping a button and receiving a save confirmation. Give them a simple way to report a failed request or a dead battery with the actual time worked.
Budget for support and shared-device care
Someone may need to help with first sign-ins, password access and a forgotten shortcut. If a computer is shared, supervise it and require people to use their own accounts. Do not leave an owner account open for everyone.
Keep the buying decision practical
The browser can avoid a dedicated hardware requirement in the Gates pilot. It does not eliminate the need for a reasonable device, internet access, appropriate employee policies and a reviewed payroll handoff.
Product guidance for the current early-access pilot. Keep your existing payroll records while evaluating the workflow. Last reviewed October 17, 2026.