Mileage Tracking for Construction Fleets: When the Time Clock Should Own It

Mileage reimbursement is one of those line items most GCs solve with a second app because the time clock didn’t ship it. The crew leader fills out a spreadsheet at week end, the office manager reimburses on the next pay run, and nobody audits whether the miles match the geofence events that the time clock already recorded.

Two consequences. First, the IRS mileage rate of 67 cents per mile on a 25-vehicle GC adds up to real dollars — at a representative 14,000 miles per vehicle per year, that’s $234,500 in reimbursements before any audit defensibility question gets asked. Second, the audit log is split between two systems, neither of which can prove the miles match the work.

The right answer is to log mileage in the same app that owns the geofence events. Here’s how that works and why it matters for the audit posture.

What the IRS actually requires for mileage records

The IRS Publication 463 standard for adequate mileage records — the documentation that survives an audit — is more specific than most GCs realize. The record has to include:

1. The date of each business use
2. The destination and business purpose
3. The miles driven for that specific business use
4. The starting odometer or equivalent (most contemporary apps use GPS distance computation rather than odometer)

A weekly spreadsheet listing total miles is not adequate. A trip-by-trip log tied to specific business destinations is.

The connection to the time clock is direct. The time clock already knows the destinations (the job sites) and the dates (the clock-in events). If the mileage log is generated from those same events, it satisfies the IRS standard by construction.

Why a separate mileage app falls down

The pattern most GCs run today: time tracking in one app, mileage tracking in a second app. The crew leader is supposed to start the mileage app at the start of each trip and stop it at arrival. In practice:

• The driver forgets to start the app on the first trip of the day
• The app stays running through lunch, recording miles to the taqueria as business
• The app battery-drains the phone by 2 PM and gets force-quit
• The reconciliation against the time clock happens manually at week end, badly

The audit-defensibility risk is the worst part. If the IRS asks for documentation supporting the year’s reimbursement deduction and the records don’t match the time-clock job-site history, the deduction is at risk.

What changes when mileage lives in the time clock

When the same app that fires the geofence event at job-site arrival also computes the mileage from the last known geofence to the new one, several things change:

• No manual start-stop required from the driver
• Miles are computed between known business destinations, not arbitrary trip endpoints
• The audit log is single-source: the time clock’s job-site history is also the mileage log
• Personal driving outside business hours is automatically excluded because there’s no geofence event to anchor it
• Reimbursement at the IRS rate auto-computes for the payroll run

This is the operational model Klees ships. Once a vehicle is associated with a crew member, every transit between geofenced sites generates a mileage record. The week’s mileage total flows into the payroll preview as a reimbursable line item.

The real-money math for a 25-vehicle GC

Let’s run a representative example. A GC with 25 service vehicles, each driving roughly 14,000 business miles per year, reimbursed at the 2026 IRS rate.

Line item	Per vehicle	25-vehicle fleet
Annual business miles	14,000	350,000
2026 IRS reimbursement rate	$0.67	$0.67
Annual reimbursement liability	$9,380	$234,500
Estimated over-reimbursement on dirty records (5%)	$469	$11,725
Estimated under-deduction on lost records (3%)	$281	$7,035

The over-reimbursement number is what a clean mileage log saves the GC immediately. The under-deduction number is the audit-tail risk — the deduction the GC took but cannot defend in an IRS review and may have to give back.

Both numbers are sensitive to fleet size and to how dirty the existing records are. We’ve audited operators where the over-reimbursement was running closer to 12% because the existing mileage app had no constraint against weekend personal driving entering the log.

How the mileage layer actually works in Klees

The mechanics:

1. Vehicle assignment. Each company vehicle is registered to a driver in the Klees admin. A single driver can be assigned multiple vehicles for week-by-week reassignment.
2. Geofence-to-geofence computation. When the driver clocks out at site A and clocks in at site B, Klees computes the road distance between the two geofences and writes a mileage record.
3. Personal time exclusion. Trips that don’t end at a registered business geofence (the driver going home, stopping for lunch, running an errand) don’t generate mileage records.
4. Manual trip add. For trips to non-geofenced destinations (supplier pickups, home-depot runs, customer visits at a temporary address), the driver can add a manual trip with a destination address; Klees computes the distance.
5. IRS-rate compute. The mileage record carries the IRS rate at the time the trip ran. Rate changes (e.g., the annual IRS update each January) are versioned in the log.
6. Payroll integration. Weekly mileage total flows into the payroll preview as a reimbursable expense line.

This is the integration that makes mileage tracking an operational expense rather than a weekly chore.

Where this matters for prevailing wage and Davis-Bacon

For GCs doing federal and state public work under Davis-Bacon, the audit standard for time records is already high. The mileage records are usually the second thing the auditor asks for.

When the mileage log is tied to the same geofence events that drive the prevailing-wage hour computation, the audit defense is simpler: one set of records, one chain of custody, one timestamp source. Inconsistencies between the time log and the mileage log — the audit-trail risk that splits the records across two apps — disappear.

How this fits the Klees pricing

Mileage tracking is included on Pro and above. For a 25-vehicle GC where each driver is also a Klees user, the math:

Klees plan	Monthly cost	Mileage included
Standard	$32 + (25 × $7) = $207	No
Pro	$48 + (25 × $9) = $273	Yes
Enterprise	$600 flat / 100 seats	Yes + custom

The Pro upgrade from Standard is roughly $66/month. Against the over-reimbursement clean-up alone (~$11,725/year on a 25-vehicle fleet), the payback math is direct.

For the broader field-ops feature set and the crew clock and live map model, the Pro plan is also the right baseline for GCs with crews of 20-plus.

What it doesn’t replace

Worth being explicit about what mileage tracking in the time clock does not solve.

It does not replace fleet telematics — the engine-data, fuel-card, accident-reconstruction layer that fleet management platforms like Samsara provide. If you need those, you need the dedicated fleet platform. The Klees mileage layer is reimbursement-grade, not telematics-grade.

It does not replace fuel-card management. Fuel cards stay on whatever platform you already use.

It does not handle CDL-specific hours-of-service rules. Construction fleets rarely hit HOS, but if you do, you need an ELD-compliant logging system, not the Klees mileage layer.

FAQ

What is the 2026 IRS standard mileage rate?

67 cents per mile for business use. The IRS updates the rate annually, typically in mid-December for the following year. Klees pulls the current rate from the IRS publication automatically.

Can we reimburse at a different rate than the IRS rate?

Yes. Klees supports custom per-mile rates on the company profile. The mileage record stores both the IRS rate at the time of the trip and the company’s actual reimbursement rate.

What about commute miles?

The IRS does not allow commute miles (home to first job, last job to home) as business mileage. Klees excludes them automatically — the first geofence event of the day starts the business mileage chain, not the trip from home.

Does the driver need to do anything?

No. Mileage tracking runs as a background consequence of the existing clock-in / clock-out events at job sites. Drivers can add manual trips for supplier runs but don’t have to start or stop the mileage app.

What if a driver uses a personal vehicle?

Personal vehicle usage is supported with the same flow. Reimbursement runs at the IRS rate, written to the payroll preview as a reimbursable expense. The audit log distinguishes personal-vehicle from company-vehicle records.

---

Run a 25+ vehicle fleet? Book a Klees walkthrough or start your free trial and clean up the mileage log in one pay cycle.