Skip to content

How to prevent buddy punching and time theft

Most time theft is small and easy: a friend punches in for you, or a paper record gets a kinder time. Here is how to close the gaps without treating your staff as suspects.

Buddy punching is when one employee clocks in or out for another. It is the best known kind of time theft, but it is not the only one. A few minutes here and there look small. Across a team and a year, they add up to real money and real unfairness to the staff who arrive on time.

This guide gives you steps that work with any system, from a logbook to an app. It also covers a fair way to use location, because the goal is honest records, not surveillance.

What time theft looks like

Time theft is any gap between the hours on the record and the hours worked. The common forms are:

  • Buddy punching. A co-worker signs the logbook, taps the card or uses the shared login for someone who is not there yet.
  • Rounded or padded times. A paper DTR (daily time record) shows 8:00 when the person arrived at 8:20.
  • Punch and leave. The person clocks in at the gate, then goes back out for breakfast.
  • Long breaks. Breaks that run over and never show on the record.
  • Edits after the fact. A time that changes in the spreadsheet with no note of who changed it or why.

Most of this is not planned fraud. A jeepney runs late, a friend wants to help, and the system makes it easy. So the fix is mostly about the system, not about catching people.

Seven steps to prevent it

  1. Write a short attendance policy. Say how staff clock in, what counts as late, what to do when they forget to punch, and who approves a change. Put it in plain words and give each person a copy. See how to write an attendance policy.
  2. Make every punch personal. Each person uses their own login on their own phone, or their own card. No shared accounts, no one signing for a group.
  3. Tie the punch to the place. For staff who work at a fixed site, check that the punch came from that site. A geofence does this. It is a circle around the site on a map, with a radius that you set.
  4. Compare punches with the roster. A punch only means something next to the shift it belongs to. When you publish a schedule, late starts, early finishes and no-shows become easy to see.
  5. Review exceptions every day. A supervisor who checks yesterday's exceptions each morning catches problems while people still remember what happened. A supervisor who checks at cut-off has to guess.
  6. Make corrections visible. People forget to punch. That is normal. Let a supervisor add the missing time, but require a reason and keep the original record. A correction with a name and a reason is honest. A silent edit is not.
  7. Treat a flag as a question. A flag means "look at this", not "this person cheated". Ask first. GPS can be wrong, and phones fail.

Geofence or biometric device?

Many employers first think of a fingerprint or face scanner on the wall. It is a valid choice. A geofence on the staff's own phones is another. They check different things, so compare them on what you need.

QuestionBiometric device at the sitePhone app with a geofence
What does it confirm?That the right person is at the deviceThat the punch came from a phone inside the site area
What do you buy?A device for each site, plus setup and repairsNothing extra if staff already carry a smartphone
Field or multi-site staffHard, because the device stays in one placeEasier, because the phone goes with the person
Weak pointQueues at shift change, device downtime, power cutsA phone can be lent, and GPS can drift or be faked
Personal dataFingerprint or face dataLocation at the time of the punch

Neither one is perfect. Whichever you choose, the daily review in step 5 is what turns raw punches into a record you can trust.

The limits of GPS

Phone location is an estimate. Indoors, in a basement or between tall buildings, it can be off by a lot. Some apps can also fake a location. For these reasons, a good system does not throw away a punch that looks wrong. It keeps the punch and marks it for a person to review. Set the radius with some room for error, then watch the flags for a few weeks and adjust.

A fair location policy for staff

Staff accept location checks more readily when the rules are clear and narrow. These practices help build that trust:

  • Tell staff what you collect and why. For example: "We record your location when you clock in and out, to confirm the site. We do not track you at other times."
  • Collect location only at the punch. Do not track staff during the shift, on breaks or after work.
  • Ask for location only where it helps. An office team that badges in at reception may not need it at all.
  • Limit who sees it. A branch supervisor needs to see their own branch. They do not need every site.
  • Let staff ask questions. Name a person who answers questions about personal data.
  • Write it down. Put the policy in a privacy notice that staff can read at any time.

These are fair practices, not legal advice. For your duties under Philippine privacy law, ask a privacy adviser or your data protection officer. You can read how we handle personal data in our privacy notice.

What a manager reviews each day

A short daily list is enough for most teams:

  • Late starts and early finishes against the published shift.
  • A missing clock-in or clock-out.
  • Punches outside the site area, or with no location when the site asks for one.
  • Punches from a phone that reports a mock location.
  • Punches where the phone clock does not agree with the server clock.
  • People who punched in on a day with no shift.

For each one, the manager either accepts it, fixes it with a reason, or talks to the person. A pattern on the same person or the same pair of people is worth a private conversation. One flag usually is not.

How Workforce Pinas handles this

In Workforce Pinas, each site has a location setting: off, optional or required. Staff clock in on the Android app or in a web browser, and the iPhone app is coming soon. The app asks for location only at the punch, and only where the site asks for it. A punch outside the site area is not blocked. It is flagged for a manager to review, along with mock location, a missing location and a phone clock that does not agree with the server. See the GPS attendance app page for the detail.

Managers can review each punch before approving it. A correction has a reason, and the original punch stays in the record. Owners can also publish a privacy notice in the web app, and each staff member reads and acknowledges it. Read more on time and attendance, or ask us for a demo.

If you still keep attendance on paper or in Excel, read DTR template or time clock app next. To set the shifts that punches are checked against, see how to make a shift roster.

See how it could work for your team.

Looking for a better way to manage people and shifts? Tell us a little about your business and we can discuss a demo and early access.

Pricing is being finalised. Ask us about pilot pricing and what is available today.

We will reply by email, learn about your team and show you a demo organisation.

Prefer to explore the web app? Create an account.

Contact the Workforce Pinas team directly: [email protected]

We use these details only to answer your enquiry. See our privacy policy.