One jobsite, thirty days. You draw the fence, print the QR poster, and run your crew and timekeeper. After you request a pilot, a payment link follows in a separate email.
VeriMuster · GPS-verified time clock
The time clock that only counts hours on site.
Crews scan one QR poster per job. The punch only counts inside the job’s GPS fence. Timekeepers see verified hours next to claimed hours, and every change stays in an audit trail.
Demo uses sample data. Try worker R-1043, PIN 1234.
-
01
Scan the job’s QR poster
One fixed code per job, posted on site. Workers sign in with company ID, employee ID and PIN, then scan to punch.
-
02
Inside the GPS fence
A clock-in only counts when the phone is inside the job’s fence. Attempts from off site are refused and logged.
-
03
Verified hours
The timesheet shows what was verified on site next to what was claimed, including overtime after 40 hours a week.
-
04
Timekeeper review
Approve, dispute or edit. Every action is kept in an audit trail, so the record can be explained later.
A walkthrough of the clock, the fence, and the timekeeper.
Wendell’s voiceover walks through the sample demo — the QR poster, the GPS fence, the parking-lot rule, and how a timekeeper reviews a flagged timesheet. It uses sample data, not a customer site. Captions are on by default.
Five site rules. No supervisor at the gate.
Every job gets a GPS fence, a parking-lot zone and one fixed QR poster. The app on the worker’s phone enforces the rules.
-
Scan the job’s poster
One fixed QR code per job, printed once and posted on site. Workers sign in with company ID, employee ID and PIN, then scan to punch. A code can be regenerated or turned off if it walks away.
-
Inside the fence or nothing
A clock-in only counts when the phone is inside the job’s GPS fence. Attempts from home, the truck or the wrong site are refused and logged, with the distance from the fence.
-
Fifteen minutes in the lot ends the shift
If a clocked-in phone sits in a parking lot for more than 15 minutes, the worker is clocked out automatically, stamped at the first lot ping, not when the timer ran out.
-
No signal never clocks anyone out
Basements, steel buildings and dead zones happen. Punches and location checks queue on the phone and upload later with their original times. A dropped signal on its own never ends a shift.
-
One phone, one person
When the same phone clocks in more than one worker, the punches are flagged as possible buddy punching for the timekeeper to review.
Verified next to claimed. Every row.
The timekeeper screen puts what was verified on site next to what was claimed, splits overtime after 40 hours a week, and flags lunch patterns and shared phones. Approve, dispute or edit, and every change is kept in an audit trail.
| Worker | Claimed | Verified | Regular | OT | Flags | Status |
|---|---|---|---|---|---|---|
| R-1041 | 40.0 | 39.8 | 39.8 | 0.0 | clean | Approved |
| R-1043 | 46.0 | 45.5 | 40.0 | 5.5 | overtime | Approved |
| R-1044 | 40.0 | 37.0 | 37.0 | 0.0 | needs review | Disputed |
| R-1047 | 40.0 | 38.0 | 38.0 | 0.0 | shared phone | Needs review |
What unverified hours can cost a year
Fill in one example week for a typical worker: the hours they say they worked each day, and the hours they were actually on site. Someone on site for 6 hours who writes down 10 leaves 4 hours unverified that day. It starts on example numbers only — 10 hours claimed and 9 on site, Monday to Friday, for a 30-person crew at $29 an hour — not measurements from any company. Every figure is an estimate from your inputs, not a guarantee, not accounting advice, and not a customer result.
a year for the crew, at 52 weeks like this one
- Unverified hours a week (per worker)
- 5
- Unverified hours a week (crew)
- 150
- Unverified hours a year (crew, 52 weeks)
- 7,800
Unverified each day = hours claimed − hours on site (never below 0)
Per worker, a week = unverified hours in the week × average rate
Crew, a week = per worker × number of workers
A year = crew, a week × 52 weeks
This is an example estimate from your inputs, not a guarantee, not accounting advice, and not a customer result. Your real figure depends on your crews, your rates and what a pilot measures on your site.
Tracks the shift. Not the person.
- Location only while clocked in. Background location starts at clock-in and stops at clock-out. Off the clock, the app doesn’t track.
- Honest time gets protected too. A worker who was on site has a verified record to point to if hours are questioned.
- No signal is not a violation. Offline punches keep their real times.
- No ads, no selling data. Records belong to the employer and are used for timekeeping. Read the privacy policy.
The fence settles the argument before it starts.
A $250 setup fee starts a 30-day pilot.
Priced for government contractors and their jobsites. Unlimited workers and subs on every billed jobsite. Nothing is charged automatically when the pilot ends.
Unlimited workers and subs. The $250 setup fee is credited toward your first bill, so that bill is $749 for one jobsite. At day 30 the pilot pauses and we email to ask how you want to move forward. Nothing is charged automatically. You can also walk away.
One jobsite. Thirty days. $250 setup.
Pick one jobsite. Draw the fence and lot zones, print the QR poster, and get your crew and timekeeper running. The pilot starts with a $250 setup fee. At day 30 it pauses, and we’ll email to ask how you want to move forward. Nothing is charged automatically.
- Set up the job. Draw the fence and lot zones, print the poster, load the crew list.
- Crew clocks in. Workers install the app, sign in and scan. No hardware to mount.
- Timekeeper reviews. Verified vs claimed, overtime, flags and exports every week.
- The pilot pauses. We’ll email to ask how you want to move forward. If you continue, it’s $999 a month per active jobsite, and the $250 is credited toward your first bill ($749). Or walk away.