Staff Clock-In Location: When GPS Says You're Far Away, But You're at the Door

At Salun Rambut Bella in Ipoh, a stylist named Yana lives ten minutes from the shop. A few times a month she taps Clock In from her own bathroom at home — "so it doesn't look like I'm late" — and only then gets ready and heads out. The attendance record shows her arriving at 9 a.m. every day, even on the mornings she doesn't actually walk in until twenty minutes later.

At Bengkel Auto Perdana in Johor Bahru, a mechanic named Faizal got stuck in highway traffic one morning. He messaged a colleague on WhatsApp: "tap Clock In for me, my phone's charging on the desk." The colleague tapped it using Faizal's unlocked phone. The record shows Faizal already at work, while he's actually still 45 minutes away.

At Klinik Pergigian Senyum Ceria in Kuching, a receptionist named Siti was standing right at the front desk and tapped Clock In. The screen immediately said she was outside the work area. The clinic's walls are thick; her phone had fallen back to cell-tower positioning instead of real GPS, and the location estimate was off by several hundred metres — even though she was genuinely standing inside.

Why this keeps happening

First: attendance based purely on a button tap proves nothing. A tap on a phone screen says nothing about where that phone actually is, let alone who tapped it.

Second: a paper log or a WhatsApp message only records the time, not the place. There's nothing in that record to check whether the staff member was actually on the premises when they tapped Clock In.

Third: a phone's own GPS is not always accurate. When the satellite signal is weak — inside a building, behind thick walls — the phone falls back to an estimate from Wi-Fi or nearby cell towers, and that estimate can be off by several hundred metres even when the owner is standing exactly where they should be.

Fourth: when several staff share one shop phone or one paper log, anyone can tap on a colleague's behalf without anyone else noticing — as happened with Faizal.

What owners try instead

Most common: a paper log or a manual punch card, one signature a day. Fast and simple, but there's no location evidence at all, and a signature is easy to fake on behalf of someone who never showed up.

Some invest in a physical fingerprint clock machine. Accurate on identity — you can't lend someone your fingerprint — but expensive for a small business, and staff still have to stand right in front of that one machine. It doesn't help at all when the real problem is a staff member who hasn't arrived yet, because the machine only knows when a finger touched it, not when the person actually got there.

Others rely on asking around and trusting people. This works when the owner is on the floor with staff every day and knows everyone personally. It breaks down once the team grows past a handful, or once the owner isn't always on-site to notice who arrived when.

Some use a generic attendance app that only logs the time a screen was tapped. The time is correct, but the app doesn't — and can't — know whether that phone was at the shop or at the staff member's home ten minutes away.

How location-based clock-in should work

First principle: the owner sets ONE workplace point, once. At Menu → Staff & Payroll → HR & Staff → Settings tab, under "Clock-In Location", the owner taps "📍 Use Current Location" to capture their own phone's GPS while standing on the premises, sets a Radius (m) — between 20 and 5,000 metres — and taps Save. (This sits inside the HR module, so that module needs to be switched on first.)

Second principle: once switched on, this is enforced in code on every single Clock In — it isn't left up to the staff member. If a staff member's phone sends no location at all, the clock-in is refused outright, with a message asking them to allow location access. If a location is sent but it's further than the radius allows, the clock-in is also refused — and the error shows the actual estimated distance, not just a bare refusal.

Third principle, and this is the part most likely to be misjudged: GPS accuracy is recorded on every successful Clock In, but it never automatically loosens or tightens the radius. Accuracy is evidence for the owner to check afterwards, not a condition the system applies live. This matters because a phone that falls back to Wi-Fi or cell-tower positioning can be wrong by several hundred metres — exactly what happened to Siti above. That's why the radius you set should be a little more generous than your first instinct, not drawn tight along the building's walls, so ordinary GPS drift doesn't reject a staff member who is genuinely on-site.

Fourth principle: every refusal is logged, not just successful clock-ins. When a staff member says "the system won't let me clock in", the owner can check the real reason — no location permission, or too far away, and exactly how far — instead of just taking the staff member's word for it or asking them to read their screen back.

Fifth principle: this control can be switched off at any time by tapping "Disable" in the same settings screen. Basic Clock In and Clock Out keep working exactly as before, with no location requirement, the moment it's off.

When it helps most

The difference is sharpest for businesses that run from one fixed premises with more than two or three staff on shift — a salon, a workshop, a clinic — where the owner isn't always on-site to notice who arrived when.

An honest word on the limits. If your business runs more than one branch under a single TempahKu account, note that only ONE location point and ONE radius are stored per account — it isn't built to control separate branches independently. It also doesn't help a business whose staff are meant to be at the customer's premises — home visits, mobile work — since there's no single fixed location to check against. And note this too: the control checks the phone's LOCATION, not WHO tapped the screen. If a colleague borrows an unlocked phone while both of them are genuinely standing at the same premises, location control cannot catch that — that's a separate trust question, and a geofence doesn't solve it.

If your team is small, everyone works alongside you every day, and attendance has never been an issue, location control may be more setup than it's worth right now. It earns its keep the moment an owner starts to wonder whether the attendance record is telling the real story.

In short

Staff attendance problems are rarely about honest staff versus dishonest staff — they're about a record that only ever captured the time, never the place, with no way to check which is which. TempahKu locks Clock In to one workplace location and radius the owner sets, refuses outright when location is missing or too far, and logs every refusal so "why won't it let me in" has an answer that can actually be checked. GPS accuracy is kept as evidence, never as an automatic override, because a phone drifting hundreds of metres inside a thick-walled building is an everyday reality, not an edge case. If you've ever wondered whether your shop's attendance record tells the real story, that alone is reason enough to start.