Geofence per site
A radius for every site, from a single house to a wide lot; 50 m is about 165 ft. The full walkthrough is on the geofence time tracking page.
4 groups location checks · no-signal days · the office · crew phones
A GPS time clock for field crews has one job: tell you who worked where, and for how long, with data you can defend. These are the GEOTT features that do it, grouped by the problem each one solves on a real job site.
Every feature included in one rate · switch modules on when you need them · no hardware
Four sets. Checks on where each punch happens, so hours from the wrong place don't count. A way to keep working when a site has no coverage or the crew moves between jobs. Reports the office can close the month with. And a phone side simple enough that nobody on the crew pushes back.
| What goes wrong today | Feature | Group |
|---|---|---|
| A worker punches in from the truck stop | Geofence per job site, radius in meters | Location checks |
| Someone fakes the phone's position | Anti-spoofing check on geofenced punches | Location checks |
| A basement or rural lot has no coverage | Offline clock-in with automatic sync | No-signal days |
| Three jobs in one day, one timesheet | Hours split across sites at clock-out | No-signal days |
| A clock-out left open overnight | Automatic close of forgotten sessions | No-signal days |
| Friday arguments about who did what | Weekly view, monthly report, Excel exports | The office |
| Old phones with no free storage | Web app opened from a link, no app store | Crew phones |
Each job site gets a circle on the project map, sized in meters. When a worker punches in or out, GEOTT reads the phone's position once, compares it with that circle and screens it for a faked location. The position is taken at those two moments only, never in between.
A radius for every site, from a single house to a wide lot; 50 m is about 165 ft. The full walkthrough is on the geofence time tracking page.
Apps that invent a location are a known trick. Every geofenced punch is screened for a faked GPS position before it counts toward the day.
Off, a punch from outside the circle is refused. On, it goes through with a flag the admin reviews. You pick per company which of the two fits your crews.
Each punch belongs to a project, and you can rename projects Site or Job. The map, the circle and the hours all live on that project.
The crew keeps working as usual. A punch made without coverage stays on the phone and uploads by itself later, and at clock-out each worker can divide the day between the sites they moved through. Sessions nobody closed can end automatically, so one forgotten tap doesn't become a 20-hour shift.
For crews that change site two or three times a day, the pattern is laid out for construction time tracking.
Live hours in one panel, a monthly report of every employee by day, a weekly view that sets expected hours against worked hours, a running hours balance and four Excel exports. Hours rules turn raw punches into hours, and GEOTT can show step by step how any single punch was counted.
The month as a grid of people by days, plus the week with the gap between expected and worked hours, so a short week shows up on Monday.
Monthly summary, by project, by employee, and detailed by employee. The by-project file is the one that answers "what did this job cost us in hours?"
Automatic breaks, rounding, overtime caps, night work. Each result comes with an explanation of how the punch became hours, handy when a total is questioned.
Hand a foreman the running of a project, with rights granted area by area: hours, documents, communications.
A browser and the invite link. GEOTT is a web app, so there is no app store step and no large download on phones that are already full. The interface comes in 5 languages, workers who want an icon can install it, and push reminders reach anyone who hasn't clocked in at the set time.
The small things that eat a foreman's day: breaks, a move to a second site, a clock-out left open, crews, overtime past 40 hours, holidays, closing the month and a record of who changed what. Most of them are a setting you switch on once, and none of them costs extra.
One tap starts and ends a break. A crew that moves to another job switches site without clocking out, and the geofence of the new site is checked again.
Group workers into crews to assign sites, filter reports and send reminders. A clock-out reminder catches anyone still on the clock late, and short messages and project files stay with the job.
GEOTT suggests a radius for the type of job, in feet or meters. After the first week it tells you if honest punches land just outside. An admin standing on a new job can create the site with "I'm here".
Each flag says why in plain words, such as an impossible speed between two punches. You can block suspicious positions instead of flagging them, see when a worker uses a new phone, and approve flags in bulk.
Overtime after 40 hours a week, with optional daily thresholds. Rules per crew with a start date and a preview. National holidays filled in for you. A month you close stays closed until you reopen it.
Tap any day in the weekly or monthly report to see the punches, the map and how the hours were counted. US date and time formats, a map of all your sites, and a daily email summary for the office.
Workers confirm a notice before their first punch and can open a screen showing what GEOTT records about them. Every change keeps who, when and why. Two-step sign-in for admins, and your data can be exported.
A worker without a phone, or who would rather not use their own, can have a manager enter or fix their hours. The reason is mandatory and stays in the change log next to the entry.
Continuous tracking: GEOTT reads the position at clock-in and clock-out, and nothing in between. Hardware: no badges, readers or terminals. A long language list: 5 languages, with no Portuguese for now. And add-ons sold on top: there is one rate, and every function on this page is in it.
Whether and how you may use GPS at work depends on the country and, in the US, on the state: read is GPS tracking of employees legal? before rollout. One rate covers everything on this page, $7 per active worker per month, with admins free: see GEOTT pricing. Your company's data stays separate from every other company's; who builds GEOTT is on the About page.
Feature questions
Start with three: a geofence on each site so punches from elsewhere don't count, clock-ins that survive a site with no coverage, and hours split between jobs at the end of the day. Then check the phone side: if the crew complains during the trial, the rollout tends to stop right there.
They close the usual gaps one by one. A punch sent from home is refused or flagged by the geofence, a faked location is flagged by the anti-spoofing check for you to review, a clock-out forgotten overnight can close by itself, and a recovered punch needs a manager's approval before it turns into paid hours.
For clocking in, yes. A worker in a basement or on a rural lot taps as usual; the punch waits on the phone and goes up by itself when coverage returns. The office simply sees it after the sync, with the original time.
No. Most GEOTT features are turned on per company when they're needed, like modules. A small crew can start with geofenced clock-ins and the monthly report, then add reminders, project managers or hours rules later, without changing the $7 rate.
The geofence and offline clock-in, on the site with the worst coverage you have. Set the radius, invite the crew and read the punches for a week. The setup takes about 2 minutes, and the 15-day trial needs no credit card. The step-by-step order is in how GEOTT works.