Drive time scheduling is the practice of treating travel between appointments as a scheduled, time-blocked event on the calendar rather than empty space. Instead of seeing a 30-minute gap between two jobs and assuming it is free time, a drive-time-aware calendar fills that gap with the actual drive, showing how long it takes, how far it is, and when you need to leave. It turns the invisible part of a mobile worker's day into something visible and protected.
The concept is simple. The fact that almost no mainstream calendar does it is the interesting part.
How a normal calendar sees your day
Open Google Calendar, Apple Calendar, or Outlook and schedule four service calls for a typical workday. The calendar shows four events, each with a start time and a duration. Between those events, it shows empty space. That empty space is not labeled, not measured, and not protected from being booked over.
For an office worker, this model works perfectly. The empty space between a 10 AM meeting and an 11 AM meeting really is free time. The "commute" is a walk to a conference room, which takes 30 seconds and costs nothing.
For anyone who drives between appointments, that empty space is not free. It is occupied by a drive that has a real distance, takes a real amount of time, and varies depending on traffic, construction, and the time of day. The calendar does not know any of this. It treats the gap between a job in the north suburbs and a job downtown exactly the same as the gap between two meetings in the same office building.
This is not a minor design oversight. For a contractor with four or five stops per day, the total driving time can represent 90 minutes to three hours of the workday. Having that time be invisible on the schedule is like having a budget that does not include rent. The numbers look fine on paper, but they cannot work in practice.
What drive time scheduling actually changes
A calendar with drive time scheduling treats each appointment as a location, not just a time. When you add a job with an address, the calendar knows where that job is relative to every other job on the schedule. It uses a mapping service to calculate the actual travel time between consecutive stops based on the time of day the drive will happen, and it inserts that drive into the schedule as its own event.
The result is a schedule that reflects what the day actually looks like in motion, not just on paper. Instead of seeing four jobs with empty gaps between them, you see four jobs and three drives, each with a duration, a distance, and a "leave by" time. The gaps are no longer ambiguous. They are either genuinely free (buffer time, lunch) or they are accounted for by travel.
This changes three things immediately.
Scheduling conflicts become visible before they happen. If the drive between a 1:30 PM job and a 3:00 PM job takes 50 minutes at that time of day, and the 1:30 job is estimated to last 90 minutes, the calendar can show that you would need to leave by 2:10 PM to arrive on time, which means the 1:30 job can only run 40 minutes before you need to be in the truck. That conflict is obvious in a drive-time-aware calendar. In a standard calendar, it is invisible until 3:15 PM when you are still 20 minutes away.
Departure timing becomes automatic instead of mental. Without drive time scheduling, every contractor runs a continuous background calculation throughout the day: how far is the next job, how long will the drive take, what time do I need to leave, should I start wrapping up. That mental overhead competes directly with the focus required for the technical work being done on site. A drive-time-aware calendar handles that calculation and delivers a notification at the right moment, freeing the contractor to focus on the job until the phone tells them otherwise.
Daily capacity becomes realistic instead of theoretical. A contractor who books five jobs in a day with no drive time on the schedule appears to have a full but manageable day. A contractor who sees five jobs plus four drives totaling two and a half hours has a more accurate picture of whether a sixth job is feasible or whether it will push everything behind. Drive time scheduling turns a guess into a measurement.
Why mainstream calendars have not built this
The technology to do this has existed for over a decade. Google Maps has offered traffic-aware drive time calculations via API since 2013. Apple's MapKit provides similar data. The mapping infrastructure is available, affordable, and well documented. The reason no mainstream calendar has integrated it comes down to audience.
Google Calendar, Apple Calendar, and Microsoft Outlook serve hundreds of millions of users. The vast majority of those users work in offices, attend virtual meetings, or have schedules where physical location is irrelevant. Building drive time awareness into a general-purpose calendar would add complexity for the majority of users who do not need it, in order to serve a minority who do.
That minority, however, is not small. There are roughly half a million plumbers, 400,000 HVAC technicians, and hundreds of thousands of electricians, pest control operators, handymen, cleaning service workers, locksmiths, mobile notaries, and home inspectors in the United States alone. Add delivery drivers, real estate agents, home health workers, and anyone else whose workday is built around driving between locations, and the number reaches well into the millions.
These workers have been using calendars designed for office work because nothing better existed. The workarounds are predictable: manually creating "drive" events between jobs, setting custom reminders based on estimated departure times, running separate mileage tracking apps alongside the calendar. All of these work to some degree, but they require daily setup, fall apart when the schedule changes mid-day, and add administrative overhead to a job that already has plenty of it.
For a deeper look at how these workarounds play out in practice, see Why Google Calendar Doesn't Work for Service Calls.
What about field service management software?
Platforms like Jobber, Housecall Pro, and ServiceTitan handle scheduling for field service businesses, and some of them include route optimization on higher-tier plans. But their approach to geography is oriented toward dispatching rather than daily schedule clarity.
Route optimization in an FSM platform typically means assigning the right job to the right technician based on location and availability. It is a tool for office coordinators managing a team, not for a solo contractor looking at their own day and wanting to know when they need to leave the current job to make the next one on time.
More importantly, these platforms are priced and structured for businesses with employees, office staff, and high-volume client management needs. A solo electrician paying $119/month for Jobber Connect is paying for invoicing, CRM, online booking, and QuickBooks integration. The scheduling component is part of a larger suite, and the drive time between jobs is still not represented on the calendar as a visible, time-blocked event. For a detailed pricing comparison, see How Much Does Jobber Cost in 2026.
How drive time scheduling works mechanically
The mechanics are straightforward, which is part of why it is surprising that the category has taken this long to emerge.
When a user adds a job to the calendar with a street address, the app geocodes that address (converts it to coordinates). When a second job is added, the app sends a request to a mapping API (typically Google Maps Directions API) asking for the travel time and distance between the two addresses at the estimated time of departure. The API returns a time in minutes and a distance in miles or kilometers, accounting for current traffic patterns at that time of day.
The app then creates a drive event on the calendar that occupies the exact amount of time the mapping service reported. If the API says the drive from Job A to Job B takes 28 minutes at 1:15 PM, the drive event is placed from 1:15 PM to 1:43 PM on the schedule. The job that follows is adjusted accordingly, or a conflict is flagged if the drive does not fit in the available window.
Departure notifications are calculated by subtracting the drive time (plus any configured buffer) from the next job's start time and delivering a push notification at that moment. The user does not need to calculate anything or set any custom reminders. The calendar handles it because it knows both the time of the next job and the travel time required to reach it.
Mileage tracking is a natural byproduct. Because every drive event has a known distance (provided by the same API call), the app can sum all drive distances for the day, week, month, or year and present a running mileage total. This data can be exported for tax documentation without the user ever opening a separate mileage tracking app.
Who benefits from drive time scheduling
The most obvious beneficiaries are independent tradespeople: plumbers, electricians, HVAC technicians, pest control operators, handymen, appliance repair technicians, locksmiths, and cleaning service operators. These are workers who typically run three to six stops per day across a geographic area, where the drive between stops is a significant and variable part of the workday.
But the concept extends beyond the trades. Real estate agents who drive between showings, home health aides who visit multiple patients, mobile notaries who meet clients at various locations, and property inspectors who visit multiple sites per day all share the same fundamental scheduling problem: their calendar does not know where their appointments are, and the space between those appointments is consumed by driving that no tool accounts for.
The common thread is any worker whose day is structured around visiting multiple physical locations, where the travel between those locations is unpredictable enough that memory-based estimates are unreliable, and where arriving late has a direct cost in customer satisfaction, reputation, or revenue.
Why this matters for the trades specifically
The trades have an acute version of this problem because late arrivals carry outsized consequences. A plumber who arrives 30 minutes late does not just inconvenience the customer. The customer may have taken time off work to be home, may have been told a specific arrival window by the office, and may have other contractors scheduled later in the day. A 30-minute delay can cascade into a negative review, a lost referral, and a customer who calls a different company next time.
Independent tradespeople are especially vulnerable because they do not have an office buffer. There is no dispatcher rearranging the schedule, no coordinator calling ahead to warn the customer, and no backup technician who can be redirected. The solo contractor is the scheduler, the driver, the technician, and the customer service representative. Any time lost to poor schedule planning comes directly out of their day, their income, and their reputation.
Drive time scheduling does not eliminate every late arrival. Jobs still run long, traffic still surprises, and emergencies still happen. But it removes the most preventable cause of running behind: a schedule that looked fine on screen but was physically impossible to execute because the drives between jobs were never accounted for.
CalenJob and the drive time scheduling category
CalenJob is a calendar app built around drive time scheduling as its core function. Every appointment includes a street address. Drive time between stops is pulled from Google Maps based on the time of day the drive will happen, with traffic accounted for. That drive appears on the schedule as its own visible event with a duration, a distance, and a departure notification.
Mileage is calculated automatically from the scheduled drives and can be exported as CSV for tax documentation. The app does not include invoicing, client management, dispatching, or any of the business management features found in full field service platforms. It is a calendar that understands geography, and it was built specifically for workers whose days are structured around driving between locations.
For a side-by-side look at how CalenJob compares to mainstream tools, see Jobber vs Housecall Pro vs Google Calendar: What Actually Works in the Field. For a broader survey of the tools available to contractors who drive between jobs, see Best Apps for Contractors Who Drive Between Jobs.
CalenJob is launching soon on iPhone. $14.99/month or $119.99/year, with a 14-day free trial and See the full feature breakdown.