This article contains no affiliate links. Vendor links in this article are plain links, so you can check each claim against the vendor’s own page.
Buddy punching is one worker clocking in for another. It usually covers lateness or an early finish, and it leaves payroll records that do not match the hours actually worked. The fix here has three parts: a written rule, one visible punch check, and a conversation with the crew before the first flagged punch. This guide is based on vendor documentation read on October 29, 2026. No price appears here, because no vendor pricing page was opened for this pack.
What is the quick take?
Buddy punching is one worker clocking in for another, usually to cover lateness or an early finish. The fix does not need an accusation to start. Put the rule in writing, switch on one check that ties the punch to the person and the place, and tell the crew what changes and why before the first flagged punch.
Geofence, photo, or PIN checks from Connecteam, Homebase, and Hubstaff each close a different gap, and none of them proves work was done inside the fence. The limit to name up front is phone sharing and GPS error: a fence stops a sofa punch, it does not stop a handed-over phone.
Best for:
- 2 to 10 person trade crews
- Owners who suspect sofa clock-ins or covered lateness
- Shops that want one visible punch check, not continuous tracking
- Not a fit for: shops that need proof of work done inside the fence, or shops that want a priced comparison
What is buddy punching, and what does it actually cost in time?
Homebase defines buddy punching as employees clocking in and out for each other, usually to cover lateness or to leave early, and frames it as a form of time theft that can inflate labour costs and make payroll records inaccurate. Hubstaff defines it as one employee clocking another into work by sharing usernames and passwords. The shared point is simple: a punch record should belong to the person who did the work.
How much time does buddy punching cost? That part is unknown in this pack. No source opened for this article states how often buddy punching happens, what share of payroll it costs, or what any reader will save by stopping it. The title figure is not a measured result, so treat the example below as arithmetic only, not as data about your shop.
Illustrative example only, with assumptions stated. Suppose one worker is clocked in 24 minutes early on each of 20 shifts in a month: 24 minutes times 20 shifts equals 480 minutes, which equals 8 hours. Those 8 hours equal one 8-hour shift only if the reader’s shift is 8 hours. If shifts are longer or shorter, the same 480 minutes is not one shift. No wage rate is attached, so no dollar figure follows, and the example is not scaled up to a whole crew. Check disputed hours against your own utilisation numbers with our technician utilization calculator.
What is the polite fix, in three parts?
Part 1 is a written rule. The rule names buddy punching, states which check is being switched on, and states how a flagged punch is handled. Homebase’s prevention list includes a clear policy on what buddy punching means and what disciplinary actions follow, plus random audits. Writing the rule down first turns the check into a shop standard, not a reaction to one worker. Rules vary by location, so confirm with a local adviser before switching tracking on.
Part 2 is one punch check tied to the person and the place: a PIN, a photo or selfie, a geofence, or a combination, chosen from the table below. One visible check is enough to start, because the crew can see what it does and what it does not do. A second check can be added later, once the first one is understood.
Part 3 is a conversation before the first flagged punch. Announce the change, state the reason as payroll accuracy and fairness to on-time workers, and give one named contact for corrections. Homebase frames stopping buddy punching as also being about trust and fairness to workers who arrive on time, not only about catching rule-breaking. That framing is a suggested approach, not proof of an outcome.
How do Connecteam, Homebase, and Hubstaff differ on the punch check?
The three tools differ on which half of the check they cover: who is punching, and where the punch happens. Connecteam and Homebase both add a who check through a PIN, a photo, or a selfie. Hubstaff’s geofence covers the where check and, on the pages opened here, does not describe a photo or PIN punch check. No tool is ranked: no price was verified and no tool was tested.
Connecteam gives every employee a unique 4-digit PIN for the Kiosk app on a shared device such as a tablet at an entrance or a supervisor’s phone. A live selfie can be required before clocking in. Selfie security is on the Expert plan and auto clock-out on the Advanced plan, per a help-page footnote.
The geofence radius runs from 500 to 2,500 feet. The vendor states employees cannot clock in or out outside the geofence; instead, a request goes to the manager’s smartphone for approval. The exact behaviour depends on the setting chosen, so no single universal blocked behaviour is claimed here. Connecteam states its kiosk does not support AI facial recognition, and the pages opened do not state that a selfie is automatically matched to a profile photo.
Homebase uses PINs and photo capture to verify the user. Every clock-in and clock-out is validated with GPS location and photos, in the vendor’s wording. The geofence radius options are 150 feet, one block, or five blocks from an address. Outside the geofence, Homebase blocks the attempt and sends the admin an alert; alerts are also sent for early or late clock-ins. The GPS clock takes a snapshot of location at clock in and out for shifts and breaks, and it does not continuously track location during the shift. Whether photo capture is required on every punch, and which plan includes these features, is not stated in this pack.
Hubstaff uses geofenced Job sites, created under Locations with a site name, address, and radius. Arrival and departure actions are configurable: start or stop the timer, send a reminder, or take no action. When the restrict-timer setting is on, users cannot start the timer outside the Job Site radius, and that setting can apply organisation-wide or per member. Geofencing is available through the Locations add-on on the Team and Enterprise plans.
| Vendor | Who check | Where check | What happens outside the fence | Limit |
|---|---|---|---|---|
| Connecteam | Unique 4-digit PIN; optional selfie (Expert plan) | Geofence, 500 to 2,500 feet; shared kiosk | Approval request to manager; behaviour depends on setting | Selfie matching not stated; no facial matching |
| Homebase | PINs and photo capture; every-punch requirement not stated | GPS snapshot at clock in/out and breaks; radius 150 feet, one block, five blocks; snapshot only | Punch blocked, admin alert sent | Plan not stated; photo matching and retention not stated |
| Hubstaff | Not stated; no photo or PIN check described | Geofenced Job sites; Locations add-on, Team and Enterprise | Restrict-timer on: timer cannot start outside radius; auto actions set: timer starts or stops at fence | Fence checks device location, not who holds it |
Source: Connecteam Kiosk app help page. No video title or duration is claimed here, because neither was confirmed in this pack.
Why is Jobber not the buddy-punching lock in this piece?
Jobber is the cautionary example, not a fourth row in the table. Its location timers help keep timesheets up to date, live location is not shared with other team members or the account owner, and GPS waypoints are logged at listed actions. The problem is one point: a team member must be assigned to a visit for the timer to start automatically, but a user can start a timer manually on a visit they are not assigned to. That manual-timer point means Jobber is not presented as a buddy-punching lock, and this article does not claim Jobber blocks clock-ins outside a fence, because the page opened does not state that.
What should you tell the crew, word for word?
Tell the crew before the first flagged punch, not after it. Keep the notice short, name the exact check you switched on, and give one contact for corrections. The full GPS notice, covering what is tracked, when tracking starts and stops, and who sees the data, lives in the full GPS notice to give the crew before tracking starts, and it is not repeated in full here.

