Crew Clock: Clock In 12 Workers in 4 Seconds (Here's How)

The clock-in is the first minute of every shift and the worst-engineered minute in most field operations. Workers stand around staring at phones while the foreman waits to start work. The math compounds fast — 4 minutes a day across 250 shifts is over 16 hours per worker per year.

Crew Clock is the Klees feature designed to delete that minute without sacrificing identity verification or compliance. It’s the operational pattern that I’ve recommended to every multi-crew operator I’ve worked with, and it’s the single feature most often called out by foremen during onboarding feedback.

This is the full explainer — what Crew Clock does, how it works, when it makes sense, and how to roll it out without resistance.

What is Crew Clock?

Crew Clock is foreman-led batch clock-in. Instead of every worker individually opening the app, entering a PIN, capturing a selfie, and waiting for confirmation, the foreman runs a single batch operation for the entire crew:

1. Foreman opens Klees and taps Crew Clock
2. App displays the day’s assigned crew list (pre-populated from the schedule)
3. Foreman marks each present worker
4. For each marked worker, the camera opens for a quick PinShot capture
5. App posts every time entry simultaneously — same timestamp, same job, individual selfie per worker

Total time for a 12-person crew: about 50 seconds in practice. For a 6-person crew, about 25 seconds. For a 30-person commercial cleaning team with multiple foremen running parallel Crew Clocks, the full team is in within 90 seconds.

The mechanics are described from the savings angle in how to cut crew clock-in time, and the broader feature lives on the features page.

What does each entry actually contain?

This is the question compliance and payroll people always ask. The answer: each Crew Clock entry includes everything an individually-initiated clock-in would, except the worker isn’t the one navigating the app.

Every entry has:

• Worker ID (matched from the foreman’s selection)
• PinShot selfie captured at the moment of marking
• Anti-spoof score (on Pro plan)
• GPS location of the foreman’s device (which is the crew location)
• Geofence verification against the assigned job site
• Timestamp (synchronized across the entire batch)
• Job and cost-code assignment from the schedule

If a worker’s PinShot fails anti-spoof or doesn’t capture cleanly, the system flags that individual entry for the supervisor — the rest of the batch posts normally. This is important: one failed capture doesn’t block the whole crew.

When does Crew Clock actually save time?

The savings scale with crew size. A rough table:

Crew size	Individual time	Crew Clock time	Saved per shift
3	~1 min	~15 sec	45 sec
6	~2.5 min	~30 sec	2 min
12	~5 min	~50 sec	4 min
20	~8 min	~90 sec	6.5 min
30	~12 min	~2.5 min	9.5 min

Over 250 shifts per year on a 12-person crew, that’s roughly 16 hours per worker, or 200 paid hours across the crew. At a blended $30/hr, $6,000 per crew per year. The ROI math article walks through the full calculation.

The savings come from three things:

1. Parallelization — selfies capture in parallel instead of serial
2. No app navigation per worker — the foreman drives, workers just look at the camera
3. No phone-fishing — workers don’t unlock their own phones

Where Crew Clock fits in the operations stack

Crew Clock is one piece of the Klees field-ops stack. It pairs naturally with three other features:

Feature	What it does	When it pairs with Crew Clock
PinShot	Selfie verification per entry	Always — Crew Clock entries include PinShot per worker
Live Map	Real-time crew location	Operations manager sees Crew Clock batches as they post
Geofencing	Job-site boundary check	Crew Clock confirms foreman is on site before posting batch
Multi-language UI	EN/ES/PT per worker	Worker notifications stay in their language even when foreman initiates

The features overview shows how these connect. The Alta Janitorial case study documents how Alta deployed Crew Clock across cleaning crews in 5 Western states with a bilingual workforce.

When does Crew Clock not make sense?

Honest assessment of where individual clock-in is still better:

1. Solo workers and small split crews — if everyone’s working alone or in pairs, Crew Clock overhead exceeds the savings
2. Highly distributed service techs — HVAC service or appliance repair where each tech goes to different sites doesn’t benefit from a batch operation
3. Union compliance constraints — some collective bargaining agreements require individual worker-initiated clock-in for billing verification
4. Strict prevailing-wage projects — some Davis-Bacon and PLA jobs require individual verification; Klees supports either mode per job

For everything else — standard 5-to-30-person construction crews, commercial cleaning teams, roofing, landscaping, painting, framing — Crew Clock is the default that makes sense.

How foremen actually adopt it

The adoption pattern across the operations I’ve watched:

• Day 1: Foreman runs Crew Clock under observation. Slightly slower than steady-state because they’re learning the flow.
• Day 2–3: Foreman runs it independently. Time drops to near steady-state.
• Week 1: Crew gets used to the rhythm — they look at the foreman’s phone, capture happens, work starts.
• Week 2: Individual clock-in becomes the exception. Foremen prefer Crew Clock because the morning is faster and cleaner.
• Month 1: Operations manager sees the variance in clock-in time drop dramatically. Shift starts are predictable.

The biggest predictor of fast adoption is whether the foreman runs the first 2–3 Crew Clocks themselves, not whether they watch a training video. Hands-on first; documentation second.

For larger deployments with multiple foremen across multiple sites, the Live Map for construction supervisors article covers how operations managers track Crew Clock execution across the team.

What workers actually think

I’ve sat in on enough crew breakouts to know that workers’ main concern about any new time-tracking feature is whether it makes their morning longer or more confusing. Crew Clock does the opposite — workers spend less time on the app, not more. Their part is one glance at the foreman’s camera, then they’re moving.

The other thing workers consistently like: the language preference still works. A Spanish-primary worker still gets Spanish notifications and Spanish reports even though the foreman initiated the entry from an English-language app. The bilingual cleaning crew article covers the bilingual mechanics in operational detail.

For broader context on what construction workers want from their time-tracking tool, see What Construction Workers Actually Want from a Time Tracking App.

The U.S. Bureau of Labor Statistics construction productivity data is the standard reference for benchmarking field productivity gains from operational changes like this.

How to roll out Crew Clock in one shift

1. Day before: 10-minute walkthrough with each foreman who will run Crew Clock
2. Shift morning: Foreman tells the crew, “Today I’m clocking everyone in. Look at my phone when I point it at you.”
3. First batch: Foreman runs it. First time is ~90 seconds for a 12-person crew. By the second day, ~50 seconds.
4. Same day: Operations manager reviews the Crew Clock entries in the admin for anomalies.
5. Week two: Crew Clock is the default. Individual clock-in stays available for edge cases.

That’s the entire rollout. No training program, no PDF manual, no consulting engagement.

FAQ

Does every worker still need to be in the system before Crew Clock works?

Yes. The foreman selects from the assigned crew list, which is pre-populated from the schedule. A worker who isn’t in the system needs to be added before they can be batch-clocked.

What happens if a worker’s PinShot fails during the batch?

The individual entry is flagged for supervisor review; the rest of the batch posts normally. The foreman can re-attempt the failed capture immediately or have the worker do an individual clock-in.

Can Crew Clock handle multiple cost codes for the same crew?

Yes. The foreman assigns the cost code at the batch level for workers on the same task, and can run a second batch for workers on a different task in the same crew. Most foremen handle this with one batch per task.

Does Crew Clock work offline?

Yes. The foreman runs the batch on local storage; entries sync when signal returns. PinShot captures store locally and upload on reconnect.

Is Crew Clock included in Standard or only Pro?

Crew Clock is included in Klees Standard at $32/mo + $7/user. PinShot anti-spoof scoring is included on Pro at $48/mo + $9/user. The pricing page has the full breakdown.

---

Want a 20-minute demo on your actual crew structure? Talk to Klees field-ops — we’ll walk through Crew Clock, PinShot, and Live Map on a live call with your foremen.