Capturing Time When You Cannot Put a Device on the Floor

There is no internet in the back half of the building, and phones are banned on the floor. So the employees who work there have no punch record at all.

That is not a hypothetical. It is a real production facility, and it is a more common problem than most time and attendance software accounts for. A lot of vendors assume every workspace can support a networked clock, a mobile app, or at least a phone signal. Plenty of workspaces cannot.

Last updated: September 2026

When the environment itself rules out the standard options

The facility above manufactures fine metal powders, which are explosive under the wrong conditions. A static discharge from a phone is a real safety risk, so phones are banned on the production floor entirely. The back half of a sixty-year-old building also has no network connection, which rules out a networked hardware clock. Employees who take breaks in the rear break room simply have no way to record time worked there, and everyone involved knows it. The company is building a new centralized break room specifically to solve it, a construction project scheduled for next year.

Until then, there is a known compliance gap that nobody can close with a firmware update or an app download, because the constraint is physical.

Geofencing fails in the buildings you would least expect

A hospitality group operating 1,500 employees across a mix of hotel properties found that geofenced mobile punching simply does not work in a couple of their downtown locations, including a building that used to be a standard office tower before it was converted into a hotel. GPS signal inside older converted buildings is inconsistent enough that employees cannot reliably clock in through the app, so those properties fall back to physical clocks or tablets, chosen property by property rather than as a single company standard.

A home health agency runs into a related problem in the field. Caregivers clock in and out at a client’s home, but spotty connectivity makes those punches unreliable enough that payroll cannot use them directly. Billing depends on documented visit time from the clinical record instead, and that number cannot be cleanly extracted as a line item for payroll. The owner ends up entering most hours from memory, because most caregivers work the same schedule most weeks.

A single company-wide clocking method assumes a single kind of workplace

Both of these employers arrived at the same conclusion from different directions: the right method for capturing time is not one decision made once. It is a decision made per location, sometimes per employee, based on what that specific environment actually supports.

• Fixed hardware clocks for locations without reliable phone signal or where phones are restricted for safety reasons
• Biometric or badge-based clocks where a shared device needs to verify identity without depending on a personal phone
• Geofenced mobile punching only where GPS signal has actually been tested and confirmed, not assumed
• Manual entry from a verified source, such as a clinical visit record, when field connectivity genuinely cannot support real-time punches
• A documented fallback for every location, so a known gap has an interim process rather than silence until construction or infrastructure catches up

The compliance exposure is real even when the cause is not negligence

None of the employers above were cutting corners. The metal powder manufacturer has a genuine safety reason to ban phones on the floor. The hotel group did not choose to acquire a building with unreliable GPS. But under the Fair Labor Standards Act, the obligation to maintain accurate time records does not have an exception for difficult buildings. An employer still needs a documented, defensible way to capture hours worked, even when the standard tools do not fit the space.

That is why the fix usually is not one universal method. It is time and attendance software flexible enough to run hardware clocks at one location, geofenced mobile at another, and a documented manual process at a third, all feeding the same payroll record instead of three disconnected systems.

Plan the fallback before the gap becomes the audit finding

The businesses above at least know their gap exists and have a plan, even if that plan is a construction project a year out. The riskier version is a business that has not tested whether its geofencing actually works at every property, or has not confirmed that field punches are reliable before relying on them for billing and pay. Testing a clocking method at the actual location, before rolling it out company-wide, catches this before it becomes a wage and hour finding.

Frequently Asked Questions

This guide reflects publicly available product information and independent reviewer data (G2, Capterra, Trustpilot, Yelp, Better Business Bureau, Reddit, Software Advice, GetApp) as of 2026. Feature availability and pricing may vary by plan. Contact each provider for current details.

Disclaimer: Any product roadmap or future plans provided herein are for informational purposes only. They do not represent a commitment to deliver any material, code, feature, or functionality. Plans may change without notification. The development, release and timing of any features or functionality described remain at the sole discretion of Netchex, its affiliates, and partners. Netchex does not give legal, tax, or accounting advice. You are responsible for ensuring your use of Netchex product meets your individual business and compliance requirements.

Print this page