FeatureGeofencing Time Clock for Contractors

An invisible fence
around every job site.

Set a boundary around each project. Crewtrace checks every clock-in against it automatically — so policy stops living in the handbook and starts living on the phone.

Crewtrace geofencing dashboard showing multiple job sites with active boundaries and live clock-in pins

Why GPS alone isn't enough

The rule you never had.

GPS tells you where a punch happened. Geofencing tells the punch whether it's allowed in the first place. Most contractor payroll leaks come from the gap between those two.

Off-site punches nobody catches

A worker clocks in from home, from the gas station, or from the truck on the way. The hours look fine on the sheet — because the sheet has no way to know they were wrong.

Policy without enforcement

"Clock in at the site" is in the handbook. But handbooks don't block a punch. Without a boundary rule, the policy only exists on the day someone decides to argue.

One rule for every job

Your 40-acre commercial site and your 1/10-acre residential service call need very different boundaries. A single GPS radius either lets cheats through or blocks honest workers in the parking lot.

Anatomy of a geofence

Three layers between a tap and a payroll hour.

Every Crewtrace geofence is more than a line on a map. It's a layered rule the clock-in has to pass before it ever reaches your approvals queue.

Anatomy of a Crewtrace geofence: boundary, site assignment, and clock-in pin annotated on a satellite view
  1. 01

    The boundary

    Enter an address to instantly create a boundary, then pull the radius to customize the zone to match the exact job site.

  2. 02

    The site assignment

    Each crew is tied to a specific job for the day. The check runs against that site's boundary — not whatever fence happens to be closest.

  3. 03

    The clock-in pin

    GPS coordinate at the exact moment the worker tapped. Stored with the event, not guessed later.

What happens at the tap

Three possible outcomes. Zero mystery hours.

Every punch goes through the same decision. The worker knows instantly, the supervisor knows automatically, and the payroll record knows before Thursday.

State 01Verified

Inside the fence

Mobile clock-in accepted with a green verified status inside the geofence boundary

Worker taps clock in inside the boundary. Event is accepted, stamped with GPS coordinates, and flows straight into payroll.

State 02Blocked

Outside the fence

Mobile clock-in blocked with a red outside-boundary status

GPS puts the worker outside the approved zone. The punch is blocked or logged as an exception per your policy. No silent pass-through. No mystery hours.

State 03Saved on device

Offline at the site

Mobile clock-in saved on device while offline, queued to sync when service returns

No cell service at the job site? The punch saves to the device with its timestamp and location, then syncs the moment the phone gets signal again. Crews aren't stuck. Records aren't lost.

Inside Crewtrace Geofencing

Set it. Enforce it. Review it.

Set the boundary · 01

A fence per job, set up in under a minute.

Enter an address to instantly generate a boundary, then pull the radius to customize the zone to match the exact job site.

  • Address-based geofences with customizable radius
  • Pull to adjust the zone to fit any site shape
Crewtrace admin setting up a geofence boundary on a satellite map of a job site

Enforce at clock-in · 02

The rule fires before payroll ever sees the punch.

The moment a worker taps clock in, Crewtrace checks their GPS against the assigned site's boundary and schedule window. Pass, flag, or block — based on your policy, not on somebody's memory three days later.

  • Block, warn, or log-only modes per site
  • Crew-to-site assignment checked at every punch
  • Time-window rules for shift windows and overtime
Worker phone showing a geofenced clock-in with live boundary check and policy outcome

Review exceptions · 03

A queue of edge cases, not a week of finger-pointing.

Supervisors see every flagged event in one place — off-site punches, missing-GPS punches, after-hours starts — each with a map, a timestamp, and an edit trail. Approve, reject, or correct from the same screen, and the record stays intact.

  • Central exception queue by site or crew
  • One-click approve, reject, or annotate
  • Every decision preserved in the audit trail
Exception review queue showing off-site clock-in events with map previews

The rule builder

Different sites need different fences.

A residential service stop and a 40-acre commercial pour can't share one geofence shape. Crewtrace gives you the rule primitives to set a boundary every site actually deserves.

