Almost every time-tracking app on the market defaults to location tracking. It's an easy sell to a manager: know exactly where your staff are, whenever they're clocked in. It's also, in our view, the wrong default for hospitality — and we built smartHOD specifically not to work that way.
What GPS clock-in actually requires
To verify someone is on-site, GPS tracking needs to know where they are continuously while clocked in — not just at the moment of the tap. That means the app is running location services on a personal phone, for hours, for a shift worker who almost certainly didn't read a detailed data-processing agreement before their first day. It means the employer is now a custodian of continuous location data for every hourly worker on staff. And it means every phone battery drains faster for a feature that solves a problem most properties don't actually have.
What the problem actually is
The thing you're really trying to solve isn't "where is this person" — it's "did this person actually clock in from the property, not from home." That's a much narrower problem, and it doesn't require tracking anyone's location at all.
QR-at-reception solves the narrow problem without the broad one
A printed QR code at the property — reception desk, staff entrance, wherever makes sense — that staff scan with their phone camera to clock in and out. No app to install. No login required for the clock-in action itself. No GPS, no geofencing, no background location permission. The code only works from a device that's physically scanning it, which is exactly the verification a property actually needs, without collecting anything else.
The trade-off, honestly
QR-at-reception can't tell you someone clocked in from the car park instead of the desk, or from a colleague's phone handed across the counter. GPS-based systems solve for that. In our experience running actual hotels, that specific edge case is rare enough, and the privacy and trust cost of default-on location tracking is high enough, that it's the wrong trade for most independent properties. If you're running a large distributed workforce where that specific fraud pattern is a real, measured problem, a GPS-based tool may genuinely be the better fit for you — that's a legitimate reason to choose differently, not a reason we think QR is wrong in every context.
Why this is a permanent design decision, not a missing feature
This isn't "GPS tracking, coming soon." Not collecting location data by default is a deliberate choice about what smartHOD is willing to ask staff to hand over in exchange for clocking in on time. Trust between a property and its team is worth more than the marginal fraud case GPS would catch — and staff notice the difference between a tool that respects that and one that doesn't, whether or not anyone ever says so out loud.