What Is PinShot? Selfie Verification at Clock-In, Explained

Time tracking with a PIN code and a job-site geofence catches some of the time fraud problem. It misses the rest. A worker hands their phone to a friend at the site entrance, the friend taps the PIN, the geofence sees a valid location, and the time entry posts cleanly. The crew member shows up two hours later or not at all. That’s buddy punching, and on overnight commercial cleaning and early-morning construction crews it costs operators real money — operators in our customer base report ranges from $400 to $2,800 per month in untracked-but-paid hours before they switch to identity-verified clock-in.

PinShot is the Klees answer to that problem. It’s a selfie-verification layer built directly into the clock-in flow, paired with anti-spoof scoring so it can’t be defeated by holding up a photo of another worker. This is the long-form explainer — what it is, how it works, what it catches, and what it doesn’t.

What is PinShot?

PinShot is the identity-verification step in the Klees time-tracking flow. Every clock-in (and optionally clock-out and break events) triggers a quick selfie capture using the worker’s phone camera. The image is run through a real-time anti-spoof scoring engine, attached to the time entry, and stored in the encrypted audit log.

The four things that make PinShot useful in the field:

1. Speed — sub-2-second capture. No menus, no extra screens, no friction.
2. Anti-spoof — every photo is scored against multiple spoof signals (photo-of-a-photo, screen replay, paper printout)
3. Works in real conditions — low light, gloves, hardhats, masks, partial face coverage; not a face-ID system that fails on real job sites
4. Defensible — every capture is timestamped, GPS-tagged, and tied to the worker record for audit purposes

PinShot is a standard feature on Klees Pro and Enterprise. The mechanics are documented at Why Klees and in the features overview.

How does the PinShot flow work?

From the worker’s perspective, the entire flow is a single tap and a half-second pause:

1. Worker taps Clock In on the Klees app
2. The selfie camera opens automatically
3. Worker glances at the phone — capture happens in under a second
4. App shows a green confirmation, time entry posts
5. Selfie + GPS + timestamp attach to the entry in the background

There’s no decision the worker has to make. No “smile for the camera.” No retry loop. If the lighting is bad or the camera angle is off, the app captures anyway and the anti-spoof engine evaluates the result. False rejections are rare in practice — under 1% on the data we’ve measured across construction and cleaning crews.

For Crew Clock batch operations (one foreman clocks in 8 workers at once), each crew member still gets an individual PinShot capture, but the foreman drives the flow. The full Crew Clock feature breakdown walks through the batch mechanics.

What does the anti-spoof engine actually detect?

This is the part that distinguishes PinShot from older “sign-in photo” features on competitor apps. Capturing a photo is easy. Capturing a photo that resists buddy-punching attempts is the hard part.

The anti-spoof engine scores each capture against multiple signals:

Spoof tactic	Detection signal
Photo of a printed photo	Texture patterns, moiré, paper edges
Phone screen showing another worker	Refresh-rate artifacts, screen reflection
Pre-recorded video	Frame consistency, temporal artifacts
Mask or face covering attempt	Depth and structure detection
Empty frame	Face presence check

If the score crosses the configured threshold, the clock-in is flagged. Operators can configure flagged entries to either block the clock-in entirely or post the entry with a review flag for the supervisor. Most operators start with “post-and-flag” for the first week, then move to “block” once the crew is acclimated.

The anti-spoof technical deep-dive covers the detection signals in more depth for compliance and IT readers.

What problem does PinShot actually solve?

Three operational problems, in order of dollar impact:

Buddy punching

The classic case. A worker who’s running late hands their phone to a co-worker at the site, the co-worker clocks in for them, and the payroll system has no way to know. A PIN doesn’t catch it. A geofence doesn’t catch it. A selfie with anti-spoof scoring catches it the first time it’s tried, and within two weeks of rollout the attempts stop.

Operator-reported buddy-punch incidents on the cleaning crews we track typically drop to zero within the first month of PinShot rollout. Construction crews see a similar curve, with a slightly longer tail because the older workforce tends to test the system first.

Ghost shifts on unsupervised work