Address-based geofence with customizable zone boundaryRule 01

Address-based geofence

Enter an address to instantly generate a boundary, then pull the radius to customize the zone to match the exact job site. Perfect for residential service routes and commercial properties.

Geofence rule editor with a schedule window and overtime guardrailsRule 02

Schedule windows

Tie each geofence to its shift window. Before 6am? After 9pm? Flagged automatically.

Per-site enforcement

Tune how strict each fence is.

Start soft on a new site, tighten as crews learn the rule. Every site carries its own enforcement mode.

Hard block

Outside the fence? The clock-in never happens. Best for tight residential service routes.

Warn + record

Event goes through with a visible warning to the worker and an exception on the supervisor queue.

Log only

Don't block anything. Just record location on every punch so you have proof if a dispute shows up later.

Multi-site command

Every fence, every crew, one screen.

Geofencing stops working when it scales to 40 open jobs. Crewtrace is built for the multi-site week — a live map of every active boundary, color-coded by status, with exceptions surfaced to the top.

  • Live status per site
  • Exceptions surfaced first
  • Bulk-apply templates
  • Role-based views
Multi-site geofencing dashboard with live status badges across 12 active job sites

Open clock-in vs. Geofenced

Same workers.Very different clock-in rules.

Week one

Open GPS clock-in

Week two

Geofenced on Crewtrace

Enforced

Where clock-ins happen

Wherever the worker's standing when they tap

Where clock-ins happen

Only inside the approved site boundary

Off-site punches

Recorded and paid like any other hour

Off-site punches

Blocked, warned, or flagged per your policy

Edge cases

Noticed only if someone complains

Edge cases

Queued for supervisor review automatically

Per-site rules

One handbook rule for 40 different jobs

Per-site rules

Custom boundary, shape, and window per site

Audit trail

GPS? Maybe. Policy decision? Verbal.

Audit trail

Rule, event, and decision stored together

Dozens of off-site punches you never see

Every punch checked against the rule, not the handbook.

What changes on day one

A clock-in rule that doesn't need a reminder email.

4

Enforcement modes from log-only to hard-block

100%

Clock events checked against the assigned site's geofence

10–30 ft

Typical boundary accuracy on active job sites

1

Central queue for every exception across every site

Geofencing Time Clock FAQ

Geofencing questions, answered

Answers to common questions about geofencing time tracking, boundary accuracy, enforcement modes, and how geofencing connects to payroll.

You draw a virtual boundary around each job site on a map. When a worker tries to clock in, Crewtrace checks whether their phone's GPS falls inside that boundary. If they are outside the zone, the clock-in is blocked or flagged for supervisor review. This prevents off-site punches without requiring any extra steps from the worker.
Yes. Each active project gets its own geofence with a custom boundary shape and radius. If you are running multiple sites, workers are validated against whichever site they are assigned to that day.
Crewtrace logs the GPS confidence level with each event. If a clock-in lands in a gray zone — technically inside but near the boundary — the event is recorded with a proximity flag so supervisors can review it. You can also adjust the geofence radius to account for parking areas or staging zones.
GPS time tracking records where someone clocked in. Geofencing adds an enforcement layer: it validates whether that location is within an approved work zone before the clock-in is accepted. Think of GPS as the proof and geofencing as the rule.
Yes. Workers can clock out of one site and clock in at the next. Crewtrace validates each event against the geofence for the assigned location, so multi-site days still produce clean, site-level time records.

See how Crewtrace fits your operation.

Answer a few quick questions and we'll send back a tailored demo walkthrough and pricing guidance for U.S. businesses running multiple crews. Reduce payroll overpayment, strengthen compliance confidence, and cut weekly payroll admin time.
Personalized walkthrough
No hard-sell call
Implementation fit check
If Crewtrace is not a fit for your workflow, we tell you directly. If it is a fit, you get a rollout sequence your team can use.
Request Your Custom Demo
Takes about 60 seconds. We respond within one business day with a walkthrough tailored to your crew setup.