Should I Charge a Travel Fee If the Job Site Is More Than 20 Miles Away in 2027?

A dispatch that exposes the gap

Picture a two-truck HVAC company based in a mid-size suburb. Most calls sit inside a 12-mile radius — a 20-minute drive, tops. Then a homeowner 34 miles out calls about a dead condenser. The technician quotes the standard $189 diagnostic fee, same as always, and heads out. Round-trip drive time: 90 minutes. Fuel burned: roughly 4 gallons in a service van averaging 14 mpg. By the time the tech touches the unit, he's already spent what would normally cover two nearby calls just getting there — and the invoice doesn't reflect a dollar of it.

That's the scenario that forces the travel-fee question. The company isn't losing money because the job itself was unprofitable; it's losing money because the trip to the job site was priced as if it were free. Multiply that gap across a handful of far-flung calls a month and the erosion becomes visible in the numbers — lower revenue per truck-hour, technicians logging more windshield time than billable time, and a dispatcher who has started quietly avoiding anything past the 15-mile mark because "it's never worth it." A travel fee isn't a penalty on distant customers; it's the mechanism that makes those calls worth taking at all.

The same dynamic shows up outside HVAC. A mobile detailing service, a piano tuner, a locksmith, a landscaping crew bidding a property 25 miles outside their core zone — anyone whose labor is delivered on-site rather than in a shop faces the identical math. The service itself is priced correctly; the *access* to the service site is what's underpriced once distance crosses a threshold.

How the travel-fee mechanism actually works

