Time Tracking for Landscaping Crews: Seasonal Schedules and Geofences

Landscaping crews run a different shape of workday than almost any other field trade. A crew might hit 18 residential properties before lunch. Each property has a different scope. Each property bills differently. The crew leader’s job is to keep moving, keep the equipment running, and somehow accurately log who was where, doing what, for how long.

Paper time sheets in this environment are a fantasy. The foreman writes one consolidated sheet at the end of the day, guesses at the property breakdown, and the office reconciles whatever they can. Job costing comes out blurred. Customers occasionally get billed for time the crew did not spend at their property. Other customers get under-billed.

This is the practical guide to running landscape time tracking that actually works on a 22-property maintenance route — and surfaces the job-costing data the next bid season needs.

What makes landscaping time tracking hard

Five structural challenges:

1. Multi-property days are normal. A residential maintenance crew can hit 15–22 properties in a single workday. Each property is its own job, with its own time block.
2. Properties are close together. Two adjacent customers’ lots can be 30 feet apart. Geofence sizing has to be precise.
3. Seasonal workforce. Spring through fall is heavily staffed, often with H-2B visa labor and bilingual crews. Winter staffing collapses.
4. Weather is a daily variable. Rain delays routes. Heat advisories pause crews. Lightning halts work.
5. Equipment time matters. Some bids include equipment hours separately from labor. The time tracker has to support both.

A time tracking app built for a single-site construction crew handles none of these well. Landscaping needs specific operational patterns.

The multi-property route problem

The clean pattern for tracking time across 18 properties in a day:

1. Crew clocks in at the shop (or first property) under a “travel” cost code.
2. Arrives at Property A — geofence triggers a property-switch prompt. Foreman taps to confirm.
3. Crew works Property A — cost code: maintenance (or whatever the scope is).
4. Crew leaves Property A — geofence exit triggers a switch to travel.
5. Crew arrives at Property B — repeat.
6. Continues for 16 more properties.
7. End of day — crew clocks out at last property or at the shop.

The output is a clean breakdown: 18 properties, each with an accurate time block, separated by travel time. Job costing per property is real and the billing per customer is defensible.

The technology has to support fast geofence transitions. Klees’ geofence engine handles property arrivals and departures with low-latency switching and a one-tap foreman confirmation. We cover the broader mechanics in Geofence Time Clock for Construction Sites — the principles transfer directly to landscaping with tighter radii.

Geofence sizing for residential landscaping

Residential properties sit close together. A 75 m radius — the standard for a commercial construction site — would cover three or four houses on a typical block. Wrong tool.

For landscaping, the right radii:

Property type	Recommended radius	Notes
Standard residential lot	25 m	Centered on the property
Large residential (1+ acre)	50 m	Adjust per property
HOA common area	50 m	Distinct from individual lots
Commercial property	75 m	Standard commercial default
Cemetery / park	100 m+	Large open area

A 25 m radius is tight, which is the right answer for adjacent properties. The trade-off is more GPS drift creating out-of-fence flags. The fix is per-property tuning during the spring route setup — walk the route once with the foreman, drop pins, set radii. After that the routes are stable for the season.

Seasonal workforce and bilingual UI

Landscaping in the U.S. runs on a workforce profile that is heavily seasonal and predominantly Spanish-primary. The H-2B visa program supplies a significant share of seasonal landscaping labor across the country.

For these crews, a bilingual time tracking app is not a convenience — it is the difference between a smooth season and a chaotic one. Spanish-primary workers who have to fight an English-only app spend their first week of the season frustrated. They call the foreman with questions. The foreman calls the office. The office runs slow.

Klees ships fully in English, Spanish, and Portuguese — UI, notifications, support docs. We document the bilingual posture in How to Manage a Bilingual Cleaning Crew, and the principles apply identically to landscaping.

The weather variable

Landscaping operations lose substantial hours to weather every season. Tracking those hours correctly matters for three reasons:

1. Customer billing — most maintenance contracts allow weather-delay rescheduling, not double-billing
2. Internal job costing — weather hours are not productive hours and should not be allocated to property cost
3. Worker pay — most operations pay weather standby; the rate may differ from working rate

A weather-delay cost code at the punch level handles all three cleanly. The foreman switches the crew to it when work pauses. The audit log shows the weather event distinctly. Billing and payroll both treat it correctly.

PinShot for landscaping crews

