GPS Time Tracking for Landscaping Crews on Multi-Property Routes
A landscaping crew hits eight properties before lunch, and the only record of who was where and for how long is a foreman's memory. Here's a workflow that turns every stop on the route into a real labor number, using geofenced recurring properties and a one-tap switch between stops.
JULY 11, 2026 · BY THE CLOX TEAM
It's 6:45 a.m. at the shop. The trailers are loaded, three crews are pulling out in three different directions, and by the time the first one dumps grass clippings at 8:15 they will already be on their second property. A mowing crew on a full route touches eight, ten, sometimes fourteen stops before lunch.
At the end of the week you sit down to bill and to run payroll. The only record of who was where and for how long is what a foreman remembers and what got scribbled on a clipboard that has been rained on twice.
This guide is about the method, not the marketing. It walks through a way to run a route so that every stop becomes its own real block of time, tied to the property it belongs to, without anyone clocking out and back in at every driveway. That's the difference between knowing your labor cost per property and guessing at it.
If you want the short version of why Clox fits landscaping crews specifically, that page covers the fit. This one covers how the day actually runs.
01
The unit you bill by is the property, so that is the unit you have to track by
A framing crew parks at one site all week, so their labor is easy to reason about. Landscaping is the opposite. Your crew's day is a string of short visits, and the number that actually matters to your business isn't the total hours the crew worked. It's the hours each individual property took.
That's the number you bid the account on, the number you renew the contract on, and the number that tells you the corner lot with the slope has been quietly losing you money for two seasons.
The problem is that a normal time clock gives you one clock-in in the morning and one clock-out at night, and everything in between is a black box. You paid for nine hours of crew labor. You have no reliable way to split those nine hours across the eleven properties they covered. So the labor line on every estimate is a shared guess, and the account that loses you money looks exactly like the one that makes you money.
The core idea
Don't track the crew's day as one long shift. Track it as a sequence of stops, where each stop is its own timed block attached to a property. Then the labor math per account falls out of the record instead of out of memory.
02
Step one: turn every recurring property into a geofenced site, once
You already know your route. The same properties, most of them recurring weekly or biweekly, in a roughly fixed order. The setup is to enter each of those properties as a worksite once, with a radius drawn around it on the map. A residential lot gets a tight radius. A commercial campus or an HOA with a long entrance road gets a wider one. You do this at the start of the season and it holds all year.
Setting this up on your own crew takes an afternoon, not a rollout. You can start a free trial and put your next job on it today. It runs 14 days, needs no card, and is backed by a 30-day money-back guarantee.
The geofence does two jobs for a route. It confirms the crew was standing on the property when they started the stop, rather than taking their word for it, and it makes the next step a single tap instead of typing an address at every driveway.
We're not going to re-explain the mechanics of geofencing here, because there's a whole guide for that. If you want the full picture of how a GPS geofence reads a location and what a tight versus wide radius actually does, read the geofencing pillar guide. For a route, the thing to understand is what it lets the crew do next.
03
Step two: one tap to switch stops, no clock-out and back in
Here's the part that makes this workable for a crew that's moving all day. When the crew rolls up to a property and starts work, someone taps the property. When they finish and drive to the next one, they tap the next property. That's the whole interaction.
Each stop becomes its own block of time on its own property. Nobody clocks out at the end of one and clocks back in at the start of the next, because that friction is exactly what makes crews stop bothering by week two.
The reason the tap can be that simple is the geofence you drew in step one. Because the property is a known site with a boundary, the phone already knows which stop the crew is standing on.
The crew isn't scrolling a list of forty accounts looking for the right one at every driveway. They tap, they work, they drive, they tap. A foreman running the biggest crew can do it from the truck before the gate closes behind them.
Drive time is a stop too
The gaps between stops aren't free. The hour a crew spends dragging a trailer across town is real labor you're paying for. Because each on-property block is bounded by a tap in and a tap out, the drive time between them shows up in the day's total and stops hiding inside the properties on either side of it.
04
Step three: the labor-per-property number you never had
Once a week of routes is recorded as stops instead of one long shift, the report you actually care about is finally possible. Hours land against each property. You can see that the Maple Street account took the crew thirty-eight minutes on average and the Oakwood HOA took two hours and ten.
You can put a labor cost on each one because you know the crew and the rate. That's the fact your next bid should start from, instead of the season-old gut feel you have been renewing on.
What a week of routed stops turns into. Illustrative properties, not real accounts, to show the shape of the report.
This is the reason to track by stop at all. Not to police the crew, but to see which accounts are worth keeping, which ones need a price correction at renewal, and how much of the day is actually spent driving rather than working. You're the one signing the checks and quoting the contracts, so you're the one who needs that number in hand.
05
The honest part about GPS on a route
It would be easy to tell you the geofence proves your crew was on every property, and it doesn't, so we won't. The location comes from the crew's phone. That makes a geofenced clock-in a strong deterrent against a stop being logged from the truck a block away or from the shop, and it's a real improvement over a clipboard.
It's not a tamper-proof guarantee that the phone reported an honest location. Treat it as what it is: a check that raises the bar and settles most honest disputes, not a surveillance system that catches a determined cheat every time.
What the record does and does not prove
The location check confirms where the phone said it was at the moment of the tap. Clox also keeps the record itself tamper-evident after that point, so a punch can't be quietly edited later without it showing. That protects the integrity of what was captured. It doesn't turn a phone's GPS reading into absolute truth, and any tool that claims otherwise is overselling it.
The practical way to use this is per crew. A stationary install crew planting for a full day can be held to the fence hard, since they're not moving. A route crew that hits fourteen stops doesn't need a fight at every one. Enforcement is set per person, so you match the strictness to how each crew actually works instead of picking one rule for the whole company.
06
What this looks like when the signal drops
Half the properties on a route are behind a treeline, down in a valley, or out past where the bars give up. A time clock that needs a live connection to record a stop is useless exactly where landscaping crews spend their day. The workflow above only holds if the tap still works with no signal.
The tap is recorded on the phone the instant it happens, with its real timestamp, and held there until the phone finds signal again. So a crew can run a full morning through a dead zone, tapping through six stops, and every one of them lands with the right time once the truck climbs back into coverage. The stop is never lost because the record existed on the device before it ever reached us.
07
The seasonal reality most tools ignore
Landscaping headcount breathes with the calendar. You might run four crews in July and one in February, or swing the other way if you plow snow. Paying a flat per-seat fee for people who are laid off for the winter is money wasted.
The plan is a low monthly base that includes your first three people, then a flat rate per additional user, and no long-term contract, so a smaller off-season crew means a smaller bill. You're not locked into your peak-season headcount in the dead of winter.
08
Putting the route method together
- Enter each recurring property as a geofenced worksite once, with a radius sized to the lot.
- Have the crew tap the property when they start it and tap the next one when they roll, so each stop is its own timed block with drive time in between.
- Enforce the fence per crew: hard on a stationary install crew, light on a route crew that never stops moving.
- Read the weekly report by property to get a real labor cost per account, and let that number set your renewals and next season's bids.
- Trust the offline capture for the properties with no signal, and treat the GPS as a strong deterrent rather than absolute proof.
None of this asks the crew to do more than tap a screen when they arrive and when they leave. That's the bar it has to clear, because a workflow a tired crew won't follow at property number twelve isn't a workflow. Everything the office needs, the labor per account, the drive time, the confirmation the crew was on site, falls out of that one tap.
If you want to try the route method on your own crews, you can start a free 14-day trial with no card required. Set up a handful of your recurring properties, run a real week of routes through it, and look at the labor-per-property report before you decide anything. There's a 30-day money-back guarantee if it doesn't fit the way your crews actually run.