- “We are changing how clock-ins work, starting on [date], so payroll matches the hours actually worked.”
- “The reason is fairness to on-time workers, and payroll accuracy for the whole crew.”
- “The check we are switching on is [name the exact check you chose].”
- “If a punch is flagged, the first step is a conversation and a correction, not discipline. Tell [named contact] the same day if a punch is wrong.”
- “A genuine mistake gets corrected the same day. Repeated, confirmed patterns are handled under our written policy.”
- “The full notice is at the link above. Ask [named contact] if anything in it is unclear.”
Do not promise a specific disciplinary outcome in the conversation, because no vendor page states one. Do not present the script as a legal notice: rules vary by where the business operates, so confirm with a local adviser before switching tracking on.
What does a geofence not stop?
A geofence checks where the device is, not who is holding it. Phone sharing is the clearest gap: a worker who hands a phone to a colleague passes the where check while failing the who check, which is why a photo or PIN layer matters where that risk is real. GPS error is a second gap, since a reading can be wrong at the fence edge. A third gap is time after the punch: a stamp proves device location at punch time, not effort through the day.
No geofence proves work was done. A fence narrows the problem from anywhere to one place, and the who check narrows it from any device to one person at that place. Shops that need proof of work done inside the fence will not find it in any tool in this piece.
What to do when a punch is flagged?
Start with the record, not the worker. Check the punch time, the location or photo record, and the assigned shift, and check whether a setting, a dead phone, or a GPS error explains the flag. Then talk to the worker and ask what happened before drawing a conclusion. A genuine mistake gets corrected the same day.
Reserve discipline for a repeated, confirmed pattern under the shop’s own written policy. One flagged punch is a conversation and a correction. A pattern confirmed across more than one punch, after errors have been ruled out, is handled under the written rule the crew was told about first. No specific disciplinary outcome is promised here, because no vendor page states one.
What should you read next?
If you are still choosing a tool, read the geofenced comparison that prices and compares the three tools. If you are sizing the buy by crew size, read the stage guide for what to buy first at each crew size. For the wider set of crew calculations, see the rest of the crew-maths toolkit.
Related: Payroll with 12 stops a day: how multi-site crews should clock time