Identity verification at clock-in matters for landscaping crews for slightly different reasons than for, say, commercial cleaning:

• High crew rotation during peak season means new workers need verification to prevent identity confusion
• H-2B crews sometimes share housing and transportation — a clock-in event that says “worker A is on site” needs to be verifiable as worker A
• Multi-property days with no supervisor at most stops require structural verification, not behavioral

The PinShot model — selfie at clock-in, anti-spoof scored, matched against reference, GPS pinned, written to audit log — fits landscaping cleanly. We cover the mechanism in What Is PinShot?.

Equipment hours vs labor hours

Many landscaping operations bid jobs with separate labor and equipment lines. The time tracking system needs to support both.

The clean pattern: the crew tracks labor hours per worker as normal, and separately tracks equipment running hours per asset. Klees supports both via the asset assignment field on the punch — the foreman selects which equipment was running with which crew member, and the report rolls up labor and equipment hours separately.

For a maintenance operation with a 20-property route, this matters: a leaf-blower bid line and a mower bid line have different reimbursement rates. The job-costing report needs to reflect that.

What the job-costing data looks like at end of season

The reason landscaping operators invest in time tracking at all is to get clean job-costing data for the next bid season. The metrics that matter:

Metric	What it tells you
Labor hours per property per visit	Real productivity baseline
Travel time as % of paid hours	Route efficiency
Weather-delay hours per season	Climate exposure
Equipment hours per property	Bid line accuracy
Maintenance hours per property type	Customer segmentation
Hours overrun rate per property	Surfaces under-bid customers

A landscaping operator with one season of clean data has a bidding advantage going into the next. Without it, every bid is a guess against the previous year’s blurred actuals.

What this looks like rolled up for a 35-crew landscaping operation

The complete time tracking stack for a mid-sized landscaping operator:

1. Mobile time tracking with PinShot at clock-in and clock-out
2. Per-property geofences (25–50 m radii, walked once at season start)
3. One-tap property switching with cost codes per scope
4. Weather-delay cost code
5. Travel cost code with auto-detect on geofence exit
6. Equipment hour tracking per asset
7. Bilingual UI (EN/ES) for the workforce mix
8. Offline support for rural commercial properties
9. Job-costing report by property, by scope, by season

Klees ships all nine on the Standard plan at $32 + $7/user and the Pro plan ($48 + $9/user) adds prevailing-wage automation for landscaping operations doing municipal contracts. The Enterprise plan at $600/mo flat for 100 seats fits large multi-location operations. The features overview and the industries hub cover the broader picture.

Onboarding a seasonal crew fast

The H-2B and seasonal hiring window in landscaping is tight. A new crew of 15 needs to be on the time tracker within the first day. The pattern that works:

• Pre-arrival — supervisor adds crew records with name, language, role
• Day 1 — crews download app, log in with bilingual onboarding screens, take their PinShot reference photo
• Day 1 afternoon — first live route with foreman supervising clock-ins
• Day 2 — operational mode

The full onboarding can run in about 90 minutes for a 15-person crew. We document the cleaning-crew analog in Training a 30-Person Cleaning Crew on a New Time App in One Shift, and the playbook transfers to landscaping with smaller property geofences.

FAQ

How small can a geofence be?

25 m is a reliable lower bound for residential properties. Smaller than that runs into GPS drift problems in cloudy or canopy-heavy conditions. For very tight adjacent properties, the alternative is one geofence covering both with the foreman tagging which property is being worked.

Does it work with seasonal staff who only work a few months?

Yes. Klees pricing is per active user, so seasonal staff cost nothing in the offseason. When the crew comes back, you reactivate their account.

Can equipment hours be tracked separately from labor?

Yes. Each punch can carry an asset assignment, and the job-costing report rolls labor hours and equipment hours separately per property.

What about rural commercial properties with no signal?

Fully supported. Punches queue locally and sync when the crew returns to a covered area. See Offline Time Tracking on Remote Sites for the full mechanics.

Does Klees support the H-2B reporting requirements?

The recordkeeping side, yes — every punch is captured with full audit detail and retained per the DOL three-year rule. The visa-specific filings remain on the employer’s HR system; Klees feeds clean hours data into payroll which then feeds reporting.

---

Run a landscaping operation and ready to scope a season-start rollout? Book a Klees demo — we will set up a sample route with property geofences during the call.