Commercial cleaning runs heavily overnight. Buildings are empty. There’s no foreman walking the floor. With PIN-and-geofence alone, a worker can clock in from a parking lot, leave, and come back at end of shift to clock out. PinShot’s selfie capture at clock-in plus optional mid-shift random recapture catches the pattern — a worker who’s not on site can’t be in the selfie.

The cleaning ghost shifts article and the Alta Janitorial case study document the actual numbers Alta saw on this when they rolled out PinShot across 5 Western states.

Defensible wage-and-hour records

When a worker files a wage claim, the question that always comes up is can the employer prove the worker was on site. A timestamped, GPS-tagged, identity-verified clock-in record is the strongest answer a contractor can give. The DOL Wage and Hour Division handles thousands of these cases per year, and the contractors with verifiable records close them in days; the ones with paper logs and PIN-only entries spend weeks.

Where PinShot doesn’t help

I’ll be honest about the limits. PinShot solves identity verification at the moment of clock-in. It does not solve:

• A worker who clocks in legitimately, then leaves the site for personal errands (you need mid-shift random capture or a geofence exit alert for this)
• A worker who underperforms during a verified shift (PinShot confirms presence, not productivity)
• Customer disputes about scope of work (you need separate SLA tracking)
• Crew leaders running schemes against the entire system (you need management controls)

PinShot is the identity layer. The full Klees stack — geofencing, Live Map, Crew Clock, and bilingual reporting — is what closes the broader loop. The features page shows how they connect.

Privacy and worker trust

Two questions come up every rollout:

1. Is this legal? Yes, in all 50 states, with the standard disclosure paperwork. The capture is during work hours, on company time, for a legitimate business purpose (accurate payroll, OSHA recordkeeping, fraud prevention). The GPS time tracking and privacy article covers the disclosure requirements in detail.
2. Will the crew accept it? Yes, in our experience. Workers don’t object to a 2-second selfie; they object to apps that feel invasive or punitive. The PinShot flow is the same as unlocking a phone with Face ID — a single glance and they’re in. The captures are stored encrypted, accessed only by HR/payroll, and the worker can request their own records anytime.

Klees ships full PinShot UI in English, Spanish, and Portuguese, which matters for the rollout conversation with bilingual crews. The bilingual time tracking app article covers the language-specific rollout pattern.

How does PinShot compare to competitor offerings?

The short version:

Product	Selfie at clock-in	Anti-spoof scoring	Bilingual UI
Klees Pro	Yes	Yes	EN/ES/PT
QuickBooks Time Elite	Photo only	No	Partial
ClockShark	No	No	EN only
busybusy	No	No	EN only

The detailed comparisons live at QuickBooks Time vs Klees, ClockShark vs Klees, and ClockShark selfie verification gap.

FAQ

How long does a PinShot capture take?

Under 2 seconds end-to-end. The camera opens, captures, scores, and confirms — the worker just glances at the phone. There’s no menu to navigate and no retry loop in normal conditions.

Does PinShot work in low light?

Yes. The capture and anti-spoof engine are tuned for the dim conditions typical of overnight commercial cleaning and early-morning construction. Standard phone front-camera performance is sufficient for the scoring algorithm.

What if a worker’s phone camera is broken?

Klees supports tablet kiosks at site entrances as a fallback. The worker takes the PinShot on the shared kiosk camera with their PIN. The tablet kiosk article covers the deployment pattern.

Is the selfie data stored, and who can see it?

Yes, stored encrypted in the Klees audit log. Access is restricted to HR/payroll roles with audit logging on every view. Workers can request their own records anytime. Retention is configurable per account; default is 7 years to cover the worst-case audit window.

Does PinShot replace the worker’s PIN?

Most operators use both — PIN to identify which worker is clocking in, PinShot to verify the person matches. Together they make the time entry defensible. Some operators on Klees Pro disable PINs entirely and use PinShot as the primary identifier; the choice is per-account.

---

Curious what PinShot would catch on your specific crew? Talk to Klees field-ops — we’ll walk through a no-pressure demo and scope what a 30-day pilot looks like.