A travel fee is really just a second line item that isolates a cost your base rate was never built to absorb. Most base service rates are calibrated around an average trip inside your primary service area — say, a 10-15 mile radius from your shop or last job. Every mile beyond that radius adds cost in three places simultaneously: fuel, drive time (which is technician labor you're paying for but not billing), and vehicle depreciation from the extra mileage. When you set a 20-mile threshold, you're declaring: "Inside this radius, my base price already covers travel. Outside it, the customer covers the marginal cost."

Here's the flow a well-run dispatch system follows once a job site's distance is known:

Most scheduling and field-service software (Housecall Pro, ServiceTitan, Jobber) can automate this entirely: you set a geofence radius around your shop or around each technician's home base, and the system calculates driving distance — not straight-line distance — the moment an address is entered. That distinction matters. A site "18 miles away" by straight line can be 27 miles by actual road route if a river, highway interchange, or lack of direct roads forces a detour. Charging based on straight-line distance when your actual cost is driving distance is the single most common mistake companies make when they build this rule themselves instead of letting routing software calculate it.

The fee itself typically takes one of two forms. A flat travel fee charges a fixed amount (e.g., $35) for any job beyond the 20-mile line, regardless of whether it's 21 miles or 45 miles. This is simpler to communicate and easier for customers to accept, but it undercharges on very distant jobs and slightly overcharges on jobs just past the threshold. A per-mile fee charges a rate (commonly $1–$3 per mile) for every mile beyond 20, which scales fairly but requires more explanation on the invoice and can produce sticker shock on a 45-mile job ($75+ in travel alone). Many companies split the difference: a flat fee for 20-35 miles, then a per-mile rate beyond that.

Real numbers, ranges, and benchmarks

The specific numbers vary by trade and region, but the ranges have converged enough across the industry that you can benchmark against them with confidence.

Threshold distance. 20 miles is a common trigger point, but plenty of companies use 15, 25, or even 30 depending on how spread out their market is. Rural and semi-rural service businesses (well drilling, agricultural equipment repair, propane delivery) often push the free-travel radius to 25-30 miles simply because their entire customer base is spread across a wide geography — a 20-mile threshold there would trigger fees on nearly every job, which isn't a "travel fee," it's just a higher base rate in disguise. Dense urban and suburban trades (locksmiths, appliance repair, pest control) more often use 10-15 miles because most of their volume sits close in.

Flat fee amount. $25-$75 covers the bulk of the market for a single trip beyond the threshold. HVAC and plumbing companies commonly land at $50-$75 given higher fuel and larger service vehicles; smaller-footprint trades (locksmiths, small-appliance techs) often sit at $25-$40.

Per-mile rate. $1.00-$3.00 per mile beyond the threshold is typical. This roughly tracks (and often exceeds) the IRS standard business mileage rate, which has hovered in the 65-70 cents/mile range in recent years — businesses charge above that rate because the per-mile fee also needs to cover the technician's drive-time labor, not just vehicle cost.

Time-based alternative. Some companies skip mileage math entirely and instead charge for drive time past a threshold — for example, one hour of round-trip drive time free, then $1-$2 per additional minute. This works well for trades where road conditions vary wildly (mountain routes, ferry crossings, seasonal traffic) and straight mileage doesn't reflect true cost.

Multi-day or overnight jobs. For job sites far enough that a technician can't reasonably return same-day — commonly 75-100+ miles or 90+ minutes each way — travel fees often shift into a per diem structure: a flat day rate covering lodging and meals, separate from the mileage/travel charge for getting there and back. This is standard on larger commercial or industrial service contracts.

Free-radius carve-outs. Many companies also build in a "no fee" exception for repeat customers or for jobs bundled with other work already scheduled in that area that day — if a tech is already driving 25 miles for one job, a second job at the same site or nearby doesn't re-trigger the fee.

Trade-offs and alternatives

Charging a travel fee isn't the only way to solve this problem, and it isn't free of downsides. The core trade-off is customer friction versus margin protection.

Flat travel fee is the easiest to sell — customers see one number and it doesn't grow with distance, so it feels less punitive on a 22-mile job than a per-mile calculation would. The trade-off is that it leaves money on the table for genuinely far jobs (50+ miles) unless you cap the flat-fee zone and switch to per-mile beyond a second threshold.

Per-mile fee scales correctly with actual cost, which protects margin on every job regardless of distance. The trade-off is presentation: customers react worse to "$2.50/mile beyond 20 miles" than to a flat number, even when the total dollar amount is identical, because it reads as open-ended and harder to budget for. Quoting the *total* dollar figure up front, rather than just the rate, largely solves this.

Rolling the cost into a zone-wide price increase — charging everyone slightly more instead of singling out distant customers — avoids the friction of a separate line item entirely. But it means customers 3 miles away subsidize customers 35 miles away, which is a real equity problem if your near-in customer base is price-sensitive or highly competitive. It also makes your advertised base rate less competitive against shops that keep it low and charge travel separately.

Declining or referring out distant jobs avoids the whole question, and for a company that's already at capacity inside its core radius, this is often the right call — chasing a 40-mile job when you're turning away nearby work is a bad trade regardless of what you charge for travel. But for a company with slack capacity, walking away from revenue that a properly priced travel fee would have made profitable is the more expensive mistake.

The alternative worth naming explicitly: absorbing the cost and charging nothing extra. Some companies do this deliberately as a market-expansion play — eating travel cost short-term to build density in a new area, with the plan to introduce a fee once they have enough volume there to justify a standing route. That's a legitimate strategy, but it only works as a time-boxed decision, not a permanent policy; without a reassessment date, "we'll eat it for now" quietly becomes "we always eat it," and the margin never recovers.

Common pitfalls and how to avoid them

Charging the fee as a surprise at arrival, not at booking. This is the single most damaging mistake — customers who learn about a $50 travel charge after the technician is already on-site feel ambushed, and it generates disproportionate complaints and chargebacks relative to the dollar amount involved. Disclose the fee (or at minimum, that one may apply) the moment the address is captured, whether that's on the phone, in a booking form, or in the confirmation text.

Measuring straight-line distance instead of drive distance. As noted above, this systematically undercharges on routes with detours, bridges, or highway-only access, and overcharges on rare cases where a straight shot exists. Use routing-API distance (Google Maps Distance Matrix, or whatever your field-service software integrates), not a radius drawn on a map.

Setting the threshold once and never revisiting it. Fuel prices, fleet composition (a switch to larger service vans or EVs with different range/cost profiles), and market growth all change the real cost of a mile over time. A 20-mile threshold and $50 fee set three years ago may no longer reflect current fuel costs; review the number annually, not "whenever someone complains."

Applying the fee inconsistently by technician or dispatcher discretion. If some techs charge it and others waive it to be "nice," customers who compare notes will feel cheated, and you lose the fee's revenue predictability entirely. Bake the rule into the booking software or a written dispatch policy so it applies uniformly.

Treating every mile past the line as equal cost. A 21st mile on a straight highway costs less in time and fuel than a 21st mile through downtown traffic. Most companies don't need to model this precisely, but if a specific corridor or job site is disproportionately expensive to reach, it's fine to price that route differently rather than forcing one blanket rule to fit every geography.

Failing to communicate the reason, not just the number. Customers accept fees they understand and resent fees that feel arbitrary. A line that reads "Travel fee: sites beyond 20 miles include a fee covering additional drive time and fuel" generates far fewer disputes than an unexplained line item that just says "Travel — $50."

Related questions

What's a reasonable travel fee radius for a service business?

Most service businesses set the free-travel radius at 10-25 miles from their shop or nearest technician, based on how spread out their market is. Dense urban trades trend toward the low end; rural trades trend toward the high end.

Should travel fees be flat or per-mile?

Flat fees are simpler and better for jobs just past the threshold; per-mile fees scale more fairly for very distant jobs. Many companies use a flat fee up to a second distance cap, then switch to per-mile beyond it.

Do I need to disclose a travel fee before the job, or can I add it to the final invoice?

Disclose it before booking, ideally before the technician is dispatched. Adding it as a surprise on the final invoice is the top driver of customer complaints and chargebacks tied to travel fees.

How do I calculate the actual cost of a long-distance service call?

Add fuel cost for the round trip, technician drive-time labor at their hourly rate, and a per-mile depreciation estimate for the vehicle (often approximated using the IRS standard mileage rate as a baseline).

Should travel fees differ for repeat customers versus one-time calls?

Many companies waive or reduce the fee for repeat customers, especially if a technician is already scheduled nearby that day, since the marginal drive cost for an add-on stop is much lower than a dedicated trip.

FAQ

Is 20 miles a standard threshold for travel fees across industries? No single number is universal, but 20 miles is a common midpoint. Urban and dense-suburban trades often use 10-15 miles, while rural trades spread across a wider geography often use 25-30 miles to avoid triggering fees on the majority of their normal call volume.

Can I charge a travel fee and still stay competitive against companies that don't? Yes, as long as your base rate stays competitive for nearby customers and the travel fee is clearly tied to actual distance. Customers generally accept a distance-based fee more readily than a flat rate increase that penalizes everyone, including nearby customers who never trigger it.

What's the difference between a travel fee and a trip charge or dispatch fee? A dispatch or trip charge is usually a flat fee applied to every job regardless of distance, covering the cost of sending a technician at all. A travel fee is specifically tied to distance — it activates only past a defined mileage threshold. Some companies use both simultaneously.

Should the travel fee scale with vehicle size or job type? It's reasonable to charge more travel fee for jobs requiring a larger truck (more fuel burned per mile) or heavier equipment, since the marginal cost genuinely differs. Most small service businesses keep it simple with one rate, but larger fleets with mixed vehicle types often tier it.

Does a travel fee need to be itemized separately on the invoice, or can it be bundled into the price? Itemizing it separately is strongly recommended. Bundling it into an unexplained higher total invites disputes and makes it harder for the customer to understand why a distant job costs more than a nearby one for seemingly the same service.

What if a customer refuses to pay the travel fee after the job is done? This almost always traces back to inadequate disclosure before the job was booked. The fix isn't a collections process — it's moving the disclosure earlier, into the booking confirmation or the initial phone quote, so there's no ambiguity by the time the technician arrives.

Sources

• https://www.irs.gov/tax-professionals/standard-mileage-rates
• https://www.servicetitan.com/blog/travel-fees
• https://www.housecallpro.com/resources/
• https://www.jobber.com/academy/
• https://www.angi.com/articles/
• https://www.thumbtack.com/p/service-call-fees
• https://www.smallbizgenius.net/
• https://www.forbes.com/advisor/business/

Related on PULSE

• How Should I Structure Dispatch Fees for Same-Day Service Calls?
• What's a Fair Minimum Service Charge for a Trip That Turns Into No Work?
• How Do I Set Service Area Boundaries Without Losing Nearby Customers?
• Should I Charge More for Emergency or After-Hours Calls?
• How Do I Price Multi-Day Jobs That Require Overnight Stays?
• What's the Right Way to Communicate Fee Increases to Existing Customers?